Ryan Monahan
47 posts

Ryan Monahan
@ryanaldo34
I gambled my mortgage on LLM tokens for my startup and lost big.
Minneapolis, MN Katılım Mart 2018
169 Takip Edilen32 Takipçiler


@ThePrimeagen I heard the NPM registry is enriching uranium to build a Nuclear Weapon
English
Ryan Monahan retweetledi

@ctatedev The company that has their web framework hacked every other day with RCE vulnerabilities has now made their own systems language! What could go wrong!
English
Ryan Monahan retweetledi

fully clauded 1 million line PR merged directly into main, what could possibly go wrong
Mehul Mohan@mehulmpt
First in my bloodline to see 1 million line change PR getting merged (Bun's master branch is now rust, it's official)
English

@thdxr And it’ll give you the same quality of output that these freaks with 1000+ line AGENTS.md files get 😂
English

HR is now “shipping to prod”. 2026 is worse than you imagine
Ryan Carson@ryancarson
GitLab announced a layoff today. Please take this seriously. There will be many, many more. Your assignment is clear: Get skilled with agents and practice shipping to prod. It doesn't matter if you're HR, eng, infra, customer success, admin, ops, sales, whatever. As a Founder/CEO, I can tell you that I won't be hiring any employees who aren't really skilled with agents and able to ship to prod. I'm not alone in this. There is no 'engineering' org in the future.
English

@somewhatdaft @WarrenInTheBuff Do you think this statement means I like Rust? 💀
English

@ryanaldo34 @WarrenInTheBuff we need a way of talking about programming languages that doesnt attract the rust cultists.
English

Ryan Monahan retweetledi

The hidden cost of "enterprise" .NET architecture:
Debugging hell.
I've spent 13+ years in .NET codebases, and I keep seeing the same pattern:
Teams add layers upon layers, to solve the problems they don't have.
IUserService calls IUserRepository.
IUserRepository wraps IUserDataAccess.
IUserDataAccess calls IUserQueryBuilder.
IUserQueryBuilder finally hits the database.
I've seen a lot of classes having one-line methods whose sole purpose was to call the next layer and that's it.
But to change one validation rule, you step through 5 layers.
To fix a bug, you open 7 files.
The justification is always the same:
"What if we need to swap out Entity Framework?"
"What if we switch databases?"
"What if we need multiple implementations?"
What if this, what if that.
The reality:
Those "what ifs" don't come to life in 99% of cases.
I haven't worked on a project where we had to swap the ORM.
But I've seen dozens of developers waste hours navigating through abstraction mazes.
This happens with both new and experienced developers.
New developers asking on Slack all the time:
"Where to put this new piece of code?"
But senior developers are too busy to answer that message. Why? Because they are debugging through the code that has more layers than a wedding cake.
The end result?
You spend more time navigating than building.
Good abstractions hide complexity.
Bad abstractions ARE the complexity.
And most enterprise .NET apps?
Way too much of the second kind.
English

Erm well akshually, if you aren’t doing Opus 4.7 for the frontend with Codex and 5.5 doing the backend, with OpenCode and DeepSeek Flash V4 auditing the code with GStack installed, your Claw marketing on X running on your 10 Mac minis that aren’t even performing any compute because it uses cloud LLMs, and Haiku 4.5 doing a technical write up…. YOU’RE BEHIND!
English

@badlogicgames It can’t resist the urge to stack as many method calls as possible. We need these 1-3 line “helpers”! Clean code!
English


















