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.

I can’t not upvote someone who brings Clipper to the table :)

“intuitive” is extremely subjective, and based on your past experiences. I’ve coded in C++ for years, and some Python, too and was able to grasp many Rust concepts very quickly, while for others I struggled (and still am). I’d say that if you are looking for “intuitive”, Rust ain’t it. It’s a system language, so it requires planning, it’s definitely not the ideal language to slap a prototype quickly together, expecially as a beginner.

It competes with C, so in 2023 this basically means embedded systems. It offers executable size of few KB and out-of-the-box cross-platform compilation. It’s a modern C, basically, and it claims to be even faster than C as some language rules allow more optimizations

My understanding is that this is possible: you should be able to take a C project, add a build.zig file and under the hood the system is calling clang to compile the C project. HOWEVER, you can now add a .zig source file, compile that in zig and link together with the output of the C compiler into an executable. If this is actually true, I can definitely see the attractiveness of the language.

I wouldn’t say it’s a new LinkedIn, but it’s definitely a defacto monopolio. It pains be that Cargo (the official rust packaging system) is so integrated with it. My own personal hobby projects are self-hosted on a gittea instance right now, but I still have a github account to contribute to a friend of mine’s project which is, sadly, hosted there.

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 love cargo, but cargo.io could REALLY make good use of namespaces. It’s insane when clear library names are taken by highschoolers at their first project and there is nothing to be done about it. I’d also like some kind of curating on the packages.