
Matt Ramos
@mattramostech
Problem Solver | Staff Software Engineer | Expert in Distributed Systems | Go, Rust, Swift | John 3:16
I've been off X and social media for a while, but I'm back to share knowledge and dive deeper into topics I love like distributed systems and building things from scratch. Excited to learn, create, and help others along the way!
Interesting!
🎯🎯
🔥 The discipline of coding with AI Agents. "There is a failure mode where you outsource the thinking and not the typing. It should be the opposite." - @thorstenball The quality of the software you create with coding agents is a function of the cognitive effort you put in.
This is very important! Unfortunately, not every workplace recognizes this, and to be honest, most companies have a culture that incentivizes this saturation of meetings as a signal of showing work rather than doing real, useful work (which takes time and focus)
When I politely decline scheduling a "quick call", it's not because I don't literally have the time — there's always room for 15 minutes here or half an hour there! — it's that I can't afford to spare the attention.
Aspas is the GOAT and the MVP of this tournament. No one has come close to his performance so far.

Great article! "AI doesn’t own the code. I still review every line, shape the architecture, and carry the responsibility for how it runs in production"
“Is 90% of code going to be written by AI? I don’t know. What I do know is, that for me, on this project, the answer is already yes.” lucumr.pocoo.org/2025/9/29/90-p…
Triste, mas foi jogão. Aspas mais uma vez provou ser o GOAT. O diff dele pro Mada foi gigante.
I really oscillate between thinking Rust is complex for other people to learn and build things with, or that Rust is easy and it's crazy how many devs struggle so much with it. When I'm building something in Rust, I never really encounter any difficulties.
This meme would be perfect with Zig instead of OCaml
an idiot admires complexity, a genius admires simplicity

About front-end: while I enjoy building mobile apps, I can't deny the fact that I still have some content in the browser. The thing is, I don't like React. I use Svelte a lot, but it hasn't brought me much joy while using it. I'm thinking about trying Vue.js/Solid this time
I have the same sentiment. The time I spend on problem-solving and designing solutions has increased a lot, and honestly, that's my favorite part of coding.
It takes some getting used to, but once you get into the swing of agentic coding, there is no activity more fun. Getting up early, staying up late, I fee like a kid again.
LOL at the people who claim "models are all that matter" and prompts/tools/scaffolding do not. Simple prompt changes make a massive impact on agent performance. 20% more accurate and 25% faster.

One of the best blogs I ever read. I can't think of how many times I needed to pretend at work that architects talking clean architecture nonsense, like the database is a detail you can swap between SQL and NoSQL, and incredible over-engineered (terrible) solutions wasn't crazy.
You asked for longer rants, so here are longer rants! After almost 10 years I'm back to blogging. Thanks for the encouragement. Link below in the thread 🔻

imo the bottleneck for using LLMs today is “how do I give it the right context & feedback loop to do this well?” and not “can it do this?”
The Go type system is fine. The issue is that some features, like type aliases, are not widely used, and functions as first-class citizens, though supported, are rarely utilized. For me, Go strikes one of the best balances among back-end languages.
The best place to handle errors is always close to the errors, because that is where code knows the most about what is happening right now. Good that it’s not your code, but every time I see someone complaining about lack of exceptions in go, the code looks exactly like this.…
Spending complexity where it is valuable is a great approach, and one of the biggest strengths of Go.
Yes, and these things are all more complicated, induce surprising bugs sometimes, and have substantial performance impacts. Why would you do that for such simple code? Spend complexity on hard problems, not easy ones. Also: the error checking would not be repetitive if you…
United States الاتجاهات
- 1. Good Sunday 42.9K posts
- 2. Discussing Web3 N/A
- 3. Auburn 46.7K posts
- 4. At GiveRep N/A
- 5. MACROHARD 7,203 posts
- 6. Brewers 66.4K posts
- 7. Gilligan's Island 5,057 posts
- 8. Wordle 1,576 X N/A
- 9. #SEVENTEEN_NEW_IN_TACOMA 37.4K posts
- 10. Georgia 68.3K posts
- 11. #MakeOffer 19.8K posts
- 12. Kirby 24.5K posts
- 13. #SVT_TOUR_NEW_ 29.6K posts
- 14. #HawaiiFB N/A
- 15. #BYUFOOTBALL 1,027 posts
- 16. mingyu 106K posts
- 17. Utah 25.4K posts
- 18. QUICK TRADE 2,360 posts
- 19. Boots 51.2K posts
- 20. FDV 5min 2,278 posts
Something went wrong.
Something went wrong.