Originally Posted by Amackera
Mind you, I'm hired as a Quality Assurance analyst, and I JUST finished a db installation along with a migration from one system to another! I should be billing the company at 400$ an hour! lol
Yeah, you should... the most important thing on any system is how it is setup initially... it's a thorough pain to change at a later date and so most systems basically keep that initial setup. If it has a performance weakness, that's going to last for 5-10 years and will affect everything.
And, if some wiseass does try to fix the weakness at a later date, they are quite likely to break something else... databases are very fragile !
My rules for IT professionals;
1. Be Lazy. Do it once, do it right and then leave it alone.
2. Be Forgetful. Document everything that you do. Even if you are the person who needs to maintain it, you will have forgotten what you did within 6 months and so you give yourself the notes so that you don't have to re-engineer it.
3. Be Disorganized. Put the documentation in the code. If it is anywhere else, it will not be updated and will probably get lost.
4. Be Stupid. Ask the dumb questions that no-one else wants to ask. Mostly, the answer will be the obvious one, but just occasionally something surprising may be revealed.
5. Avoid Technical Solutions. When someone asks you for a technical solution to a problem, check whether there is a manual process that would work instead. Get the manual process working and only then consider automating it. Automating a bad manual system results in a terrible automated system. Automating a good manual system helps everyone.
6. Do not Multi-Task. Few people can do it well. Get your projects prioritized and work on one at a time. Get it to a clean status (even if not finished) before starting on another one. Otherwise, you end up with 25 half-finished projects... most of them are kinda-sorta working and so your boss won't let you waste time finishing them properly but there are continual issues that need fire-fighting and disrupt everything else.
7. Cheat. Use something else that does 90% of the job, use someone else's code if it does what you need, ask someone else for help if you have questions, look for information on the Net, if you need it. IT is not about "all my own work", it's about finding solutions. The 1% of people that might gripe about stealing their code are outweighed by the rest of us that are honored by it.