#Estimation
6 notas · última:
Hard Things in Computer Science
The post argues that computer science has many hard problems beyond cache invalidation and naming things, including timezones, estimates, distributed systems, and proving code is bug-free.
Drive development with budgets not estimates
The post argues that software planning should start from what a feature is worth, not from time estimates, because budgets force tradeoffs, expose assumptions, and help teams ship more within constraints.
Developers Shouldn’t Measure Twice, Cut Once
The post argues that the “measure twice, cut once” rule fits construction, but not software work. In programming, rough estimates and early coding are more useful than long planning and estimation meetings.
How to Solve Google’s Crazy Open-Ended Interview Questions
The page explains how Fermi-style estimation tests whether someone can think through an open-ended problem. It walks through piano tuners and the Empire State Building to show how assumptions, boundaries, and rough calculations work.
How to be a Programmer: A Short, Comprehensive, and Personal Summary
The chapter argues that programmers need strong debugging, performance, documentation, estimation, and teamwork habits, and that all of them depend on experimentation, judgment, and clear communication.
Why is Estimating so Hard?
The post argues that estimates fail when people confuse how easy a task feels to do by hand with how hard it is to write the procedure. Human judgment hides procedural complexity.
