“This is great, this is ok, this is great.” is an amazing tool. People will always focus on the negative, so presenting a negative as a positive, but juxtaposed with even better positives, shifts the scale. It makes people think about it, without being too hard on themselves. I call it the compliment sandwich.

Another tip that has served me well is the tick of approval, followed by the question “With this part, what would you do differently next time?”. It frames it as self improvement feedback.

That being said, I’m not part of a traditional code review process, so this could all be totally misguided advice.

The Hobbit.

I used to do it with reams of dot matrix printed BASIC.

I hate how fragmented they are. I’ve given up on various guides out there for ‘setting up the arr stack’ because of getting bogged down in since miniature detail that, IMHO, shouldn’t even be a thing. I get that hosting seperate services has advantages. But the disadvantage of giving up on the whole thing because you have to sort out networking and file permission issues between the service that downloads video files over an hour long and the service that downloads video files under an hour outweighs those advantages.