I did suspect as much, but if you’re going to put something in the title, perhaps don’t use limited definitions?

This is not a good article

A lot of people seem to be realizing that knowledge work is mostly pointless

From wikipedia

Examples of such professionals include ICT professionals, physicians, pharmacists, architects, engineers, mathematicians, scientists, designers, public accountants, lawyers, librarians, archivists, editors, and academics

Are they genuinely claiming all most of this work is pointless?

The article continues

What’s different about this moment is that the questions are not just economic but existential, the kind of questions that cause high-earning technical professionals to contemplate throwing it all away to start a goat farm in Washington or become a surf instructor in Costa Rica.

I’m sure I’d seen memes about software engineers wanting become woodworkers before the AI deluge.

The writing continues with needlessly crass language. I stopped reading.

what exactly is the rush?

In ginormous letters written across the sky, this

human minds … can only handle so much volume before getting overwhelmed.

One might even consider flourishing employees as opposed to not-burned-out ones.

PR departments

lol, I read this as a psuedonym for open source developers under the deluge of AI pull requests

What did you read of the article? Of course programming can be hard. Some of the brightest engineers and academics in the world have spent years on problems.

Hmmm, you might be right. It’s definitely a build system. I’m trying to think if it’s a package manager, and if it’s not, what is playing the role of the package manager.

EDIT seems to be both, which admittedly makes my point less relevant.

https://moderncppdevops.com/pkg-mngr-roundup/#build-systems-and-environment-managers

It’s been a while since I used it in earnest, so my memory is hazy enough that I can’t be specific. One of the largest pieces of work I’ve done in C++ was not writing C++, but working out how to ask bazel to build a single shared library that imports other bazel libraries. I’ve never used such a confusing and frustrating package manager. It was frequently unclear how to do things, despite the project having quite a lot of documentation.

When I read it supports multiple languages, I had two thoughts:

• Why? That feels like trying to write a single style sheet for both English and Mandarin.
• That might explain why it’s so confusing. I surmised: I has to bend over backwards to support all these different languages and their different module and packages architectures. And it doesn’t manage to hide that complexity from the user.

If you’ve ever tried using bazel, you might understand why writing a single package manager for multiple languages is a bad idea (at least, that’s why I assume bazel is so god-awful)

Thanks but not considering hardware adjustments. I’ll look at the bios board efficiency, turning it off, and the wall meter thing

desktop … lots of browsing, lots of coding/compiling, some gaming

Here’s the list

• AMD 9950X
• Deepcool AK620
• MSI B850M GAMING PLUS
• TEAMGROUP 2x32GB DDR5-6000 CL38 Memory
• KIOXIA EXCERIA PLUS G4 2TB PCIe 5.0 SSD
• AMD 9060XT 16GB GPU
• Jonsbo D32 PRO MESH MicroATX Case
• Corsair SF850 PSU
• 3x ARCTIC P12 120mm Fan
• 1x ARCTIC P14 140mm Fan

part list here https://programming.dev/post/52768664/24715637

I suppose I mean “which is most efficient out of the box?”

the best git command

I feel we disagree on a number of fundamental things. We’re not going to get anywhere on a site like this

You mention lots of options. Given people are varied, and you want that in a company, how about letting the candidate decide how to prove themselves? It’s pretty established that it’s not “fair” to stick to a single style, so why hang on to that?

I meant judging people for feeling anxious, as opposed to judging aptitude.

for those who this affects, this lands badly

deleted by creator

Stress is not something you can reason about in the way you imply. It’s an emotional response, and people vary wildly in how they will react. It’s great to hear you don’t get stressed, but judging people who do is, well, concerning.

Live coding in interviews is a completely different experience to pair programming, night and day. I don’t ever recall being asked to code in front of a group.