Preferences

My two takeaways is you build 1) Having a precise vision of what you want to achieve 2) Being able to control / steer AI towards that vision

Teams that can do both of these things, especially #1 will move much faster. Even if they are wrong its better than vague ideas that get applause but not customers


void-star
Yes this! The observation that being specific versus general in the problems you want to solve is a better start-up plan is true for all startups ever, not just ones that use LLMs to solve them. Anecdotal/personal startup experiences support this strongly and I read enough on here to know that I am not alone…
techpineapple
What's the balance between being specific in a way that's positive and allows you to solve good problems, and not getting pigeonhold and not being able to pivot? I wonder if companies who pivot are the norm or if you just here of the most popular cases.
enos_feedler
Are you a student of Robert Fritz? He says this exactly. The only two things you need is 1) a vision and 2) ability to see present reality clearly. Beyond this it’s all about the skill to nudge a creation towards the vision without being prescribed to a process. The art is knowing when to just use the status quo tool or try something new at any point during the nudging is key. Based on his teachings I can easily see vibe coding fitting into creation process quite easily. Where it becomes tricky is “seeing current reality clearly”. If you have been vibe coding for two weeks and perhaps a weak programmer or worse no technical ability, can you actually see reality at that point? Probably not. It requires understanding the software structure. Maybe. Its all up in the air right now. But I truly believe that LLMs make software creation more like creating art.

This item has no comments currently.