The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I am Indian, and would use "Thanks in Advance" when it is more like a request from my side, the person addressed to is from a different department, and is somewhat not officially obliged to answer you.
So I have a query from business that they want to change one of the application that prints label based on certain condition and now they wanted to add one more condition and asked me for a number of days it will take me to do that. Everything is there it is just addition of one more condition in if statement so I said it can be done in a day. I got a reply from one of the project manager saying never quote a day at least keep 2-3 days buffer so he chaned it to 5 days.
So I have now 5 days to add one condition to if statement and test it. Good thing is I have 15 projects going on at the moment so I can use some of this time on other projects. Corporate world. You gotta love it !!!
Zen and the art of software maintenance : rm -rf *
Math is like love : a simple idea but it can get complicated.
But what about unit tests, documentations, specifications, meetings, demos, approval processes?
Surely that would take some times?! :P
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station....
My programs never have bugs, they just develop random features.
No no no, quote a number of story points for the task and then say we'll be able to calculate our velocity after approximately three project iterations which will allow us to gauge a real world value for a story point and hence give an estimate. Shouldn't be more than 6 weeks...to provide the estimate.
He is right:
1. In about 98% you won't need the extra time, but in the one case you really need it, it will really save your butt.
2. Frequently, urgent problems are not urgent. About half of the problems are solved within 20min by the one who asked you to change something. For another half, it solves in the next two days, so that you actually only need to wait three days to reduce 3/4 of the incoming requests.
3. Being too much reactive brings up the impression that what you do is easy. This should only be done when the request is obviously easy, but not if it is not.
4. And remark 1. offers you extra time in 98% of the cases to work on some other things (as you have already noticed)
Last Visit: 31-Dec-99 18:00 Last Update: 31-Jul-21 16:34