You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- This is another big friction to find. Having to say to customer - that we are now building the same thing - of features which are nothing new, after the first version is handed over! How often, and frequently (if ever) can you afford to tell this to customer? or how do you even explain?Dipan Mehta– Dipan Mehta2011-11-12 09:46:37 +00:00Commented Nov 12, 2011 at 9:46
- You have two basic options, either first you simply tell the simple truth - that although what you have works its a mess and it needs to be tidied up to move forward or second that you say that you are building infrastructure to support the ongoing development (which is no less true but is spun so as to be a bit more positive). You can wrap both of these up by saying that in order to deliver the functionality we incurred a technical debt that now needs to be repaid.Murph– Murph2011-11-12 11:27:30 +00:00Commented Nov 12, 2011 at 11:27
- @Dipan Mehta: Well, suppose a customer wants a two-storey house. You design it and deliver it. Then they want to have four additional storeys. You say, well, I have to spend this time just to make the present building more robust so that it will hold four additional storeys. So I do not think this should be a problem for the customer if the original plan only included two storeys. If six storeys were planned from the very beginning then, yes, it could be a problem to tell the customer.Giorgio– Giorgio2011-11-12 20:39:17 +00:00Commented Nov 12, 2011 at 20:39
- @DipanMehta We're also a bit lucky in that the customers don't necessarily know about this project. It's an upgrade to a product they currently use, with a semi-vague completion date of around the end of this year. So they don't even need to know about a delay for refactoring ;) (The manager handling most of the design decisions is in-house)Izkata– Izkata2011-11-12 21:08:18 +00:00Commented Nov 12, 2011 at 21:08
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you