Het verlies van elke Buffalo doet pijn, maar dit raakt ons extra hard. Leonard (17) was er elke wedstrijd, thuis en uit. We gaan je missen, Leo. π«π #NiemandGaatVerloren
Software estimates are one of the oldest lies we tell ourselves.
We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan.
I focused a big part of my undergrad on software estimation.
After graduating, I wrote plenty about the topic.
Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built.
I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom.
Here is the most important lesson I learned:
People can't estimate software. It doesn't matter who they are or how much experience they have.
Estimating software reliably is science fiction.
And the best part:
They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable.
And then they will. They always do.
There are two solutions for this. Let's start with my recommendations for those who don't have a choice:
1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work.
2. Never volunteer an estimate. Everything you say will be used against you.
3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours."
4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours.
But we all know your manager will force you to give an estimate. Here is what you should do:
1. Estimate how long you think it will take you to complete the task.
2. Multiply the number by 3. This will be the lower range of your estimate.
3. Double the lower range of the estimate. This will be the upper range.
Example: If you think something will take you 1 day of work, say "between 3 and 6 days."
Here is the funny part:
It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of.
The true solution for this problem:
Work for a company that doesn't care about estimates.
Veel gepalaver over 38 miljoen voor een niet-kerntaak. Terecht. Maar kunnen we het ook eens hebben over *130 miljoen per jaar* voor een andere niet-kerntaak? @IvanVandeCloot
https://t.co/PqzVVbjr4o
Next step for esave. Together with RecAp - Resilient Cities Accelerator Program, we are on a mission to make buildings a lot more energy efficient without huge investments. If you are interested to know more or want to help, feel free to reach out.
#enerβ¦https://t.co/yzGUDYsgDF
Maturiteit: nul. Leiderschap: nul. Als Buffalo nog nooit zo gedegouteerd geweest. @SvenKums, enige man op niveau. Geef die man een nieuw contract, @KAAGent, en voor de rest: pletsen. Proficiat, @ClubBrugge, welverdiend.
@donnycura@vanranstmarc@ruudvdmeer Relevantie ontgaat mij. Hetgeen hij net zegt is dat iedereen zich moet verzetten tegen racisme. Dat laatste is niet heel netjes (en misschien een tikje kinderlijk)