Software Engineer at IKEA | 🇧🇷 living in 🇳🇱 | tweets are my own
Amsterdam, The Netherlands
Joined July 2009
- Tweets2K
- Following2.3K
- Followers525
- Likes7.5K
Pinned Tweet
Minha gente, fiz um site aqui pra visualizar os casos de COVID-19 por munícipio: mapadocovid19.com.br
Completamente open source, subindo nos ombros de gigantes como next.js (@zeithq), chakra-ui (do @thesegunadebayo), vx, d3.js entre outros ❤️
🧙♂️Juliano Farias retweeted
Holy smokes. You can absolutely swap "Editor" with "Developer" and it all still applies.
🧙♂️Juliano Farias retweeted
I have thoughts on the recent ai bot craze:
- Grok Bot
- OpenAI Dot
- Muse
- OpenMuse
- Cue
- Fo
- Instinct
- Gemini Spark
- Claude (agent mode)
- Microsoft Copilot Autopilot / Scout
They're cool. It's like hiring an employee, and firing them will be likewise painful unless you set yourself up right.
Each one of these products (and the others inevitably on their way) are going to do their best to make theirs the winner. But the fact is that they will continue to leap frog each other in capabilities. Not to mention some will be locked down to specific models.
There will be plenty of reasons you want to fire one and hire another. Or even hire multiple of them. But the thing is, they all want to drive their claws so deep into the flesh of your business (to be useful of course), that it will be a huge chore to get rid of them.
The integrations, automations, memories, secret tokens, etc etc etc. All of these will be locked into the assistant and they are not incentivized to make it easy for you to transfer these things to your "new hire."
In fact, they're incentivized to do the opposite. To become so core to the way you do business that you could never replace them.
This is why I think now more than ever kody.codes is filling in a critical gap. Instead of your agent putting everything inside its own home for the work it does for you, connect it to Kody and put it there. Then when you hire another agent, it can work off the same platform.
I think a lot of people are going to feel this pain in the coming months. When they do, Kody will be ready!
🧙♂️Juliano Farias retweeted
This video was made by opus 5.5 with a single prompt (posting below). Unbelievable.
🧙♂️Juliano Farias retweeted
This is the sort of thing that @kodykoala enables
🧙♂️Juliano Farias retweeted
you now have the ability to
- play with every possible solution to a problem
- refactor everything when you think of better patterns
so many people complaining about the code the LLMs produce, if you're not producing the best software of your life right now something is wrong
I've been using @kentcdodds kody mcp and this is possibly the best usage I've seen from an mcp. you can set it up once in any of your harnesses and all your integrations become available safely through kody. no need to reconfigure any oauth app again or share secrets yet again
🧙♂️Juliano Farias retweeted
Take a look at your favourite skill.
Go on, take a look.
Check for lines like:
- "Make the commit message very detailed"
- "Be thorough"
- "Make the implementation easy to read"
What do these lines have in common?
They're no-ops. They do nothing to change the agent's behavior.
Agents always write good commit messages. They always try to be thorough. They always try to create easy-to-read implementations.
Try removing them. Does the output change? No? Then the line was a no-op.
Agent-authored skills are LITTERED with no-ops. Entire paragraphs and sections of text that does nothing to change the agents' behavior.
No-ops make skills harder to evaluate, harder to maintain, and burn tokens uselessly.
Learn to spot them, test them, and remove them. Your skills will thank you.
🧙♂️Juliano Farias retweeted
Announcing mattpocock/skills v1
- Achieved a 63% reduction in token cost for skill descriptions
- Split skills into model-invocable and user-invocable skills, adding /codebase-design, /domain-modeling, and /grilling
- (UPDATED) /writing-great-skills - rewritten from the ground up, encoding my skill-writing best practices
- (UPDATED) /diagnose -> /diagnosing-bugs - now model-invocable, awesome for fixing hard bugs
- (NEW) /ask-matt: a router skill that teaches you how all the engineering skills work together
🧙♂️Juliano Farias retweeted
/teach is live
Learn anything, from rubik's cube to vocal harmonies to software fundamentals.
npx skills add mattpocock/skills --skill teach
Best skill I've ever built, video coming soon
github.com/mattpocock/skills…
🧙♂️Juliano Farias retweeted
Making implementation cheaper has made creating bad code cheaper
But it's also made creating good code cheaper
You just need to know the difference
🧙♂️Juliano Farias retweeted
4 of the most confusing terms in AI, defined:
Model: a blob of parameters, written during training. Does next-token prediction and nothing else. Stateless.
Harness: everything around the model that turns it into an agent: tools, system prompt, context window management, etc.
Environment: the world the agent acts on. Anything outside the harness that the agent perceives and acts on via tools.
Agent: a model, harnessed, in an environment.
---
Opus is a model.
Claude Code and Claude Web are different agents, because their harnesses differ - even though the models are the same.
The file system is an environment. MCP servers add tools to the environment.
🧙♂️Juliano Farias retweeted
Writing code is cheap
Maintaining code is not cheap
Anyone who's hired an external contractor knows this
For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews.
This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system.
LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it.
If you're a Yes Engineer, the next decade is yours.
🧙♂️Juliano Farias retweeted
Just shipped Sandcastle 0.4.1.
- OpenCode, Pi, Codex support
- Podman, Daytona, Vercel support
It's becoming the simplest way to run any agent, sandboxed anywhere
🧙♂️Juliano Farias retweeted
Just implemented a feature using GitHub spec-kit.
It's an opinionated workflow for coding via an LLM. I used it with Claude Code, but it works with many different LLMs.
Wow. It does a LOT.
- Creates feature branch
- Generates a high-level plan
- Creates a quickstart doc for trying the feature
- Generates research docs about decisions and alternatives
- Outputs a detailed spec
- Creates a list of tasks based on the spec
- Implements tests first and enforces that they fail (TDD)
- Does the implementation using task list.
- Validates it all works by running linting, build, and tests (it fixed its own minor mistakes at the end too).
It's VERY thorough and organized, and walks you through a highly opinionated development flow.
I told it to create an admin feature for my restaurant app and it generated and implemented these 32 tasks, checking them off as it progressed.
If you're coding with AI assistance, you should absolutely try this. It's a real eye-opener to how far you can take things.
🧙♂️Juliano Farias retweeted
Agora é oficial: sou Lead Developer Advocate na @meteorjs ☄️
“Mas pera, MeteorJS ainda existe?”
Não só existe como tá mais vivo do que nunca! Tem versão nova, comunidade engajada e produtos além do framework.
Ansioso pra trabalhar com open source e por tudo que vem aí ❤️
Welcome @o_gabsferreira, our newest Lead Developer Advocate!
ALT Say hi to Gabs Ferreira! Gabs has been in the tech industry since 2007. After creating his first blog, he fell in love with content creation and devrel. He works on his tech podcast and a few other side projects in his free time.
🧙♂️Juliano Farias retweeted
We have an announcement
remix.run/blog/merging-remix…
🧙♂️Juliano Farias retweeted
I couldn't be happier today - we're entering a world without forwardRef ✨
🧙♂️Juliano Farias retweeted
React 19: Never forwardRef again
We just published the first beta for React 19! This beta release is for collecting feedback and preparing libraries for the next major version of React.
To see what's included, check out the release post:
react.dev/blog/2024/04/25/re…
