Development Approach: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
(Redirected page to Development Guide)
Line 1: Line 1:
=Steps to Success - Hardware=
#REDIRECT [[Development Guide]]
 
'''On Development'''
 
It's either figuring out a new concept, setting dimensions/details for a new technology, or pondering how to make something.
 
Order your projects well- do you have the right tools? Get some first to avoid transition losses due to "darn, we need to order that". Do you have the right software? Set it up so that you avoid timesinking into learning it half-way through a project.
 
Before you start a project, intend to finish it. Prepare well so that each step is straightforward.
 
'''On [[Collaboration Resources]]'''
 
Working with others? Set up the communication channels, work out the finances, be clear and detailed to avoid misunderstandings.
 
'''On [[Design Resources]]'''
 
Designs frequently use the same concepts over and over again. Record these concepts and make them easy to navigate, then attach info about design considerations and associated mathematics.
 
Getting and using great design software can be a hassle. If possible, try using software that is accessible to others for the collaborative access boost.
 
'''On [[Suppliers]]'''
 
Avoid spending too much time with broad search bars. There's a finite number of great suppliers applicable to your area- find them to focus your navigation scope.
 
Make a hyperlink list of reliable suppliers that stock well and ship fast. Be sure to categorize the list for easy navigation.
 
Get tool and material sourcing to a pow-pow-done straightforwardness.
 
'''On [[Action Resources]]'''
 
From design to execution. So the workshop has a bunch of tools and a bunch of materials all organized in some way. Now, how to make the design? Safety first- accessible equipment and warnings! Then proper signs, effective organization, instructionals and especially first-hand experience.
 
Using any part of the workshop should eventually become pow-pow-done straightforward.
 
'''On [[Documentation Resources]]'''
 
For documentation, keep things clear and concise. Avoid long strings of hyperlinks. Make navigation simple.
 
'''On Concept into Details into Execution'''
 
Grasping the concept of a cup is easy enough. But try adding dimensions and you'll need math equations about human hand ergonomics. Even past dimensions, how to get the right tools and materials and how to know the exact techniques for actually doing it... crippling.
 
Fortunately, a lot of tools should already be in the workshop and the material supplier list should easily handle the rest of the sourcing. Excellent design resources will handle the itty-bitty details. Finally, a well-developed, well-maintained workshop with accessible use information will handle the rest. Everything will become ridiculously simple- eventually.

Revision as of 09:30, 13 December 2012

Redirect to:

Retrieved from "https://wiki.opensourceecology.org/index.php?title=Development_Approach&oldid=83833"