3 ms·

Potentially the problem could be that their constant hurry could stress out other team members (including me). They could forget about the fact that not everyon

Potentially the problem could be that their constant hurry could stress out other team members (including me). They could forget about the fact that not everyone is accustomed to their way of thinking. I mean, sometimes, well thought out ideas can be more beneficial in the long term as well. Others could drop out or lose motivation as everything is changing so fast.

withinboredom 5y ago
Don’t stress. That’s rule number one. Nobody is going to die if you don’t go faster and it’s not a race. Instead, slow them down to speed you up. Review their code, even if it’s been merged already (introduce them to post-commit reviews)! Most of my code is actually reviewed this way — a basic requirement to keep momentum on a team spread over 3 continents. But anyway, ask questions. Ask the why’s and seek to understand. Ask lots of questions. Whomever seems the nicest or jives with you the best, ask to pair program after lunch or something. You do the typing and let them do the talking. Learn from them, don’t argue or come across as judgy. Just learn. Eventually, you’ll be a fast one too and one day you’ll get a review on some code you merged a few days ago…