More elements on why we should all be concerned about Visual Studio Code and the state of development tools overall. It's clearly moving more and more proprietary. Visual Studio Code's ecosystem is a very well designed trap. I see it more and more around me (even tried it for a little while to see what it was all about). What can I say... Go Kate Go! And also we clearly need many more LSP servers.

I think this is a fair account on the state of OCaml in 2022. I wish it'd have grown more and have a bigger community by now. Nice little language still.

Very good summary on how to process currencies properly in software. Goes all the way to explaining how such a library must behave (should you make one or decide which one to pick).

I definitely recommend adopting this mindset. Been doing most of that for a long time and this definitely helps.

Very nice catalog! Looks like a useful reference.

I already do some of that reading code for some profiles, although it's more geared towards finding mistakes in the code. I like the proposed approach here, will try to do some more of it.

Hear hear! It's not supposed to be easy, you need to hone your practices.

Nice new feature coming to C. This is useful stuff. It required quite some fighting to get in though.

In the end, this is a nice conversation about language design...

I don't quite subscribe to some of the terms used (even though I see the point of not calling this API). Still I think this is a very good way to approach design, it's also why I like TDD, the tests force you to see how the code is used. If it ain't pretty there's a problem.

Good set of advices around dicts. This is Python centric but some of it applies to other languages as well. Mind the lack of anti-corruption layer.

And this is why you likely need to optimize your data pipelines at some point. There are plenty of levers available.

Excellent collection of surprising behaviors in Python. If stuck or wondering why something works in a surprising way to you, it's a good place to look.

Interesting interview which explores quite a bit mob programming, where it's coming from, why Woody Zuill pushed for it, how it is done, etc. I didn't expect his opinion on why he thinks the name being controversial actually helped spark the conversation around the practice... Very inspiring how he practiced for years to feel comfortable being on stage. I also love at how humble this person is through and through.

Good exercise of prospective for our field. I don't subscribe to all the analyses in there but the value is in at least starting the conversation about it.

Interesting balanced view about Rust. Looks like it highlights strengths and weaknesses properly.

Interesting way to see where to spend time in reviews.

Bunch of good advice. In a way it boils down to: name things properly and use static analysis tools extensively. Still, couple of nice operational guidelines which work in most languages.

Interesting and fair list of pain points around Rust. This is a change from the pure fan boy articles we see most times.

Good primer on refactoring, I especially appreciate the big fat warning about language erosion... the number of times I hear "refactoring" for something which is not a refactoring at all...