tl;dr: (1) Doing all technical design work yourself. (2) Doing all the project management yourself. (3) Neglecting to give feedback on non-technical issues. (4) "Hoarding information" i.e. not providing business context to your team or distilling and communicating it effectively. (5) Focusing too much on your personal output and not the team's output.
tl;dr: (1) Software engineers, like all humans, need to feel ownership. (2) Your data is the most important part of your system. (3) Look for technological sharks (old technologies that have survived time). (4) Don’t mistake humility for ignorance. (5) Software engineers should write regularly. And 15 more.
tl;dr: SCIM is a popular protocol for user lifecycle management - i.e. making sure that users are added and removed from an app with the right permissions. Should you do just-in-time provisioning or sync to a directory. Let's dig into the details.
tl;dr: "We have a duty to ensure our systems don’t degrade our society. But in the tumult of so many software projects, it can be difficult to step back and understand the implications of our work." This is a catalog of techniques that can be used to address this problem.
tl;dr: After the FB outage last week, Julia wanted to explored BGP and shares 5 tools that are helpful to learn more about the protocol, listed here.
A Note From WorkOS
WorkOS is a developer platform to make your app enterprise-ready. With a few simple APIs, you can add enterprise features like Single Sign-On, SAML, SCIM user provisioning, and more. Get your app enterprise ready.
tl;dr: (1) Don’t write code on the critical path i.e. where you're the blocker to deploy. (2) Defending your calendar. (3) It’s not necessary to be in every conversation. (4) You don’t have to be the most experienced engineer in the team, and more.
tl;dr: "If you're interested in how to productively build a maintainable website using modern tools that is fast all over the world despite every user getting content that's completely unique to them, then please continue."
tl;dr: Joseph received a bug report claiming he "caused 100% CPU util on a VM when it should have been idle." He runs a retrospective on what the issue was and how else it could have been handled.
tl;dr: "There are probably more than 100 different routers available, all with different APIs, features, and behaviors." Alex evaluates 30 popular ones with a shortlist of the best options with a flowchart to help guide you.
