3 ms·
If you are a developer and good at what you do, you will layer your application to buffer against changes. That's a good place to start. That's 80's and 90's b
by stcredzero 11y ago
If you are a developer and good at what you do, you will layer your application to buffer against changes.
That's a good place to start. That's 80's and 90's best practice, though. (Most of the industry is stuck in this mindset, to be fair.) I'd say the 21st century version of this would be to structure your code in such a way that transformation tools can be easily applied.
- partisan 11y agoSo you understand my point.
- stcredzero 11y agoThe code architecture "win" is always to dodge the big manual rewrite. The "lose" is to have to do the big manual rewrite. People make it into a game of ideological purism, but really, it's as simple and pragmatic as just that. They who dodge the manual rewrite -- those are the real gurus.
- partisan 11y agoBeing a guru and finishing product have close to 0 correlation. It doesn't matter how you would've/could've/should've done it if in the end, you didn't do it. I'm just trying to encourage OP to finish a product and we've gone pretty far from that starting point with this discussion.
- stcredzero 11y agoBeing a guru and finishing product have close to 0 correlation. Finishing a project and the number of large-scale manual rewrites tend to be negatively correlated.