24,136 reputation
352103
bio website
location
age
visits member for 4 years, 3 months
seen 2 days ago

2d
comment How to keep legal rights when hired to make a program
I think in general if you accepted the contract, the rights belong to the peopel with the money not the developer. I have never seen a case where the dev had the rights to code written on someone else's dime. Nor should they have the rights to it. If it wanted, it needs to be negotiated before the contract to provide the work is signed. Consult a lawyer for if it is even possible in your legal jurisdiction, these things tend to favor the corporation over the individual in most countries.
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.
Oct
1
comment Databases: Where should the application logic run?
Stored procs can be as subject to SQl injection as prepared statements, that is not the only security need that can be handled by stored procs. When you use prepared statements, you have to grant access at the table/view level. When you use stored procs the access can be at the stored proc level only and thus no one can do anything that is not in the proc. If you combine that with not using dynamic SQl, then it is more secure. In a financial system for instance it would be a necessary internal control to not allow anyone except the admins to do anything to the database not defined by a proc.
Sep
30
answered Databases: Where should the application logic run?
Sep
18
comment How much pair programming is ideal?
@JeffO, for an introvert, it would almost certainly be exhausting as person interactions suck energy from them and private timerenews the energy. I can see it as demanding too as it would be harder to take a few minutes break to think of something else which some people need because they tend to problem solve with their unconcious brain. Plus you have to deal with negotiating personality and and work style differences all the time. It exhausts me to even think of it.
Sep
18
comment How much pair programming is ideal?
THe answers would range from 0 - 100%. As an introvert, personally I find it can be effective, but If I had to spend 100% of my day attached to another person, I would run screaming out of the room. 10-20% would be fine. If you feel uncomfortable with the 95%, then go with your gut feel that this is not the job for you. It doesn't matter what anyone else would choose.
Sep
16
comment Using JOIN keyword or not
Of course that left join syntax never did provide the correct results reliably (see BOL for SQL Server 2000) so even if it was faster, I would have replaced it.
Sep
12
awarded  Nice Answer
Sep
10
awarded  Yearling
Sep
9
awarded  Necromancer
Sep
4
awarded  Good Answer
Sep
4
comment Stored Procedures a bad practice at one of worlds largest IT software consulting firms?
@Quant_dev, if you are accessing a database you must care about performance. It is attitudes like yours which is why I see so many badly designed and poorly performing datbases. That is not optional and that is why database specific code is often preferred, but it is almost alawys more performant.
Aug
16
awarded  Nice Answer