Reputation
24,872
Next tag badge:
83/100 score
18/20 answers
Badges
3 54 106
Newest
 Nice Answer
Impact
~910k people reached

Oct
8
comment Database is performing slow, even all the tables are having normalization
I would never suggest denormalization as the first performance fix. This is the fix of last resort as it often creates data integrity problems. And I certainly would never mention it without discussing how I would avoid data integrity problems and how denormalizing could slow inserts/updates/deletes but speed up selects. Likely proper indexing would make the normalized tables perform well without the risks of denormalizing.
Oct
7
comment How to code review without offending other developers
'The code doesn't progress until the reviewer approves it, and the reviewer won't approve it until the questions are answered." I thnk this is key. If you do code review after teh code has moved to Qa or even prod, then people will resist chaning it even more. If they know that they have to pass code review, they will be more open to making changes.
Sep
24
awarded  database
Sep
23
comment Sprint planning and accommodating slack
@KrisVanBael, in an ideal world yes. But I would wager that most people who think they are doing agile do not plan that way. Of course I would also wager that many of the organizations that think they have agile processes, don't.
Sep
17
answered Best practice in application design / SQL authentication
Sep
11
answered Why isn't protection against SQL injection a high priority?
Sep
11
comment Is rotating developers on a project a good or bad idea?
What I would suggest is that you make the intital team that starts the project composed of some current legacy devlopers and some current new project devlopers. Keep them through the porject. At the end the lagacy devlopers support the new product and the new devlopers join some other legacy developers to do the next project. That way the team is teh same through the project (Or major release) but legacy people get up to speed on what they will be supporting later. New hires shoudl generally start on legaacy unless they have some special skill you team doesn;t havea nd needs for the project.
Sep
10
awarded  Yearling
Aug
13
comment What makes C so popular in the age of OOP?
This answer is also the answer to why do we still need SQL!
Aug
13
answered Safely fixing production database data
Aug
10
awarded  Nice Answer
Aug
5
revised How should I deal with problems with completed stories in agile
fixed typos and capitalization
Jul
30
comment How to create better OO code in a relational database driven application where the database is poorly designed
This book might give you som eideas of how you can start to fix the datbase problesm and keep the legacy code working: amazon.com/…
Jul
29
awarded  Nice Answer
Jul
29
comment Does dealing with legacy code help one evolve as a programmer?
@RossPatterson, since this is banking, yeah I hope they really do work correctly now. At anyrate if there are no tests, then the risk of making a change is huge in banking and writing unit tests to help you learn the system should be an easy sell.
Jul
29
comment Does dealing with legacy code help one evolve as a programmer?
It also helps you to understand taht the method you think they should have used was not available when the code was written.
Jul
29
answered Does dealing with legacy code help one evolve as a programmer?
Jul
22
comment Getting related foreign keys from parent entities
If you do denormalize, you need to maintain the client_id through triggers on all the relevant tables. It is the only way to ensure consistency no matter how the data is changed. (There is an exception for bulk inserts which can avoid triggers but peopel doing this type of thing generally know to reproduce the trigger code they are avoiding after inserting or updating the ten million records.)
Jul
19
revised How to represent days and time graphically for a project I have done
fixed spelling error
Jul
18
answered Good Practice : Storing variables and classes names in database for direct call