This is definitely a good musing on when not to go for "cloudy architectures". Most often people don't really need it, this needs to be properly thought out for each project. There are costs involved which you might not make sense to pay for in your context.

Nice little database pattern to avoid row contention with counters.

It's nice to see Tor is still winning even in difficult countries.

This looks like an interesting set of extensions for Java projects. Unsure if it's been properly battle tested yet. Likely need that before being really advisable.

Very cool map. Definitely useful tool to push for more train use.

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.

Nice tool to spice up your interactive shell scripts.

Good collection of tools, I knew a couple but not all of them. Will go well with markdown uses or similar.

That's nice to see a reusable framework to help organizations get started with their engineering ladder.

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

Looks like a somewhat recent alternative in the search engine and document indexing space. Sounds potentially interesting.

One of the best developer tools around for analysis and profiling. I'm glad it exists, saved me a few times.

This is an interesting (and concerning) type of rootkits. Hard to tell how much of it really is in the wild at the moment.

An advice I often give, it's nice to see the theory behind it well laid out like that.

Very interesting musing about the technical terms we often use wrongly and how it difficult it is to be understood.

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

Wow, this is a very good exploration of the performances of several common languages and runtimes. This is one of the most thorough I've seen. A good resource for deciding what to pick.

Now this is a well balanced piece about estimates. Starting from the "why" to decide how you approach the estimates and the level of details is just very good advice.

The developing type system in Python is really having some nice properties now. Well used, it can help quite a bit with checking an API is properly called by user code. This is nothing new to languages with stricter type systems of course.

This shows quite well why I stay away from Spring Data JPA...