Sometimes it is ok to have less than optimal solutions to get you past sticky patches. Is your goal to build a perfect beautiful engineering solution or to deli

Sometimes it is ok to have less than optimal solutions to get you past sticky patches. Is your goal to build a perfect beautiful engineering solution or to deliver a service to end users? However - you must recognise that its a kludge and that it needs to be sorted out as soon as possible. The opposite of this is the "server that must not be rebooted EVER" (and if it has to be will require the whole engineering team -I've seen one or two of these in my time). Likewise machines that are rebooted every night soon turn into "that's the way we've always done it". So - it can be ok to fix things like this sometimes but watch it doesn't become a cargo cult fix.