Readit Newsspikey_sanju commented on AI Is Learning Taste sanju.sh/thoughts/ai-is-l... · Posted by u/spikey_sanju
Hey folks, I wrote a short blog on something I’ve been thinking about—what happens when AI starts to understand taste?
Everyone talks about AI replacing coders and writers.
But what if the real shift is when it starts to replace taste?
spikey_sanju commented on Stop Trying to Do It All, One Task Is Enough sanju.sh/thoughts/the-nex... · Posted by u/spikey_sanju
Hey all, I explain in the blog how focusing on the most important task helps me move forward. I stopped multitasking and started making real progress.
- Sanju
spikey_sanju commented on Why overplanning makes projects fail? sanju.sh/thoughts/why-gre... · Posted by u/spikey_sanju
lol, your "irl examples" are fantasies, made up on the spot by you to support your own made-up claim that "Success rarely comes from what we aim for". You should at least google some of the existing but exceedingly rare examples so your claims are not just hot air.
Made up? Hardly. I hear you, but reality isn’t as tidy as a research paper. Planning only gets you so far; timing and luck do the rest. IYKYK!
spikey_sanju commented on Why overplanning makes projects fail? sanju.sh/thoughts/why-gre... · Posted by u/spikey_sanju
I've noticed one obvious commonality to failed projects: the plans are made in a vacuum of information, before data is gathered. This leaves land mines everywhere in the execution path, leading to big risks and large error bars on estimates.
Instead of course correcting to any new data, failed projects tend to double down on the process. Even as more information comes to light, it gets systematically ignored in favor of "sticking to the plan". This is the death of software.
Of course I've seen projects that have basically no plan at all beyond the 2 week sprint. It's not the presence or absence of a plan that hurts, it's about the quality of the plan. Duck tape and prayers don't constitute a plan either.
We need a tight feedback loop between planning and experimentation. Otherwise planning goes off the rails with bad assumptions, and experiments can go off the rails chasing new technology for its own sake. A planning process without a data-gathering period and an iteration loop to refine the design isn't software engineering!
Plans are guesses... treating them as facts is the real danger. Adapt as you learn, or they become traps.
spikey_sanju commented on Why overplanning makes projects fail? sanju.sh/thoughts/why-gre... · Posted by u/spikey_sanju
“It’s too hard to change the plan now.”
That one sentence alone is enough to explain the failures and I’m not even accounting for the very real cost overheads of planning.
Don’t try to change this! You can’t convince a PM that their job is not needed, their pay depends on it being a necessary function and they will fight dirty to protect that income no matter what.
"It's too hard to change the plan now"
+1 Agreed. Plans fail when sticking to them matters more than adapting...
TBH, the best plans know when to shift.
Flexibility > Rigidity
spikey_sanju commented on Why overplanning makes projects fail? sanju.sh/thoughts/why-gre... · Posted by u/spikey_sanju
This is a great reminder of how unexpected success often comes from things we don’t plan for. Focusing too much on perfection can sometimes limit creativity, but you can’t just sit back and wait for things to happen either. It’s all about balance.
This is the whole point of the post...
Success rarely comes from what we aim for—it’s often about timing & flow. Perfection can hold us back, but staying open leads to breakthroughs.
Few irl examples:
1. Spend hours perfecting a video, 100 views. Post a raw clip, and it goes viral.
2. A polished product flops, but a scrappy weekend tool takes off.
3. A masterpiece gets ignored, but a casual sketch goes viral.
4. A failed dish turns into the next food trend.
Don’t wait for perfect. Keep creating, stay open, and let the unexpected happen.
P.S. Success is personal. But if you aim for something and it doesn’t happen, that’s a failure in that context.
That question invites vague feedback from people who don’t use your thing. You want behavior. Friction. Patterns.
Wrote a short note to remind myself too!!!
What's your thoughts on this?