We need a new feature. Ok add this controller, add some if statements for this business logic, make some api calls, add this to the db, write some models. Ok done, same thing over and over again.
Id certainly love to be able to do the architecting part and have someone do the work
There are plenty of people on this site who must be able to relate to that (and who are much better than I am - I was a Championship player playing for a League Two club and there are Galactico's active here).
That's long gone and now I'm turning into Eddy Howe (a football manager) not Steve Bull (who was an excellent striker who played for Wolves his entire career in the lower leagues but really should have moved to a good club because he was too good for them).
I wonder sometimes if that's the hump that top class sports stars have to go through when they retire from playing, it took me a few years to understand and accept.
It truly is. One could say it could be an addiction. Something is an addiction only if it makes your life dysfunctional, and boy I have been coding for 3 days straight (!) without eating way too many times. I am completely in the zone and I neglect myself and everything around me. Yes, I know, it is bad and unhealthy, but it still happens often. I wonder if I am alone in this, I would hope not. :D
I don't have kids, but given that I can easily work 6-8 hours straight on completing a feature, I have to curtail it to maintain a high-quality relationship. (I also weightlift, which can take up a lot of time.)
It's very difficult for me to get into the zone in three-hour spurts, and coding at night at the cost of my sleep is something I've retired. Shoot, a three-hour work session might be me trying to fix _a single bug._
Regarding "the hump," the show _Ted Lasso_ actually does a great job of describing this. A star player retires as they realize that they are no longer as spry as younger talent. Part of this show is about how they choose to deal with it.
Basically you get to a point in your life and career where you have to decide whether you want to be the absolute best engineer, or whether you want to be building the best environment for building and retaining the best engineers. I kicked the can down the line but it was eventually having three kids which made me realise that the latter was my path. That and it was becoming increasingly harder to actually do #1 when you seem to be surrounded by incompetents taking the second path who, as they often never became competent engineers but seem to have a large influence on decisions as a group.
It's not that I like writing code exactly it's that the domain of the code I can write to a professional level doesn't overlap with the code I find interesting to write. Or in the case of web frameworks, worth spending two days understanding the new dialect of whatever the latest fad framework is so that I know what I'm doing and not copy/pasting or otherwise working from example.
What might make it hard to understand is that the vast majority of people who call themselves engineers don't do so to the level I consider professional; especially in the app / web development / start-up world.
I'm confused—can you expand on this? What's "the work" that you've "grown to hate?" Is it "coding," or is it your "responsibilities?"