3 ms·
If you're in the middle of development and craving for rock hard solid systems, you don't fuzz around changing everything here and there, quite probally somethi
by ichverstehe 19y ago
If you're in the middle of development and craving for rock hard solid systems, you don't fuzz around changing everything here and there, quite probally something you shouldn't be touching, you're asking for a breakdown. And when it comes, you're OK, because, that's the way it's supposed to be, and most important:
You will definitely learn something from the recovery process!
- henning 19y agoIf there are many different things you could change on a production system you're probably doing something wrong. You should have as little software on it as possible, for security and stability reasons.
- ichverstehe 19y agoI just read my post again. A bit drunk, so I missed some points. Duh. Basically saying the same as you. Sure thing, on a production system / server / whatevz don't screw around. But on non-critical systems it can be rewarding to break things. When I break my system I need to realize WHAT I broke and WHY it broke and HOW to fix it. In the end I have learned something that will help me setting up stable production systems. No?