alt Hacker NewsMissing the point. Which is, some people like the details, code as craft; others like the high level, product/business impact, systems, etc, code as a means to an end.
The profession used to have a need for both, now the “coding machine” and artisanal code crafter are trending obsolete in most companies.
I think I reacted exactly to this. What is "code as craft", or as often read, "code is poetry"? It is variable naming, structure, hierarchy, import logic, all patterns that can be strictly controlled still. Opinions vary if this still carries enough value - I like these details, exactly because I value the "craft" and the expectancy of human oversight these presume, but I could argue about it to some manager less and less (compared to what frontier models generate already).
So when all this can still be kept, "hand craft", the muscle memory of typing code, or, as OP said,"dev who liked more the micro parts", what is this other than some nice myth the industry wove for itself?