Programming blueprint Feb10 '06
Programming is really just like speaking a certain language. You combine words to form a sentence.
If you can explain (in English), in full detail, how you want something to work on a web page - that is 95% of the battle. The actual programming part is the easy part. It’s visualizing how it’s supposed to work that’s tough.
And the more layers you add into the picture - HTML, JavaScript/DOM, server-side/database - the harder it becomes to organize your approach.
I find that my approach usually involves these three steps:
- Event
- Actions
- Results
Of course, in between all of that is much more detail - but this is the "skeleton."
The Event is what happens to trigger something. Everything on the web happens as a result of an event. In fact, everything in life happens as a result of an event. (You put one foot in front of the other, and wa-la! You’re walking!)
The Actions are what happens as a result of the event. This is the biggest section, as it contains all of the actual procedures that perform the desired task.
The Results are what you see when it all finishes.
I am working on refining this approach into a "blueprint" model - one of which I can use, each time I’m presented with a new task. It really helps break things down into more digestable chunks.
Categories: Efficiency 
, Programming
Add Feedback (view all)
Leave feedback
is published and produced by Matt Thommes - an independent publishing enthusiast, mobile blogger, content creator, informative writer, web developer from Chicago.
Never one to conform, Matt intends to promote the effect the web has on our lives, in an effort to intensify, instruct, and clarify all that is happening around us.
Similar Entries
- Best practices for programming and web development (4 recent visits)
- PHP OO programming references? (7 recent visits)
- Some basic programming tips (6 recent visits)
- A new programming approach (1 recent visits)
Stats
2 unique visits since October 2008