Refactoring is cleanup code WHEN you touch the same code again. To be able to refactor you should have written enough test that will make sure you don't fuck up the old code. This is the way that works for me. I build, write test, and refactor.
The pace sometimes dictates what a DEV can or cannot do. Example: Deployment on Friday night, Business logic changes on Mon, Tue, Wed, Thu, and Fri cause they could not figure it out for over the three weeks before (meaning it was a tight schedule till deployment). I do 100% agree with you in the kitchen (since I roughly started the same as a kid) and when coding.
Love this type of content Jason, we can tell a lot of work has gone into this. Great storytelling as well! I only know you from livestreaming, but this is a whole new level 🚀
Oh man, I come from kitchens too!😂 I actually got this advice from a very experienced friend of mine after I asked him how can I start documenting a huge code base. He said the furst thing to do is cleanup every chance you have. Thanks man for the content and for the effort! How wad yiur experience creating this one?
it was fun! this was a brand new approach for me, so lots of things I see that I want to improve next time, but I learned a lot and I'm excited to keep making more like this 💜
We call it boyscouting. Leaving the place better then you found it. It is highly incentivised to do so to get that sweet additional praise during a PR code review ;D
it's hard to compress a real-world example into a comment, but one example might be: you're assigned a ticket to update the notifications in the app dashboard, and while you're in there you notice a TODO comment from the initial push to launch it where a shortcut was taken that makes this code harder to maintain. As part of building the new change, you might be able to clean up that small mess as part of making your changes more future proof and easier to maintain. It's very case-by-case, and there's balance (e.g. you can't refactor the whole app as part of a PR), but small, incremental improvements add up over time into a much cleaner codebase.
Coming from 15 years of hospitality I can agree 100% on this mindset ❤
Refactoring is cleanup code WHEN you touch the same code again. To be able to refactor you should have written enough test that will make sure you don't fuck up the old code. This is the way that works for me. I build, write test, and refactor.
Goes for anything in life! Love this Jason
Can't wait to this getting into Netflix
The pace sometimes dictates what a DEV can or cannot do. Example: Deployment on Friday night, Business logic changes on Mon, Tue, Wed, Thu, and Fri cause they could not figure it out for over the three weeks before (meaning it was a tight schedule till deployment).
I do 100% agree with you in the kitchen (since I roughly started the same as a kid) and when coding.
Love this type of content Jason, we can tell a lot of work has gone into this. Great storytelling as well! I only know you from livestreaming, but this is a whole new level 🚀
thanks so much!
awesome video man you clearly put so much work into it♥
This. 100% this. Thanks for making this one. So relevant.
Oh man, I come from kitchens too!😂
I actually got this advice from a very experienced friend of mine after I asked him how can I start documenting a huge code base. He said the furst thing to do is cleanup every chance you have.
Thanks man for the content and for the effort!
How wad yiur experience creating this one?
it was fun! this was a brand new approach for me, so lots of things I see that I want to improve next time, but I learned a lot and I'm excited to keep making more like this 💜
Best tech advice ever
I like this
We call it boyscouting. Leaving the place better then you found it. It is highly incentivised to do so to get that sweet additional praise during a PR code review ;D
But how? Show me some bits of cleaning!
it's hard to compress a real-world example into a comment, but one example might be: you're assigned a ticket to update the notifications in the app dashboard, and while you're in there you notice a TODO comment from the initial push to launch it where a shortcut was taken that makes this code harder to maintain. As part of building the new change, you might be able to clean up that small mess as part of making your changes more future proof and easier to maintain.
It's very case-by-case, and there's balance (e.g. you can't refactor the whole app as part of a PR), but small, incremental improvements add up over time into a much cleaner codebase.