Carlos Precioso

@precioso.design

44 Followers 79 Following

Founding Engineer @wasp.sh he/him 🌈

Screenshot of the game showing the four achievements as completed: "Lovers survive", "Clear board", "Future generation", and "Rat pacifist"
Screenshot of a Claude Code skill file called "babysit-pr." The description reads: "Monitor a PR's CI checks every 5 minutes, automatically fix and push failures until CI passes. Ignores flaky Railway/Fly deploy jobs." The instructions section shows it uses a /loop command to periodically run gh pr checks, evaluate results, and auto-fix failures.
In the style of the "You wouldn't steal a car" meme: "You wouldn't download a skill"
Screenshot of the Claude pricing page, focusing on the Max tier. The $200 regular price is strike-through'd and instead it says $0, with a notice reading "100% off Max 20x for 6 months".
A shell script called "tell-off.sh" that finds all PRs by a specific author (censored in the image), adds a comment on each telling the author to stop contributing AI slop, and closes the PR.
A developer can't install their preferred version of React in a Wasp project. By setting `wasp.overriddenDeps.react` in their `package.json`, now their project compiles!
Crude drawing of a man touching his own face, basking in relief and contentedness
Screenshot of a video call with all the team members having a composited boat captain hat on top of their heads.
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**
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)
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.
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"
A screenful of TypeScript code, with template placeholders inserted, which are triggering IDE errors.
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.
An illustration mashing up the cover of Tame Impala's "The Less I Know The Better" and Magic the Gathering's "Pondering Orb"
A screenshot of the Windows 7 Start Menu, with the pointer over the "Hibernate" button
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.
An extract of code from vite.config.ts: export default defineConfig({ // ... resolve: { alias: [ { find: /^\.prisma\/(.+)$/, replacement: "node_modules/.prisma/$1", }, ], }, });