You have special expertise in database design. How is what you do different from what a generalist computer programmer might do when it comes to creating a database back end?

Jules Bohanon, Lakeland, Florida:
     Sorry, but I don't know the mind of a generalist programmer, so I'm not sure I can answer this. I will say, I am very strict about normalizing databases, and on several projects I've "taken over," the database design has been sloppy. "Normalizing" is a technical term, and I don't tend to use it with my customers, so if you're not familiar with it I'd be glad to define it.

Assem Bayahi, Mourouj 1, Tunisia:
     A database designer must aim for the future.

Md. Obaidul Haque Sarker, Dhaka, Bangladesh:
     A computer programmer always thinks the coding approach of the software. Their design meet the functional requirement of the software, but not non-functional requirements such as performance, adaptability. But they don’t know better way to design the database.
     A professional database designer or DBA design the database in optimized way. A DBA knows better way to design the database. So, DB design professional rate is higher.

Ehtisham Rasheed, Sialkot, Pakistan:
     the main difference is that i didn't start physical database design at the beginning which is the root of major problems during back-end database connectivity and operations...

Christian Koch, Berlin, Germany:
     My approach is different because I have created programming rules over the years.

Mark Horner, Bristol, England:
     Well I tend to follow best practice – you may ask given my background how do I know what best practice is, I know because I have done substantial reading on relational database theories and going to the Nth degree with the pros and cons of each. I will look at the requirements, and see what data needs to be stored and work out the best way on how to store it and ensure it allows the integrity of the data to stay intact.

Ven Grollmus, George Town, Tasmania, Australia:
     A lot of the run of the mill programmers will get a brief understanding of what the client wants, then jumps in and starts building the database. They then find out down the track, that something has been missed, and need to go back and change the whole structure of the database and coding to accomplish what was missed. What I do differently, and this has been learned over 20 years, is to gather the business requirements from the client, document the requirements, and ensure that the client it happy with the requirements gathered. This gives the client a physical document that they can take to their key stake holders, to ensure that a crucial part of the work process isn't missed, and that all data and business rules are covered. This then means less work and re-work because of oversights.

Bruce Bray, Phoenix, Arizona:
     A lot of programers I talk to merely create tables and use them as a data store, which is really not much different than a file system at that point. I actually use aspects of SQL such as user defined functions, stored procedures, indexes, views and triggers to create efficient applications as well as enforce business logic.

Yuriy Sultanaev, Ufa, Russia:
     - Using ORM
     - is harmful in large amounts of data and small projects

Temitayo Ilori, Berea, Ohio:
     The database I design have data integrity and there is no data redundancy.

Grace Elaiza Seballos, Davao City, Philippines:
     I do not really what makes me different from generalist computer programmer. Maybe if I will compare myself back in highschool, the time where I still do not know how to use SQL. I create my own database management using "Bucket Chaining" technique. When I was an OJT of a software development firm, that is where I learned about SQL, normalization, and data integrity.

Artiben prashantbhai S., Bhavnagar, India:
     I do it with relational tables and the field names are quite understandable.. Table names start with tbl..