Quotes About Troubleshooting

What about the Vimes manual, then? snapped Vimes. I notice you've never bothered to learn how to use me! The demon hesitated. Humans come with a manual? it said. It'd be a damn good idea! said Vimes. True, murmured Angua. It could say things like 'Chapter One: Bingeley bingeley beep and other damn fool things to spring on people at six in the morning, said Vimes, his eyes wild. And 'Troubleshooting: my owner keeps trying to drop me in the privy, what am I doing wrong?

You could say I'm on the troubleshooting squad." "Troubleshooting?" He put a hand on the back of his waistband. "I see trouble and I shoot it.

There has never been an unexpectedly short debugging period in the history of computers.

Making a movie is a lot of problem solving.

If you don't find problems quickly, you end up finding them months later. By then, the problem is lost in all the other changes that every other developer made, so the link between cause and effect disappears without a trace.

Who's been calling you, and what do they want?" I ask, frowning. "Usually it's other it people who are having problems fixing something," he replies, rolling his eyes. "When something goes down, I'm apparently the only person who knows where to go looking.

I like problem solving. I like taking a crisis, breaking it into manageable pieces, and finding a solution. I don't like the minutiae. I don't like paperwork." "You

La culpa es mía por ser el informático del departamento: cuando las máquinas se estropean, agito mi pollo muerto y escribo encantamientos vudú en los teclados hasta que vuelven a funcionar.

A PEBCAK is a Problem that Exists Between Chair And Keyboard.

For instance, if a computer does not power up, you can start testing at the electrical socket; move to the power supply, power supply connectors, power switch, motherboard; and then move to the devices. This process moves through the sequential chain along the possible path that power would flow. Following a possible resolution path from one end to the other is sometimes referred to as the layered or linear approach.

There has never been an unexpectedly short debugging period in the history of computers.

The strangest problems often turn out to be misconfigured DNS. DNS

soldering himself. When they completed a board, they would hand it off to Wozniak. "I would plug each assembled board into the TV and keyboard to test it to see if it worked," he said. "If it did, I put it in a box. If it didn't, I'd figure what pin hadn't gotten into the socket right." Paul Jobs suspended

In theory, cars are fairly simple. If they don't start, it's either the fuel system or the electrical system. Teach yourself about the path of each in your engine and tracing it is fairly straightforward. But at the beginning, mastering each new system seems like an unreachable shore. The car is effectively a black box.

When a watch is broken you take it apart to analyze what is wrong with it. When a technique does not work, if you analyze it carefully you can always find out what is wrong.

I prefer to think about problems the way engineers do. If a valve doesn't work, they don't say, "Well, we must have valves, so let's try two valves." If a valve doesn't work, they say, "Well, what would work?" Their rule is, if it doesn't work, don't do it more, do something else.

If a user is having a problem, it's our problem.

Those highly trained armor specialists were responsible for major repairs, upgrades, and modifications, but in Alicia's opinion, anyone who didn't want to stay hands-on with the standard maintenance and, especially, troubleshooting of her own armor just before a drop ought to be confined somewhere in a nice, soft-sided room where she couldn't hurt herself or anyone else.

that solving problems is what leaders do. The day you are not solving problems or are not up to your butt in problems is probably a day you are no longer leading.

I spend almost as much time figuring out what's wrong with my computer as I do actually using it.

By my estimation, dating was 1 percent confidence and 99 percent troubleshooting.

Designers need to focus their attention on the cases where things go wrong, not just on when things work as planned.