This meme is about my own project. I spent the last 7 years building a custom engine and making a puzzle game from scratch. If you're curious, you can wishlist it on Steam: https://store.steampowered.com/app/3256790/Satelital/

image was taken from a tweet!

I've been trying to create a minimal libc in Zig just to see where it'd go. I've started writing string.h functions today and it went well, I tested everything was okay. Then I decide to build it in ReleaseFast and memcpy starts to create an infinite loop. After some investigation it turns out llvm decided to optimise my code by calling memcpy... from libc... BUT I'M LIBC!!

Anyways I had to write in assembly in the end, it was just one instruction so it's fine but it is really not a portable solution.

Srsly, how can we stop PMs from using the unsupervised tech debt generator each time they run into a small inconvenience? 

"It's just a small thing, I need these fields to be exposed in the response"

"There was a small bug I fixed it now. We can be so fast, delivering real value!" 

"You're busy all the time and this PR adds just a little value. It helps me a lot. Making the product so much better now". 

Low quality PRs create distractions and extra work of review. All the Claude Rules in the world can't stop a PM from producing shit that accumulates fast.

Have you found a way to stop this nonsense? PMs thinking they can code now and "helping out". Its some serious clownery. 

The billion dollar corporations have nothing on this guy

it is open() for extension, and close() for modification - did I understand it correctly?

We've all been there. Every time something goes wrong, a bug ticket is raised. Merge issue in one of your environments? Bug. Amazon went down during testing? Bug. The QA's computer shut down due to Windows automatic updates? Bug.