- sarcastic comments bout AI
- simple productive setup
- vibe stories
What to expect
- AI generated code is a sin made against gods will
- amount of over-hype is killing me
- the ship has sailed, every CEO and investor EXPECTS AI, so we have to find a ways to survive
- to be fair, AI in the last year started to be actually useful. It was a good choice to ignore it for some time
Whats my opinion?
Tooling fatigue
Facts
- every month/week there's NEW SHINY TOOL
- there's probably IDE you already like
...so use OpenCode
1. install it
2. log into API you have access to (copilot supported!)
3. don't overthink it - all you need to know is already on the screen
CEBULA TIP:
COPILOT FOR OPEN SOURCE IS FREE
AND ITS GOOD
THERES CODEX AND OTHERS AVAILABLE
- single, most important step is using PLAN MODE
- iterate over it, make AI prepare questions and recommendations
- save it to file as reference for later
- click go and watch clanker go brrr
How to use it
Tip: there's little cool tool called Git, use it to make checkpoints
PS: AI can write commit msg too
- can connect to headless Chrome, SO YOU DON'T COPY PASTE ERRORS
- can click on stuff!!
- Next.js docs for agent
- npx @next/codemod@canary agents-md
- feels like it makes a difference
Tools that made impact
- never used xcode
- some exp with micro controllers, but not a fan of using c
- knew I won't have too much time for this project
Vibe Case:
Look ma, I'm a iOS/embedded dev now!
Takeouts:
- during planning you can ask for manageable checkpoints
- one day microcontroller, another ios app, another connection between those two
- opencode is great, cli based agents dont fight with the IDE
- you can create something outside of your expertise. Just try it
- STOREFRONT REWRITE!!1!
- thought bout trying bun+htmx stack for a looong time
- wanted to see how much of a additional context I had to provide
Vibe Case:
datastar-front
Takeouts:
- having schema is great
- necessity of codegen for vibe coding was challenged
- AI handles webdev outside react world too!
- feedback loop between dev server and agent is a king
- how far can I go with vibes?
Vibe Case:
reconsole
Takeouts:
- v0 is exceptional for designing dashboards
- hot take: we could drop macaw-ui
- don't try to one shot projects like that
- start with most exciting thing
- mock APIs, but plan for it beforehand
- check if dependencies provide their own MCPs
- did I mention that schema is a king?