Sort By:
+38 Rank Up Rank Down
Sep 20, 2013
because of overly complex relational database?

more likely: "schema? we don't need no stinkin' schema! we'll just store everything everything as json - in the CLOUD!!! structure & input validation just slows down the developers - they know what they're doing!"

fast forward 3 months: "what do you mean 10% of the records don't have {pick an attribute}, 50% have it but with various names, 20% have multiple conflicting values & 20% are actually 'clean'?!? how the H3__ did that happen?!?!?"

gee, I have no idea...
Sep 20, 2013
I hate Friday status meetings.
Sep 20, 2013
Yes, much of that means the same as "Lazy Management".
+51 Rank Up Rank Down
Sep 20, 2013
It's surprising that an engineer of D's experience thinks he can get away with this - giving a technical excuse to a non-technical manager almost always backfires.
+81 Rank Up Rank Down
Sep 20, 2013
It must be near the end of the project's life. The hunt for a scapegoat is already beginning. Or is this the fixing the blame phase. I always got those mixed up.
Get the new Dilbert app!