Advertisement

Danielcmorris Login Name
Premium Service Member Account Type
29,139 Expert Points
10/18/2003 Registration Date
0 Points this month
Member Profile:
http://morrisdev.com

I run a small business making web based database interface systems for small to mid-sized businesses.  I'd talk about my degrees and certifications, but I just don't have time to get any.  I've hired people with all sorts of these certifications, but the best people have always been the grunts who only ever did programming because they needed to get something done.  People who don't care how it "Should" be done, just that it "Gets" done.

I'm a coat hanger and duct-tape kind of guy.  I can pull a V8 Engine apart and put it back together with no problem.  I can speak English, Spanish, and French. However, my engine repairs always have an extra piece left over and my  verb conjugation sucks.  When it comes right down to it, my engine runs and people understand what I'm trying to say to them in other languages.

I started building Access Databases in 1996, moved to SQL Server in 99 and started using ASP as the frontend interfaces in 2000. It wasn't until a few years ago that I gave up listening to fights between managers who wanted the impossible and developers who insisted that, no matter what it was, it be done in Java.  I watched dot-com after dot-com go down the tubes because developers spent so much time making things work .00002% faster or writing them in such a solid manner that they couldn't flex with the business environment.  

My business is primarily Intranet, not Internet.  When I make a contract I always tell the director that he/she can have a system for $20,000 and it will work on all browsers, or, if he/she has the authority to tell the users to use strictly IE 5.0 or better, the system will be done faster, do more and cost half as much.  The decision is usually made in less than a minute.

So, I tend to use IIS,  I don't care if it takes 2 seconds for a page to load, I don't even care if variables are dimensioned.  I want it to work.  If there is a speed or memory issue down the road, I'll fix it.  However, it is much more likely that they will want 50 changes to the design before that happens.


Basically, my motto is, "If it works, and your client is happy, don't fix it. -just bill them"
 
124 Questions Participated In
356 Comments Posted
 
61 Questions Asked
0 Questions Open
57 Questions Graded
4 Questions Deleted