Martin is an enthusiastic software engineer building and operating microservices in the JVM stack using Kotlin. Currently working for Albert Heijn in the role of DevOps engineer.
I do see a difference between an Architect, Engineer and Developer in my organization. It is certainly not a label to describe knowledge level of the people. I do see it as the point of view they have on the software they are building or helping to build.
Our architects are flying over the whole technical landscape, they monitor the things we do and build. We discuss all our decisions with them. They are the one with the 'biggest' picture.
Our engineers are designing, thinking on how a problem can be solved. They focus on their domain but take a look around them to see how other teams are doing things. How can fit a solution the best way in our infrastructure?
Our developers are focused on the thing they are programming. They do not have that much interest of the bigger picture but do have interest in building the software they must build in the most effective way possible.
Yes, the labels are just bullsh*t. Why? Because they make you feel less than someone else. But we need all of them, we need every person in the organization. Together, we build great things for our customers. Sometimes I am feeling like an engineer. Sometimes I feel like an architect. And sometimes I feel like a developer.
At the end we all want to make good software, and it depends on our perspective on what we do. We can do our things on all level. But it depends on the interests of the person themself.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I do see a difference between an Architect, Engineer and Developer in my organization. It is certainly not a label to describe knowledge level of the people. I do see it as the point of view they have on the software they are building or helping to build.
Our architects are flying over the whole technical landscape, they monitor the things we do and build. We discuss all our decisions with them. They are the one with the 'biggest' picture.
Our engineers are designing, thinking on how a problem can be solved. They focus on their domain but take a look around them to see how other teams are doing things. How can fit a solution the best way in our infrastructure?
Our developers are focused on the thing they are programming. They do not have that much interest of the bigger picture but do have interest in building the software they must build in the most effective way possible.
Yes, the labels are just bullsh*t. Why? Because they make you feel less than someone else. But we need all of them, we need every person in the organization. Together, we build great things for our customers. Sometimes I am feeling like an engineer. Sometimes I feel like an architect. And sometimes I feel like a developer.
At the end we all want to make good software, and it depends on our perspective on what we do. We can do our things on all level. But it depends on the interests of the person themself.