It’s the companys fault for looking at the 151 and saying, what if we replaced all this with random bullshit? I miss the og pokemon. I tried playing newer games but damn, it’s pure chaos.

I would reject this pull request. Why is the indenting all over the place? Why is your keyword capitalisation all over the place? WHY YELLOW?!

Edit: the more I look at this the more it pisses me off. Wtf is going on with your kerning? Just random number and placement of spaces. Also, why is the table name in caps? Who does that? Select * is lazy. Do you really need every field about a girl? Really? Worst of all, not a limited request. I sware this is just the kind of thing that would return 30 million rows and brick the database for twenty seconds.

Sir Chad carries a twelve pounder hand cannon, and when he ignites the powder the ball sails true into the main deck of the pirate, but the recoil capsizes his vessel.

Stupid sexy Flanders.

It’s code, but without automated tests, comments, style rules, and often stored in binary files making change management a nightmare.

It’s trying to paint but you can only use your fingers and also one of the other devs ate all the red.

An amazing story, and just downright perplexing. It is a shame you never found out what on earth was going on in the CTOs head. I would love to understand the thought process (or lack thereof) that went into that.

This thread went unexpected places. I can’t even imagine the pain. I hope you keep printing little bits of joy for them.

This looks similar to a problem I was having. Turned out that my extruder wasn’t calibrated properly and it was pushing far less material then expected. Try running an extrusion test like described in https://ellis3dp.com/Print-Tuning-Guide/articles/extruder_calibration.html

I think about it like the tires on a car. They are (hopefully) the only part of the car that touches the road. If they aren’t working correctly everything else isn’t going to save you from a gentle curve in the road.