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, 9 months
485 profile views
Last seen Jul 13 '18 at 16:46
- The Workplace 139.1k 139.1k 2626 gold badges245245 silver badges506506 bronze badges
- Stack Overflow 87.6k 87.6k 1111 gold badges104104 silver badges169169 bronze badges
- Software Engineering 28.3k 28.3k 44 gold badges6565 silver badges114114 bronze badges
- Database Administrators 3.1k 3.1k 1414 silver badges1818 bronze badges
- Meta Stack Exchange 279 279 11 silver badge66 bronze badges
- View network profile
Top network posts
- 576 Can a foreign key be NULL and/or duplicate?
- 298 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?
- 225 Team members spending too much time on Stack Overflow
- 224 If you're overwhelmed at work, how do you choose what takes precedence?
- 204 How to deal with a workplace that spreads you too thin?
- 180 Use email address as primary key?
- View more network posts →