24,739 reputation
354105
bio website
location
age
visits member for 4 years, 7 months
seen Apr 23 at 14:33

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
Jul
9
answered Is there value denoting a key as “Primary”?
Jul
8
comment What are some possible interactions between multiple bugs?
I would add that sometimes a particular bug may result from a poor understanding of a type of code and that poor understanding may be elsewhere. I'm thinking of things like failing to handle the case where a divisor turns out to be zero or someone who never handles nulls correctly. Each implementation may be a different formula or unrelated piece of code but the same fundamental misunderstanding of what to do is through the application. Sort of like Entropy sprinkler only the code isn't necessarily related except through the coder's misunderstanding of how things work.
Jul
5
awarded  Guru
Jun
26
comment Should we persist with an employee still writing bad code after many years?
I suspect this guy woud be absolutely flabbergasted to find out that his manager is thinking of firing him. Some people you just have to hit over the head with a plank and flat out tell them that they have to improve or they will be fired.