So yah, a rip off.

Storypoints are such an artificial concept it doesn’t even make sense. Same thing with estimation though. Most numbers are “I pulled it out me arse” unless the task is a one line change. And even then, shit breaks and it becomes useless, so the one line change is estimated to be a day anyway

Not really an opinion when most companies run on self documenting code since time immemorial.

I have given well documented code to plenty of juniors, it comes with being a senior dev / techlead. And it was perfectly understood. Maybe you simply don’t write self documenting code.

Lmao. Sure buddy.

The only moment you write comments is when you are doing something extremely weird for a specific reason that will not be immediately obvious and you want to warn the person doing a refactor in the future. In any other case, writing self documenting code is the way. If you are unable to do that, then your code needs to be rewrtitten.

K.

Yeah you’re just proving the point more and more.

You also made a post online about it to complain. That’s a lot of notches.

Yes it is so show your proof or gtfo and I’ll assume you don’t have anything other than wishful thinking

Extraordinary claims require extraordinary evidence. If it is so easy, instead of writing 15 comments you could’ve shown it. So do it or you are a weak ass troll and nothing more.

EU for online purchases mandates that the lowest price from the last 30 days be displayed alongside the actual price and discount. So they can’t pull the “make the price higher and discount to a higher price than it used to be” trick, best they can do is make price higher and discount it to what it has always been. Which is pointless to them because they’ll just get less sales in the month before. Also a month is enough time for the loss of sales to be significant that it isn’t worth it to keep the price high to create a “bargain”.

Time to introduce the “lowest price from the last 30 days” requirement like in Europe.

It doesn’t mean extravagant, it means “a lot of food to eat”. I know how to cook. The intuition of how much I need to cook comes with more experience, but it means I’d need to go through months of me cooking too much and either throwing it away, or eating the same thing for a long time. When you cook for two or more, the dishes just disappear. You can skip a day, your partner will eat it though. So then you do, and suddenly four days worth of meals are gone.

Yeah, for sure. The problem is cooking for one. If you are inexperienced, you tend to overcook and then you either waste that or eat the same thing for five days. Also picky eaters sometimes can’t eat the same thing two days in a row, let alone more. Buuut if you treat cooking as “a job” that pays more than ordering out (where you don’t pay with your time), then it is really worth it for sure.

I’m eating shitty delivered food (including mcdonalds) and I am losing weight. The problem isn’t “bad food” it’s all about controlling calories intake. The only moment where that might not work is if you have some issues - hormonal imbalance or some sort of other illness. But if you eat less and can maintain / withstand that, you will lose weight.

I chuckled at the Harry Kims from alternate realities all being ensigns with one lieutenant among them

I loved Michelle Yeoh as the emperor, a spinoff where everything is focused on her? Sign me up. Star Trek has space for a “darker” side of the Federation imho

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.