If your code comments are sufficient enough to tell a story, why do we onboard engineers using pair programming?
For further actions, you may consider blocking this person and/or reporting abuse
If your code comments are sufficient enough to tell a story, why do we onboard engineers using pair programming?
For further actions, you may consider blocking this person and/or reporting abuse
env0 Team -
Manouk Draisma -
Gittech -
Bharath S R -
Top comments (1)
I never get onboarded using pair programming. There is usually some explanation required about the business domain, but other than that the code should speak for itself, without comments. For example i dont give two shits if you have a comment in your React component
// side-effectsfollowed by a bunch of
useEffecthooks. I can already tell its a side-effect from the fact that it's wrapped in auseEffecthook...