Sam Reis retweeted
This kind of feedback makes my day! ♥️
Super cool to see people building their own code forges on top of @enroute_sh.
We’ve also built our own forge for dogfooding Enroute, so it works exactly the way we want. The UI is super clean, and instead of PRs we have a simple breakdown and summary of everything your agent changed.
Fun fact: It runs on a single @flydotio machine and is still the fastest thing out there.
Sam Reis retweeted
Nice comeback from @github after the (re-) launch of @GoEntire this week. Seems like 7k+ pushes/s is how you build Git infra these days.
Go check out @enroute_sh if you want to build on open-source git infra with that kind of performance already today!
Sam Reis retweeted
so many gems and great tips in this talk from @yminsky about how to improve your codebase for agents
• agents thrive on feedback, and types are one of the best kinds
• make illegal states unrepresentable with types, and it enforces global rules across your codebase
• property based tests, fuzzing, and even full-system deterministic simulation testing
• expect tests: just print stuff out and capture it in the test. makes behavior legible. it's very similar to how compilers have fixture tests, it reduces the review surface area
• formal methods used to be very expensive: seL4 is about 8,700 lines of C and took around 25 person-years, with 23 lines of proof for every line of C code, but agents change the roi
youtube.com/watch?v=rUYP4C29…
Sam Reis retweeted
We’re launching incident management in @openstatushq. Built for small teams that live in Slack.
Live on Product Hunt today. 🐱
producthunt.com/products/ope…
Sam Reis retweeted
After 5 years in v0, it's finally happening.. Dagger 1.0 is in beta and we need your help testing it.
If you've tried Dagger before, a lot has changed... We've been cooking.
Announcing Dagger 1.0 beta.
Replace Jenkins and GitHub Actions with CI that matches the speed and scale of coding agents without wasting compute or tokens.
Featuring: test-native CI, dev shells, local and remote execution, official modules, and more.
dagger.io/blog/dagger-10-bet…
Sam Reis retweeted
isn’t it beautiful the competition that ai has enabled?
we have people trying to build more scalable git, postgres, sandboxes… the result of that competition will benefit our entire industry, and this wouldn’t have been possible years ago
Sam Reis retweeted
We are verification engineers now. With the cost of code going down, we have to reassess the trade-offs of technologies that make coding relatively more expensive but increase robustness.
What might have been too much of a hassle in practice in the past, is now worth it.
We've since undertaken the mission to make IDOR bugs much less likely on our platform using proofs enforced by the typesystem.
Introducing gdp-ts: Ghosts of Departed Proofs for TypeScript.
gdp-ts is a library, linter and AI skill for safer API design. Under this contract, sensitive functions require 'proofs' that the caller performed an authorization check.
The typechecker verifies these proofs at compile time, preventing your team and agents from shipping catastrophic security (and other kinds of) bugs.
While these patterns have existed for quite some time, especially in ecosystems like Haskell, ① human code review and ② cognitive and syntactic overhead made these solutions niche.
The situation is now inverted. Agents are writing more code than we can review, and they *thrive* in tight loops with hard constraints that would frustrate us. We see this with the rise of Rust, borrow checker, code aesthetics debate and all.
The README and examples model a real-world Vercel API product constraint: changing the password on a Project requires a proof of a certain role + a certain entitlement. Thanks to Matt Noonan and Ollie Charles for their research in this space.
github.com/rauchg/gdp-ts
Sam Reis retweeted
If you work with Tokio, this is a must read: "Principles for fast Tokio applications" dial9-rs.github.io/blog/prin…
Sam Reis retweeted
✨ Wrote about building and growing Internet services with feature boundaries, data autonomy, cell-based architectures, service dependencies, graceful degradation, unique identifiers, idempotency, SLOs and quotas, and observability. rakyll.medium.com/how-to-pea…
Sam Reis retweeted
We’re brewing something hot 🧙♂️🔥 ..
> “Allow your users, team & 3rd party developers to extend your product’s functionality + integrations in minutes. 🚀”
Let me know if this sounds interesting and I’ll get you on our “secret” early access list 😎 First come first serve. 🍦🍫🍬
Sam Reis retweeted
I had so much fun giving my talk about apollo-rs and its compiler! Thank you so much for having me #rustconf.
(It's been a while since I've done this, but!!!) here are my slides ✨
slides.com/lrlna/writing_a_g…
Sam Reis retweeted
Oh. My. God.
CPU time:
To start 5000 threads each with a signalfd: 60s
To deliver a signal to every thread simultaneously: 140s(!!)
To start 5000 threads using epoll_pwait() for signal delivery: 4s
To deliver signals to all of them: 100ms.
Sam Reis retweeted
"Use One Big Server" (specbranch.com/posts/one-big…) is trending, and while it's mostly reasonable it misses a couple of big things (or dismisses them). But there's one misconception here that I wanted to talk about: peak load.
Sam Reis retweeted
I'm starting to write about SQLite internals which are both fascinating and surprisingly accessible. This first post is on the file format, pages, & b-trees.
I've got plans for future posts but I'd love to hear what folks would like to know more about! fly.io/blog/sqlite-internals…
Sam Reis retweeted
This book on PostgreSQL internals looks like a great resource on isolation levels, concurrency control, and various storage engine topics postgrespro.com/community/bo…
Sam Reis retweeted
"Dependency Injection frameworks are built by very clever groups of very clever engineers in very clever ways to very cleverly avoid simply passing parameters to functions"
Sam Reis retweeted
There’s a whole talk on this very topic, that made it to my best of 2021 list. It was definitely one of those rare times my mind totally went 🤯🤯🤯
See my synopsis, and do check out the talk!
youtube.com/watch?v=A-7j0QlG…
Sam Reis retweeted
"Newer, low-pause GCs are significantly more expensive than older GCs."
Yet more evidence that GCs need to focus on throughput and not just latency. Don't just quote pause times!
I'm very pleased to announce another interesting pre-print.
This work is lead by @caizixian, in collaboration with Mike Bond and @martin_maas.
We develop a new methodology for measuring the cost of GC, and evaluate JDK17 collectors.
The results are 😬
tinyurl.com/3k244r5p
Sam Reis retweeted
🗣️ "Creating read-optimized views is essential for scaling systems. However, transitioning to a stable, denormalized view without causing system downtime is not at all trivial"
Insightful post by David Vaks of @WixEng 👍.
wix.engineering/post/5-chall…