shipping paypal credit and other things

Raleigh, NC
Joined January 2012
Ryan Magoon retweeted
Mocking your code gives you two products - a well tested app for your tests - an untested app for your users network interception lets you test the actual prod code against fixture responses, which is way more reliable
Replying to @kettanaito
What it actually means is that MSW allows to have two things simultaneously: 1. Your requests happen for real. 2. Your can intercept and handle them. Traditionally, API mocking meant a compromise in reality in favor of control. MSW eliminated that compromise at its root.
8
1
1
76
5,317
This thing fuckin rules
3
11
1,414
Ryan Magoon retweeted
i'm convinced burnout has nothing to do with 'working too hard' and everything to do with betraying yourself for an extended period of time
Burnout happens when you work too hard with not enough meaning. "He who has a why to live for can bear almost any how" — Nietzsche
91
1,674
97
15,448
362,679
Ryan Magoon retweeted
Colocation is the big one If you’re using React (or similar) you ALREADY have a way to share and reuse styles Making a Card component and giving it a .card class is like mixing React and Handlebars in the same app
CSS Modules work well for smaller MPAs, but as an app starts growing in size, atomic CSS in general, and StyleX in particular, starts to make more sense. 🧵
1
2
1
58
7,701
Ryan Magoon retweeted
Replying to @rawkode
i’ve yet to see compelling evidence that not reading the code works. i’d be happy to be proven wrong.
30
44
16
542
97,398
he asked for nude tayne
wow. i just got a fallback chain all the way from fable 5 -> opus 5 -> opus 4.8 -> fucking sonnet 4.6. crazy stuff
4
554
Ryan Magoon retweeted
agree - a good software emerges through iteration, stacking small, well-tested automations/loops and triggers over time. If you set out to "build a factory" you are gonna struggle. The only "factory" wisdom you should be following is: Figure out your bottleneck, automate it, then find the next bottleneck. Thanks Eli Goldratt
Very hot take: you should not be building a software factory
35
43
9
653
49,934
Ryan Magoon retweeted
the self-own that's happening to the ai industry right now is a great reminder of why human brains are just as important as ever all the compute in the world and they couldn't foresee this basic situation ai not gonna save you from having to be competent
73
89
7
2,034
117,642
Ryan Magoon retweeted
my single biggest piece of advice when choosing OSS tech is this: make sure you and the authors have aligned incentives e.g. if you're a SaaS platform looking at a web framework built by a consultancy that sells courses, consider you have different outcomes in mind
A short story about deferring tech choices to thought leaders: Early days at Disqus (~2010-2012), we made several frontend choices based largely on what thought leaders were promoting at the time. One example: there was a big movement toward "micro-frameworks." Instead of larger, well-tested libraries like jQuery, you'd stitch together tiny interoperable micro libraries (Ender.js was one). Disqus was an embeddable JavaScript app, so file size mattered. It fit our use case, so we went with it. Then it went live, and we were serving millions of users. The reality of those choices became clear. Micro libraries meant that instead of one good semi-bloated library, you ran 6-7 smaller, less-tested, crappier ones. We burned a ton of cycles fixing bugs and covering corner cases when we could've been shipping product. We made a few choices like this. At conferences, I'd track down those same thought leaders and ask for advice. "I'm hitting problem X, Y, Z. How did you solve this?" That's when I learned my lesson: they rarely had answers, because they'd never reached our scale. Their energy went into promoting new stuff, not running it. You should know this has never stopped. It's happening right now with AI. It'll happen again with whatever comes next. Do your own homework. Test a lot. Don't just go with what somebody tells you.
2
3
54
5,066
Ryan Magoon retweeted
This topic is so dumb and I’m sorry to participate in it. Hire competent people. Let go of underperformers. You will be left with people who thrive in your environment. Repeat.
Why Remote Work is White Collar Fraud. "I have a three-year-old and a five-year-old. The idea that I could do any work at my house is like a total fantasy. The kids come home at 3pm, your work day needs to keep going. I'm highly against it." @typesfast
19
8
352
19,537
Ryan Magoon retweeted
Replying to @file_mutex
people who dont read the code are not serious people and it takes a serious person to ship production software
36
94
29
958
125,722
Ryan Magoon retweeted
Instead of waiting for a new model to fix your problems Why not just fix your problems
75
40
8
745
41,901
Ryan Magoon retweeted
A lot of people see this and go “oh distribution is the problem.” That presumes that these apps all don’t suck. Who is gonna tell ‘em.
Massive output uptick due to agentic AI. Complete flat adoption.
22
8
3
140
21,901
Ryan Magoon retweeted
how to be good at your job - realize this one thing is actually made up of two separate things - realize instead of solving the direct problem you can solve a broader problem - instead of implementing thing, implement other thing that makes it easier to implement thing
130
230
32
3,952
125,781
Ryan Magoon retweeted
this is mostly a guardrails problem: - teams can't keep up with code review - existing testing is mostly "fake" - the good ICs care, most don't give a shit. tokens amplify this problem
🦔Uber's COO Andrew Macdonald said on Saturday that the company is having a harder time justifying its AI spend. After CTO Praveen Neppalli Naga went viral in April for admitting Uber burned through its 2026 Claude Code budget in four months, senior engineering leaders concluded higher token usage was not translating into proportionally more useful product. Macdonald said the link between AI consumption and shipped features is "not there yet." CEO Dara Khosrowshahi confirmed on the earnings call that Uber is slowing hiring to fund its AI spend. Duolingo also walked back its decision to include AI usage in performance reviews last month. My Take Uber is the first major enterprise where the C-suite has publicly admitted, on the record, that the AI productivity story is not closing for them. That matters because Uber is not a skeptic. The company went all-in on AI tooling, set internal targets, and burned through its annual research and development budget in four months trying to make it work. The conclusion from the people running the experiment is that tokens consumed and value shipped are not the same number, and management is finally noticing. Duolingo's reversal lands in the same week for a reason. CEO Luis von Ahn said employees were asking whether they needed to use AI just to use AI, which is Goodhart's Law showing up in a performance review system. When usage becomes the metric, employees optimize for usage, not output. Microsoft canceled internal Claude Code licenses, Google AI Pro stripped credits from paid subscribers, and now Uber is admitting the ROI does not close at scale. The narrative has shifted in the last 30 days from "AI productivity is here" to "AI productivity is harder to measure than we thought." The companies pushing tokenmaxxing internally are now the same companies signaling cost pressure externally. The IPO calendar for OpenAI and Anthropic is going to get a lot more complicated if the largest enterprise customers keep saying this out loud. Hedgie🤗
31
7
3
230
48,726
Ryan Magoon retweeted
the paradox of ai adoption at tech companies is that individuals are getting way more done but teams as a whole are not shipping products any faster. in large part this is because the things that were previously low roi / not worth doing are getting automated, but the core business is still too complex to yeet without following the pdlc.
38
28
6
505
31,197