Depressing code
I have seen some code that may require serious consulting sessions, but this is probably the most depressing piece that I have seen so far:
And before you ask, it is about people...
I have seen some code that may require serious consulting sessions, but this is probably the most depressing piece that I have seen so far:
And before you ask, it is about people...
No future posts left, oh my!
Comments
Erm..."CreateDeathProcess"??
Please tell me you are not trying to take over the universe...'cause, ya know, that kinda interferes with my plans to do so :D
Is this for a mortuary or an HR department to deal with laid off / terminated folk?
Can you post the code?, I'm always thinking about a routine that can kill someone :D
Alk.
Well, I suppose it makes sense, in isolation, as long as there's never a need for a 'OnKillDeathProcess' below the current 2 classes.
Let me guess: It is for a hospital. If someone dies, there must be some procedures fulfilled. The original developer had a strange kind of humour and a knack for design patterns.
I once had to write a method called MarkDeceased to handle ticking a checkbox when a patient dies. Yeah, pretty depressing.
Jon,
ERP for a nursing company.
Markus,
See my comment above.
The design is actually solid, but the details are horrifying because the domain is so depressing.
The property list for some of the entities...
You should send it to the WTF site.
Comment preview