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
Speedy emails, satisfied customers
Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.
Read next
Debugging HTTPS localhost: httponly cookie issues
0x2e Tech -
BLACK HOLE ANIMATION WITH HTML CSS AND JAVASCRIPT
Prince -
Combine 5 Trained Models: A Practical Guide
0x2e Tech -
Fixing Z-Axis Character Jitter: A Practical Guide
0x2e Tech -
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...