A bit of incoherence between this

'We are destroying software telling new programmers: “Don’t reinvent the wheel!”. But, reinventing the wheel is how you learn how things work, and is the first step to make new, different wheels.'

and this

'We are destroying software pushing for rewrites of things that work.'

But generally speaking I grok it.

The rewrite line is about "Let's rewrite this big system from X to Y", not about experimenting creating new variants.

I think that's actually pretty pragmatic. Sometimes the answer is to reinvent the wheel. Sometimes the answer is to keep improving the system that already works.

The problem, IMO, is globally applying either rule.

Any alternatives? That's like saying that producing food for people is the biggest ecological footprint.

This website is fantastic

When the website looks like this you know the takes will be hot (thoughtful and erudite). Probably the last website standing in the webring.

...and then there is the real world...

You can actually really turn off the stove after the water starts boiling again. As long as you of course keep the lit on. That's how I have been doing it for a while, no dramatic difference in the end result (and yeah I am Italian, so I tend to complain about the details in food related matters).

In Berlin I smell weed everywhere I walk. I love it

In this video (where among the other things they explain huroboro), they show an example of code that prints out exactly the same output (itself) whether it's compiled/executed in c, python or ruby

https://youtu.be/6avJHaC3C2U?t=1957

Any hint on what technology they are going to use?

It's based on [eIDAS](https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/2019...)

As far as I remember, mostly COVID certificate tech. I don't think the standards are done yet.

Wallet because European ID is a tabu.

What's the data science-specific part of this terminal configuration?

The SEO?

Just wait until you see the "How to set up a terminal for DevOps with oh-my-zsh" article!