Hacker News new | ask | show | jobs
by nakedlunch 1917 days ago
On point 4 - I do think it’s tempting to say “we used to do it this way at my old place, and it was much better”. I call it “at my old place” syndrome.

However, if you never take your learnings from place to place, that’s also pretty useless isn’t it?

I think it’s more about how you communicate those learnings. Perhaps start by not suggesting they are better, just that you’ve also seen it done a different way in the past (I.e. avoid “at my last place...”) and you’re wondering why we do it this way instead. People are going to be much more receptive to not opening with “I know better”, especially because when you do it this way you often find they’ve already tried it the way that your previous place did it and it didn’t work for them for very straightforward reasons.

1 comments

I think it's good to take notes on how you could improve things based on past experience for the first 30-60 days. Keep the notes to yourself. Review after you have more experience in the team.

You'll either find that the suggestions have some merit, in which case you'll have more credibility to make them, or that you learned enough about the new environment to know they weren't useful.