A friendly reminder that Javascript is an endless pit of surprising behaviors. Watch out!

For sure the aforementioned manager need to fix his communication style. That being said the core advice was indeed good.

Or why analogies with physical work don't work...

Again that confirms that all the hype and grand announcements are not deserved. It also gives a good idea of the skills which are required to use those tools, clearly the setup process is involved if you want to don't want to be overwhelmed and drowning in bad code.

Despite the marketing speak... it's definitely not there yet. So far all the attempts at using LLM for coding larger pieces end up in this kind of messy results. It helps kickstarting a project indeed but quickly degenerates after that.

Indeed, it's something where we lack consensus across languages and sometimes within the same ecosystem.

Definitely ugly in the end. Still it does the the trick.

With the little Go I wrote, I admit that the multiple return values feature is... odd. Worse though, it has bad ramifications.

The whole field is unfortunately a bit fuzzy. That said, this article gives interesting ideas about what to pay attention to when writing code to ease the readability.

Ever wondered how to make a code formatter? This post does a good job showing the main problems you might encounter. The impact of Unicode is especially funny. Very interesting stuff.

Nice post. Explains well why the answer is not a number to target. You want to impact the distribution.

Nice exploration of the important areas in the kernel.

An evolving list of how to write idiomatic Go.

Interesting class of data structures with funny properties. Looks like there's a lot to do with them.

This is an important concept in Rust... but clearly it's harder to grasp than you'd expect.

Nice little Python trick using bidirectional generators.

Makes sense, the "boyscout rule" has a psychology impact as well.

A long piece which explore the reasons why Rust is likely not the best pick for enterprise software. It's niche is clearly system programming but beyond that and because of its qualities in that space it quickly become a sharp and dangerous tool.

Interesting endeavor... this is nice to have an attempt at a formal definition with no axiom introduced.

This is definitely a problem. It's doomed to influence how tech are chosen on software projects.