How to Respond to a Request for Estimates on Software Development

Response to: Do We Really Need Estimates?

I think it is a question of addressing the purpose those see for estimates. If they just say "lots of people do it, so we should" then your answer is fine in my opinion.

If they say they need some way of deciding if doing that work is wise or something that is going to be so difficult that it isn't worth it then a different answer is needed. If they talk about scheduling then other explanations make sense to me - talking about the issues with fixed estimates etc. but giving them alternatives of fixed schedule with variable features (if there is a business need to deliver on some date)., etc.

Related: Agile Story Point Estimation (2012) - Assigning Story Points to Bug Fixes (2011)

A College Degree Isn't an Acceptable Hiring Screen

Comment on: Do You Need a Degree to be Hired to Develop Software?

In all the time I hired developers (about 10 years), I never made a college degree a requirement.

The best developer (who was also much more - designer, coach, architect, program manager...) I ever helped hire didn't have a college degree.

Our company had just hired a new HR person that started "showing their worth" with new rules such as the dictate that all hires must have a college degree. Thankfully our team agreed to hiring him was wise and the CIO decided that dictate was nonsense and we hired the applicant.

I have written about what a great software development team we created.

In addition to a college degree being a lousy hiring screen, so are most of the automated screen poorly designed HR departments use. Years of experience, experience with a list of specific software, keywords listed, etc. are just lazy and poor criteria to use to reject applicants.

Related: Dee Hock on Hiring (2010) - Hiring – Does College Matter? (2007) - Google’s Answer to Filling Jobs Is an Algorithm (but yours shouldn't be) - The Illusion of Knowledge - Working as a Software Developer

Quick Mistake Proofing Ideas for Preventing Date Entry Error

I found a new failure mode for online bill pay. I had an electric bill due April 24. I mistakenly entered May 23 as the pay date 

So, by April 30, I had a late payment termination notice from the electric company. Kudos to them for the fast cycle time on getting those out. I paid the bill via credit card on their website. 

I’m not sure how to error proof “wrong date.” You?

It is easy to put in a filter that checks and then puts a big flash message:

  “The date you entered is after the due date. Are you sure you don’t want to put in a date prior to that...”

You can also make the data entry bias toward a on-time payment: require an extra step to go beyond the due date, default the value to be the due date... How you implement this would depend on the entry method.

It is really easy to do well if you are using calendar point and click – grey out all the post due date entries, if click on a greyed out entry, pop-up a message that says “that date is after the due date are you sure...” It gets less effective/cool if it is just text entry...

Even with text entry thought you can popup the message on submit of the form if the date is too late (so they enter the wrong date but you catch it before the action is completed).

You can also follow up with (using this method alone is better than nothing but it is pretty lame so I wouldn’t suggest it as the only method unless nothing else can be done reasonably) email saying “you entered a date after the due date in your last bill payment, if you don’t pay before that late fee…

Anyone what to hire me for a few minutes at a time to think of ways to make it harder to make an error just let me know. I don’t like processes that allow errors so have become fairly good and thinking up ways to make it harder pretty quickly :-)

Related: Mistake Proofing Deployment of Software Code - Improving Software Development with Automated Tests - Poka-Yoke Assembly