4 ms·
- Mimicking the existing coding style a bit too closely - including some of the mistakes which made some stuff brittle, despite having some reservations about i
by MaulingMonkey 10y ago
- Mimicking the existing coding style a bit too closely - including some of the mistakes which made some stuff brittle, despite having some reservations about it.
- Kicked off a major refactoring which I wasn't able to secure time to finish, leaving behind partially refactored code. Would've been better to break it up into several smaller refactorings, instead of having the codebase straddling two different styles of doing the same stuff.
- Not reaching out to the rest of my coworkers aggressively enough. I annoyed my lead a bit by asking him all my questions at the beginning.
- Not pushing back heavily enough on code readability in reviews, leading to a couple of mudballs (generally under a KLOC fortunately, but still hard to figure out in a couple cases.)
- Crunching, firefighting, and not taking care of myself better.
I also didn't start with any real experience with project management, time estimation, or the art of managing expectations and keeping managers in the loop - although I managed to learn quickly enough to stay out of trouble, for the most part.