Replying to Avatar Egge

I have fully integrated goose into my workflow… what can I say, time to remove the “Toxic anti-vibe-code maximalist” from my bio lmao…

I still believe that you should do research, iterate, fix bugs yourself to grow. Read to learn about design and architecture. Don’t let LLMs take this away from you. But when it’s time to go fast, let AI help.

It’s like Star Wars. Let the computer plot your hyperspace routes, it is better at this than you ever could be.

But when it’s time to dog fight at close range you better have some sick piloting skills ready to take up the fight
Avatar
dshf 5mo ago

I find this vibecoding idea just to risky in a form it is presented now. Even if an app is finally working you still do not know if it is working as intended.

I am no coder. My approach is to work as a BI: discuss ideas, specify requirements, ask questions, review the code and ask more questions, ask agent to write tests and execute and then test yourself. In the process of that you will learn a lot, have fun and do stuff.

I started with Cursor but #goose is on my list.

Reply to this note

Please Login to reply.

Discussion

No replies yet.