Thanks for sharing. That's an interesting approach.
Do you have any example of applying the boy scout rule?
Our team is improving test coverage along with the development, but that's the only thing I can think of. I'm wondering if you have any other example of tackling technical debt when doing development task.
A really great article !! Thanks a lot for your work and for mentioning me. I’m deeply grateful and honored 😊. Looking forward to your upcoming projects and/or future ideas !!
Thanks for sharing. That's an interesting approach.
Do you have any example of applying the boy scout rule?
Our team is improving test coverage along with the development, but that's the only thing I can think of. I'm wondering if you have any other example of tackling technical debt when doing development task.
Thanks Adler, happy it's useful for you.
Look at this example:
- Your team is working in a new feature that involves a backend and a frontend.
- Once your team adds new code, your team could also refactor the existing code.
Actions over the existing code could be:
- Add some test that was pending
- Act in some TODO that was pending from previous pull request
- Revisit the way the package organization
- is the use case "X" still valid?
- Are we keeping good separation of responsibilities?
What do you think about this Adler?
Let me know if you want me to provide more examples, happy to help on this 😉
I see. Thank makes sense. Thank you!
I've always tried to apply the boy scout rule. It's a great habit and no need to ask for extra time.
Thank you for the shout-out at the end!
Thanks for sharing Rafa!
Sometimes we feel the pressure to deliver news stuff, but taking time to technical debt always pays off.
A really great article !! Thanks a lot for your work and for mentioning me. I’m deeply grateful and honored 😊. Looking forward to your upcoming projects and/or future ideas !!
Thanks to you Lorenzo for replying my email an propose something to write about that solve people's problems!