Go from idea to code the easy way
Business, Conceptual May 7th, 2008
Stumbling around the internet today I noticed that there is a resounding movement toward the usage of UML diagraming applications. I agree that these programs like Microsoft Visio are cool and a required tool of most business development cycles, but they are a waste of time. There hasn’t been anything that can replace the tried and true methodology of diagramming on paper. Visio can never add enough features to match a developers artistic skills. So here I am to teach you in the next two paragraphs how to take an idea and turn it into code the easiest way possible.
Obviously the first thing you need is the idea you want to develop. Now grab a sheet of paper and start writing an overview only focusing on the “meaty” portions of the idea. Once this is completed take those meaty portions and turn them into objects. If you do not know object-oriented programming, I suggest you stop now and google some tutorials on the subject.
Congratulations your on the last paragraph! Now elaborate on those objects and define the attributes that each object contains. There you go, you just defined your object-oriented structure in a matter of minutes. All you have left to do is create the object classes from those objects and then setup the main control structure/relationships if any exist. All of this is completed within minutes while your Visio buddy over there is still wondering if he should use the arrow or the lightning bolt in their diagram.
Being a smart businessman does not mean you have to use technology. Using technology just because it exists does not mean it is the best option. Diagramming applications have their place in large corporations, but do yourself a favor and skip them for your startup. The only time they will ever prove useful is if the designer cannot write legibly or you’re presenting to a venture capitalist and if that is the case just hire an intern to convert it to digital form.
Add Ri to Favorites
Follow us on Twitter
Add Ri on Facebook
See our Stumbles
See our Diggs
Check our bookmarks
May 7th, 2008 at 7:23 pm
I have never been a very big fan of UML Diagrams for development projects. Especially for smaller development teams. We typically document to the size of the project. However, each project has an owner and a backup. There too many examples of applications being owned by one person and then they leave or get hit by a bus which leaves organizations in chaos.
May 12th, 2008 at 7:20 pm
I’d probably go crazy trying to model in Visio as well. There are some open source programs like Umbrello that are designed specifically for modeling which are much easier to use.
May 13th, 2008 at 9:28 pm
Hey Justin! Golly! I haven’t seen a UML diagram since 2 years back while I was still in school majoring in IT Mobile Computing. It was fun having to create the attributes and all. Until the part where I get additional ideas to add into the existing diagram, and the entire thing was done using pen and paper, or I’ve maximized the whitespace and found it almost impossible to fit any more items in.
May 14th, 2008 at 4:08 am
Yea.. But it’s a necessary evil in school. We need to polish the documentation to the neatest way possible. Is this really how it goes?