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
Read next
AI Breakthrough: Context Analysis Boosts Visual Puzzle-Solving Accuracy to 76%
Mike Young -
Implementing Route Guards in React: Protecting Your Routes with Authentication and Roles
Abhay Singh Kathayat -
React.js Explained: A Comprehensive Guide to Building Modern Web Applications
Abhay Singh Kathayat -
Toggle Switch Realistic illusion using the core html and core Css Code
Prince -
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...