methodology

Guesswork Based Development

Guesswork Based Development is an informal and often criticized approach to software development where decisions are made based on assumptions, intuition, or incomplete information rather than data, research, or established best practices. It typically involves skipping requirements analysis, testing, or validation steps, leading to unpredictable outcomes and potential technical debt. This approach is generally considered anti-pattern in professional software engineering due to its high risk of errors and inefficiencies.

Also known as: Gut-feel Development, Assumption-Driven Development, Intuition-Based Coding, Speculative Programming, GWD
🧊Why learn Guesswork Based Development?

Developers should avoid Guesswork Based Development as it contradicts modern software engineering principles like Agile, DevOps, and data-driven decision-making. It might be used in rare, high-pressure scenarios with tight deadlines or limited resources, but even then, it's recommended to apply minimal viable practices like quick prototyping or heuristic-based estimation instead. Learning about this helps developers recognize and mitigate such practices by advocating for evidence-based approaches like test-driven development or user research.

Compare Guesswork Based Development

Learning Resources

Related Tools

Alternatives to Guesswork Based Development