Worked on an app for a manufacturing company. Took literally 3 hours to run. Brought it down to under 3 seconds, for the exact same thing. 3 seconds made them v

Worked on an app for a manufacturing company. Took literally 3 hours to run. Brought it down to under 3 seconds, for the exact same thing. 3 seconds made them very, very, very happy with the UX. At 3 hours run time, it really f-cked up the assembly line, like, a lot. The speedup happened on the exact same computer - same CPU, same memory, same hard drive. So it had zero to do with hardware, and everything to do with coding. And if you threw faster, better hardware at the problem, it would not change anything for shit. So never depend on the false hope hardware will solve shitty software design issues. The whole idea that it is cheaper to code fast to get something out fast is bogus. It just takes knowledge on how to do it correctly in the first place. I don't think the coding that I did took any longer than the original coding. The original person just sucked ass. So, whatever language you code in, you should start watching videos or reading articles on how to maximize your application's speed. It usually is not that difficult, if you spend some time. Most of it you can copy and paste. Do searches on "Top 5 ways to speed up x language". So easy. That really drilled the lesson home on the importance of the approach to making real fast systems on the design side and not on the hardware side.