Explore >> Select a destination
|
You are here 
|
dmitryfrank.com | ||
| | | | |
www.morling.dev
|
|
| | | | | Update Jan 13: This post is discussed on Reddit Update Feb 7: This post is discussed on Hacker News As software developers, we've all come across those annoying, not-so-useful error messages when using some library or framework: "Couldn't parse config file", "Lacking permission for this operation", etc. Ok, ok, so something went wrong apparently; but what exactly? What config file? Which permissions? And what should you do about it? Error messages lacking this kind of information quickly create a feeling... | |
| | | | |
alexrichey.com
|
|
| | | | | A pattern for distinguishing and handling client and internal errors in Go that leverages the power of Go's interfaces. | |
| | | | |
blog.carlana.net
|
|
| | | | | The other day, I was reading a website about some historical documents, when I saw that it had an error message on top: Screenshot from the site Some quick searching online for the error message revealed that it was caused by a mismatch between the site's versions of PHP and WordPress. Older versions of WordPress had a bug in the switch statement of a certain localization component, and later versions of PHP dump a warning about this bug out to the end user HTML. When I came back to the site a few days later, it had been fixed. The ultimate reason for my seeing for the error message as a random reader is that PHP has too many ways to deal with errors: Builtin PHP functions, and therefore any PHP project, have a whole range of error handling mechanisms - erro... | |
| | | | |
ineza.codes
|
|
| | | Learn the basics of setting up push notifications in your progressive web app | ||
