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.

Nice article explaining unikernels and showing the example of MirageOS.

An old one but since I'm aware of companies still doing their performance reviews this way... Don't fall for it, use a more humane process whenever you can.

Interesting research, this shows opportunities to push CRDTs to the next level.

Another partial quote which led to misunderstanding. One should indeed think about performances early on.

I tend to agree with those, they are among my pet issues with C++.

Good set of patterns indeed. The article is web oriented but this makes sense in other type of applications as well.