If I write this correctly it'll be the last guide you'll ever need to read about pull requests. Aimed at software engineers of all levels my hope is you'll better understand why Pull Requests (PRs) matter and how to write/review them... and then share this post with your friends/team to achieve the same.
This is one piece in a soon-to-be complete series named "Profit Engineering". What's that, you ask?
Profit Engineering is what I call the art of writing code to generate profit for a company.
Put another way: writing code that makes more money than it cost to create & maintain - not code that's perfect, "cool", or impressive to interviewers.
This requires a different way of thinking and can be uncomfortable at first, but time and time again this mindset has proven invaluable to many a business and can undoubtedly increase your perceived value as a contributor...
Top comments (0)