Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
CTO, Developer, Sysadmin, Network Admin, currently using Clarion on Windows, Drupal for websites, and picking up Ansible for sysadminning. Yes, I wear many hats, why do you ask?
Location
Marietta, Ga
Education
Asbury College, BA in Bible with Computer Science minor
Work
CTO/Developer/Sysadmin/Network Admin at Accelerated Design, Inc
Which may be not only a dev problem, but also a management problem. Tom DeMarco points out that we don't estimate well because we get so little practice at it. What we call 'estimation' is often actually haggling over what the schedule will be, at times going up against an attitude of "What's the earliest you can't prove you won't be done?" Between that and a potential ego motivation to make shorter estimates, it's not surprising that underestimating is common.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agreed! Also, underestimating is very popular among devs
Which may be not only a dev problem, but also a management problem. Tom DeMarco points out that we don't estimate well because we get so little practice at it. What we call 'estimation' is often actually haggling over what the schedule will be, at times going up against an attitude of "What's the earliest you can't prove you won't be done?" Between that and a potential ego motivation to make shorter estimates, it's not surprising that underestimating is common.