Slashdot Mirror
The Worst Development Job You've Ever Had?
manavendra asks: "I'm currently working for a solution provider for telcos, and as part of product migration the entire API has to be 'internationalized'. Owing to a legacy architecture, most (if not all) application logic is still embedded in PL/SQL stored packages. My job: find hard coded strings, and replace with calls to the globalization API.
Yes there is a script written to handle most tasks, but its quite primitive (not to mention fears of automating 'too much'). Boredom is at all time high. Have tried all means of whittling away the time, and hence this question to other Slashdot users: What's the worst ever job you had to do in the name of 'software development' (or as a software developer)?"
- We need to use the most expensive JSP interpreter we can find.
- We need to use the most expensive JSP IDE we can find.
- We need a separate computer for each person (including those who will work primarily from their computer located off-site), plus a test server and a backup for the test server and an extra computer just in case.
- We need to make the database as related as possible - if you can make a lookup table for a Yes/No field, then by all means you should do it!
- Make sure each and every table has an auto-increment integer index, expecially those tables that will contain over 100 million records.
- Development time must take at least 18 months to provide a proof-of-concept, but cannot produce anything that may be actually used.
Needless to say, I was kicked off the job and threatened with being charged under the Patriot's Act for complaining about the job on my BLOG. Now, I'm out of that environment and wrapping up a 4-month conversion of a VB/SQL2000 application to PHP/PgSQL. Practically the same job, but I really love this one.The previous comment is purposely vague and generalized, but all of the facts are completely true.
I landed in the middle of a project that had been in development for TWO YEARS, and was poster child of evil software engineering malpractices: hardcoded numbers and strings, no separation of content and logic, no coding standards, no comments, no docs, no NOTHING. Mixes of PHP, javascript and HTML in the same line. Copied and pasted javascript code that nobody knew what it did, but when pasted in worked. And, of course, with fire-breathing bosses looking over your shoulder. And with crappy dell computers on 14" monitors that gave 70Hz at 800x600. I had left a job coding java in a decent environment with people from wich I could learn lots, but switched for the money. Not long after that I realized there's more than money to a job. I left that job with the begginings of stress-induced breakdown I would suffer a month later, and a vow to never again work anywhere before asking about the documentation policy.
Well, I feel your pain on most of your post...but, in the area of database...if there isn't a proper natural key for the primary key, I'm a big fan of sequences and triggers to generate unique integer primary keys. And if the database is to be on a RDBMS, then hell yes, it had better use a related model...gotta be normalized. If you have a good model, the rest will fall in place.
However, I will agree with you about the expensive gear, but, with Gov. rules, they pretty much rule out trying to do things with open source...something I try all the time. Heck, have linux on many desktops around here...but, they are trying to get them out....and forcing that NMCI piece of crap down everyone's throat....
But, I gotta speak up for the database parts you complained about....you can't shortcut on that...ESPECIALLY if you are dealing with 100+ million records....
Light travels faster than sound. This is why some people appear bright until you hear them speak.........