AntonZ234

Yeah, my bad. Changed that.

I don't think the right solution is to have the opposite of them - all of them have some value. The point of the article is to not follow them blindly.

Thank you, I got multiple such comments. I edited a bit, and will do it better for the next ones.

Yeah, good point. Might be feeling a bit too sleazy now. Edited :)

Thanks tzs.

OP here. I actually feel that having ads that are relevant to the people reading are better both ways, as you might actually learn about a good tool :) (I try at least to only work with products I believe in).

I felt that having the ad between line dividers, and having this: "Thanks Linear for supporting today’s article!"

should be enough, but maybe I'm mistaken.

Yeah I didn't try, it is an ad :)

OP here. In this one the closest is probably: "I love the process at Pylon: engineers merge their own code and only request reviews if they need input, think they have a risky change, or are still onboarding. "

But I fully agree that for juniors it makes sense to have it mandatory.

What's the big upside that offsets the downside? Knowing what people are working on?

So true

Damn. Glad to hear I’m not alone… transactions is indeed the way to go here.

Scary moments

I’m used to using limits purely in select queries, honestly I didnt event know its applicable for update queries.

Still, it would probably have been after the where, and ignored too.

not using transactions is probably my biggest mistake here.

The answer is actually a bit complex. I simplified in the article, the orders are in fact internal ‘missons’, that our operations team needed to execute (I work at an Agtech company, and each such mission is a drone flight above a field).

Due to some bug, there were duplicate missions created, and it messed up the systems and confusing the operations team.

Right, but as I had no way to understand which orders should be ‘hidden’ and which don’t, from the systems side it was the same as if I hard deleted everything.

Interesting, I’ve never heard about that pattern, only is_deleted everywhere

I don’t know why the decided for a default like that. In Editor > Editor SQL > SQL Processing

There is a setting called 'Blank line is a statement delimiter' which is on by default for some reason

That's a great metaphor.

I've had similar experiences with internal stakeholders.

I can relate to the senior developers in PM roles. I only worked with one such PM, but he was amazing.

Most of the PMs come from non-tech background, more project-management types, and it shows.

Yeah, most of the article is direct quotes from his book 'Competing against luck'. I felt he tells it in an amazing way, so no need to ruin that :)

Thanks for the recommendation for Dekker, added it to my list!

Honestly, I'm not super with the title too :) It's hard to find something that's eye-catching but honest to the truth. What would you choose?

"assuming that what your sales people say the customer wants is actually what they want or need. This one is tricky. I've had sales people go "unless you build X, I can't close the deal" and then you build X and it doesn't make a difference. Reason: the sales person's analysis was wrong."

this is SUPER common, and very hard for organization to counter. As salespeople usually interact the most with users, PMs tend to just do what they say.