javascript-professionals
-
-
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." (Now I've forgotten who said it; I had to find a post by leppie to get it.) Need a status? Make one. Need a second one? Go right ahead. Need a third? Hey! They don't grow on trees! It reminds me of a job I used to have... I was assigned the maintenance of the credit card processing part of the system. Each member's account had fields for credit card number, type, and expiration. So far so good. Then we got a new client who wanted a backup credit card... OK, we added a second set of credit card number, type, and expiration plus a field to indicate which one was used last time to the table. Then we got another new client who wanted to do EFT and before anyone told me about it, they added account and routing number (or whatever) to the table. When I went to talk to the DBA and suggest we should have some sort of PaymentSource table that could have any number of sources associated with an account. His response was that, although it was a good idea, the inmates had taken over and there was nothing we could do at that point. X|
-
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach." (Now I've forgotten who said it; I had to find a post by leppie to get it.) Need a status? Make one. Need a second one? Go right ahead. Need a third? Hey! They don't grow on trees! It reminds me of a job I used to have... I was assigned the maintenance of the credit card processing part of the system. Each member's account had fields for credit card number, type, and expiration. So far so good. Then we got a new client who wanted a backup credit card... OK, we added a second set of credit card number, type, and expiration plus a field to indicate which one was used last time to the table. Then we got another new client who wanted to do EFT and before anyone told me about it, they added account and routing number (or whatever) to the table. When I went to talk to the DBA and suggest we should have some sort of PaymentSource table that could have any number of sources associated with an account. His response was that, although it was a good idea, the inmates had taken over and there was nothing we could do at that point. X|
PIEBALDconsult wrote:
The rule of three: "The first time you notice something that might repeat, don't generalize it. The second time the situation occurs, develop in a similar fashion -- possibly even copy/paste -- but don't generalize yet. On the third time, look to generalize the approach."
Yes, very true.
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon