A highly maintainable Design is a Key for coding

If we get used to the OOP, we know this it often mentioned the concept about "reusable", actually that bring different lay ERs of meanings about software design, one could is, if it's reusable, then we'll be able to use it in new software with Less effort.

I think the real problem for a coder, was that, we had developed some software, and changes always happened, whatever it ' s A upgrade, a new feature request, or sometimes we move it for another use, we'll have an it for this case.

to the change existing codebase, could is a nightmare, if it ' s complex due to a large amount of code, or bad design. The reason is quite simple, if the code isn ' t well designed for maintenance or flexible enough for different use and then Cha Nging the codebase, could break the logic of the system design, thus it'll bring more uncertainty of it, usually means m Ore bugs. Because of the uncertainty, we could trap in the bug loop, fixed one, brought another, and forever, the worst, the Whol E changes bring the software to a wrong direction, eventually to fix it isn ' t an option for cost.

as a coder, I really dislike to waste time in maintain codebase when it's bad for maintenance, it's like someone is push ing you into a puzzle map, you just see a bit clue around you, but never get to know the whole picture of it, the long Tim E Lonely walk certainly would kill us patience, especially when someone was there call us out, and whipping we into a stres Sful State for reporting progress. Unfortunately, that's usually happened as what a project owner cared was the progress, progress means cost, cost means money, Now we know why.

But as a-coder, to-write a software, we take the maintainability-to is the first case of all, could help us to write bet ter software, maintainability isn ' t really as same as "reusability", as maintainability are all about the caring of Ourselv ES, its more like a special healthy care insurance for coders, if we had it done, we'll be benefit on it for a long Tim E.

Also to write a better maintainable software, was Also pushing you to think it more, and choose a better solution, could fo Rcibly bring your speeding race slow down, have a cup of tea, ease your mind, and then focusing on the problem, get the Solution, it'll increase your lifespan, seriously, we all know a high speed spinning gear'll be less lifespan, so do O ur organs.

There could be a lot different ways to write a better maintainable software, whatever it oo, or not oo, the key is, think ing more about it.

To has fun with it, I considered how to maintain a database design more easily, and I wrote a small NodeJs code to genera Te SQL from OOD style description of database design. Take a look, it might still work or not.

The plain text to describe the database table and its relationship by OO methodology, and generate Differen T SQL create scripts for different SQL Server.

Https://github.com/hellomaya/db-test/tree/master/oosql

A highly maintainable Design is a Key for coding