arithma wroteThe amortized value of an employee is quality x rate.
That's actually true. But still, no matter how good you are, certain solutions require significantly more time to implement.
arithma wroteThere's definitely a problem that you're trying to share, which has some more specifics and context to this question. Maybe for more help, you'll need to share more.
Not exactly. But it has happened on several occasions that I was forced to do things that could have been done in a much better way.
rtp wrotewhich will cost more on the long run, but if thats is the time they give me then that is what they will
get, i can't make miracles...
This is exactly what I try to explain to the project manager every time. The good thing is that he is very understanding and knows that a bug which costs $100 now, will probably cost $1000 to fix when the project goes live. But eventhough he does understand that, sometimes he makes it clear that we cannot afford investing 3 days working on a feature when it can be done in a 4-6 hours the "hacky" way.
rahmu wroteI behave differently at work, from when I'm coding in my free time and posting on LebGeeks. I don't particularly enjoy it, but sometimes work simply cannot afford "the correct way". I have written half assed code that's used by several teams now, and I don't have the time/budget to work on improving them. People have developed crazy tricks around bugs in my software, we won't fix this unless we have a very good reason to.
We have all done that before, we're in the same boat my friend. But what really bothers me is that this is plain wrong by all means! It makes me sad to write a piece of code I cannot be proud of. And it makes me feel horrible when I see other colleagues with less experience adopting things I've done "the wrong way" as a pattern. And then I have to explain that this is a bad practice and they shouldn't be doing stuff this way, while in fact I did it myself :)