Ask HN: What's your "it's not stupid if it works" story?
Engineers and tinkerers share dozens of “it’s not stupid if it works” stories, from production systems built on SQLite, headless browsers and mmap’d SSDs to hacked-together plumbing, heating, and car repairs. Across wildly different domains, the anecdotes highlight a recurring theme: quick, ugly solutions often outperform “proper” architectures for years, revealing how constraints, deadlines, and real-world reliability frequently trump elegance. Many also note the downside — these stopgaps tend to become permanent infrastructure and technical debt once they prove themselves in the wild.
Infrastructure & DevOps Workarounds
- Many stories revolve around “just restart it”: cron jobs or scripts that periodically reboot Pis, restart flaky services, or bounce databases until a bad table can be dropped.
- Memory leaks and structural crashes are often “solved” by regular restarts, failovers, or scheduled bounces instead of root-cause fixes; some argue this is effectively standard DevOps practice, others see it as dangerous tech debt.
- People bypass complex deployment stacks with simple tools:
envsubstorsedfor templating, single giant serverless functions withwhileloops for robustness, or using OpenResty/Lua hardcoded auth. - VPNs and firewalls get sidestepped via sshuttle, HAProxy port-forward tricks, or scripts that reboot consumer routers to rotate IPs.
Home, Hardware, and Physical Hacks
- Numerous “keep it alive” hardware stories: Arduino/ESP32 relays to auto power-cycle boilers, freezer tricks to revive failing electronics, magnets or heating/boiling to resurrect drives and CDs.
- Mechanical bodges: servo-geared thermostats, coins or frozen sausages as heatsinks, oscillating CD trays or mouse movements to prevent screen blanking, sanded fans jammed into tight PC cases.
- Plumbing and household hacks include air compressors or improvised tools to blast clogs, toilet tanks as plant watering reservoirs, and ad‑hoc CPAP or humidifier mods.
Web, Enterprise, and Legacy Integration
- Heavy use of browser automation and screen-scraping (Watir, Selenium, Capybara, AutoHotKey) to integrate with ancient CRMs, IE6-only vendor sites, and green‑screen mainframe systems.
- Creative abuse of Google Sheets, Outlook, Access, Lotus Notes, and Word via macros/COM to build shadow systems when proper APIs or integration servers are unavailable.
- PDF and image generation frequently delegated to headless browsers (Chrome, Firefox) because purpose-built converters are unreliable or inconsistent.
Data, Storage, and IPC Hacks
- SQLite appears everywhere: as an IPC mechanism, lightweight server DB, or even coordination layer; many report it scales far beyond expectations for their workloads.
- Some systems mmap entire SSDs into a single C++ struct or flat file, deliberately skipping filesystems and databases to gain huge speed, with acknowledged fragility and recovery risks.
- Others hardcode massive arrays (e.g., 100k coupon codes) or treat text files under version control as “databases,” with surprisingly acceptable performance.
Security, Anti-Abuse, and Policy Games
- “Not really security” measures are used to placate scanners or business needs: CSP
upgrade-insecure-requestsjust to improve grades, or hidden JavaScript/time-delayed form fields to deter spam instead of CAPTCHAs. - Homegrown WAFs and request filters in front of WordPress and other apps successfully block years of attacks, sometimes effectively reinventing commercial products.
- Participants note the tension between clever hacks and long-term maintainability, but the thread overall celebrates pragmatic solutions that keep systems—and businesses—running.