DON'T Refactor Your Code If...

[anirudhganesh]

don't worry, you'll upgrade the Gradle and it'll fuck up everything for you

[jenovas]

I'd say this is a bad practice. You should keep your code as clean as possible and should refactor even if you don't need to.

Don't create tech debt or your company will drown in it just a few years down the road. Went through it, it ain't a nice experience.

Imagine hiring new talent, imagine trying to get back to code nobody any longer understands 3 years later. Imagine joining a project with a codebase being one huge mess, because "it works so don't touch it".

It's a lot easier to do small incremental improvements all the time instead of building up so much tech debt that you need a system rewrite later they will take a year to do.

So please do refactor your code, please so keep it up to date, please don't create tech debt cause you are lazy and don't want to spend an hour a week improving your old codebase, you not doing it just makes everyone later hate their job and hate the codebase.

[DalvinderSinghSandhu]

When I read or learn about android from articles or blogs, I feels its hard to understand everything but I watch your videos I feel everything is so easy
Love you man, you make our life easy ❤❤

[ban_droid]

I think we still have to give ourself a challenge on refactoring our old project which makes us know wether we're improving or not, cause when i'm looking up at my project when i'm starting to code, it makes me think "why i ever write a code like this?!?!" And refactoring it into better implementation makes me understand what i have learn before

[luciferGOD]

So Philippe is trying to teach us how to become good manager now, not developer 😂😂 because these words we generally hear from our managers 😂

[larrybird]

You refactor code to make it more manageable and clearly to understand if you don't your code is not manageable and can not be clearly understood so scaling or adding any sort of feature in the future will be a huge issue also if your code is running more efficient its cheaper to run in the cloud and most important part if you refactor the code there is no more bottleneck to the person who coded it, now that same code can be passed on to anyone with no time wasted trying to figure it all out

[ChrisAthanas]

If you do have the urge to refactor, take a not of the time you start and leave a comment for the next dev to tell them how many hours you worked on it before giving up and reverting the changes...

Ie: "Beware thar be dragons here!"

[redaelmadini]

I disagree with you as this decision usually depends on the coverage of the tests written for this project. They are there for this reason. Even poor quality test code is as important as the main code.

[maximooze]

Lets re-phrase your advice here @Philipp. "Sometimes its better to stop being dogmatic", saves alot of time, money and respect from your peers.

[vinaykumarpatel]

I recently joined new company, they have very old source code which has zero unit tests, so called MVC architecture, they have not seperate the different layers everything is mess, UI instances accessed everywhere. 95% their existing issues are related to UI only. I proposed to rewrite the App with all latest technologies and the CTO says no we have to refactor existing one. Total bullshit, I’m looking for new role in meantime now. So sometime the decision is not in our hand, even if you try to convince your leaders by telling them pros and cons they don’t understand and the result is very poor app. The app in my company has 2.6 star rating.

[prageeth]

Only refactor for performance tuning or new requirements for ever changing Android architecture, if it’s a must. Else leave it there until you have enough free time to get into it 😅

[snnim]

Something i should have been taught way before 😌

[chinesischesser]

I have to disagree. It's a boyscout rule to leave the code always cleaner than before. I it's about to take small steps, so you don't run out of time. I just recently split a 3000 line method in two 1000 line methods. It's it still shit? Yes, but better than before

[tarekrefaei]

But sometimes you may have some ideas about improving some existing features or correcting some terrible things in it... we already laze don't encourage us to be more 🤣🤣

[PandukaDeSilva]

Not sure I agree with you on this one though, Nokia did the same thing and we all know how that ended up 😜

[zareenwilhelm]

WHO is this video FOR??? 😂 enjoy spaghetti 🍝

[abderrahimelgomri]

you will know that when you work as a professional . if it works don't touch it

[CriticasDeCriticas]

Just one thing!
If you are going to do new implementation on it, consider refactoring it