Carter Bryden 🇨🇦

@carterbryden.com

Dad, founder of approximated.app, developer (usually #elixirlang). Friendly and sincere. I mostly post about dev, things I'm working on, and stray thoughts about business/work/entrepreneurship.

Despite how we all might feel about another competing #elixirlang LSP, Dexter is *surprisingly* good. I haven’t had a single problem with it after using it for a few days, which just hasn’t been the case with others. And it’s _fast_. Fast enough that I don’t need to think about it.

I have a theory that a lot of the problems we see with agents are the same problems we’ve always had working with and managing actual devs, too. When we compare agents with people, we tend to imagine some ideal dev in comparison. But even the best devs I’ve known also occasionally do things like:

Approximated.app runs thousands of servers, and this is true. Similarly, each 9 added to uptime is exponentially harder. Downtime allowed by uptime percentage: 90%: 36.5 days/yr 99%: 3.65 days/yr 99.9%: 8.8 hrs/yr 99.99%: 52.6 min/yr 99.999%: 5.26 min/yr 99.9999%: 31.5 sec/yr (!!)

Jason Cohen@asmartbear.com · 5mo ago

If you have 1000 servers, each experiencing a fatal error randomly once every 3 years… you will get random, unpredictable, unstoppable failures every single day. Scale is hard because it makes rare things common.

Picked up a Mac Studio recently because my daily driver Linux desktop hardware was showing its age at about 10 years old (some upgrades along the way). Most impressive to me is that it seems to generate no heat or noise, EVER, despite maxing out every core pretty often with elixir concurrency work.

I have the dumbest trick ever when I can't figure out how to implement something, but it works. I ask "If a person had to manually do this, how would they do it". That's it. So many things feel complicated when I think only in coding terms, but dead simple if some guy named Steve had to do it.

Added upstream load balancing to approximated.app! Now you can: - Set multiple upstreams per custom domain - Set policy (least conns, round robin, etc) - Optional sticky connections - Upstream health checks and rerouting - Configurable over API or dashboard And it'll just... work!

We should 100% steal this idea for #elixirlang Phoenix. Such a simple but obvious in hindsight idea. Automating turning controllers/routes into importable frontend packages would eliminate a lot of boiler plate for frontend heavier teams.

Joe Tannenbaum@joe.codes · last yr.

From the galaxy brain of @tim.macdonald.au, with just a dash of Tannenbaum, presenting Laravel Wayfinder. Automatically generate TS functions for your controllers/named routes so you can call your endpoints directly in your client code. Available now in public beta. github.com/laravel/wayf...

So far I've found pair programming with AI to be a bit like pairing with a junior dev who has an insane breadth of knowledge, not much common sense, and doesn't ask the right questions. Using claude 3.7 with reasoning mode + a 200k context window, it's an intermediate dev who asks half of them.

Sometimes people ask why there's a 'restart cluster' button on Approximated, since the whole idea is that it manages itself. Partly it's just a relic from early days. But also, I like when products let me give them a bit of a kick if I want to. Its *your* cluster, that's why you can restart it.

#elixirlang devs, what are your personal guidelines in liveview for when you make a function component vs a live component? Function component: no state, send events to the parent for handling Live component: maintains it's own separate state, event handlers, etc.

I’m speechless. Watching these arrogant, undisciplined, childish fools yell and threaten a legitimate hero on live TV is so fucked up. I hope the rest of the world sees it too.