Rachel knot, named after the inventor's wife. I like it, it looks interesting and isn't that fiddly to tie. Requires a half turn at the back of the neck though or the pleats show the wrong side.

As a software engineer and public speaker, I want to leave a legacy when I'm eventually free()d, just not legacy software :D

That COBOL system written in the 70s that no one dares touch because it has no tests and still handles all your money. A software suite where every released version of .NET since 2002 is still in use because upgrading them is too expensive.

A legacy piece of software is a point of friction in your business and something your developers want to avoid. Often it needs to be replaced – at considerable cost.

The ancient Egyptians' legacy is the pyramids. Tourists travel from all over the world just to have a look at them, more than 4500 years after they were built. Mozart's legacy is his music. People pay good money to listen to it more than 200 years after his death.

Why is legacy negative when applied to software but positive when applied to people? If we talk about people's legacies, it is usually positive: something that they left behind or are remembered for.

We're going to manufacture painted metal plates with product information on them!

If I ever start a product company, that's what I'm naming it.

AI-bottarna är ju ungefär lika bra på att följa regler som småbarn, så varför inte 😁

Maybe they're actually named VendorCo? 😁

Margaret Hamilton will be remembered. As it happens, I'm drinking a beer. So here's a toast to the memory of the first ever software engineer!

One thought occurred to me while browsing whe schedule: are talks about using GenAI more or less likely to contain AI-slop compared to "other" talks? I.e. are the speakers talking about these topics more likely to let GenAI produce the content and, if so, are they better at preventing the slop?