Hacker News new | ask | show | jobs
by bripkens 519 days ago
There are often additional hints to go by, e.g., the executed network requests, the user path taken or "breadcrumbs", i.e., custom events captured.

Of course that requires a certain operational maturity.
1 comments
gunian 519 days ago
In my head that feels like triaging but idk people really be patching bugs without reproducing? That sounds crazy to me idk why

I've never worked at a place that had local dev used to think computers hated me but wondering if this is better dev practice in general

link
nottorp 519 days ago
Who said anything about not reproducing?

It just takes a lot less time to reproduce if you have some logging in production... and some people seem to believe that's not needed.

And if you have logs, you may not need to reproduce it because said logs give you all the info you need.

Disclaimer: circumstances may vary. A bug is a bug is a bug and you may solve it by reading one log line, or you may spend a week with a debugger in your development environment and it will still crash in production when you deploy the fix.

Happy now?

link