4 ms·
I like this framework–it captures different levels of autonomy in different development jobs. As my career has advanced, it's definitely moved from implementer
by SatvikBeri 11y ago
I like this framework–it captures different levels of autonomy in different development jobs. As my career has advanced, it's definitely moved from implementer to problem solver, with occasional elements of problem finder. I have a lot of autonomy, but still get to spend most of my time writing code (or rather, thinking about code.)
I don't think I want to be a problem finder, at least not yet. Being given business problems and solving them feels like the point where my brain can really engage without feeling like my work is either too vague or too controlled to be important.
- RKoutnik 11y agoGlad this article helped you out - and no worries about needed to shoot to the next level. There are some great advantages to the Solver level - as you've mentioned, there's plenty of space to play & learn without worrying about incredibly vague instructions. Enjoy it all you want. I can't begrudge someone who's found someplace that makes them happy.
- mindcrime 11y agoand no worries about needed to shoot to the next level I think it's a bit off to characterize them as "levels" in the sense that a "higher" level is "better" than a lower level. My sense is that some people want near complete autonomy (I do, for example), but other people would be very uncomfortable in that kind of role (or at least, ineffective). I suspect this overlaps to some extent with some basic personality characteristics as well as goals / intrinsic motivation. Still, it's a very interesting and worthwhile article, and I believe this definitely contributes something new and useful to the overall discussion. I'll definitely use some of these ideas in the future when it comes to hiring and what-not.