3 ms·
The only thing harder than "understanding bad code" is "explaining to your manager why you're going to need oodles of time to accomplish simple things because t
by JohnBooty 5y ago
The only thing harder than "understanding bad code" is "explaining to your manager why you're going to need oodles of time to accomplish simple things because the code is bad."
I've been in this industry for a couple of decades and I'd consider sacrificing a limb if the latter could somehow become easy.
- Waterluvian 5y agoAgreed. Two comments: 1. I’ve had some luck using the “I have to clean the work site before I can assess the situation” analogy. 2. I’ve learned to refactor bad code as an effort to learning it, even if the refactor is not going to be pushed into the codebase. For me this is the best way, by far, to figure out messy code.
- kkapelon 5y agoI prefer the "let's clean the kitchen first, before trying to cook new dishes"
- 908B64B197 5y agoIf the manager isn't technical or won't understand, that's a red flag for the org/company.
- JohnBooty 5y agoI wish I shared your optimism. At this point I think it is a red flag, even if your manager DOES understand. Because chances are THEIR manager won't understand. Or their manager's manager. Etc. You will look bad no matter what. At this point I am beginning to think it is basically a no-win situation. No matter what.
- JohnBooty 5y ago(Maybe "no-win" is not literally true. In a literal sense, I suppose I really mean: "Dismally low odds of winning, best not to get into such situations")
- 908B64B197 5y ago> Because chances are THEIR manager won't understand. Or their manager's manager. Etc. You will look bad no matter what. Maybe that's why FAANG and top 5 capitalizations all have former engineers as CEO.