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

help-circle





  • You replied to the person explaining this and ignored all of it - she was one out of 3 teams, each using different methods to arrive at the same conclusion. They simply made a photo of her when she got a result and was excited. They didn’t “choose a representative”. She said “everyone deserves the credit”. So why are you pushing this, instead of saying “all the teams deserve credit and this is a cool photo”?









  • 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.


  • 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.