jvidalv
Claude/Codex app all the way baby. What a crazy world.
Estimated 33 trillion trees. I think they will do fine with 250k less trees.
All my apps are on Railway, deployments has been down since yesterday morning (24 hours), feels nuts that they have waited until 2AM to say this.
This is my pack: https://i.imgur.com/hnoioNy.jpeg
You never know what awaits behind the corner.
Heavy user of WebStorm and Datagrip since at least 2019.
But I can’t shake the feeling that discussing this stuff is indeed void on the AI era. I considered my self a JS/TS/React expert dev, derivate, state duplication, url as a source of truth…
All of these points feel void now, I have not checked/cared how my React code looks like in months now. I only care about more high level stuff like schema definition and overall wiring.
Now it’s a prompt away on some terminal done by any random dud.
And I dont mention the velocity of iteration or that they will be even better in 1 year.
At least in Spain this is exactly the case, and is really scary how much people falls for it.
My advice: the best claude is the raw claude, with some custom tailored skills. That’s it, no plugins.
https://discord.com/channels/876711213126520882/148058965798...
Leaks memory left and right. And the core team seems unable to fix it.
https://berrus.app/ (game) https://josepvidal.dev/ (my site) https://fescims.com/ (mountaineering community)
Even my mobile app for the mountaineering community is tailwind (Yes, there is Tailwind for ReactNative): https://apps.apple.com/us/app/cims-mountain-challenges/id674...
My point being, quick AI slop landing pages and products will share the same vibes, but at the end Tailwind is just a collection of css classnames, allowing you to build and create as much as cool and unique pages as with plain css if you put the effort.
It's actually why I stopped at Railway level instead of going full VPS.
I wouldn't switch from Vercel just to save X% per month, because the real cost was all the extra time to build and maintain the infrastructure myself. The savings never justified the hours.
With agents that math changes. The build and maintenance work moves onto the agent, so the savings threshold where switching makes sense drops a lot.
On top of that there are other goodies. Vercel is serverless, so you can't co-locate the API with the DB, which means extra latency and yet another bill (Supabase?). That's one more thing you can now own for basically no effort.
I only use Google to search for reddit posts.
The rest is ChatGPT or Claude.
I'm lucky to be part of different codebases, +200 engineers codebase in a 10 years old company and code, +5 engineers on fresh code. My personal projects, that are beyond POC's, real users, hundreds of commits.
The LLM agent sweet spot is the last one, they are perfect, as I can contain most of the knowledge in my brain of how it works in/out. Speed is insane as a solo developer.
Then the 5 engineers codebase, is also really good, but here you already start to see the problems, thanks to agents you don't even need to care how it works, I have been working on it for +6 months, it uses TRPC and I don't even know (I don't care) how TRPC works. You feel that no one in the team really knows how stuff works at 100% (fresh codebase, we have build this ourselves!!).
Then there is the old codebase with +200 engineers, this is the worst of all of them, you described it perfectly, a bottomless pit of tech debt. This codebase before agents was an old non-typescript one, it was not perfect, but you could build a mental model and understand it perfectly after a few weeks working on it. Now, is a hot-mess of code duplication and the quality is degrading faster and faster as the code gets worse and the Claude Code adoption increases within the engineering team.
Not sure what will be the outcome of all this, but I wouldn't be surprised if some company wakes up in 2027 with a codebase that maintenance and development has increased by x100 fold thanks to Agents.
A normal engineer may be running a couple of sessions with every session spawning sub agents left and right.
80 persons or even 10 having this workflow on this setup doesn't work, and this is the standard engineer workflow today.
Don't ask me why, thanks for the correction
My father is a farmer and does a siesta every day of the year. He comes back at home of working in the farm every day around 1PM, then we have lunch together and he goes on to take a nap (siesta).
In winter they are shorter, 30 minutes, as the day is short.
In summer, they can go over 1 hour easily, as the day is longer and is hot between 2 and 5 PM.
Of course, my father is it's own boss and old school farmer, young farmers don't do that, and try to work on an schedule.
And is the same about school, when I was a kid no one was driving me to the school or taking me back, I walked there on my own, went home at mid day for lunch, played some football after it, and then went back to school for a couple of hours at 3PM.
I feel we are slowly drifting away from natural times and actions to forced on schedule behaviour to fit within the cogs of a late-stage capitalism productive machine.
Trying to run it as a replacement for node in persistent backend/api scenarios is just plain broken.
RSS grows unbounded under Bun: https://discord.com/channels/876711213126520882/148058965798...
There is too much and there are too many, and some of their takes don’t fly if you use Claude daily.