原文在此：
These Aren’t the Developers You’re Looking for
在吃饼干的过程中偶然看到这篇文章，立刻被UC化的标题吸引到了。
全文读完，感觉作者还是有点刻薄的。比如，里面似乎提到，相比前端技术来说，ABAP的学习曲线过长，人工有点小贵。而现实恐怕恰恰相反。当前的前端技术本身也许不算更复杂，但是，如果考虑到它正处于快速演变的历史时期，缺少成熟的学习方案，学习过程中要付出的机会成本还是比较高的。此外，前端的人工也并不便宜，至少我还没遇到过工资比我更低的前端开发者...
但即便如此，我依然赞同该文中的绝大部分内容。我认为这篇文章抓住了问题的关键，也就是里面提到的、影响当前技术发展的重要因素：
- The growing momentum of cloud adoption
- The consumerization of IT
- Ever-increasing demands for agility
此外，作者还提到ABAP开发者的SAP UI5/Fiori学习路径：
- First, this resource would have to learn JavaScript. And, to be clear, we’re not talking about the JavaScript that was used in the early 2000s to validate forms, etc. To understand the SAPUI5 SDK, you have to understand a LOT about OO in JavaScript (which is night and day different from say ABAP Objects), asynchronous programming & promises, closures, and much more.
- Once a foundation in JavaScript is built, the developer is then ready to learn how to build web applications in UI5. This takes roughly the same amount of time it took for these developers to learn how to use Web Dynpro ABAP, if not more.
- If the developer wants to be a full-stack developer, then they’re also going to have to learn about RESTful services in general and the OData protocol in particular. For some ABAP developers who haven’t done much in the way of web development up to now (and Web Dynpro doesn’t really count much here), they may also need to spend some time understanding how HTTP works, too.
- The OData learning exercise is complemented by some in-depth study on SAP Gateway technology.
里面提到了ABAP和UI5/Fiori的巨大不同，我很高兴地看到，虽然自己并不熟悉ABAP Objects、Web Dynpro、SAP Gateway之类的东西，但至少还了解一点asynchronous programming、closures、HTTP...
总之，无论我们喜欢与否，变化确实在发生着。因此我把这篇文章介绍给大家。
