Click any tag below to further narrow down your results
Links
Building something well and shipping it are opposite skills—perfectionism that makes you a good craftsperson makes you reluctant to release work. The only way forward is forcing yourself to publish despite thinking it's flawed, because volume and iteration beat polished isolation.
- Gifted programmers and writers often sabotage themselves by refusing to ship work that doesn't meet their standards, but imperfect shipped code beats perfect unshipped code every time.
- You can't predict what people will find valuable, so producing high volume of work yields better results than agonizing over individual pieces—your throwaway posts often outperform what you labored over.
- Shipping is a learnable skill that gets easier with practice; the more frequently you publish, the less perfectionism paralyzes you, and you stop being able to distinguish between work you felt good about and work that actually resonated.
Traditional start-ups follow a rigid plan—write a business plan, pitch investors, build a product, then sell. The lean start-up method flips that sequence: you build minimum experiments, measure customer feedback, and iterate, which sharply cuts the 75% failure rate.
- 75% of traditional start-ups fail (Harvard research by Shikhar Ghosh), which the lean method aims to fix by testing ideas via MVPs before fully building them.
- Dropbox validated demand with just a two-minute demo video, gaining 10,000 sign-ups in 24 hours before building the product.
- Flickr pivoted from a multiplayer game into a photo-sharing site after noticing that's what users actually loved, becoming one of the fastest-growing sites of its era.
- GE's FastWorks program applies lean-start-up methods internally, saving millions by killing or reshaping failing projects early.
Exploring the effectiveness of coding agents hinges on effective user input, constraints, and context. By applying Steven Johnson's patterns for generating ideas, the article demonstrates how to enhance coding agent outputs through structured prompting and feedback mechanisms. This approach encourages incremental development, reuses existing solutions, and fosters a collaborative environment between humans and AI.
- Coding agents produce better output when users apply Steven Johnson's "good ideas" patterns (adjacent possible, liquid networks, slow hunches) as prompting strategies rather than treating the agent as a one-shot answer machine.
- Structured constraints and iterative feedback loops—not just clearer instructions—are what actually improve agent performance, mirroring how innovation historically emerges from recombination rather than isolated genius.
- Treating coding agents as collaborators to think alongside, rather than tools to extract finished answers from, leads to more incremental, reusable, and higher-quality code.