Carlos Precioso
LightNews LightNews
banner
precioso.design
Carlos Precioso
@precioso.design
27 followers 28 following 47 posts
Framework Engineer @wasp.sh
he/him 🌈
Posts Replies Media Videos
precioso.design
that feeling when you merge a PR that closes a bunch of longstanding issues in one go
Crude drawing of a man touching his own face, basking in relief and contentedness
October 29, 2025 at 8:27 AM
precioso.design
aye aye my cap'n
Screenshot of a video call with all the team members having a composited boat captain hat on top of their heads.
September 16, 2025 at 2:18 PM
precioso.design
We've been looking at other frameworks at @wasp.sh to look at what they do well. Would y'all say this is a fair assessment of @laravel.com?
A slide with the text: Q: Why is Laravel nice? All of these are nice, but normal enough in any web framework [footnote] A: Laravel is not the core library, but the **ecosystem** A slide with the text: The Laravel ecosystem is _complete_, _curated_, and _cohesive_. The Laravel ecosystem is not _huge_, _strongly coupled_, or _permeable_.
September 1, 2025 at 12:22 PM
precioso.design
Did a small rant today on the @wasp.sh Discord wrt. to what impact are the AI assistants and agents are actually having in the software industry right now.
I have two main opinions here: It seems AI usage shifts the bulk of dev time from writing code to reviewing it. For one-man projects this is fine because you sometimes don't feel the need to review your code, or spend the same amount of time working on it, but with something "working" way earlier, and more iteration (incidentally, this is how designing a solution always should be, iteratively). For bigger companies with established processes, you're involving more people earlier in the process. So maybe the individual gains in dev time are offset by the collective losses in review time. (This is basically the same effect a Jr. Dev has in a team, but without the ROI of them becoming a Sr. Dev sometime in the future.) IMO big gains of productivity from AI come from the LLMs bridging or bypassing tech debt. It says so in the article you linked it: "You probably wouldn't even know where to go, but we're going to ignore all that.". Not knowing where to go is a synonym for architectural tech debt. And they're doing the equivalent of paying for a loan by taking out another, bigger loan. It's getting you out of the immediate problem but giving you more debt to work with in the future (as the code that's being created is just being put on top of the old debt and getting it more interlinked). Meanwhile, leaner codebases are seeing way more modest productivity gains from agents, but nonetheless going faster and not putting more messy code on their shoulders. So all in all, we're looking at a Senior Developer shortage in a few years, because companies are not investing in the Junior-to-Senior pipelines anymore. And for those Senior developers, they're gonna be left with byzantinian codebases that will be extremely difficult to work with. So let's all get ready for the software quality crisis coming in about 10years. (Long enough for the OpenAIs and Googles of the world to have made their money though, which is the only important thing)
August 27, 2025 at 9:00 AM
precioso.design
writing an RFC for CI at @wasp.sh and this is what I have to say about the 🐐 @dagger.io
screenshot of a text message, saying the following: add a personal note: i really like Dagger, they turned the Docker model (immutable filesystem "layers" for isolated containers that you apply shell commands on and produce a new copy-on-write layer) into a programmable engine, so that you can use regular paradigms like variables, functions, and easily share layers/data between modules. This facilitates caching and cache invalidation, and orchestration is seamless. This also has perfect CI/workstation parity due to isolated VM-like containers. If I had my way, our full CI system would be a only a dagger run check-pr call. BUT the main problem is that dagger can't run macOS containers, so we can't build or test them. I'm sad about this.
August 7, 2025 at 10:51 AM
precioso.design
Me realizing all my teammates at @wasp.sh have one more holiday in August
A close-up photo of a person wearing a black LA baseball cap with the following text overlaid: "Hey guys when you say something is for the croatians can you include me in that as well? The croatians and Carlos it's not too much trouble thanks guys"
July 23, 2025 at 1:00 PM
precioso.design
Hey, I wrote something for @wasp.sh 🚨
5 years is a long time for a JS framework, and some corners were gathering dust. But now, we're taking a closer look, and paying down a whole lot of tech debt. Come with us on a tour of the most interesting parts! ⬇️

wasp.sh/blog/2025/07...
A screenful of TypeScript code, with template placeholders inserted, which are triggering IDE errors.
July 18, 2025 at 12:33 PM
precioso.design
Learning about monad transformers today
A modified screenshot of an Instagram story. The original screenshot was a picture of a 20+ lane highway, with a text pleading repeatedly for "just one more lane bro". It has been modified so it reads "just on more monad bro" repeatedly.
June 3, 2025 at 11:11 AM
precioso.design
@miho.dev this week
An illustration mashing up the cover of Tame Impala's "The Less I Know The Better" and Magic the Gathering's "Pondering Orb"
May 21, 2025 at 1:37 PM
precioso.design
And I shall call it: stateful serverless
A screenshot of the Windows 7 Start Menu, with the pointer over the "Hibernate" button
May 20, 2025 at 10:32 AM
precioso.design
⚠️ macOS trick alert ⚠️
If you do:
$ mkdir -p ~/Developer
$ touch ~/Developer/.localized
You get a Developer folder on your home directory that the system recognizes so it has a nice icon (both the folder and as a bookmark!)
A screenshot of my home directory with a Developer folder highlighted. It has a hammer icon (like Xcode's icon) in the style of the other default folders in this directory. There's a bookmark to this folder in the sidebar of the Finder, with a hammer outline icon instead of the regular folder icon.
April 24, 2025 at 11:20 AM
precioso.design
My guess is that the leading dot confuses their `node_modules` resolver, and thinks that it should be a local file. Nothing that an `alias` can't solve!
An extract of code from vite.config.ts: export default defineConfig({ // ... resolve: { alias: [ { find: /^\.prisma\/(.+)$/, replacement: "node_modules/.prisma/$1", }, ], }, });
March 25, 2025 at 5:03 PM