Quick Start: Git for personal use
SVN client over SSH to remote Unix server from Windows
Quick Start Grinder - Part V
Quick Start Grinder - Part IV
Quick Start Grinder - Part III
« Google API
» One alternative to MS Office
My previous post about adding XML-RPC interface to our search script brought forward an interesting observation. To make the search XML-RPC enabled, I had to essentially make a copy of the script, strip out the HTML and then return the XML-RPC packets. I think the problem is with the flawed approach many programmers with web-only experience take.
The "wrong" way: Many "database driven" web programs I’ve seen are typically made as template HTML’s first. Then you plugin ASP or PHP code to show "dynamic" data instead of junk text. This is such a bad programming design. There is no concept of splitting code into reusable blocks like procedures and functions. Most of the time code reuse means putting two include files called "header" and "footer".
What I consider the right way: One should first focus on the data - that is why database designers and programmers make such good general application designers - and then work your way to HTML.
My philosophy has been that even for 100% web oriented applications, HTML is only the current interface. It will change soon, or you’ll be needed to make new interfaces soon enough. Simple examples you do during a web programming course - like guest book or feedback form - are not enough to make lasting applications.
Here is my cheat sheet (assuming that the platform is already decided):
ddl
for database definition scripts, dml
for reports or initial data creation scripts, doc
for programmer’s documentation, html
for all the things that go under a web server. This way, ddl and dml scripts don’t end up under you web site and get picked up by search engines. You don’t want the world to know your database design or passwords, right?adding primary and foreign keys
, creating indexes and constraints
and commenting columns and tables
.What is the big deal with all this? Almost any software developer programs like this. Problem is, there are lot of people in the web field with no prior experience developing other types of applications. They tend to focus on the presentation part and not the underlying architecture. This works fine for guest book and poll scripts. Not for bigger applications.
That is why I like Zope and Python. It is still possible to write code that looks like a legal brief in these, but these platforms scream out the value of refactoring - or making building blocks and then assembling these. Perhaps that’s why people with database experience and no web experience (not even HTML) found Zope to be pretty easy to use, while people with only web experience find it an impossible hurdle to cross!
If you are here, that means you were not bored. Repeat I will refactor my code 3 times before you start any new coding project
There are lot of case tools out there that can help you with this. But believe me, none of them are as simple or effective as plain old post-it notes. If you master these tools, these will certainly help. But it is a steep climb. I know only Oracle Designer. I can personally vouch that it is amazingly complex - amazingly powerful too.
Oracle Designer is only a 'Process' Driven Tool.
agree or disagree with the above statement