4 ms·
P = programmer; NP = non-programmer NP: How long will it take? P: It'll take as long as it takes. NP: I don't understand. What does that mean? P: Whe
by robomartin 15y ago
P = programmer; NP = non-programmer
NP: How long will it take?
P: It'll take as long as it takes.
NP: I don't understand. What does that mean?
P: When you tell me that the product is finished, it's done.
NP: You mean you can't estimate how long it'll take?
P: I can't estimate when you'll decide that it is done, therefore an
accurate prediction is impossible. From experience I know that a
project like this can take from three to nine months. A lot
depends on you, the choices you make and how well you communicate
them to me. A lot also depends on how many times you change your
mind during the process and how many times you change the
specifications during the job. Major changes can even cause the
project to be scrapped and start over. Rest assured that I will
not be the one slowing this down.
NP: How much will it cost?
P: It will cost as much as it costs.
NP: I don't understand. What does that mean?
P: You just learned some programming!
Go back to your first question and re-read the entire thing.
This is called an endless loop.
- bravura 15y agoWhat are the implications on the universe if P=NP?
- deleted 15y ago[deleted]
- buu700 15y agoThe real question is, are they the same person?
- doktrin 15y agoThis takes a fairly narrow view of a development process, IMO. The "but you didn't specifically tell me to do X" attitude can border on the irresponsible and/or lazy. It's all nice and well to expect accurate step-by instructions to be communicated by a PM, but the onus also does fall on developers to meet them half-way. While machines may require explicit and literal step-by instructions, a human being value-add is in thinking rationally, making inferences and (when necessary) asking questions.
- Silhouette 15y agoP: Rest assured that I will not be the one slowing this down. It would be hard to trust a programmer who was so comprehensively trying to avoid taking any responsibility for anything. Of course many factors will affect the overall time and money required to complete a project. Any decent manager knows this. But a programmer who can't even estimate a project given a reasonable set of assumptions is just trying to cover his ass. IME, he almost certainly will also be the guy who will slow things down, because being completely unaccountable for his performance he has no incentive not to.
- glanch 15y agoNP: You're fired.
- wpeterson 15y agoThis is the difference between an engineer and a programmer. That programmer is giving literally correct answers but acting like a passive subject in what should be an active relationship. Our role as engineers is to push back on all of the possible negative choices/directions a product-owner or business person makes and guide them to the simplest, scoped solution that solves their problem.
- ssmoot 15y agoSo you have an easily identified problem to solve. Specification and Responding to Change are not mutually exclusive. You do the first. You get an estimate. When a change is mandated, you specify the change. You estimate it. When you discover a feature was under-specified, you re-specify it. You wouldn't find out your code doesn't work, and then not update the tests. Why would you treat specification any differently? When the 3 month project ends up being a 9 month project, you have clear, actionable documentation on where your process needs fixing, and if the developer truly did hit all their marks, they get their well deserved rewards/kudos despite being saddled with a poorly managed project. There are projects (I'm sure) that are practically impossible to specify well. I've never worked on one though. Web Development is, by it's nature, a rather straight-forward process. The more unpredictable portions (design, data-migration) can be sandboxed in a pragmatic manner. I've been a part of projects that have run very well and satisfied the client despite changes doubling the original project cost. That's what Change Requests are for. To make sure you're all on the same page and everyone knows what they're paying for. The fallacy of Agile for the projects I've worked on is that the clients will be delighted to recieve "what they want" if they don't know the ultimate timeline, can't make their own plans around it effectively, and have payed a lump sum of money thinking they were buying X, but instead recieved X--. Since let's be realistic, when you talk about shifting to an "lean" process in a fixed-bid environment, you're not talking about delivering a better suited to the needs Y to a client who paid for X. You're talking about delivering a subset of X that fit within the time allowed. And who ever walked away happy when they got less than they paid for? If you take for granted the Perfect Specification is impossible, you don't have to shoot the whole process in the head either. Would it be valuable to spend a few minutes post-design on deciding what Validations apply to the Form fields presented? Or how to map those fields to your data-store? Spend a few minutes thinking about what business-logic applies "in the background" once that Form is submitted? What happens on error? What test-cases should be defined to ensure we get the basics covered like HTML escaping, CSRF protection, etc? Even a deliberate attempt to cover half of what you might ultimately need to consider to deliver this feature makes the rest so much easier, more predictable and easier to estimate. The dirty secret is estimates (again, speaking from experience in Web Development) aren't all that difficult. It's just a Garbage-In-Garbage-Out situation. I've been doing this for 10 years. Estimating the time it'll take me to write a Form is not difficult to do accurately. Just like I can't off-the-top-of-my-head estimate the effort involved in writing a Web Framework or O/RM before breaking it down into Routers, Actions, Templates, etc, I can't estimate a Feature without breaking it down into smaller chunks either. The overarching theme in most of the comments to this post is that estimates are hard, impossible or not worth doing. I respectfully disagree on all counts (within the context of web-development anyway, which is all I can speak to here). It certainly doesn't benefit the Developer to have all the accountability and none of the authority when working on an extended project without strong Project Management backing him or her up. So it seems to me pretty self-defeating when instead of figuring out what works and what doesn't, like your average Developer would tackle any other problem, instead the popular opinion seems to veer towards throwing out the baby with the bath-water and absolving oneself of responsibility instead. The Executives are going to blame someone, and it's rarely going to be themselves. At least not in any meaningful way. Like it or not if you're working on a Doomed Project, and you don't have someone to back you up, realistically you're going to be looking at a reevaluation in the capital of your own reputation. Fair or not, that's the way it works in my experience more often than not.
- robomartin 15y agoIt's a JOKE. Relax.