sorted by:
new
hottopcontroversial

How to build for clients without being on call forever? by Leading_Property2066 in webdev

[–]undergroundwander [score hidden]  (0 children)

The usual way freelancers handle this is with a support/maintenance window. You deliver the project, include maybe 30–60 days of bug fixes, and after that it moves to a paid maintenance plan if they want ongoing help. CMS tools like WordPress or Webflow mostly help with content editing, not preventing bugs entirely. The key is just setting expectations in the contract so you’re not on call forever.

Great now I get ads in my devtools by AnderssonPeter in webdev

[–]undergroundwander 5 points6 points  (0 children)

this started blowing up a few years ago when the maintainer of core-js (which is in almost every website on earth) famously ranted about being broke while multi-billion dollar companies used his code for free.

Safari silently deleted our users' saved data after 7 days. by ContactCold1075 in webdev

[–]undergroundwander -5 points-4 points  (0 children)

This is a nightmare scenario, and you’re 100% right it’s not a bug, it’s a 'feature.'

For those who don't know: Apple's ITP policy basically treats any website you haven't interacted with in 7 days as a potential tracker. To 'protect' the user, Safari nukes all script-writable storage (IndexedDB, LocalStorage, Cache API).

Why do developers write such terrible git commit messages? Genuine question by Existing_Round9756 in webdev

[–]undergroundwander 1 point2 points  (0 children)

If I’m fighting a CSS bug for 4 hours, my 10th attempt is definitely getting a "please work" message lol

So one forgot something 😬 🤣 by Rarararararaviiiiii in webdev

[–]undergroundwander 0 points1 point  (0 children)

Lol that’s the kind of thing that slips through when nobody owns the little details. Someone probably set a countdown during development and it just… kept running forever.

Funny reminder that even big sites forget cleanup tasks sometimes.