Database geeks
One thing I've noticed about this group versus the php group; You guys don't work 16 hours a day, or live, each, and s**t this subject, like the PHP guys do.
I make the assumption that most of you are more mature, steady eddie types who do throrough planning in your projects and have less emergencies during there rest of the night. Also, perhaps, being one layer removed from the customer interface means less complex UI problems to get hammered on day and night, and therefore less to go wrong and less opportuntity for it to go wrong.
Perhaps this is a result of the cost of failure?
What I mean to say is that very often database apps have to deal with *huge* volumes of data. As such, you could end up wasting *hours* if your app doesn't work correctly.
With PHP dev, for the most part, you refresh your browser to test. If it doesn't work right you make a quick change and you're off.
My $0.02
--------------------------
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
Show quoted text
-----Original Message-----
From: Dennis Gearon [mailto:gearond@cvc.net]
Sent: Friday, June 20, 2003 3:51 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Database geeksOne thing I've noticed about this group versus the php group;
You guys don't work 16 hours a day, or live, each, and s**t
this subject, like the PHP guys do.I make the assumption that most of you are more mature,
steady eddie types who do throrough planning in your projects
and have less emergencies during there rest of the night.
Also, perhaps, being one layer removed from the customer
interface means less complex UI problems to get hammered on
day and night, and therefore less to go wrong and less
opportuntity for it to go wrong.---------------------------(end of
broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
Import Notes
Resolved by subject fallback