‣ and designs before the actual implementation to avoid spending work pointlessly.

One of the ‣.

To Make many different bets more effectively.

Ways to verify ideas:

• Speaking with users, surveys
• Speak with a teammate or a friend: bounce ideas off him.
• Prototype to buy information; ‣
• Write a test first: use Test-Driven Development (TDD)
• Model and simulate systems

Related:

• ‣
• Ideas for reinforcing risky invention
• ‣
• Take smaller steps in an unknown environment
• ‣

References

‣

‣

https://news.ycombinator.com/item?id=5496914 For those who work inside Google, it's well worth it to look at Jeff & Sanjay's commit history and code review dashboard. They aren't actually all that much more productive in terms of code written than a decent SWE3 who knows his codebase. [...] Jeff or Sanjay (or any of the other folks operating at that level) will spend their time running a proposed API by clients to ensure it meets their needs, or measuring the performance of subsystems so they fully understand their building blocks, or mentally simulating the operation of the system before building it so they rapidly test out alternatives. They don't actually write more code than a junior developer (oftentimes, they write less), but the code they do write gives them more information, which makes them ensure that they write the right code.