這不是我想要的ABAP開發者

 

原文在此：

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...

 

總之，不管咱們喜歡與否，變化確實在發生着。所以我把這篇文章介紹給你們。