I don't want to sift through docs and man pages and debug cryptic compiler and runtime errors in my spare time.

There are far richer things for me to do with my life.

I want to use my computer to get my tasks done and be done with it. Slogging through technical details an LLM could crush in minutes is a much better use of my resources.

The whole point of this sentiment is that the personal tools wouldn't EXIST due to the time sink needed.

The tradeoff makes sense for a lot of people even if it's not a good fit for you.

The vast majority of students and employers treat them as vocational certificates in practice, and the profession would almost certainly benefit from adapting curricula to more closely match that reality.

Foundational concepts are still necessary, but I don't buy the argument that we should continue teaching like it's 1946.

I, too, think it's important to put dreams out there even if they have holes in their implementation or are easily torn apart by naysayers. We can and should collectively dream of a better future if we want something worthwhile to aim at.

Rotten people put on a good face in the interview and then spread their misery around for decades to some of our most vulnerable. It happens in pretty much every unelected position in the public sector in my experience.

Current manufacturing numbers are a small part of the story of the overall lineage.

This is the classic "perfect is the enemy of the good" type scenario.

Let's make imperfect progress if that is what we're currently capable of.

How would you do this instead, and why?

I was terrified to do so, but the only alternative I could see at the time was killing myself if I had to continue as is (lots of mental illness prior to and greatly exacerbated by my time in tech).

It is the biggest leap of faith I have ever taken, and I do not have a big appetite for financial risk.

After those forays I designed and built a trailered coffee from scratch and now I run it on a public park that overlooks the ocean.

I am more fulfilled than ever, I can pay my bills, and I get to do WAY more "real" engineering than the bureaucracy of my past life at FAANG ever allowed for.

Your battery blower sounds like it's just not very good.

I can move piles of wet leaves easily with my makita blower that uses two 18v batteries. It's a pretty old model too.

Batteries can surge power and not risk fire hazard like AC over a long extension cord. Manufacturers know this and have to intentionally limit draw way below the 15A ceiling so a 100ft 14AWG cord doesn't trip breakers or burn houses down.

It's always better to go with batteries for electric outdoor stuff for that (and other) reasons.

I say this because my experience is very different from yours: I get a very perceptible "high" once I get into the rhythm of a good workout. Think mild euphoria, mood lift, and general feeling of "rightness" in my body once it's been well wrung.

This only happens if I'm in decent shape, though. If I've fallen out of shape it's a slog.

Edit: I can't remember the podcast, but I recall some discussion of emerging clinical evidence in exercise response variability along many dimensions that may help explain the disconnect.

You could easily scoff the same way about some number of API endpoints, class methods, config options, etc, and it still wouldn't be meaningful without context.

It's ok to split or lump as the team sees fit.

Mockito shouldn't change whether or not this is possible; the code shouldn't have the prod creds (or any external resource references) hard coded in the compiled bytecode.

Spring Boot and other similar frameworks come to mind; by forcing huge amounts of indirection you lose a lot of visibility of your call stack because the convenient "glue" code is now orchestrating everything at runtime, but that code isn't yours, and it isn't easily inspected or fixed.

AIUI the Turing award is primarily CS focused.