3 ms·

> 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

> 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.

dougk16 4y ago
They've coded for 10 or 20 years, and now just sit back and design interfaces, write specs, evaluate technologies, mentor juniors, do code review, and of course the ultimate mind blow when you're trying to figure out who to fire: they remove code instead of add it. Unfortunately for the company, these "imposters" do indeed get weeded out in preference to the recent college grad copy/pasting thousands of lines of StackOverflow answers. I usually escape before all that drama though!
- flohofwoe 4y ago
  > they remove code instead of add it 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.
  - strix_varius 4y ago
    Yes, that was OP's point.
chronid 4y ago
I am in that condition, so personal experience here: - 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.

3 ms·

> 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

by dominotw 4y ago

> 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.

dougk16 4y ago
They've coded for 10 or 20 years, and now just sit back and design interfaces, write specs, evaluate technologies, mentor juniors, do code review, and of course the ultimate mind blow when you're trying to figure out who to fire: they remove code instead of add it. Unfortunately for the company, these "imposters" do indeed get weeded out in preference to the recent college grad copy/pasting thousands of lines of StackOverflow answers. I usually escape before all that drama though!
- flohofwoe 4y ago
  > they remove code instead of add it 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.
  - strix_varius 4y ago
    Yes, that was OP's point.
chronid 4y ago
I am in that condition, so personal experience here: - 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.