3 ms·
I feel this is a bit more nuanced. You need to account for what is likely/possible to happen in the future. There's no "easy to change" that remains that way. T
by viraptor 5y ago
I feel this is a bit more nuanced. You need to account for what is likely/possible to happen in the future. There's no "easy to change" that remains that way. To give a specific example, I've recently created some small apps for automating interaction with a terrible-enterprisey-crud software. The first one was written as a quick script. The next one had some organisation but remained a crappy script. The next one as well... The problem is that now I need to maintain the previous scripts for a very long time. Every new app I make now abstracts the windows it interacts with into separate controller classes. I made the change in my approach too late and it's both too much work to rewrite everything written initially and it's really annoying to support it too.
I know it's a bit of a hindsight thing, but the time to change the approach was when I was about to write script no 2. I should've invested a little bit of time into research and proper structure, but didn't. A bit of complexity saved me in later development...