software engineering 👩‍💻 💯

Julia Evans once said "behind every best practice is a horror story." If you don't understand a Best Practice, look for the horror story that inspired it. It might make the best practice make sense. It might turn out to be something that's completely irrelevant to you, and then you can feel comfortable doing a different practice instead.

When working on a team, you should usually ask the question

There’s a spectrum of “trying to figure out everything for yourself” to “bugging your coworkers with every little question”, and I think most people starting their careers are too far on the former side. There’s always someone around that has been in the codebase longer, or knows... See more

Never be afraid to say that you don’t know something

Don’t be afraid to ask for help

We all suffer(ed) impostor syndrome

If you can’t easily explain why something is difficult, then it’s incidental complexity, which is probably worth addressing

My favorite manager in my career had a habit of pressing me when I would claim something was difficult to implement. Often his response was something along the lines of “isn’t this just a matter of sending up X when we Y”, or... See more

You've probably heard the advice that software as a field is changing all the time , and that you shouldn't get swept up in the framework treadmill, just focus on learning fundamental skills. This is a true, but doesn't explain the "why". For structural reasons, information in software propagates really quickly. This is due to a lot of factors

... See more

Assess the trade-off you’re making between quality and pace, make sure it’s appropriate for your context

There’s always a trade-off between implementation speed and how confident you are about correctness. So you should ask yourself: how okay is it to ship bugs in my current context? If the answer to this doesn’t affect the way you work, you’re... See more

If you’re lucky, you will have many challenging moments in your career. Moments when you only understand a portion of the problem in front of you, when you know you’ll have to try a few things to see what works, when you aren’t fully confident that you can do the job. We’re lucky to have these moments because that’s how we grow. By pushing outside... See more

Don’t underestimate the value of digging into history to investigate some bugs

I’ve always been pretty good at debugging weird issues, with the usual toolkit of println and the debugger. So I never really looked at git much to figure out the history of a bug. But for some bugs it’s crucial.

I recently had an issue with my server where it was leaking... See more

Bad code gives you feedback, perfect code doesn’t. Err on the side of writing bad code

It’s really easy to write terrible code. But it’s also really easy to write code that follows absolutely every best practice, which has been unit, integration, fuzz, and mutation-tested for good measure – your startup will just run out of money before you finish.... See more