- to name a few popular ones. Coursera
Digital Marketing, CMS, Ecommerce and Omnichannel
being introduced for Adobe AEM on the server side, which later paved its way into the IEA - Integrated Experience Architecture
. With almost one year down the line one extremely positive outlook common with people who have worked on this concept on different projects was the "separation of concerns
" and the inherent advantages of it.
However such a model of development could be a cause of concern at times when there is no mediator who would understand the "backend" and the "frontend" frameworks patterns well, and allow the two teams to gel together. Even without such a person, projects would still move on, but what is produced at the end may not be elegant or easy to understand.
advances on making the language better
. The TypeScript
" and object oriented, while libraries like Underscore
make it a functional language. This further enables you to take the best of the different programming paradigms and write better programs. Add to that, the programs you write can run on Server or on the client. Isn't that interesting?
I would recommend that more and more people on the "backend
" come forward and learn the front-end
and architects and create better applications. For when you plan to give training to the developers, do also consider that the training can also include the interested backed developer. A "frontend
" aware backend
architect and developer can make such a difference that you will end up more time productively creating application than arguing that "it works for me
", or "please do whatever to make this work on your end
". And remember the Atwoods Law
" as a corollary to "The Rule of Least Power