- #1
rigetFrog
- 112
- 4
I've been maintaining and updating some legacy code for a while at my job. These Dilberts came up the other day
http://www.dilbert.com/2014-08-11/
http://www.dilbert.com/2014-08-12/
I see people disparage others work/code all the time, and it frustrates me. I give people credit / benefit of the doubt for making the best decision at the time. However, I'm starting to think my acceptance is holding back my career.
Like every engineer, I think it's easier to re-write than to modify, but my bosses priority is to be as efficient as possible with my time, and re-writing has a large over head in time. But some times, I genuinely think the last guy did a pretty good job. I suspect saying so, i.e. "hey, the last guy did a pretty good job with this code" to my boss reflects poorly on me and impede my career.
Here's my concern and pro-con analysis.
_____
Pro's of re writing
allow me to take ownership and credit for it.
makes it easier to debug in the long run.
I get more hands on learning experience
_____
cons of rewriting
Large investment of time
_____
pro of not re-writing
Boss potentially saves time
_____
Cons of not re-writing and just maintaining
My perceived contribution is very little. (Even though modifying code is very hard)
Boss will grieve losing previous employee that did a good job.
_____
What are the PF community's thoughts on this?
http://www.dilbert.com/2014-08-11/
http://www.dilbert.com/2014-08-12/
I see people disparage others work/code all the time, and it frustrates me. I give people credit / benefit of the doubt for making the best decision at the time. However, I'm starting to think my acceptance is holding back my career.
Like every engineer, I think it's easier to re-write than to modify, but my bosses priority is to be as efficient as possible with my time, and re-writing has a large over head in time. But some times, I genuinely think the last guy did a pretty good job. I suspect saying so, i.e. "hey, the last guy did a pretty good job with this code" to my boss reflects poorly on me and impede my career.
Here's my concern and pro-con analysis.
_____
Pro's of re writing
allow me to take ownership and credit for it.
makes it easier to debug in the long run.
I get more hands on learning experience
_____
cons of rewriting
Large investment of time
_____
pro of not re-writing
Boss potentially saves time
_____
Cons of not re-writing and just maintaining
My perceived contribution is very little. (Even though modifying code is very hard)
Boss will grieve losing previous employee that did a good job.
_____
What are the PF community's thoughts on this?