it’s crazy how we have both the World Cup and America 250 this year and almost no one cares about them because the administration has wholly sucked the joy out of even momentous national events
I regret to inform you that Ask Jeeves is dead. The site closed yesterday. Web 1.0 lost another founder.
Ask Jeeves: 3 June 1996 - 1 May 2026. Send no memes.
Vance had the absolute gall to criticise Europe for censorship - yet jetted in last week to defend the one EU country which literally banned the opposition from appearing on its public broadcaster and whose propaganda would make Kim Jong Un "lick his lips" (PM Magyar) 👇
@SocrFutbolForum@sgevans@Tri_Rail Minnesota United’s stadium is right on the light rail line. Took it the one time I went to a game there. Great experience before and after.
When the 2026 World Cup was announced for the United States back in 2018, I told myself there was no way I’d miss it. I was going to be there in person, experiencing a World Cup on home soil and I know so many of you felt the exact same way.
Fast forward to now, and the ticket prices are completely astronomical. Outrageously unaffordable. What was supposed to be the dream of a lifetime has been priced out of reach for regular fans like me. I’m going to miss watching my country host the biggest event in sports… something I may never get to experience again in my lifetime.
Yes, they’re going to make money off this massive event on U.S. soil. But the greed has gone too far. It’s ruining the beautiful game and turning it into something only the wealthy can enjoy. A World Cup should be for everyone not just those who can drop thousands without blinking.
This is an absolute shame.
@EricBlake12@webberweather I got you Erics mixed up on Twitter this past winter and kept wondering why Blake had become so obsessed with NC snow events. You probably don’t care but I found it amusing.
@mario_chavez@lucianghinda I’ve used @mario_chavez upgrade skill and it worked really well (and affirmed for me that my rails upgrade practice was not out of touch with best practice). Do either of your skills also guide you through upgrading other gems in your app?
This might be the weirdest part about Trump’s horrible reaction to Mueller’s death. His strict approach to the law, and refusal to engage in a PR war, probably produced the best outcome the president could have hoped for. From @davidfrum https://t.co/FLpj4IkU1Z
@iCyclone Fascinating! What jumps out to me is how rare it is for Cat 5 in the Gulf, in particular, originating in the Gulf. Only 3 I think? Clearly takes more than very warm water to build that strength since I think the Gulf gets very warm relative to other regions in this map?
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.
Yes, Fix Bugs Now is the only way I’ve ever worked. Jump on them right away. Troubleshooting the cause is often 95% of the fix. Finish it off. Move on.
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.)
A quite brilliant essay on AI, the law, and the future of the republic.
An upshot: If the US govt can go to any company, demand any contract language, and reserve the right to destroy your company if you have qualms, there is no such thing as private property rights in America.
@Travis_Sawchik@TomLeyden What is Dodger Stadium like in person? It never gets mentioned in these discussions, but for me, it’s iconic and unique on TV. (And Angels stadium, almost as old, is not.)