Why frontends fail when you approach them like a backend

The three-state dark mode toggle is the correct answer

An application should not take away the decision a user has previously selected. That is the main point of the argument. All other details are insignificant.

• Three-state dark mode toggle proposed as solution
• Addresses time-of-day bug in two-state toggles
• Adopted by GitHub, StackOverflow, CodePen

1d ago ·dev.to

QBittorrent breaks out of sandbox to commit crimes

1d ago ·beige.party

Your zero-downtime deploy is probably fine. Check your p99 before you believe it.

I went looking for dropped requests during a rolling restart and found something more annoying than dropped requests: a deploy that looks perfect and isn't. Setup is deliberately boring.

• Zero-downtime deploy may appear successful but can fail during process.
• Lack of signal handling in Node/Express app causes mid-flight requests to die.
• Monitoring p99 latency, not just error rates, crucial to detect deploy issues.

1d ago ·dev.to

I built Rewind: A zero-dependency TIME-TRAVEL DEBUGGER with live in-browser hot-patching (Open for Contributions)

Debugging modern applications is still surprisingly painful. Whether you're building a Python data pipeline, a Node.js microservice, or a Go API, debugging usually boils down to two tedious options…

• Rewind is a zero-dependency time-travel debugger
• Offers live in-browser hot-patching for code adjustments
• Open-source under MIT license, accepting contributions

1d ago ·dev.to

Ask HN: How do you manage skills files?

How do you find skills, keep them organized, and make sure they actually work? Do you keep improving them over time? I believe skills will eventually be eating by model capabilities, but until then…

1d ago ·news.ycombinator.com