Fellow programmers will feel my pain
Dec. 1st, 2009 11:07 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
We're in the midst of a crash development project, that's being sandwiched in around November close, prep for year-end and everyone's understandable desire to take vacation days before they lose them.
The goal is to build a new subset of the corporate spend database. Last week they created a test database for this project and I've been asked to pull sample data to load into it so we can start the analysis.
- The corporate spend database model has 12 dimensions.
- The test model that they built for me has 18 dimensions. The person who built it is on vacation this week and no one can explain why we have the 6 extra dimensions, or whether or not it is safe to delete them and go back to the regular 12 dimensions.
- The SQL queries that load the corporate spend model create an output file with 42 fields (dimensions). Several of these dimensions are obvious duplicates (three different formats for department numbers, for instance) but no one can explain to me which of the 42 fields are used to load the 12 dimensions in the corporate model and which ones are ignored. The expert on this is too busy to talk to me, and the backups are... you guessed it, on vacation.
And now the project lead is IM'ing me to ask why we haven't been able to load sample data yet.
The goal is to build a new subset of the corporate spend database. Last week they created a test database for this project and I've been asked to pull sample data to load into it so we can start the analysis.
- The corporate spend database model has 12 dimensions.
- The test model that they built for me has 18 dimensions. The person who built it is on vacation this week and no one can explain why we have the 6 extra dimensions, or whether or not it is safe to delete them and go back to the regular 12 dimensions.
- The SQL queries that load the corporate spend model create an output file with 42 fields (dimensions). Several of these dimensions are obvious duplicates (three different formats for department numbers, for instance) but no one can explain to me which of the 42 fields are used to load the 12 dimensions in the corporate model and which ones are ignored. The expert on this is too busy to talk to me, and the backups are... you guessed it, on vacation.
And now the project lead is IM'ing me to ask why we haven't been able to load sample data yet.
(no subject)
Date: 2009-12-01 05:02 pm (UTC)(Yeah, right. I'll wait while you stop laughing.)
(no subject)
From:(no subject)
Date: 2009-12-01 05:24 pm (UTC)I hope you can get it smoothed out with a minimum of bloodshed and tearing out of hair!
(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
Date: 2009-12-01 05:33 pm (UTC)(no subject)
From:(no subject)
Date: 2009-12-01 05:42 pm (UTC)(no subject)
From:(no subject)
From:(no subject)
Date: 2009-12-01 11:45 pm (UTC)When I was in Naval Aviation Electronics school years (decades?) ago, we were going over a circuit schematic and noticed that it used way more diodes than was really needed to do the job. The instructor said it was a result of the "brother-in-law effect." Yeah, the circuit designer's brother-in-law manufactured diodes.
Dave
(no subject)
From:(no subject)
Date: 2009-12-02 02:36 am (UTC)Yeah, this kind of thing (on a smaller scale) happens all the time where I work. Of course, mostly that's because we have N the Network Guy and his sidekick S instead of, like, a proper IT department, but there's also the issue of "Oh, you mean when you said 'database' you meant an Access database? Doesn't an Excel worksheet work the same way?" ::facepalm::
(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
From:(no subject)
Date: 2009-12-02 02:37 am (UTC)(no subject)
From:(no subject)
From: