Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Fucking yes. All of my yes.
All I ever hear is:
"How long will this take?"
"I don't know. I've never done it before."
"But if you had a gun to your head."
I can't know what I don't fucking know!
@Charon92 as a team leader in an agile environ, I used a nice solution for this problem:
created a 3 day research/estimate task that was used to define, scope, specs, and timetable for a given unknon whatever.
in essence, shutup, and let me find out what needs to.be done, we can estimate based on something other then a wild guess.
So it's basically about being adamant that you need time to scope?
I always seem to have to answer immediately. Every time I've said "No, I don't know and it would be irresponsible to say." I always get the "But if you had to..." speech and no matter what I say nobody seems to listen.
@magicMirror I wish they would let me have time to define things like that. Instead my projects often get the combination of what the sales team feels like it should take, and whatever gets the numbers low enough to get the sale. Then they say "hey we lost money on project x". "You didn't account for the research and issues from not knowing how to do this"
@Charon92 not that hard. Ask yourself this question
does it take a year?
does it take six months?
does it take 3 months?
there's always an estimate.
Also divide long migrations to sub-tasks. Try to search what code will be affected, and estimate work om these parts.
Also, always ask your boss to give you time so you can estimate. Tell them you'll study it and reply in an hour. They can't really say no to that, or they'd just be stupid, assholes, etc... not uncommon :p
Just give the highest one you think works. If you end up finishing sooner, do code cleanup, documentation, testing,etc...
just some hints :)
And if I just have no idea? That seems to be my issue. Having not done a great deal of things before means I have little to no idea of how to even scope it properly.
I know how to break down tasks into roughly 3 hour blocks but if I don't even know what I'd need to break down...
How did he become President?
@Charon92 @steaksauce : don't make it personal. Make it as inclusive as possible. Avoid using the first pronouns.
Donts: I need more time. I have no idea. I never done this before.
Do: In order to give the client a feasible cost esimate, and look more proffesional, we should....
Never give a "from the hip" answer. always ask for more information about the requriments. Tell the asker that you (asker included) require more info, or the ROI will be negative for this project.
tl;dr : delay, obfuscate, annouy, and never answer the question.
Brolls38111yGet this sort of thing all the damn time. It’s because traditional management holds estimation as gospel.
Problem is that you’re damned if you do and if you don’t.
Either you’ve got it way out and you don’t have enough time to get it done, and end up being branded incompetent.
you’ve got it way out and get it done sooner than you said, and you get branded greedy / lazy / as taking advantage.
Occasionally you get the planets aligning and they understand or everything just works to schedule, but yeah, that’s a rarity.
I think this is why we’re so stressed all the damn time.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job
TangChr4"Difficult" takes a day. "Impossible" takes a week.
mickel1"How long will it take us to build X?" "How long is a piece of string?" Very similar indeed. Time estimates ...
PonySlaystation1We as developers often get a lot of pressure considering the deadline for $someProduct™. But sometimes it h...