You want real connection to code? You earn that. You dig in. You wrestle with segfaults at 3 in the morning. You pace your apartment muttering about pointer arithmetic. You burn through Handmade Hero until you get it.
Absolutely the best learning happens at 3AM. This guy is selling being overworked to the breaking point as some kind of rite of passage. That’s not working. Or learning. It’s the road to sucking off a 9mm 4 weeks later.
Well, I’ve done that… partially. However, since I’m not a top-1‰ superstar rock-dev, my solutions took several attempts, still make a lot of assumptions, and are generally kinda bad.
Until I’ve reached an actually good boilerplate automator, Copilot has its place.
The constant nagging by you systemd people worked. I’ve written a unit that does what I need it to do. That was more annoying than I think it needed to be, but well… my solution didn’t work at all.
Chocolate production is infested with slave labor, child labor and child slave labor.
As if anyone cared if they had to wait a total of 3 seconds in a workday. If it’s a second per user action, we’re talking, but this is some bare-metal CPU wrangler’s take on how ‘efficient’ code should behave; completely disregarding that most users who touch a computer need 5 seconds to type ‘hi’ into MS Teams.
It’s interesting that everybody else preaches ‘Write for the human first, for the machine second’.