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.

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.

It might be a little better to put the thanks at the top of the ad instead of the bottom.

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

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?

Given the decades of information about how bad open offices are for programmers I think the upside is similar to the upside making supermarket cashiers stand when they request chairs...

there is no upside to inhibiting the means and methods of production.

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.