4 ms·

Totally agree, that's exactly how it works for me. I join a company, work hard the first year to get a promotion and do the fun stuff, after that, I relax and

Totally agree, that's exactly how it works for me. I join a company, work hard the first year to get a promotion and do the fun stuff, after that, I relax and stick around to vest most of the stocks and leave around the 2nd/3rd year. I have seen so called "architects" at big co that had been there for decades bringing absolutely no value to the table. And always asked myself why would the the company retain, promote and pay these guys big bucks. Nonsense. I call them : the legacy guys. The only thing I can think of is that the "legacy guys" retain the memory of all the legacy stuff, and the ability for them to maintain that piece of legacy/core/monolith piece of software that no one dares to touch. I guess that's valuable for the company, but not certainly for the employee. They stagnate exactly because by working on that legacy stuff they can rarely learn new tech, thus they wont be able to find a job at that level anywhere outside their current company. They are stuck.

burntoutfire 5y ago
There are jobs for architects out there.
N_A_T_E 5y ago
My title is Architect. It can be easy to stagnate. Recently I've had success working on brand new projects. Setting up the skeletons of code bases, CI/CD, database/persistence layers and internal/external dependencies before teams get onboarded. You might think of that like a glorified lead engineer. I stick around for 6-12 months to help the team get up to speed then move onto the next project. The architect part might come into play in finding engineering economies of scale. At this point I know how many of our internal applications work so I find ways to reuse existing code and services when we start new projects.
otikik 5y ago
Do you have kids?
- WYepQ4dNnG 5y ago
  I do. I know it is impossible to getting prep for interviews when having kids. What I do is to leave my current job, give myself a month to prep, interview get a new job. So far it has worked fine with me.

burntoutfire 5y ago

There are jobs for architects out there.

N_A_T_E 5y ago

My title is Architect. It can be easy to stagnate. Recently I've had success working on brand new projects. Setting up the skeletons of code bases, CI/CD, database/persistence layers and internal/external dependencies before teams get onboarded. You might think of that like a glorified lead engineer. I stick around for 6-12 months to help the team get up to speed then move onto the next project. The architect part might come into play in finding engineering economies of scale. At this point I know how many of our internal applications work so I find ways to reuse existing code and services when we start new projects.

otikik 5y ago

Do you have kids?

WYepQ4dNnG 5y ago
I do. I know it is impossible to getting prep for interviews when having kids. What I do is to leave my current job, give myself a month to prep, interview get a new job. So far it has worked fine with me.