3 ms·
Not really strong enough in a post about what to do in a codebase you’re not familiar with. In that situation you’re probably new to the team and organisation a
by jbjbjbjb 6mo ago
Not really strong enough in a post about what to do in a codebase you’re not familiar with. In that situation you’re probably new to the team and organisation and likely to get off on the wrong foot with people if you assume their code “hurts”.
- hamburglar 6mo agoThe post is “here’s what I do”, not “here’s what you should do and then confront the team about the results.” It’s just showing you a quick way to get some insights. It’s not even guaranteeing it’s accurate, just showing you some things you might be able to draw some quick conclusions on. I’m not sure why HN attracts this need to poke holes in interesting observations to “prove” they aren’t actually interesting.
- jbjbjbjb 6mo agoIt’s a bit reductive to call it poking holes. The author shared his valuable knowledge and I shared mine.
- hamburglar 6mo agoYou said this analysis “isn’t strong enough” for an inadvisable scenario you completely invented.
- deleted 6mo ago[deleted]