One Diff, One Thesis

One of the biggest and easiest ways to level up your code doesn't even lie in the code itself and is about how you split it up when submitting it for code review instead. This lesson will teach you:

• The most common way low-performing software engineers mess up their code when submitting it for review
• Why championing the concept of "One Diff, One Thesis" massively boosts your productivity alongside your code quality
• How to tell whether your pull request follows the principal of "One Diff, One Thesis" or should be broken up into smaller pull requests instead
• How to split up your technical task or project into chunks, so you can map out its pieces to a series of pull requests following "One Diff, One Thesis". We do this with an in-depth example further digging into the login flow