90% of programming I have seen after a decade plus of doing it full time is minor changes being made to code that was already made by someone. Likely not documented. Likely already changed in a dozen little ways. Math isn’t the problem. Understanding what the guy who wrote it is often the problem.

Oh and you can’t ask them because they likely don’t work here anymore.

Being a programmer is more like being a detective than anything else unless you work for a small company.

I am saddened to see that this thread had no mention of how many horses it takes to run a router. What do y’all think? Would one be enough? It would need to work in shifts to keep up time at 100%. Maybe 3 to be safe?

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

The future is already here – it's just not evenly distributed.

The Economist, December 4, 2003, William Gibson

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.