3 ms·
Probably can troubleshoot a bit. How do you know they don't like you? What's your guess as to why?
by xyzelement 3y ago
Probably can troubleshoot a bit. How do you know they don't like you? What's your guess as to why?
- Supermancho 3y agoI almost always clash with someone who rather spend the team's time trying to do it right (for whatever that means to them) as opposed to sooner. This is often expressed as "making a second change is more time than taking a week to think about it carefully the first time". What's more, the results: * turns out it's a delaying tactic to avoid doing work * feature creep * added complexity, which is brittle (feature has to be reworked, nobody is happy) * constant nitpicking + the assumption that you will adopt their higher standards Is this better? For some projects maybe. At least we have alerts that go off every day and nobody pays attention to them and multi-tiered shared libraries that result in esoteric problems (mostly from package upgrades) that affects projects X, but not Y and Z. Not to say these engineers don't add value, but they are daily problems that everyone has to work around. This includes product stakeholders.
- Exoristos 3y agoDo you not have leadership? Whether to ship classy or shoddy work sounds like a business decision.