OWNING your sandbox.
As software engineers we all like to work on latest technology and coding new applications.
People generally don’t like spending a lot of time maintaining the code.
However, in the world of microservices the owners of each microservice are very well known and defined unlike in the world of monolithic applications. That means that you own it in the true sense.
You own the code.
You own the QA environment.
You own the Stage environment.
You own the production environment and all the errors that come along with it :)
On positive note, you have a lot to be proud of and you can turn it into opportunities :)
You own something that is contributing your company’s customers and what you do responsibly affects the lives of many people in a positive way.
Almir Mustafic
Brand New programming language and one solution OR Two existing programming languages, one solution for EACH? I understand that there is no right or wrong. It all depends on your software architecture, team structure, team skills and other factors, but I still want to explain the scenario as it may look familiar to some. Let me explain. Let’s assume that you have microservices and common libraries in two major programming languages. You have some teams who are experts in one and some teams experts in the other programming language. Now you need to come up with a solution for a scenario that all teams will need to leverage. Let’s assume that your cloud platform has an off-the-shelf approach for this but it is supported by a 3rd programming language that your teams do not have much experience in. What is the right thing for your organization and not just from the technical point of view? A) Do you embrace what your cloud platform gives you off the shelf and implement thi...
Comments
Post a Comment