I have over 20 years of database experience. and over 40 years of work experience. I am seriously old.
The most important thing to remember is that data has meaning and the developer needs to understand that meaning to get correct results and the database should never be used as a black box that the dev doesn't need to understand.
The next most important thing to remember is that the data will persist for many years longer than the current application and that it is usually critical to the operation of the business. As such, data work should generally be the number one priority in development in an Enterprise environment instead of the afterthought.
Virginia, United States
Member for 8 years, 1 month
6 profile views
Last seen Apr 16 '13 at 17:48
- The Workplace 137.4k 137.4k 2626 gold badges242242 silver badges501501 bronze badges
- Stack Overflow 83.2k 83.2k 1111 gold badges9595 silver badges159159 bronze badges
- Software Engineering 28k 28k 44 gold badges6464 silver badges111111 bronze badges
- Database Administrators 3k 3k 1313 silver badges1717 bronze badges
- Meta Stack Exchange 279 279 11 silver badge66 bronze badges
- View network profile →
Top network posts
- 469 Can a foreign key be NULL and/or duplicate?
- 288 How should I deal with an employee who has slept with my wife?
- 241 My employer is forcing its employees to defraud its customers, how should I handle this situation?
- 224 If you're overwhelmed at work, how do you choose what takes precedence?
- 222 Team members spending too much time on Stack Overflow
- 202 How to deal with a workplace that spreads you too thin?
- 175 Use email address as primary key?
- View more network posts →