Very cool tool to generate random maps, go all the way to per-city generators through this:
https://watabou.github.io/city-generator/

Really cool stuff.

Looks like an interesting approach to keep in touch with people. Doesn't seem too horrible to maintain once the first setup is done.

Definitely a welcome move... will need to be enforced of course. Let's hope it won't turn into yet another text without teeth.

This asks very valid questions. I'm a bit less optimistic than in the conclusion though... I suspect that if it truly falls, it will be replaced by another cargo cult.

This looks like a nice way to somewhat safely expose self-hosted services to the outside.

Excellent article about best practices for logging errors, most of it applies for other type of logs though.

Thank you indeed. The amount of upstream contributions their efforts fostered is enormous at this point.

You thought averaging two unsigned was trivial? Think again, here what needs to happen in all its glory.

Interesting musing on the skills required, why it's actually hard to apply them... clearly it's because you never find a real place to learn them so that ends up being on the job.

I like this position. There's been too much of a move to "kill all the settings!" in some products. Some of them definitely make sense, and the "on boarding" point of view mentioned here makes sense.

I obviously agree quite a lot with this.

If you didn't try Kate for a while... the next release in the spring will be a good time to try it again.

Interesting use of WebAssembly for fast and very portable code. Also especially interesting is the care in the move to the new software architecture.

Good reminder that the words we use matter. Fuzzy terms like "clean" indeed hide various dimensions to look at the code and the tradeoffs we make.

That looks like an interesting way to share data between applications. Reminds a bit of the semantic web movement back in early 2000s (talking entities and aggregates), maybe less heavy on the schema side though. I'd need to look at the specification more.

Lots of food for thought in that article. Shows very well some of the trade offs in complexity languages have to deal with when they bring a strong type system to the table. Hence some limitations being in place... and that's why it can get into nasty metaprogramming territory quickly. This show a couple of interesting examples on how this can be mitigated although we don't have any perfect solution yet.

Type annotations become quickly complex with Python. This is in part because it's rolled out incrementally on top or existing practices. Here it collides a bit with decorators. Nice to see this hole is getting plugged though. Also nice to discover an alternative to mypy which seems a bit more precise (at least for the time being).

Interesting example of using a strong type system to avoid mistakes in code using a parsing and serialization library. The fact that it's about IMAP and I'm still traumatized by it has nothing to do with my interest in that article, really.

Good guidelines to improve end to end tests. I especially relate to the first one, the test API is very important for those, otherwise they become a chore to maintain and understand.

Interesting tips for potential bottlenecks in your queries.