Earlier quoted context omitted.
I generally tend to interview every year to see what's out there in the world (sometimes I find something worth switching for, other times not). I'm not even looking very hard but have had 4 interviews in the last month. Personally I think it's a bit more nuanced than senior vs junior (though it is very hard for juniors right now). What I've seen a lot of hunger for is people with a track record of getting their hand…
> I'm very much a "builder" type dev that has more fun going from 0-v1 than maintaining and expanding scalable, large systems. Maintaining and expanding is more challenging, which is why I’ve grown to prefer that. Greenfield and then leaving is too easy, you don’t learn the actually valuable lessons. As experience shows that projects won’t stay in the nice greenfield world, building them can feel like doing illusory…
Maintaining and expanding is optimizing for throughput or reducing headroom so you can pack more compute.
Developing a greenfield solution requires innovation beyond a simple scaling issue. Often times, once a project like this is done, it lives in maintenance mode for the rest of its life and my skills would be better applied elsewhere.
Don’t get it twisted, I’ve scaled 0-1 to 10M and maintaining and expanding is a different skill set than innovating and invention.