Comments by "Christian Baune" (@programaths) on "1970's Camera Tech: How they showed you what settings to use" video.

@trippmoore I worked as a QAM and for some part of the implementation that had to be done according to regulation, I had to jump in and code it myself. The team wasn't apt enough. When I did quit, they attempted to rewrite it in a "simpler" way (i.e. consolidating everything into a function). That didn't end well as the new code was impossible to "prove" and testing was a nightmare. Devs were really pissed by that "shitty code" 😃 At some point, I had to shove the dependency injection and have them follow a training on design patterns and refactoring, because the code became routinely a mess. I even had to explain to a guy what are SQL injections and why sending SQL to the back-end was quite a bad idea. Even had someone doing batches by having the front-end calling the back-end repeatedly and hitting browser limitation on number of concurrent requests and the having issues with back-end also dropping requests ^^ Educated on stored procedures and even coded that batch which took like an hour and went in few seconds as a result. I was the "QA department" and I can confirm that devs despised when I cam to talk seriously to them😁 Now, I am back to the full dev thing (aka "full stack", but more "do everything") and I wish we had at least QC, It's nice to have someone check your work so you don't have to stray too far from your main job. There is a bit of QC built in IntelliJ and I like that too, better than nothing!
3