JOURNEY FROM DEVOPS TO ENTERPRISE CLOUD INFRASTRUCTURE
Amazing Journey
Chapter 1: The developer
If you are a developer you must be learning to use framework, patterns, code optimization, refactoring , TDD, pair programming and other eXtreme programming Technics, you're purpose in life is to deploy a bug free, unit tested, continuous integration green light integrated code. Considering in your design the size of the screen, the device, the workstation, the language displayed to the user if you are a front end development or the exception error handling if you are a back-end developer. if you are a full stack developer well, you know it all don't you :)
Chapter 2: The build master
Once you had your share of integrating pieces of code and learned enough design patterns, you than start to become curious about where does your code go? how its branched? how is merged? how its packaged to be delivered as a final product. You will learn release management, gated checking, and started code reviewing other developers code, helping debugging code and fixing the broken build. Code coverage becomes familiar to see how team is doing with unit tests
Chapter 3: DevLead
The time has come to peer review, to drive developers teams, to set the pattern and provide team progress, using burn down charts if you are agile or scrum team. You will learn like i did that other developers are not you, they don't do things the way you want and you learn your first lesson of leadership "humility" and "empathy"
Chapter 4: Application Architect
Time to shine, time to think of the right choice of components, right integrations, right skills and right design to meet business requirements. you might miss the workstation CPU power, the deployment, the OS version and other outside factors of your solution
Chapter 5: Solution Architect
Now, you no longer are the "master of your domain", you probably were the king of the Microsoft or java country, but now, it's time to get clever and ask how questions to "vendors". You are responsible of making your solution work with finished products, this is no longer "green field", welcome to integration world. HTTP vs TCP vs FTP vs SMTP vs other communication protocols. Time to attend a training session at vendors to understand how SAP works, how IBM MQ works, how Azure works etc
Chapter 6: Enterprise Architect
You are getting old, hehehe. You have now the opportunity to be the "neo" and see things coming to you miles a way from technology perspective, but you soon learn there is more to IT architecture than technology it's called "business architecture" the famous "unicorn", how to turn your thinking towards process description, business objectives and put aside your acronyms and dearly beloved abbreviations. You will also learn the balance score card, the strategic value chain, the process mapping and heat map.
Chapter 7: C Level Exec or Enterprise Architecture its your choice
This chapter belongs to you