A good proof that it's still possible to innovate with interesting performance gains for rather mundane tasks. If you're into calendars this is an interesting read.

A good reminder that you better measure the right thing... otherwise you might consider someone as unproductive while he has in fact a large impact.

Interesting and unfortunate security issue... This is admittedly a somewhat unusual setup though, but to be kept in mind I think.

First time I hear about this application. It seems really nice, I'm taking it for a spin. Not sure I'll use it to replace OsmAnd just yet. That said it's UX seems better than OsmAnd so far.

I'd take the more stack related side of this article with a pinch of salt. It seems a bit too specific to the company behind the story. The rest of the article rings true and spot on though.

Now this is actually an interesting and good use of the latest trend in large language models. You can simulate difficult conversations, getting more experience there can help.

Are we surprised? Not at all...

USENET lives! Another revival coming?

Indeed, at this point it's not that people don't want to switch. Very often they just don't have a choice.

Good list of advices, I regularly see people failing because of fundamental things like this... despite explaining my expectations first. So I'd add: listen to what the interviewer says about how he's going to assess you.

Interesting evolution... looks like people will all go back to some chat system? It'll be the 90's all over again? Maybe IRC will make a comeback? :-)

The level of details these techniques are giving now... this is very impressive.

And now the part two, with more warnings about what you measure. Also proposes a few ideas toward the end.

Microsoft doing Microsoft things in Windows... unsurprising, will never end. Maybe at some point people will move to platforms they really have control on?

If you only stream it, it won't be available forever. Keep this in mind when it's something you find culturally relevant... it might require some conservation work.

It's clearly not clear cut, it's a whole spectrum. I wish more web developers would at least ask themselves the question before having knee-jerk reactions reaching for their favorite framework of the day.

The claim is huge. The story doesn't quite say how much is really about Elixir and how much from the revised architecture. That being said, going for something like Elixir has definitely an impact on the architecture... could it be that it pushes for better patterns?

Excellent piece. Be careful what you measure. If you measure the wrong things people will game the system.

Nice overview of the good uses and wrong uses for classes. We're far from the abuses of the early times now.

Interesting opinion piece. Very often we see people mandating a "process". It's almost always the wrong way and how you end up with people following blindly "Scrum by the book" or "SAFe". The approach proposed here is smarter: give the business constraints, let people choose what works best for them, support them along this journey.