• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: August 6th, 2023

help-circle





  • Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written “in blood” from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don’t just upgrade, see that the app is up and push to prod, that’s not testing, that’s asking for trouble.


  • Cool. Do you trust a random catering company to get it right for millions of students? To maintain the exact diet that’s needed to get every nutrient, at a kitchen that hires random cooks and asks them to make food for 200 people at a time?

    In reality, cooking a meat based meal is easy, fast and scalable. Cooking a plant-based one and only doing that isn’t. There is a reason why laws exist - and this one exists because they were cheapening out and serving substandard meals. So they made it mandatory to at least contain some protein in the form of meat.


  • Okay, let’s be angry at the company and frown a lot at what happened. Gurr, bad company, evil.

    And now think of what you’d rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. “Latest” is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It’s absolutely not a “best practice” if it isn’t even a code smell or an outright bug. You could’ve had a slightly outdated version, which won’t be “exploitable” - you wouldn’t have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.

    Instead of putting out the fire, you could’ve been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren’t supported, chilling till they are supported or complaining that they aren’t.

    Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.