I didn’t stop working when I burned out … I just became a school bus driver. Nothing like a 90% pay cut to spice up your life, but at least now I can’t be replaced by AI. sob
Hey, me too! Although I took a transition job in between as public works foreman for a small village. (Single person doing everything from water treatment to sewer cleanouts, snow clearing to cutting grass.)
I remember reading an article about how we’re already able to simulate basic tastes, like sweetness and sourness, digitally. So just you wait, we might have lickable HTML elements in the future
And Comic Sans is missing small-caps versions of the letters ᴀᴄᴅᴇᴊᴋᴍɴᴏᴘᴏᴛᴜᴠᴡᴢ (which is most of them), which would put reading your code from hard to nightmare difficulty.
Wikimedia and W3C log their chats with bots developed by themselves. I admit though that I am not expert in this topic, but I know that LiberaChat’s policies forbid logging.
IRC archivers just idle on a server and record anything that comes by. You can do that with Discord. Matter of fact, I keep regular archive backups of a server we have that’s full of news
Servers can be hosted by anyone; there is usually no account needed to join the chat; it would not randomly demand a phone number or an ID; it does not get pissed over people not using a very specific piece of bloated spyware… So nope, not against.
I’ve literally written expressions of existential horror in commit messages. No one reads past the preview, so just make sure the first couple lines are on topic
Yes, it is. Mostly because “real engineering” isn’t the high bar it’s made out to be. From that blog:
Nobody I read in these arguments, not one single person, ever worked as a “real” engineer. At best they had some classical training in the classroom, but we all know that looks nothing like reality. Nobody in this debate had anything more than stereotypes to work with. The difference between the engineering in our heads and in reality has been noticed by others before, most visibly by Glenn Vanderburg. He read books on engineering to figure out the difference. But I wanted to go further.
Software has developed in an area where the cost of failure is relatively low. We might make million dollar mistakes, but it’s not likely anybody dies from it. In areas where somebody could die from bad software, techniques like formal verification come into play. Those tend to make everything take 10 times longer, and there’s no compelling reason for the industry at large to do that.
If anything, we should lean into this as an advantage. How fast can we make the cycle of change to deployment?
We might make million dollar mistakes, but it’s not likely anybody dies from it.
I had a coworker who got a gig writing PDA software for a remote-controlled baseball machine. He was to this day the most incompetent programmer I’ve ever met personally; his biggest mistake on this project was firing a 120 mph knuckleball (a pitch with no spin so its flight path is incredibly erratic) a foot over a 12-year-old kid’s head. This was the only time in my 25-year career that I had to physically restrain someone (the client, in this case) to prevent a fist fight. I replaced my coworker on the project after this and you can bet I took testing a little bit more seriously than he did.
In many cases this is accurate. Programming alone doesn’t amount to engineering. Lotta low quality lines of code being churned out these days because standards have dropped.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.