The Utilization Saturation and Errors (USE) Method is a methodology for analyzing the performance of any system. It directs the construction of a checklist, which for server analysis can be used for quickly identifying resource bottlenecks or errors. It begins by posing questions, and then seeks answers, instead of beginning with given metrics (partial answers) and trying to work backwards.
The USE Method can be summarized as: For every resource, check utilization, saturation, and errors.
Some gripes about Go from this blog, specifically around developer ergonomics (syntax highlighting and language-inherent error detection), politics, packaging and distribution, GOPATH, and the tuple-oriented error handling idiom. As R. I. Pienaar noted, the Go community seems full of “at-Google-wes”, which is an excellent way of putting it.
"logging.basicConfig configures the root logger : this is not something you want to do in practice, because it causes debugging output for all loggers in your program, including every library that uses logging.
In general, you'll want ot leave the root logger alone and configure a specific "main" logger for your program and put all the other loggers under that logger."
FoldFold allExpandExpand allAre you sure you want to delete this link?Are you sure you want to delete this tag?
The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community