4 ms·
Yes. This is the problem with estimates, a problem that is by design. :) It in indeed a sucky problem, just ask any person or business doing contract work, from
by dahart 10y ago
Yes. This is the problem with estimates, a problem that is by design. :) It in indeed a sucky problem, just ask any person or business doing contract work, from software to plumbing, from construction to law. There is no way to make a deal without guessing the value of both sides of the deal.
But it's a problem we're stuck with, it cannot be manifestoed away. The contract that follows an estimate is an unavoidable problem because the business has a time & money budget it has to fit into. This is a universal problem that all people have - how to get the most of what we want given limited resources. How do I decide which side project to start with an hour a night after the kids go to bed? How do you tell someone else you can do something -- anything moderately complicated -- without estimating how long it'll take? How can I make sure I die happy? How do you get someone's business without making promises that you can deliver a reasonable product in a reasonable amount of time? How can you write code for an employer without thinking about how long it will take? Why should an employer even employ you if you don't believe in the value of budgeting, and instead prefer to build "the highest quality" for unspecified and unlimited amounts of time?
It's a balancing act, and it's painful to be expected to estimate work and then somehow meet those inaccurate estimates. But managers are in the exact same position, it is important to understand why they're asking for estimates -- because they need them. Is it better to improve, to learn how to estimate better, and how to communicate better, or is it better to avoid conversations about the budget and have a never ending fight with the organization's attempts to manage it's expenditures?
I've tried fighting that fight, because I too used to be naive. I now understand why estimates are good for the company, and I understand why they're good for me as an engineer. In my experience, the more fruitful avenue is to give managers what they need and help them do their jobs. You will earn allies that can help you defend your schedule when it goes long, you will earn trust by the company and become respected as an engineer who can do what he says he can do. Once you have that trust, spotting errors in your own estimates are likely to be believed and even valued.
- pdimitar 10y ago> I've tried fighting that fight, because I too used to be naive. Sounds derogatory to the person you're arguing with. Is that your intention? > I now understand why estimates are good for the company, and I understand why they're good for me as an engineer. I realize this might be a wrong interpretation from my side but you do sound like you were dragged in a meeting, and the mystical they "explained how the real world works" to you, and then you took their side. A bit extreme interpretation I admit but IMO you should've chosen milder language if that interpretation isn't your intention. Look, I too think this "manifesto" is worded stronger than it should have been, and that it's a bit extreme. Nobody can realistically expect that the people paying salary to you will just leave you the hell alone and wait for you to contact them to announce stuff. That's not gonna happen. But the way you word your responses here makes me think you're more of a business person now and not an engineer. On the building trust point however you're 100% spot on. I've found that to be an extremely precise description -- be upfront, try to serve the business needs as best as you can, make honest effort to make yourself a predictably producing asset and when sh*t hits the fan the people you work for will give you the benefit of the doubt. I think the disconnect between managers and programmers always stems from if we should look at the programmers as assembly line workers or craftsmen. The difference between how you treat either is pretty obvious however, so I won't go there.
- dahart 10y ago> Sounds derogatory to the person you're arguing with. Is that your intention? No, I was referring to the manifesto, and circling back around to my initial comment on the manifesto. Moreover I did intend for this to be self-deprecating, as I said, I have gotten this wrong in the past and been naive in the same way that I critiqued the manifesto for being naive. I am sharing lessons I've learned the hard way. > IMO you should've chosen milder language I'm honestly surprised, saying "I understand" is pretty friggin' mild language... I don't see clearly what your interpretation is or why you're finding it offensive (it sounds like you're finding it offensive?), feel free to clarify. > you do sound like you were dragged in a meeting, and the mystical they "explained how the real world works" to you, and then you took their side Well, I am summarizing here. We all are. I can't share the subtleties or make this soft without writing my life story. I do try to extend benefit of the doubt in forum discussions, and I hope to receive the same. I try to assume that people understand there are always corner cases and subtleties we don't have the time to explain. > But the way you word your responses here makes me think you're more of a business person now and not an engineer. Is that somehow bad? I have been an engineer in the past, I have been an engineering manager leading teams inside large businesses, and now I am a (startup) business owner and engineer at the same time. I believe my experience doing both gives me a unique perspective that many engineers who have no business experience lack, and I'm sharing that perspective here. I happened to have come to the conclusions I've written down here while engineering, before I ever became a manager or business owner, but I think my management and business experience only makes my case stronger, not weaker. The manifesto reads as if it was written by an engineer who has no business perspective, and my issue with it is not that it was strongly worded, it is that the goal is misguided. I believe, based on my experience as an engineer and a business person that avoiding timely communication and avoiding budget discussions in the name of a personal definition of "quality" are bad goals that rarely result in actual high quality software that actually helps the business. Moreover, engineers adding their own unchecked notions of quality is a super common highly documented and much discussed way to incur mountains of technical debt, waste large sums of money, and deliver projects extremely late. > I think the disconnect between managers and programmers always stems from if we should look at the programmers as assembly line workers or craftsmen. The thing is, this is a fear programmers have that business people, by and large, do not share. Managers need programmers to work their craft, they generally don't know how to write code, and know it, and broadly speaking they have a deep respect for people that write code. When programmers declare they're not going to participate in estimates, or even just drag their feet and complain that estimates are impossible or inaccurate, and when programmers avoid talking to managers and complain that email is preferable and weekly face time has no point, the programmers are the ones putting themselves in the position of being thought of as assembly line workers.