> architect stuff
how can someone be good at architect-ing stuff if they never code or code very little.
seems like the method GP is describing would be good to weed out such imposters.
how can someone be good at architect-ing stuff if they never code or code very little.
seems like the method GP is describing would be good to weed out such imposters.
- i do most meetings with internal stakeholders to understand needs and changes, and document them
- i do most "architecting", as i have most context on the systems my team is responsible for (also I am the oncall escalation point all the time as I am the senior person)
- i write about 10% of the code, usually what other colleagues aren't comfortable with (legacy systems mainly these days)
"Development" is not only writing code, and senior roles tend to code far less because we get wrapped up with the rest of the company so other folks can code and deliver. My team, manager and customers seem very happy about the whole thing (but hey, maybe everyone hates me!). I do want to code more, maybe with a good PM i would be able to, but I have no illusions about that.
If you can remove code from your code base without hampering the functionality, that's usually a much better time investment than writing new code.