in my experience, very FEW withstand the test of time, any “legacy” application I worked on have code that was the best way , over-complicated and useless subclassing just for the sake of have thousands of lines of code when in reality, everything could have been done with a fraction of the code;
never do something that is unnecessary(subclassing like crazy, using frameworks that just came out, interfaces all over the place for the sake of hiding implementation, etc.), do the bare minimum that does what it should and you’re future self will thank your younger version
Every single day.
That’s me migrating a large Laravel 4 project to Laravel 5.
been there… #refactoringwhilereleasing
This is me today realizing that the app sending the email is at fault and not the email I created. And launch is early next week.
in my experience, very FEW withstand the test of time, any “legacy” application I worked on have code that was the best way , over-complicated and useless subclassing just for the sake of have thousands of lines of code when in reality, everything could have been done with a fraction of the code;
never do something that is unnecessary(subclassing like crazy, using frameworks that just came out, interfaces all over the place for the sake of hiding implementation, etc.), do the bare minimum that does what it should and you’re future self will thank your younger version