2 ms·
Do you think a housing contractor is "making excuses" when they apply the rationale requesting to take down a wall in the house by saying: 1) we need to investi
by jshowa3 7y ago
Do you think a housing contractor is "making excuses" when they apply the rationale requesting to take down a wall in the house by saying:
1) we need to investigate the condition
2) check if its load bearing
3) check if it runs electrical or plumbing
4) check if it is to code
No, they're telling you the rationale of what goes into making a change. I agree that this isn't something you should send to clients. But, even sending a summary to someone who invokes this question will ask the same thing for any item you summarize. The next question will be, "Why does it take 4.5 hours to manually test?"
So, explaining the rationale, at least once, will help the customer understand the process and could contest specific elements rather than trying to hide it in vagueness.
- jmilloy 7y agoReally, I don't think that the developer is "making excuses" here. Which makes it all the more unfortunate that the letter as written sounds like excuses. > The next question will be, "Why does it take 4.5 hours to manually test?" I'm not sure it will. In my experience, clients are usually surprised about how long something takes not because they think specific tasks are taking too long, but because they aren't really aware of what the tasks are nor of their tradeoffs. "You're right, it took longer than expected. I chose to spent some time setting up automated tests. That took extra time now, but will save much more time later."