Coding since 11yo, that makes it over 30 years now ~~~
Have a PhD in Comp Sci ~~~
Love to go on bike tours ~~~
I try to stay as generalist as I can in this crazy wide place coding is at now.
Also: a good developer has internalized that it's not about code.
The root cause of that task on the kanban board is to solve someone's problem, or allow a person to do more than before; even though that one task may seem to be all about coding, the deeper motivation for the task has nothing to do with code. If there was an easy way to achieve the same core thing without code we'd likely do that instead.
When on the clock, we're coding as a way to get to that end, not to play with our toolchains.
It's a kind of eyes-on-the-prize mentality that's an essential part of being a good dev imo.
Also: a good developer has internalized that it's not about code.
The root cause of that task on the kanban board is to solve someone's problem, or allow a person to do more than before; even though that one task may seem to be all about coding, the deeper motivation for the task has nothing to do with code. If there was an easy way to achieve the same core thing without code we'd likely do that instead.
When on the clock, we're coding as a way to get to that end, not to play with our toolchains.
It's a kind of eyes-on-the-prize mentality that's an essential part of being a good dev imo.
</10c>
Like that point very much!