Job frustration
-
new job.
very old system. expected to work daily with unpaid overtime for the course of next whole year.
sounds ok if you like programming. except...
- the "developer document" to explain data relation is just displaying table and it's column names. no explanation on keys relationship.
- system is OVERLY FLEXIBLE. they(the original designers) would want to think their system is flexible. you can "configure it to your heart's content" from the front end. but really, it's not enough. you'll have to also program the logic. a complicated mess. thousands of repeated codes. and some codes has extra checking which has no explanation.
- a database view calls a view which calls another view which joins another view. OVERLY DEPENDENT on views. DB is not hidden from the programmer.
sure I can redevelop a new system. but new clients keep coming in, the mess will amplify, the project "can" support multiple clients on same website. more mess, more headaches. the ppl here all look like zombies, having no life besides work work work.
HUARGHHHHHHHHHHHHHHHHHHHHHHHH
-
@zzzxtreme said:
the ppl here all look like zombies, having no life besides work work work.
You mean the people on TDWTF?
-
@b-redeker said:
@zzzxtreme said:
the ppl here all look like zombies, having no life besides work work work.
You mean the people on TDWTF?
You mean people?
-
You can use HTML in your posts to make them more readable...
-
@zzzxtreme said:
new job.
very old system. expected to work daily with unpaid overtime for the course of next whole year.
sounds ok if you like programming.
Doesn't sound ok to me.
@zzzxtreme said:
1) the "developer document" to explain data relation is just displaying table and it's column names. no explanation on keys relationship.
I'm going to take a wild-ass guess and say that the relationships are also not encoded in the database itself, so you can't just query for them?
@zzzxtreme said:
2) system is OVERLY FLEXIBLE. they(the original designers) would want to think their system is flexible. you can "configure it to your heart's content" from the front end. but really, it's not enough. you'll have to also program the logic. a complicated mess. thousands of repeated codes. and some codes has extra checking which has no explanation.
Yup. Huge problem.
@zzzxtreme said:
3) a database view calls a view which calls another view which joins another view.
That's actually not necessarily a WTF, depending on how complicated the views are.
@zzzxtreme said:
the ppl here all look like zombies, having no life besides work work work.
Remember you have to kill the brainstem to kill the zombie!
@zzzxtreme said:
HUARGHHHHHHHHHHHHHHHHHHHHHHHH
OH NO YOU'VE TURNED INTO ONE OF THEM!!!
-
yayyyy I quit. and they grant my request for early release!
-
