3 ms·

In my experience it means you rarely write software but you've moved into architecting software platforms and telling other people how to write software. I'm j

In my experience it means you rarely write software but you've moved into architecting software platforms and telling other people how to write software. I'm just a devops guy but my current project is like that, where our lead architect has really impressed me by drawing up the design of a very scalable system. My task is merely to implement and manage kubernetes for it and we have other devs who are using java, .net and golang to write the components. This impresses me a lot how our lead can come up with such a design and make it work from paper to practice.

EliRivers 6y ago
Just so. A lot of the problems have already been solved before anyone starts typing code. It is SO common in this industry for people to literally not know what some software is meant to do, and just start typing code anyway. There's an entire software philosophy, "agile", based around that. If it IS known in advance what the software is meant to do, the quality of software that can be created is just astounding.
pbourke 6y ago
If you rarely write software then you are not moving towards mastery in engineering it. There is no such thing as a master painter who is primarily a manager of painters. You can be a masterful manager, can deliver much more value than a single programmer, etc. But the engineering of software occurs primarily in the thinking about and directly working on it in its specifics.
- INTPenis 6y ago
  I see what you mean but it's more nuanced than that in my case. It's not like he turned 50 and suddenly stopped coding. I'm talking about a real nerd, a person who codes even on their free time. And he still writes code in other projects, he's a consultant, but in our project he's not touching any code, only advising. And he's 50+ now so he has 15 more years until retirement. Of course I've seen people here work beyond retirement because our field is so easy on the body.
- selimthegrim 6y ago
  Jeff Koons likes to think he is

EliRivers 6y ago

Just so. A lot of the problems have already been solved before anyone starts typing code. It is SO common in this industry for people to literally not know what some software is meant to do, and just start typing code anyway. There's an entire software philosophy, "agile", based around that. If it IS known in advance what the software is meant to do, the quality of software that can be created is just astounding.

pbourke 6y ago

If you rarely write software then you are not moving towards mastery in engineering it. There is no such thing as a master painter who is primarily a manager of painters. You can be a masterful manager, can deliver much more value than a single programmer, etc. But the engineering of software occurs primarily in the thinking about and directly working on it in its specifics.

INTPenis 6y ago
I see what you mean but it's more nuanced than that in my case. It's not like he turned 50 and suddenly stopped coding. I'm talking about a real nerd, a person who codes even on their free time. And he still writes code in other projects, he's a consultant, but in our project he's not touching any code, only advising. And he's 50+ now so he has 15 more years until retirement. Of course I've seen people here work beyond retirement because our field is so easy on the body.
selimthegrim 6y ago
Jeff Koons likes to think he is