The things he asks to do are the reasons why I find no joy anymore working in coding. Hammering my thumbs seems to be more interesting than doing most of these actions. I swear, I got so bored I couldn’t finish the read. Specifically “if you find yourself commenting on every line of code” the right thing to do is to setup a meeting with te hiring department.

I’d say it suggests it’s “legally” the wrong thing to do.

Code review can’t fix incompence though. I lost count of how many times my boss told me “review that PR well because X is not very good”. Also my point is that they are overrated, not that they are useless.

Probably unpopular opinion, but peer reviews are overrated. If coders are good AND know the project, the only thing you can do in a PR is nitpicking. They are more useful for open source collaborators because you want to double-check their code fits with the current architecture. But people here are reacting as if peer reviews could actually spot bugs that tests can’t catch. That happens rarely unless the contributor is junion/not good.

I would fire you for incompetence and sabotage. Problem solved.

Lol I feel so old reading these replies… I learnt copying BASIC games from magazines and typing them manually on the computer.

But jokes apart, when it comes to learning, I think the best thing is to tinker with weather language you choose and don’t worry about making the “right choices” since the start. Forget about writing “pythonic” code and don’t worry about being “idiomatic”: just build something. Building good software is not just constructs, but also knowning which subsystem to improve and when. That’s what makes experience.

When it comes to improving, you can dig deep into the language.

Yeah, this is also useful when learning a new programming language, even when you are an experienced coder, already.

Ofc I knew! Yeah, (neo)vim takes time to adjust. Personally I only use a bunch of commands, never bothered with the advanced stuff.

Personally, I mostly use neovim, both at home and at work. My reasons are:

1. I hate any kind of screen cluttering. The minimap comes straight from hell.
2. it’s very responsive. I don’t even bother using language servers as they occasionally introduce micro delays that I hate.
3. it helps me in organizing the code better. No minimap means I keep the file size manageable, not seeing the definition of the function straight away means I keep the static complexity of the code in check (tend to reduce the number of delegates). It doesn’t help when I have to read cose from legacy codebase, but I don’t care too much about that.

I salute the author of this for drawing a CRT monitor.

Follow up of: “Mmm… should I put lifecycle annotation in these 10 structs or just use and Rc and call it a day?”. Rc and Box FTW.

I second this game. The cat can also find a mate abd have kittens