Hi There ..
This Post is in brief about the Wide Jump into the Current Active Career migration from the traditional software Architectures and design into the most practical and modern techniques. The point here is our career has become more “Economically” Oriented in a way to think how to “Save” while you “Achieve”. Cost now is the most Bold edge in the triangle to push the Skills into different direction.
Lets First enumerate the basic objective from this turn over:
- Build Cloud ready Artifacts by minimizing the Platform coupling.
- Utilize the Opensource libraries to handle and automate your donkey works.
- Move to the Skill not to the Title “This is very critical in today market”
Regarding Point 1 Build Cloud ready Artifacts by minimizing the Platform coupling
Old School SharePoint Developers used to Build SharePoint Farm Solutions that rely in Server Side Codding for Communication with SharePoint Objects (Libraries, Items, Web, Site , Security …etc.) and That was very Expensive actually.
Server Side Coding require Specific Operating System, FrameWork, and sometime some ThirdParty Runtime (c++, Java, ..etc.), I know some one used to Host his WCF Services on Windows AZURE APP Service and he migrated to host in a AZURE Virtual Machine because he used a component that need C++ Runtime Installed !!!
Regarding Point 2 Utilize the Opensource libraries to handle and automate your donkey works
Old school Web Developers used to Use the whats called (UI Developer) for handling the HTML, CSS tasks and the NON-UI Developers to write the code and build the Pages to either deliver to the UI Dev. to “Decorate” or Integrate with the “already decorated empty” pages. that was a nightmare. we always hate this part.
New School Web Developers use the new smart concepts to deliver the page in less time and effort and more and high maintainability, the dream was “how to push the Data Change to the UI” .. static HTMLs was always the Limit !!!
Regarding point 3 Move to the Skill not to the Title “This is very critical in today market”
Avoid The Titles that can be a skill for another title, for example, Who Said we have to Split the Development into Server Side Dev., Client Side Dev., UI Dev. …etc. I have the practice in my team to Make the UI Dev to write a Server Side code and the Coder to Create a Fancy UI. its Simple .. Just feed the missing Skill and you will Shrink the Title and create new “STRONG” Developer.
Thats in Brief to share with you my point of view and indeed this is just a point of view ..
Share your thoughts and discuss .. things already changes faster than this post is published 🙂