Skip to main content
Software Engineering

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.

Required fields*

6
  • Re-asking a question to narrow it down to your specific use-case is not encouraged, and you are unlikely to receive any better feedback. Commented Sep 19, 2010 at 21:59
  • Sorry. I was trying to look for a more specific answer. I'll keep it in mind next time. Commented Sep 20, 2010 at 4:40
  • 18
    Why is it not encouraged? If the answer he is looking for doesn't exist in the initial question I think it is better to ask another question narrowed down to a specific case. Commented Oct 13, 2010 at 19:47
  • 7
    Remember that speed is not the only metric for judging a coder's abilities - quality is also essential. In addition to speed, consider the amount of rework too. Commented Nov 11, 2010 at 14:56
  • 1
    @Chucky - I daresay it has. But with regards to the context of the question, I've learned that raw speed isn't a reliable metric by itself. There are just too many variables (e.g. people involved, environment, complexity, etc.) involved in development that can affect how long you work on a particular task. A record of previous estimates you've made and what you've learned from them definitely helps in giving out future estimates on how long one's work will take. Commented Dec 11, 2014 at 13:58