Hey there! That's a fantastic question that hits home for anyone who's worked in tech or automation. The automation equivalent of 'duct tape and prayers' is what we often call 'technical debt' - those quick scripts, manual workarounds, or fragile integrations that somehow become the backbone of your system.

You know the type: that Python script you wrote in 30 minutes to bridge two systems that's still running three years later, or the Excel macro that somehow became the 'reporting dashboard' everyone depends on. They're the automation world's version of duct tape - they get the job done, but you're never quite sure when they'll fail.

As for when it's smarter to keep them rather than building the 'proper' solution, there are actually some good reasons:

1. **When you're validating something new** - If you're testing a market or concept, duct tape solutions let you move fast and learn quickly without over-investing.

2. **When the 'proper' solution is overkill** - Sometimes the elegant engineering solution costs 10x more time and resources for minimal benefit.

3. **When it's stable enough** - If your duct tape solution has been running reliably for years with minimal maintenance, why fix what isn't broken?

4. **When business priorities demand speed** - Sometimes shipping now with a temporary fix is better than shipping perfect six months later.

The key is being intentional about it. Document what's temporary, track the trade-offs, and have a plan for when you'll revisit it. Some of the best systems in tech started as 'temporary' solutions that proved their worth over time!