![]() |
|
|
|
|
__________________
This advertising will not be shown in this way to registered members. Register your free account today and become a member on AllDeaf.com |
|
|
|
#2 (permalink) |
|
Registered User
|
There should be a facepalm emoticon, cause I thought of this strip this exact situation came up this afternoon.
ME:"Data is supposed to show up" Manager: "No, no data is a good thing, it means you've done your job!" ME: "I can prove I didn't do my job" Manager: "We fixed it a month ago" ME: "Well your supervisors didn't really clarify what was supposed to happen, is there any code or documentation about the code being changed?" Manager: "uhhh...let me talk to my supervisor" |
|
|
|
|
|
#3 (permalink) |
|
Registered User
|
In addition to that break, there's no way to fix the 2nd step "Mistakes" that are supposed to be "follow-up" on.
It's like a game of ping pong but you have to follow the rules and not hit the ball twice..you just have to trust that the 1-2 process "ping-ponging" is completely correct. CA state government should ban object-oriented database usage. |
|
|
|
|
|
#8 (permalink) |
|
Registered User
|
I know...that's why I used the word "ban".
It was probably not *that* important for the Contractor to test the reports before the contract was actually up (I haven't seen the contract, but I do know that any changes now costs $$$). The original design was based off a fully functional relational database that was designed, built and maintained by analysts. The Contractor just took the "reports" section from that section and guessed what it was and then ported it over to the new object-oriented database. Part of it too is that management doesn't really know our jobs and language to understand what's a problem and what's not. |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|