Nick Weaver

Imagine every pixel on your screen, streamed live directly from a model. No HTML, no layout engine, no code. Just exactly what you want to see. @eddiejiao_obj, @drewocarr and I built a prototype to see how this could actually work, and set out to make it real. We're calling it Flipbook. (1/5)

WPackagist has been acquired by @wpengine. For over a decade, Outlandish built and maintained this service. Now WP Engine is carrying it forward - with the same commitment to the developer community in the WordPress ecosystem.

This Iranian warship thought it was safe in international waters. It wasn't. The @DeptofWar is fighting to win. 🇺🇸

When I first saw @artman’s post about Fixing Bugs First at Linear, I nodded a bit, and then a lot. I'm so glad @thorstenball and I radically adhered to this from day 1 on @AmpCode. Here's what I've learned: • Fix Bugs Now (not First): The overhead to file an issue, prioritize the issue, assign the issue, and update the issue is often greater than the time it takes to fix it. Just Fix Bugs Now, right when you hit them or hear about them; don't bother filing an issue. The reporter need not be the fixer, but you must confirm it's going to be Fixed Now before you let go of it. • Backpressure: You will never be drowning in bugs if you truly Fix Bugs Now because you won't have time to build new features that would introduce new bugs. If you're drowning in bugs, it means you're insufficiently adhering to Fix Bugs Now, and new stuff is sneaking through. Fix that. Cut scope immediately if needed, no matter how painful. • Go Direct: When fixing a bug, devs talk directly to customers. No middlemen. Fixing Bugs Now for a real person you're talking to is rewarding and effective; anything else is grunt work that requires a lot more motivation and management pep talks. Plus, customers love talking to devs. • The 15-Minute Rule: From the moment a customer reports a bug, you need to be able to ship a fix to them within 15 minutes. Some fixes take longer, of course, but let's say it's a simple one-line fix: 15 minutes to the customer's screen. If it takes longer, you break the customer's flow, so they won't bother reporting most bugs (since they wouldn't benefit from the fix in their current task). Also, you kill the reward loop for your own devs and kill their focus, since they'll keep mentally tracking the bug until it's resolved. And if it takes days to ship a fix, then you'll need a process for tracking and communicating fixes, and so on, and all of a sudden the overhead dominates the time to code the fix. • Repeat Repeat Repeat: Fixing Bugs Now is so radically different that your team won't believe that you really, truly mean it at first. Or even after you've repeated it 10 times. You need to say it in every single team message for it to stick. Even knowing you need to repeat it more than you think, you won't repeat it enough. • The Stick: Yes, praise your team for Fixing Bugs Now. But for 80% of devs, the reality is you'll need to (at least once) give them direct, constructive feedback when they stray (with good intentions) from Fixing Bugs Now. You need to use the stick for it to stick: "I know you had good intent in building xyz feature while ignoring bugs, but that is not how we build here, and I need you to not do that again." • Sorry and Thanks: Bugs are a fact of life, but that doesn't make them OK. Call me old-fashioned, but I think you should apologize to customers when they hit a bug and thank them for raising it. Knowing you appreciate it, customers will give you more feedback. (Caveat: We build for devs, we have an amazing team who we trust, and we started Fix Bugs Now on day 1 at @AmpCode. This probably doesn't apply to existing products with existing bug lists or for non-dev products. I imagine what works for us will also change over time.)

x.com/i/article/2028…