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

Apr
23
awarded  Good Answer
Apr
22
awarded  Good Answer
Apr
21
awarded  sql
Mar
24
revised What to do when client have unrealistic expectations?
added 3 characters in body
Mar
16
revised When should I stop programming / coding?
edited body
Feb
23
revised How do you respond to: “Ever since the update…” questions from clients?
added 956 characters in body
Feb
22
awarded  Nice Answer
Feb
18
comment Why is naming a table's Primary Key column “Id” considered bad practice?
Try writing something with 30 joins and you will see why it is an antipattern.
Jan
21
comment How to make significant technical decisions given very little time
It takes less than ten minutes to set up the structure in a spreadsheet (the most complicated part is deciding what factors you want to compare priorities on) and then it is easy peasy to fill in.
Jan
20
answered How to make significant technical decisions given very little time
Jan
9
revised SQL Triggers and when or when not to use them.
added 11 characters in body
Jan
6
comment Why is prefixing column names considered bad practice?
I never write a production query without aliasing all the columns. It makes maintenace so much easier. Of course I write complicated reporting/export type queries with up to 10-20 joins and 30-50 columns and six months later it is hard to remember which table that column came from.
Nov
12
comment What is the appropriate way to handle implicit requirements?
The implict part had to do with how we were handling exceptions and what those really should have been. The people who did it thought they were just common sense but since they introduced a bug...
Nov
12
comment What is the appropriate way to handle implicit requirements?
For the record, both performance and security should under no circumstances be implict requirements. Making them implilct is why so many systems have bad security and worse performance.
Nov
12
answered What is the appropriate way to handle implicit requirements?
Oct
23
awarded  Necromancer
Oct
8
comment Databases and Unit/Integration Testing
Again to re-iterate, you cannot unit test sql code agaist a blank database or opne with few records, you lose the meaning of the query and a query with correct syntax is irrelevant if it returns incorrect results. Ther result set is what you need to test not just the syntax. Unit testing for data is far differnt thatn application unit testing.
Oct
2
comment Databases: Where should the application logic run?
I agree that the Hybrid approach may be the best one.
Oct
2
comment Databases: Where should the application logic run?
@MatthieuM. and you may have requirements that don't allow that. And you may not even own or be allowed to change all the applications. You may need to use 3rd party applications which don't allow that.
Oct
1
comment Databases: Where should the application logic run?
No you absolutely cannot do the same thing with views. Yes you can limit what specific field can be updated through views, but with stored procedures you can specifically limit the particular actions that can be taken by a user in a much more detailed way. YOu can make them have to do multiple tasks for instance in a particular order on different tables which you can't do by managing securty through views. In a financial system, if you do not use stored procs your system is wide open for fraud.