Ryan Rodemoyer

In hindsight, I've created somewhat of a unique way of coding Starting new is hard. Few people have the entire ecosystem of code loaded in their mind. Progress is excruciatingly slow at the beginning * connect the database * build repos * setup DI * database migrations * HttpClient's * configuration files * Docker files list is endless API's are frequently shifting and changing We know how to code but how these things all connect together takes time to figure out Losing hours to dumb bugs is a MASSIVE DRAIN My approach is obvious, but: * no one talks about it * no one recommends it * no one even realizes it exists It's not a hack It's not a shortcut But here it is I write a lot of code I figure out the little ways to do stuff I create a TON of examples 1-2 times per year I code a big project The big projects are based on the previous projects so I always get a head start on the next thing In the big projects, much of the code comes from my samples So that's the secret Write more code that you think is reasonable Make examples out of it Use them later on

not sure why I would buy a 5090 for $6000 (used) when instead just get Mac Studio or premium tier MacBook Pro which will at a minimum double the GPU memory to at least 96GB

>"therefore are responsible for continual optimization and maximal automation (and sharing those enhancements with your colleagues - success at Proton is a team sport)" Literal communism

instagram.com/reel/DfDWIfkSn… I guess I’m a local because the rest of the world isn’t sure if this is English

Feels like there’s a version of Stack Overflow that could exist on X. Humans are no less interested in communicating now than they were in the 2010’s The Blue Sky effect killed SO more than AI. Read the accounts for yourself - a hostile and awful moderator base killed the good will of contributors. What works against the idea is that what we need today … moves fast. There’s now no waiting for information, it’s as instant as you want it.

I challenge you to name a group of people more difficult to work with than DBAs

My daughter and two friends want to get an off campus apartment They found a house. $2400/month plus utilities Seems the lease is guaranteed as a collective, each student + co-signing parent. Feels weird… am I overthinking it?

How is this even possible? Is this sustainable? Two years ago the 3090 on FB Marketplace was $700.

Kinda weird to be all privacy focused AI local models just to rip it through Slack, Telegram, etc

What’s the recommended way to ship an agent skill with a Nuget package?

Good advice. Can be a pain to get it working on a chiseled image but no excuse in the agent era.

cyber security in 2027 ... bearish or bullish? make your best case

We are learning in real time tech security was a product of people not trying hard enough

Throwback to the best NFL draft photo of all time

Jekyll still kicking? Who’s left using it?

I ported Basecamp's Campfire to C# as a drop-in replacement for the original Rails version. Then we paired agents with a profiler and what we found 33x'ing the Rails performance (and leading 3 benchmark categories over Rust and C) might surprise you. Drop-in means you point it at your Rails Campfire's database and storage, reuse your SECRET_KEY_BASE, and everything works exactly the same. Same schema, same cookies, same HTML. Every speedup required a real-life performance tuning loop to unlock the next 10%. The benchmark is Basecamp's shared harness, run on one Google Cloud VM: 4 dedicated cores per app, 16 clients, every port measured twice from scratch. 196 million responses were checked against the route contracts before they counted. 0 invalid. C# vs Rails, req/s: Messages page: 2,183 → 71,154 Sidebar: 2,407 → 78,359 Search: 2,491 → 76,385 Room page: 2,388 → 37,115 Post a message: 265 → 2,598 Rails runs behind its Thruster proxy as shipped. C#, Rust, Go and C serve HTTP themselves. The loop: an agent attaches the dotnet-diagnostics MCP to the container under load, finds the single biggest cost it can explain, makes one change, and proves it on the harness. Then a fresh chat starts the next round. Most of the big wins changed a design, not a hot loop. Why borrow when you can steal? Designs we took from the other ports: • C: check for database changes outside the cache lock • Rust: checkpoint when WAL pages pile up, not every commit (posting 50 → 1,449/s) • Rust, Go, C: serve HTTP with no proxy hop (~3× on reads) The profiler found the rest: • read SQLite's 48-byte WAL-index header instead of querying for changes: +14–24% • reuse HMAC and AES-GCM contexts per thread instead of .NET's one-shot calls on OpenSSL: +10–14% • stop writing 2 log lines per request: +15–20% A lot of the speed came from @jlchavezGT, who ran the same profiling loop on his own and sent a stack of PRs: cookie and cache-key code without throwaway strings (51 KB → 29 KB allocated per request, about +10%) and an avatar cache. Thank you, Jose. But "C# is faster" would be the wrong takeaway. C# leads 3 workloads here because of design changes the profiler found, in the same language that started at 2–3× Rails. C leads the room page and Rust and Go post faster. Reading C's source, its lead is design too. The fast ports are all within about 3× of each other, and the order flips from route to route. What moved C# up was finding where the time went and changing the design, one round at a time. Any team can run that loop. I wrote it all up as an 11-part .NET series: learninglinqpad.com/blog/202… Try it on your laptop, then open localhost:8080: docker run -p 8080:80 -e SECRET_KEY_BASE=$(openssl rand -hex 64) -e DISABLE_SSL=true ghcr.io/ryanrodemoyer/once-c… Code, harness and every raw result, including the other ports' numbers: github.com/ryanrodemoyer/onc… Thanks to Basecamp for Campfire and the shared harness, and to everyone who built the other ports. C# got where it did because of what they figured out first.