Taylor Lindores-Reeves (@codertlr) header
Taylor Lindores-Reeves (@codertlr) profile picture

👨‍💻 Founder https://teapawt.net/t.co/Q1SQyyEIJ8 🎬 https://teapawt.net/t.co/aZiq5gJUiw 👾 https://teapawt.net/t.co/GdyB9sSVDb

Book a call →
Joined August 2021
Replying to @teslaeurope
When FSD in UK 🇬🇧
2
2
45
When's Google going to release Gemini 3.5 Pro?
323
Replying to @bcherny @trq212
This is a bit simplified - would be great to see detailed implementation docs for #3 and #4 - minimax had a really good blog with diagrams on agentic systems, but again, no implementation details
169
Replying to @LiuLawrence45
Is it actually unlimited?
13
Looking forward to #LondonTechWeek #LTW26 Are you attending? My DMs are open!
1
27
Search "best API documentation tool" and you'll get the same names every time. We tested them. Then picked one that never shows up. The project: a developer platform built inside a regulated banking environment. The docs couldn't just look good. They had to be: → Self-hosted → Self-serve → Embedded directly inside the app we were building → Flexible enough to pull documentation from multiple sources @Redocly, @scalar, @mintlify, all genuinely good tools. But "good in general" isn't the same as "right for this." Each came with trade-offs on hosting, customisation, or how the docs were managed. The kind you don't get to make when you're building for a bank. So we kept testing. And landed on a name that never autocompletes: Fumadocs, FOSS created by @fuma_nama It gave us full customisation, clean self-hosting, and the flexibility to bring documentation into the app on the client's terms, not the tool's. The lesson isn't "use Fumadocs." It's that the most popular tool and the right tool are rarely the same thing. Test against your real constraints, not the internet's defaults. That's where the good engineering decisions actually happen.
2
4
490