Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
If it can be modified or improved, do it.
If you don't schedule maintenance, your equipment will schedule it for you.
The external struggle in manufacturing:
“My machinery is having too much downtime. It needs comprehensive maintenance.”
Ok, I need 12 solid hours and I’ll give it back to you good as new.
“What?! 12 hours! That’s insanity, it’s already racked up 20 hours of downtime this month, I can’t spare 12 hours! Can’t you just do it next month?”
Repeat every month.
An ounce of prevention is worth a pound of cure.
Software
That's how you get into tech debt, stuck with entire infrastructure written in COBOL.
And even for purely UI changes, the UI totally impacts user adoption. Eg, a 90s style grey everything form is going to feel outdated to many users and they'll associate that with the rest of the software being dated (regardless of whether or not it's true). If your goal is adoption/sales, you often have to keep changing the UI even if it's not broke with regards to functionality.
Preventive maintenance? As in, where you take your car in every year for an oil change so it doesn't end up as one gigantic blob that gums up your entire engine or having your brake pads completely disintegrate, cleaning the lint out of a sewing machine, greasing your bike gears, ...
If broke, fix it.