Hiring a sysadmin at @synteq (cloud + GPU infrastructure). Greater Chicago or Austin area.
Requirements:
- Deploy HVs, remote and on-site
- Have opinions on cable management
- 10 years of experience with Claude Code
DM me or @benchaupt. Tag someone you’d trust with prod.
Extremely highly export controlled item. Have needed sign offs from C-suite of DC facilities, our company, and in some cases in-person inspection of site (reputable, massive T3 datacenter providers doesn’t matter). Specifically to avoid b300 in garage scenarios.
Eventually? It’ll happen.
@clemissima@Uber@Waymo robotaxi, waymo, hell i've even just started renting cars or changing flights to when friends and family can grab me. uber is just such a thoroughly rotten experience, i will pay more to avoid it at this point.
@sur4js This is a serious problem atm on both sides. Just a by-product of insane demand, opportunity, lack of qualified individuals everywhere.
Few that are qualified don’t have enough minutes in the day.
If you are;
- chronically online
- US based
We’re hiring for growth
Influencer partnerships, performance marketing, X, and DevRel.
DM me with why’d you be a good fit
I’ve now gotten over 250 pull requests from developers trying to write the fastest possible API for a $12/month server (1vCPU 2G RAM).
By popular demand, I built an official leaderboard for it: https://t.co/97WZjJ6tyj
Every submission runs is tested via the following method:
→ Built from source on the exact same 1 vCPU box
→ Has to pass the full test suite before any load
→ Ramped up with realistic users until it breaks
→ Scored on the most users it holds for 5 minutes (p95 under 500 ms, p99 under 1 s, under 1% errors)
The current top 3 on the $12 server:
→ Rust (io_uring): 264,000 users
→ C++ (io_uring + EASTL): 219,000 users
→ Hand-written x86-64 assembly: 171,000 users
The range is pretty nuts. The same 1 vCPU box goes from 3,500 users (Bash) all the way to 264,000 (Rust), across 25 languages so far.
The community involvement on this has been incredible. People have written their own event loops, used io_uring directly, and pushed languages I never expected to see on a server leaderboard. I’m really glad so many of you jumped in.
Every implementation is open source, so you can read exactly how each one works, see how your favorite language stacks up, and send in your own. New submissions get benchmarked and added to the leaderboard automatically.
Hiring a sysadmin at @synteq (cloud + GPU infrastructure). Greater Chicago or Austin area.
Requirements:
- Deploy HVs, remote and on-site
- Have opinions on cable management
- 10 years of experience with Claude Code
DM me or @benchaupt. Tag someone you’d trust with prod.
I told my QA engineer the checkout failure wasn’t a bug.
He stared at me.
I said, “It’s a known limitation of the current architecture.”
Silence.
Then: “What does that mean?”
I looked at the open laptop full of red Sentry alerts.
It means we have a technical debt registry.
It’s a Notion page with 83 unchecked boxes, color-coded by vibes.
Someone made it during a hack week in 2023.
Nobody has opened it since.
Including me.
I told them, “We’re optimizing for long-term velocity, not short-term correctness.”
They asked how I decide which failures are worth fixing.
I locked eyes with them across the table and said, “You’ll just know.”
They looked puzzled.
I, however, understood.
This is how modern engineering works.
There is no severity matrix.
There is only pattern recognition.
And the pattern is usually something a Staff Engineer said on a podcast while holding a Yeti mug.
Two sprints later another report came in.
Clear reproduction steps.
Video of the failure.
Impacted revenue numbers attached.
I asked about the root cause.
They said, “Race condition in the payment service under load.”
I knew right away it wasn’t the right kind of problem.
Not ambitious enough.
I told them we were only interested in failures that reveal deep systemic truth about distributed systems at planetary scale.
They asked how many of those we’d actually shipped fixes for this year.
I gave a small, knowing smile.
“We’re compounding.”
They asked what that meant.
I said, “If you have to ask, you’re not ready.”
That night I posted on LinkedIn.
“Great teams don’t chase green builds. They design systems that make entire classes of bugs impossible.”
11,400 impressions.
Three VCs slid into my DMs.
All of them wanted to talk about “agentic reliability layers.”
I marked one of the new tickets as “Won’t Fix.”
I still don’t fully understand what the feature does.
But the PR description said “eventually consistent multi-region consensus” five times.
And something about it felt exceptional.
@AJButton2 Long time ago I was all-in Airbnb, now Ambassador Elite at Marriott (and I don't even think they're that good overall). I just don't want to deal with bullshit, I'm somewhere away from home for a reason and that reason doesn't include lying hosts or doing their laundry.
airbnb was nice early on to get a unique rental in an unusual place. it's now flooded with misrepresented properties and more rules than sunday school. im just trying to travel for work that isn't fun, so ill stick with marriott where the experience is at least identical and predictable and they at least pretend to be happy im there.