3 ms·
rule 1 dont try to be clever by refactoring rule 2 underpromise so you can overdeliver. if you dont meet your short deadline they'll think you're lazy or incom
by uncomplexity_ 2y ago
rule 1 dont try to be clever by refactoring
rule 2 underpromise so you can overdeliver. if you dont meet your short deadline they'll think you're lazy or incompetent. if finish in your long deadline they'll think you are employee of the month. always x2 or x3 your estimates.
rule 3 hang out with the seniors, listen to them. they know the landmines and how things are. not only in technical but also in office politics.
rule 4 spend time with people closest to your end users. this may be your sales people and support people. they dont code, they dont know the inner technicals, but they know the things that matter business wise.
- bodegajed 2y agoThanks, yes, refactoring. Please allow me to vent. First, I totally agree with you on Rule No. 1. I would never refactor legacy code or suggest a rewrite. It's always a terrible idea. The downside is that I worry I might look like a ghost engineer. This is why I hate this industry sometimes. I heard about this paper at Stanford on ghost engineers a few weeks ago. Where LOC as their basis, it's just absurd. It went to the mainstream media as well, but looking at the paper, it has no metrics on the non-coding aspect of programming. It seems the industry hates the dev, like we should not be paid this high. Did execs make poor product choices? Let's fix this by increasing shareholder value by another round of layoffs. Which department? Engineering, we have metrics who does not provide enough value!