👍Maximum Derek👍

The worst code I ever wrote ended up in the first batch of OSS sent to the Github Arctic Code vaults.

I’ve done a lot of things I’m proud of and now I have to imagine a distant future where the only thing that remains of me is the time I tried to treat nodejs like a procedural language (before promises) and mongodb like sql.

Look! I know this code is correct! OKAY!

No one is a real programmer until they’ve experienced that sensation.

It was more fun before blame, because sometimes it would take 10 minutes to figure out you’re the dumbass.

PHP variable variables

Brands starting doing this in the 486 days to match customer expectation. In the 286 and 386 days it slowed the PC down to 8MHz. It was called turbo because it was 8088 Turbo mode, as the 8088 nominally operated at 4.7MHz.

Source: Those of around since the 8088 days viciously mocked the brands that did this on newsgroups because they were catering to newbs… or whatever we called them back then.

This is why computers should still have a Turbo button that limits the CPU to 8MHz.

I honestly need to remember the debugger exists. They weren’t common for interpreted languages when I got started.

deleted by creator

How very dare you share my opinion!

I like when you give it an answer and you tell it where it made an error. So it changes it to something that’s even more wrong, then you point that out and it says, “Sorry. Here’s the first wrong thing I told you, again.”

Im my experience, if your logs are growing that fast for a reason, you’ll get to see it again… and again… and again. And show it to people going, “WTF, have you ever seen anything like this before?”

Sadly the consumer laser printer market is in decline and a couple of companies have already exited. I’m not sure how much longer they’ll be available (new).

Home printing is a declining market overall, SMB printing has plateaued, and a lot of the die-hard laser printer users are moving away; because bringing big canisters of microplastics into one’s home is less appealing than it once was.

Having worked in a lot of scrum teams in positions ranging from Jr Dev to CTO, I have become a huge proponent of scrum masters.

1. The scrum setup is that way for a reason. The Stake Holders speak for the company, the devs speak for the infrastructure, the Scrum Master speaks for the process, and the PO is also there. And none do each others speaking jobs well. The process of scrum will tend to drift back toward dev burnout without a good SM.
2. Devs shouldn’t be spending their time managing tickets, we should be developing. Backlog grooming, sprint ready ticket reviews, fighting with POs, stake holders, and Support, and fretting about velocity should be left to the scrum master.
3. I will never again act as scrum master if I can help it.

And in my experience a SM becomes a full time position at about 15 devs.

deleted by creator

That’s why scrum teams need aggressive POs and scrum masters.

I like “Cleaver is another way of saying hard to maintain” and “What jackass wrote this? Oh it was me.”

Maybe it’s because I’m only using it as plan B or C (after the documentation has already failed me), but I have never gotten any usable code out of chatGPT.

And yet co-pilot is able to finish my code perfectly after I type the first few characters… even though they’re the same model.

Those signs all got their price data from the Reddit API.

Finally a cord for my vacuum that only has an rj45. If anyone spots a 220v to mico-usb, let me know. My stove has been offline for weeks.

• Needless hoop to jump though - red flag 1
• Having not switched to GraphQL - red flag 2 /s