I mostly post about dev, things I'm working on, and stray thoughts about business/work/entrepreneurship.
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.
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.
👇👇
www.kickstarter.com/projects/pee...
Today I use components a lot, and like them, but I still think nesting LVs have more use cases than people realize.
#ElixirLang #ElixirPhoenix #phoenix #reading-list
Today I use components a lot, and like them, but I still think nesting LVs have more use cases than people realize.
#ElixirLang
#ElixirLang
pca.st/episode/3f3a...
pca.st/episode/3f3a...
“We literally cloned an N billion-dollar company in 20 minutes with {vibe coding tool}. This changes the game forever.”
No, you didn’t “clone” a billion-dollar business. You created a landing page similar to it. That’s all.
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.
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.
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!
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!
Automating turning controllers/routes into importable frontend packages would eliminate a lot of boiler plate for frontend heavier teams.
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...
Automating turning controllers/routes into importable frontend packages would eliminate a lot of boiler plate for frontend heavier teams.
Using claude 3.7 with reasoning mode + a 200k context window, it's an intermediate dev who asks half of them.
Using claude 3.7 with reasoning mode + a 200k context window, it's an intermediate dev who asks half of them.
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.
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.
A while ago I wrote a developer guide with a companion example repo to help:
approximated.app/guides/larav...
A while ago I wrote a developer guide with a companion example repo to help:
approximated.app/guides/larav...
Function component: no state, send events to the parent for handling
Live component: maintains it's own separate state, event handlers, etc.
Function component: no state, send events to the parent for handling
Live component: maintains it's own separate state, event handlers, etc.
Listening to your podcast and you guys talking about reflections and glare on your glasses. Try putting some polarized lenses or film in front of your cameras, it completely eliminates screen light.
Ex) a.co/d/43evQwM
Listening to your podcast and you guys talking about reflections and glare on your glasses. Try putting some polarized lenses or film in front of your cameras, it completely eliminates screen light.
Ex) a.co/d/43evQwM
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.
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.
approximated.app/self-hosted
You can use the same cloud API endpoints and dashboard, but run traffic and SSL certs through your own infra instead of ours. Great for compliance and we'll set it up for free.
approximated.app/self-hosted
You can use the same cloud API endpoints and dashboard, but run traffic and SSL certs through your own infra instead of ours. Great for compliance and we'll set it up for free.
Any B2B SaaS add-ons or ideas you would like to exist in the world?
I’ll mention you in the video if we use one you suggest 😉
Any B2B SaaS add-ons or ideas you would like to exist in the world?
I’ll mention you in the video if we use one you suggest 😉
If you ever want to allow users to connect their own custom domains to your app, avoid JS that gets a tenant ID/slug/etc from the address bar (client side).
Super common with frontend stacks, and it can make life difficult when you want to replace that with a custom domain.
If you ever want to allow users to connect their own custom domains to your app, avoid JS that gets a tenant ID/slug/etc from the address bar (client side).
Super common with frontend stacks, and it can make life difficult when you want to replace that with a custom domain.