@bstorer said:
@unfriendly said:I am going to have a serious talk with these persons come mondayWhy are you waiting until Monday? Did you write the serious talk down and mail it back to them?
The snailmail takes until monday to arrive...
@bstorer said:
@unfriendly said:I am going to have a serious talk with these persons come mondayWhy are you waiting until Monday? Did you write the serious talk down and mail it back to them?
The snailmail takes until monday to arrive...
Not the most hilarious post of the day... but still... I had a good laugh when it happened.
We are building reports for a large retailer. To validate the reports we need to verify the reports to what the stores have in their systems.
Fine, we pick a store, pick a couple of weeks, email one of our superusers and get him to ask for reports from the store for that timeperiod.
We wait a couple of days... then the boss walks in with a 4" thick envelope addressed to us...
Turns out this is how a report request is processed.
Us -> email superuser -> superuser calls store manager -> store manager generates excel report from store system -> store prints excel report -> store faxes excel report to superuser -> superuser puts 100 pages of fax into envelope -> snailmails it to us.
I am going to have a serious talk with these persons come monday... how can this pristine business process work without them using the wooden table and crappy camera provided by us!
Plz give me ur SSN and PIN so I can see the wtf and also deposit $10k in your accounts
The database I am currently working on contains around 1500 tables.
I would personally mutilate anyone with the bright idea to name the pk of every table to "ID".
You don´t want to spend 10 minutes checking the business logic everytime you look at the column named ID in a temp table and wonder what the hell it is referensing
It would perhaps work in a small application that is web-oriented and has no cross-referencing... but not in a full-scale business system.
*Selfexplaining* naming standards is a good thing... *Confusing* naming standards kills kittens...
The database I am currently working on contains around 1500 tables.
I would personally mutilate anyone with the bright idea to name the pk of every table to "ID".
You don´t want to spend 10 minutes checking the business logic everytime you look at the column named ID in a temp table and wonder what the hell it is referensing
It would perhaps work in a small application that is web-oriented and has no cross-referencing... but not in a full-scale business system.
*Selfeplaining* naming standards is a good thing... *Confusing* naming standards kills kittens...