[HN Gopher] Implementers, Solvers, and Finders ___________________________________________________________________ Implementers, Solvers, and Finders Author : kiyanwang Score : 63 points Date : 2023-04-17 06:16 UTC (16 hours ago) (HTM) web link (rkoutnik.com) (TXT) w3m dump (rkoutnik.com) | dgreensp wrote: | A lot of start-ups in my experience see all their engineers as | "high-autonomy feature implementors." It's not really autonomy in | the sense of power or choice, though, just being left alone to | implement features. The thing is, "features" are product-level | things that require technical design as well as implementation. | Product design and implementation and technical design and | implementation are all different things. Even within programming, | implementation has sub-problems that require creativity. I | implemented a Java VM, once, for example, and it was really fun. | So it's not necessarily the case that once something is a matter | of "implementation" it is just straightforward work to give to a | junior programmer, or that implementing things is boring. | | What sucks is, for example, being good at technical design but | that not being valued. And management being disconnected from | employees, which is not unique to software companies. | yawnxyz wrote: | I love how well this framework maps to academia -- PhDs are | implementors, Post-docs are Problem-solvers, and Professors are | Problem-finders. | montecarl wrote: | This post made me realize why I am hesitant to leave my role in a | struggling start up. I get paid to discover what our problems are | and solve them as fast as possible which leads me to constantly | learning new skills and fully owning our product and R&D output. | I like that more than the lack of job security and must be why | I've been so resistant to searching for a new more secure | position. ___________________________________________________________________ (page generated 2023-04-17 23:00 UTC)