Bumped into this. It's indeed nice, full of good advises for handling code reviews.
This is a good summary of why I like my type system to be "tight", strong and statically checked.
Good (and long) exploration of the field, going into the different variants provided by various languages.
Good cautionary tale about burnout in general, the big wave of it induced by the pandemic... and the likely huge resignation wave coming up in some places.
Definitely a nice tool, but I often struggle to use it (honestly I suspect it tries to do a bit too much). This is a good cheatsheet to go back to for learning.
Definitely worth it indeed. Couple of interesting tricks in this article.
Nice description of the community management in the Rust community.
Pile up enough complexity and it'll quickly become insecure.
A good reminder to use the right tool for the task. Sometimes all you need is really a POSIX shell with a couple of well optimized tools.
A good reminder of what the Web really is. Yes, it's hard to add features to it, but look at the amazing backward compatibility! Everyone can write web pages and that's what matters.
Interesting exploration and workaround for the Postgres query planner.
Nice summary of the abilities coming from CSS transforms.
Interesting exploration and rough explanation of why SAML has so many issues. Complexity by design in such critical components is a bad idea...
Good set of guidelines to figure out what works or not in virtual meetings vs in-person meetings.
Interesting analysis on the impact of lazy-loading images in your pages. Bottom line is: don't do it blindly, it's actual better to not lazy-load some of the images.
Another couple of attempts at supply chain attacks. This time in the Python ecosystem. The skill level of those attempts isn't high though.
Funny and somewhat balanced. It shows in the subtext that it's not just about "the good old days".
Yep, definitely do this on a regular basis. It takes only a minute several times a day.
Interestingly I'm less interview averse than what's explained in this article. Depends how it's done of course, but since I think I'm also evaluating the potential employer, seeing more people gives you a better idea of how things are internally.
There's been an announcement of MediaWiki adopting Vue.js. I think it's interesting to not stop at it and look what their workgroup evaluated and looked at to decide it was a good choice for them. There are a couple of interesting points in there.