Digital janitor. Actually a surgeon with git rebase. Frontend/react/typescript. The writer labors so the reader need not.
Ugly part if a nice building
- Tweets 13,237
- Following 2,500
- Followers 812
- Likes 11,446
Bro the gap has ALWAYS been there. You worried about lgbt accessibility and wtf Trump is doing, you're going to be less productive. Honestly anyone sufficiently into politics is less productive that those who are literally always working
Hot take: as AI gets increasingly political, liberals will adopt it more slowly than conservatives. That hesitation will turn into a future productivity gap.
18
@DevinRhode2@mas.to retweeted
“Action produces information. Just keep doing stuff.”
— Brian Armstrong
Reads with Ravi
4
141
980
263,819
This has never been more true. The opportunity cost of endless planning and contemplation just went way up. Agents allow you to just try vastly more stuff, so let them, and you'll learn way more, way faster.
128
465
5,322
250,638
Code was expensive. Big tech has a walled garden. Had?
Bitcoin didn't hit the mainstream, no merchants accepted it. Networks will remain the same, iMessage, Messenger, etc.... but wait... If the Oma ecosystem can sufficiently emulate the real environments apps support (Android) ... Idk how far could we take it? We can access almost everything in a web browser. You can program a selenium/playwright style bot on top that clicks taps and types like a human
From there you have perf to fix
71
@DevinRhode2@mas.to retweeted
one Opus 5.5 prompt, and now I run around a virtual office managing agents to work on github issues and merge conflicts
126
172
3,729
476,904
That's what the other David was just tweeting about few weeks ago @DavidKPiano
I want some tool that turns a codebase into an architectural diagram. As you make changes, the diagram updates and shows diffs some how.
1
1
91
@DevinRhode2@mas.to retweeted
JavaScript has been through this before.
In 2011, Google set out to replace JavaScript with Dart, arguing JavaScript couldn't be fixed by evolving it. Then ES2015 shipped.
It's time to do that again.
13
8
569
45,993
@DevinRhode2@mas.to retweeted
JavaScript was never designed for the server. If that doesn't change soon, JavaScript on the server will be replaced by Rust.
The fix needs to happen in the engine. Sound types. Ahead-of-time compilation. Threads with shared objects.
"I love Rust! Rust is amazing ...if you never, ever, EVER have to look at it yourself." — @dhh
302
162
3,843
899,571
@DevinRhode2@mas.to retweeted
I'm focusing a significant amount of my time trying to build a cure for Kate's endometriosis. It's a gnarly and devastating disease that affects 10% of women. Relative to the suffering it creates, it's underfunded, poorly understood and has largely been ignored.
465
636
14,088
811,397
Lolol 😂
Nobody reads the employee handbook.
I proved it.
Last month I added one sentence on page 73:
“First employee to email HR this sentence gets $1,000.”
Thirty days passed.
Yesterday an analyst finally found it.
I congratulated him and paid the $1,000 immediately.
Then I terminated him.
People don’t randomly read employee handbooks.
They read them when they’re looking for leverage.
$1,000 is a very reasonable price to identify your next lawsuit.
52
piped.video/qsiPh4ZxDTw?si=IlBR…
Huberman eye sleep hack
45
@DevinRhode2@mas.to retweeted
As weird as it is, it works. But the reasons are not cryptic. To fall asleep you have to.
1) lower your heart rate
2) stop thinking about the past and future
3) get into pure sensation
4) forget about your limbs’ positions
108
296
7,309
369,815
@DevinRhode2@mas.to retweeted
Step into the craziest visualization of the fourth dimension you have ever seen
698
5,456
47,472
9,718,114
@ModernSoftwareX I'm working on a greenfield app, doing the UI architecture. We're using TypeScript, TanStack Router, and TanStack Query. We're also using a tool called Kubb.dev. It can generate TanStack Query hooks.
When provided an open API spec, I used this tool on my last team, which I was on for the past year. However, the API specs that the Spring Boot backend would generate were notoriously buggy and didn't match the actual API responses, which we agreed upon. I've had the idea that we should agree on an actual discrete API spec up front, as opposed to maybe a general shape of the payload.
The UI kind of has a workflow where we align on a Figma with business, and then we go to implement that design that we aligned on. That Figma design also tends to tell you about 90% of the details you need for the backend API. The problem is, I'm asking our backend Java devs to change their workflow. Instead of having an idea of the JSON payload they want, and then developing it, and then the UI implementing it, what I want from them is, before implementing it, to try to agree on the open API schema up front. This completely unblocks the UI and allows the UI to define mock data in collaboration with other teams.
Even without mock data, we can complete maybe 80% of the coding that we need just by having TypeScript type defs, which are generated from Kubb based on the API spec. My question for the Modern Software Engineering channel is how should an API specification pipeline work?
2
1
66
