Engineering Best Practices
In my current pursuit to organize all of the knowledge I have stored across tools and apps, I've been decluttering my digital “stuff” and came across some old docs from a quality assessment framework we used when I started at Dropbox back in 2016. I first learned about
Team Culture & Leadership
I've been the "first QA" in three different ways over the course of my career: as an advisor to a tiny startup that ultimately didn't make it, as the first quality hire in the satellite office of a company with an established QA team
Tech Musings
I had an interview earlier today. Sometime during a chat with a possible future boss, a former colleague (now an engineering leader at this same company) walked in to say hi. We got to talking shop, and flaky automated tests came up. The two QA folks in the room joked
Quality Assurance & Testing
You’ve identified your quality gaps. Now what? Knowing what’s broken doesn’t automatically tell you how to fix it, and that’s the part where a lot of teams get stuck. So if you’re staring down a list of issues and wondering: Do we need to hire
Quality Assurance & Testing
So, you’ve moved past the question "should we hire a QA?" and on to "what kind of QA do we actually need?"* In my last post, I talked about the QA roles that I think should exist and how I wish companies would evolve their
Quality Assurance & Testing
Lately, I’ve been spending some time looking into interesting companies. Part of it is curiosity, but mostly, I’ve been scoping out places I might want to work next 😅. One thing I’m noticing is that more and more companies don’t have a dedicated QA or testing function.
This site uses Umami for privacy-friendly analytics. No cookies, no tracking, no personal data collected.