24,076 reputation
352103
bio website
location
age
visits member for 4 years, 2 months
seen yesterday

Oct
25
comment My coworker created a 96 columns SQL table
key value stores are almost alawys the worst choice for perfomance and queriability.
Oct
25
comment Biggest mistake you've ever made
Actually your biggest mistake was in not developiong against a database of the appropriate size. Never use a small test datbase to develop for a large production database. You can't write performant code unless you have the right sized dabase.
Oct
25
comment Biggest mistake you've ever made
Which is why updates should be done on dev first! No hot fixes directly to prod. And be very grateful for audit tables if you have them when you do this.
Oct
25
answered How to gain understanding of large systems?
Oct
25
answered Which comments instantly ring alarm bells when a programmer says them?
Oct
22
comment Job hopping, is it a problem?
And BTW HLGEM is a she not a he.
Oct
22
revised Job hopping, is it a problem?
added 4 characters in body
Oct
21
answered How can I bootstrap a software development community at my school?
Oct
21
answered How do programmers quit a job?
Oct
20
comment What's stopping Oracle from supporting identity (auto-numeric) columns?
GUIDs can significantly slow down performance compared to integre identities. And I haven't yet seen anyone who wants to write queries using them in the where clause. I can ask a user to give me the person_id of the record (Name not being a unique identifier) that they think is a problem, I can't even show them a GUID or the average user freaks out. GUIDs are far worse on a day to day basis than identities. So to solve a happens-every-once-in-a-while problem, you permanently cripple you system. Seems short-sighted to me. Now if you are doing replication yes you need them.
Oct
20
comment What's stopping Oracle from supporting identity (auto-numeric) columns?
Strongly disagree. The idnetity column is the least troublsome in a complex system becasue it doesn't change. And very, very few "natural" keys really are unique and unchanging as they should be. As fara as import/export, etc. I do that daily and it's not hard at all, you just set up a cross match table and you are in business.
Oct
20
answered How do you portray to non programmers what programming involves?
Oct
19
answered What legal considerations do I need to have when programming?
Oct
19
answered How to recognize a bad client before you start to work for him?
Oct
19
answered Managers X Motivation
Oct
14
comment Production-safe SQL stored procedure debugging
I disagree, stored procedure are the best place for this kind of complex database logic. They are easier to preformance tune and easier for the dba to knwo what is affected by proosed changes to the data model and far more secure (if you aren't useing dynamic sql) because you can prevent direct access to tables and views. In a financial application, not to use stored procedures means your application is very open to internal fraud.
Oct
14
answered Production-safe SQL stored procedure debugging
Oct
14
answered What's wrong with circular references?
Oct
12
answered Being a good mentor
Oct
12
answered What do you consider to be the prime cause of software defects (and how to minimize them)