Is writing software in the absence of requirements a skill to possess or a situation I should avoid?

Posted by Brian Reindel on Programmers See other posts from Programmers or by Brian Reindel
Published on 2012-05-29T01:17:57Z Indexed on 2012/05/30 22:50 UTC
Read the original article Hit count: 320

I find that some software developers are very adept at this, and often times are praised for their ability to deliver a working concept with abstract requirements. Frankly, this drives me crazy, and I don't like "making it up" as I go. I used to think this was problematic, but I've started to sense a shift, and I'm wondering if I need to adjust my thought (and programming) process when given very little direction. Should I begin to acquire this ability as a skill, or stick to the idea that requirement's gathering and business rules are the first priority?

© Programmers or respective owner

Related posts about agile

Related posts about programming-practices