S.T.A.R.S.
banned
Awesome! 

This scientist builds this robot and treats it like a son (think Pinocchio). Every night, the scientist has to put it into "sleep mode" to charge its battery. One day, the scientist puts him to sleep, but doesn't get woken for 5 years. One day, a surveyor comes to check the place out the home/lab before putting it up for sale. When he flips on the power, the robot wakes up. The robot asks the surveyor where his "creator" is (tentative name) and the surveyor says the building has been abandoned for a long time. He says maybe someone in town knows something about the creator. So, the robot sets off on a journey to find his creator.
*snip*
Im no expert, but wouldn't it be smart to set an objective, then break it down into discrete parts, and delegate based on desire/skills?
Plan it, do the work and present it.
See that's where it fell apart. No one agreed on an objective. We had nothing to break down. I stayed busy and ended up letting things slide.okedokey said:Im no expert, but wouldn't it be smart to set an objective, then break it down into discrete parts, and delegate based on desire/skills?
To be fair, we didn't do anything because we didn't have an idea to work from. Code/design complexity has nothing to do with it. When you are working a large project you do it in manageable chunks.S.T.A.R.S. said:There is nothing wrong with a small project for a start.
Someone will work ONLY on design.
Someone else will work ONLY on error messages.
Someone else will work ONLY on the main code (this might even take 2 people to finish it faster).
Some else will ONLY test it and report bugs.
.....
snip
.....