mystickphoenix

Tone feels a bit harsh but I'll try to take it in the best light possible.

It's not that I never liked coding to begin with. I enjoy it, but at the same time I also enjoy solving problems. Coding is and was a means to an end: solving a problem. The argument/statement can also be extended to say "Why did you go into coding if you didn't enjoy binary?" (substitute "binary" with any appropriate level of complexity: OOP, C, Java, Python, Waterfall, Agile, etc).

Not only that but so much of my work is and always was not coding. Meetings, stakeholders, PMs, roadmaps, estimates, etc.

My volunteer work is also solving problems, they just happen to be very human-focused in the real world.

Also, "coding" (solving problems with tech) is a fairly low-risk way to make a living that I happened to be good at. I also spent time on a drilling rig. Could have probably made significantly more doing that than I was at the start of my tech career, however, it wasn't worth the risk. We all gotta eat and in our capitalist society, can't reasonably do that without having a job.

TBH I've struggled with enjoying work for years now. Prompting AI has actually recovered some of the enjoyment. I enjoy solving problems, not necessarily writing code, though that's fun too. Maybe reframing your enjoyment can help?

Mostly I just work to live. If I didn't have to worry about that sort of thing, I'd pour my hours into volunteer work. Search and Rescue is the volunteer "work" I enjoy most at the time being. I'm limited in my ability to do it as much as I'd like because it doesn't pay.

The funny (not-so-funny?) thing is that reading this if I didn't know better, I'd figure we worked at the same company and I'm sure that most people reading this have a similar story. That's the sad state of the tech industry right now. The reins are controlled by a few at the top that seem to be exceptionally vulnerable to believing whatever AI slop is presented to them, whether it comes from AI or from their underlings.

It'll sure be interesting to see where this goes in the next year or so. The companies that have flamed out due to C* AI Psychosis. I'm sure the next set of "startup leadership" books will be around "how to avoid AI psychosis" and/or "how to use AI psychosis for fun and profit!"

For this use-case, maybe compression and then encoding would get more data into the URL before you hit a limit (or before users complain)?

I.e. .md -> gzip -> base64

for me it's Liquid DnB, anything by Liquicity is amazing, especially their year mixes and the couple that Maduk did on youtube during the pandemic

Likely my own personal bias, but I have never once found git log/commit messages to be useful when debugging or understanding what happened. I'm sure that others do so I try to write useful commits (conventional commits syntax is helpful here) but I'd much rather spend my time and effort understanding the current state of the codebase instead of trying to diagnose how "fixed bug related to file naming" relates to a website going down.

> you should probably take a step back and redefine what a PR is for your organization

I agree with this wholeheartedly if you are in a role that allows you to redefine what a PR is. In almost every organization that I've worked for, the PR is defined several levels above my pay grade and suggesting changes/updates/etc is usually seen as complaining.

May not be the most shiny/flashy thing, but I'm trying to figure out how to get out of burnout (adhd/autism/tech - all the varieties) without having to quit the world for six months.

Also, don't be afraid to revisit your favorite fiction and/or try young-adult fiction. IMO what you read matters less than building a habit or routine of reading.

I purchased the collection after reading this review. It was always a series that I wanted to read when I was younger but never did. Trying to get back into reading fiction again and this felt like a great place to start!