Blackthorn

Still impressive!

Yes, that's actually pretty rare in Hollywood: an actual friendship between a man and a woman, without having to jump the other.

Not yet. I have mini metro though. Very similar but somewhat different feeling. It's probably the closest thing.

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.

Sometimes I wonder if this pure search for being "idiomatic" is worth the effort. On paper yes, more idiomatic code is almost always a good thing, it feels more natural to create code in a way the language was designed to be used. But it practice, you don't get any points for being more idiomatic and your code isn't necessarily going to be safer either (smart pointers are often "good enough"). I'm fine using references to pass parameters to function and I love the idea to "force" the programmer to organize objects in a tree way (funny enough I was already doing that in C++), but I'll take a Rc rather than a lifetimed reference as a field in a structure any day. That shit becomes unreadable fast!

EDIT: but I love cargo clippy! It tells me what to change to get more idiomatic points. Who knows why an if/then/else is better than a match for two values, but clippy says so, and who am I to question the idiomatic gods?

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