It’s a balance. I more-or-less learned the first time that I needed to be getting more out of it than the “release success”; nowadays I’d codify a specific part of that as “always carve out the time to improve your skills as part of the project.”
I’m teaching the computer how to do something, at the same time I’m teaching myself how to do it.
That said, when that’s not possible - At least one project had at least a few weeks (it’s been awhile) of stupid wrestling with undocumented Xcode CLI internals. That was nearly completely wasted time. It sucked then, and it (dilutedly) sucks now.
It’s a balance. I more-or-less learned the first time that I needed to be getting more out of it than the “release success”; nowadays I’d codify a specific part of that as “always carve out the time to improve your skills as part of the project.”
I’m teaching the computer how to do something, at the same time I’m teaching myself how to do it.
That said, when that’s not possible - At least one project had at least a few weeks (it’s been awhile) of stupid wrestling with undocumented Xcode CLI internals. That was nearly completely wasted time. It sucked then, and it (dilutedly) sucks now.