Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.
Click here to check if anything new just came in.
December 06 2010
The process of writing a technical specification - Stack Overflow
* You create a list of requirements or a functional specification* You look at all possible ways to solve the problem
* You decide which ways fits best or leads to the best result
What you describe shows that they didn't make a good (if any) analysis of the pro's and con's. In the end it comes down to how well the Junior's themselves are able to gather the right information and then make the correct decision. This might involve asking more senior programmers ;-)
Some examples of design methods to decide what the best possible options are:
* http://www.wikid.eu/index.php/Itemised_response
* http://www.wikid.eu/index.php/Weighted_objectives_method
* http://www.wikid.eu/index.php/Harris_profile
* http://www.mycoted.com/Brainwriting
* http://www.qicbok.com/tools/creativitytools_brainwriting635.cfm
