Very interesting post about the history of UML and the MDA approach. Clearly MDA and UML v2 was the beginning of the end for UML. That's too bad, I find UML still useful for sketching and communication between humans.

A good list of tools for making diagrams in various situations.

This is definitely a big deal both for the kernel and for Rust.

Interesting career ladder example. I especially like the various dimensions they focus on.

Although I disagree with some of the examples she summons, I think she indeed has a point.

Good point, this little wisdom from Kent Beck goes further than just code and refactoring.

This should hopefully ease the pain of mixing Rust with other languages.

The most addictive and also tracking you everywhere it can (unsurprisingly). Toxicity at its highest.

This looks interesting. Definitely something to add to the tool belt. Coupled with jq this becomes very powerful.

This! There's definitely something interesting with those very focused devices. The problem though is carrying them + something else for other uses. This adds up quickly.

I definitely agree with this opinion. We definitely don't use state machines enough

Definitely a case of a very interesting bug found in production. In the end, the root cause is the loss of context because people working on the components changed. Never underestimate the knowledge lost when someone leaves.

A little collection of dirty tricks that you should probably not use on Flatpak installs.

This is good news, this provide more venues for improving performances in Python modules next to switching to compiled Rust with something like PyO3. There's clearly a case to be more for not having to rewrite when the codebase was already mostly Python.

Interesting points about complexity. Indeed it's everywhere the problem is when you start to silently (and unwillingly) worship it... coupled with fear of changes this can only lead to piling more and more complexity in your systems.

Good explanation of the relationship between memory and learning... it's not quite what one would intuitively think, things need to be in long-term memory first which means you need to repeat things somehow so that they end up there (otherwise they're just in the temporary working memory).

This is an interesting simple rule so know when to split something, I like it.

This is an interesting way to frame it. I generally talk with people about making sure you got vision and horizon in your product backlog (which then requires adequate grooming). Still this sounds like a simpler to grasp wording here. Probably good for a first approach.

Interesting set of tips for interviews. Definitely inspiring to dig deeper on a candidate motives and behaviors.

Interesting way to highlight Goodhart's Law. Indeed you can be corrupted by the very system you put in place if if it's mainly driven by metrics. As much as possible, think qualitative, not quantitative.