Quotes About Maintenance

My dad was always busy. You would pop round for a cup of tea, and within minutes you would see him walking past with a step-ladder. He was always fixing things.

A single Sherman tank took three hundred man-hours to waterproof, occupying the five-man crew for a week.

Roads deteriorated in the autumn rains, and a dearth of spark plugs, fan belts, and tools hampered mechanics; one company with forty-one trucks possessed a single pair of pliers and one crescent wrench.

I've got two old Volvos, two old Subarus, and an old Ford Ranger. If you've got an old car, you've gotta have at least several old cars, 'cause one's always gonna be in the garage.

A sense of the past is far more basic to the maintenance of freedom than hope for the future. The former is concrete and real; the latter is necessarily amorphous and more easily guided by those who can manipulate human actions and beliefs.

Fruit is definitely on the maintenance diet. It's on the lifestyle diet.

Always keep your home presentable, assuming you keep a home for purposes of presentation.

Why don´t you fix bad code when you see it? Your first reaction upon seeing a messy function is ´This is a mess, it needs to be cleaned' . Your second reaction is ´I'm not touching it!´. Beacuse you know that if you touch it you risk breaking it; and if you break it; it becomes yours

When you see commented-out code, delete it!

I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance close to optimal so as not to tempt people to make the code messy with unprincipled optimizations. Clean code does one thing well. -Bjarne Stroustrup, inventor of C++ and author of The C++ Programming Language

If we all checked-in our code a little cleaner than when we checked it out, the code simply could not rot.

Duplication is the primary enemy of a well-designed system.

If you let the tests rot, then your code will rot too. Keep your tests clean.

Good software designs accommodate change without huge investments and rework. When we use code that is out of our control, special care must be taken to protect our investment and make sure future change is not too costly.

The primary cost of maintenance is in spelunking and risk. Spelunking is the cost of digging through the existing software, trying to determine the best place and the best strategy to add a new feature or to repair a defect.

The fact that we did not have a database running for 18 months of development meant that, for 18 months, we did not have schema issues, query issues, database server issues, password issues, connection time issues, and all the other nasty issues that raise their ugly heads when you fire up a database. It also meant that all our tests ran fast, because there was no database to slow them down.

The goal of software architecture is to minimize the human resources required to build and maintain the required system.

The majority of the cost of a software project is in long-term maintenance.

Recall that the goal of an architect is to minimize the human resources required to build and maintain the required system.

One of the best ways to ruin a program is to make massive changes to its structure in the name of improvement. Some programs never recover from such "improvements." The problem is that it's very hard to get the program working the same way it worked before the "improvement.

the architecture of a system has very little bearing on whether that system works. There are many systems out there, with terrible architectures, that work just fine. Their troubles do not lie in their operation; rather, they occur in their deployment, maintenance, and ongoing development

Architecture should reveal operation. The architecture of the system should elevate the use cases, the features, and the required behaviors of the system to first-class entities that are visible landmarks for the developers. This simplifies the understanding of the system and, therefore, greatly aids in development and maintenance.

O objetivo da arquitetura de software é minimizar os recursos humanos necessários para construir e manter um determinado sistema.

It doesn't take a huge amount of knowledge and skill to get a program working. Kids in high school do it all the time. Getting it right is another matter entirely. When software is done right, it requires a fraction of the human resources to create and maintain.