A Django API server in a single file of 70 lines is quite a statement.
An explanation of how it’s possible to program withoutusing your hands using eye-tracking and voice recognition.
A fractal treatment of the various level of engineering management.
Something I have to keep reminding people of: “Once you reach a certain level, all problems are solved by people. There is no such thing as a purely technical problem.”
The nice part of working on open source is I can finally share some of the amazing work my team has been doing. Here’s some forthcoming Suricata contributions by Sascha and Frank with more on the way.
A guide to designing an interviewing process tailored specifically to the staff engineer level.
“I am successful if I’m saying the right “No”s to my manager. If the ICs that report to my manager end up feeling like “I told you so” or “We knew this was a bad idea” and that wasn’t surfaced for a discussion, that’s on me.”
“I confidently trade on my manager’s authority in ways my teammates may struggle with. Because of my time and my deeper involvement in the technical details being discussed, it is my responsibility to step in and deescalate if a technical conversation is starting to circle the drain.”
I really like this explanation of the variety of things that a staff engineer can do (and does).
It sounds very familiar here that the mark of a senior is to have continuous pressure against getting anything done and then still getting stuff done.
One part of it is that if you’re capable in a platform, you should be able to get out the same amount of code in a fraction of the time.
I’d add glibly: if you’re getting stuff done, maybe you’re not a senior?
A nice interview with Gergely Orosz about building engineering teams.
Once you’ve worked with post-commit reviews, I promise you will not want to go back to the PR way of working again.