This is a common problem. This issue plagued me early in my career. Some may disagree, but I'd suggest always writing the best code that you reasonably can, even if this means doing some unpaid over-time. You'll find that given time, people will come to recognize and respect this work ethic, and you will be able to move on to opportunities where you have more leverage to do things the 'right' way.
OO can help. Concentrate on developing robust modules, which can be re-used. More work up front, but you will be building yourself a valuable tool-chest to carry with you throughout your career.
There is an old book called 'Code Complete' by Steve McConnel which still has a lot of relevance to this issue. Good luck.
Slashdot Mirror
This is a common problem. This issue plagued me early in my career. Some may disagree, but I'd suggest always writing the best code that you reasonably can, even if this means doing some unpaid over-time. You'll find that given time, people will come to recognize and respect this work ethic, and you will be able to move on to opportunities where you have more leverage to do things the 'right' way. OO can help. Concentrate on developing robust modules, which can be re-used. More work up front, but you will be building yourself a valuable tool-chest to carry with you throughout your career. There is an old book called 'Code Complete' by Steve McConnel which still has a lot of relevance to this issue. Good luck.