How To Write Code You Love (& Still Finish On Time)
Вставка
- Опубліковано 1 лип 2024
- This is my simple yet effective strategy to enhance code quality without compromising on feature delivery timelines.
📖 Chapters:
00:00 Intro
00:44 The pressure cooker
02:14 The Two Commit Rule
03:31 Its unexpected origin
05:13 Putting it into practice
06:46 Beyond the code
🚀 Let's connect
www.jcfontecha.com
/ jufontech
/ jfontech
#softwareengineer #bigtech #selfdevelopment
Love how practical and actionable advice this is. It’s just not the same as having an intention or ideal of “writing good code”. I tried it today at work and you’re right, it does feel like I was finally striking the balance (I did not even know I was lacking) between progressing fast and contributing to keeping/maintaining our codebase clean.
I will be sharing this with my team, hopefully we can adopt it as part of the team culture. I can see how this would benefit us all in the long run.
Can’t wait to see more of your new videos!!
This is awesome to read. Thank you for watching and sharing! 🙌🏻
A nice pleasant way to introduce code refactoring
Small PRs are critical to a healthy team / code review culture. You're dead on about PR titles and descriptions setting context and scope for the reviewer. I like the two commit idea, but I'm curious about a couple of things that are outside of the scope of this video. Is the 2nd commit just an additional step to force yourself to clean up the code, or does it exist as a separate commit that can be removed if the reviewers are resistant to the improvements? Do you apply PR fixes after the improvement commit, or do you rebase and place them before the improvement commit?
That's a really good question. Originally the thought behind the second commit was just that it's a fairly common and atomic "unit of code change" if you will 😄 and can (should?) be small enough to remove the friction of actually doing it. But I agree that there's the added benefit that if there's disagreement with the change or if reviewers think the cleanup would benefit from a separate PR, you can always just revert it. About the second question, I actually hadn't thought about it! I usually default to just addressing feedback on top of everything, but you bring up a good point, for more delicate matters a rebase might be worth it! Thanks for watching, by the way!
Hello, Juan! How are you? Hope you're doing great!
Thanks for sharing another amazing video!
Have an amazing weekend ahead!
Cheers from Brazil!
Thank you so much for the continued support Eduardo! Hope you're doing well too! 🙌🏻
Hello sir. Sir I am not good at maths so can I learn and practice dsa and actually become good at it??
Yes! I actually failed a lot of my beginner math courses. Practice will definitely help you. Best of luck!
I think you don't need the constant zooms in and out