LINEヤフー Tech Blog コード品質向上のテクニック: 第 1 回
その例外、いつキャッチするの？
Logging Best Practices: The 13 You Should Know
Log Analytics Logging Best Practices: The 13 You Should Know When you search for things on the internet, sometimes you find treasures like this post on logging, e.g. creating meaningful logs. This post is authored by Brice Figureau (found on Twitter as @_masterzen_). His blog clearly shows he understands the multiple aspects of DevOps and is worth a visit. Our thanks to Brice for letting us adapt
【第14回】Go言語（Golang）入門～Twitterアプリ作成編～ – 株式会社ライトコード
Go 1.13時代のエラー実装者のお作法 - Qiita
pipeエラーのハンドリング - Carpe Diem
Apollo platformのチュートリアルをやった - $shibayu36->blog;
Working with Errors in Go 1.13 - The Go Programming Language
Damien Neil and Jonathan Amsterdam 17 October 2019 Introduction Go’s treatment of errors as values has served us well over the last decade. Although the standard library’s support for errors has been minimal—just the errors.New and fmt.Errorf functions, which produce errors that contain only a message—the built-in error interface allows Go programmers to add whatever information they desire. All i
Error-Message Guidelines
Summary: Design effective error messages by ensuring they are highly visible, provide constructive communication, and respect user effort. Over 30 years ago, Jakob Nielsen created 10 Usability Heuristics as general guidelines for designing digital products. These heuristics equally apply today as they did back then. Usability heuristic #9 emphasizes the importance of good error-message design: "He
Error Handling in Go
This post is part of the “Before you go Go” series, where we explore the world of Golang, provide tips and insights you should know when writing Go, so you don’t have to learn them the hard way. I assume you have at least some basic Go background, but if you feel at any point you’re not familiar with the materials discussed, feel free to pause, research and come back. Now that we got all of this o
go/typesパッケージを使って型チェックを行なうハンズオンを作った #golangtokyo - My External Storage
Error Handling in Go
Two commonly perceived problems of the programming language Go are that handling errors is verbose and repetitive parametric polymorphism is not available This post is about the intersection of those problems and Rob Pike’s recommendation on the former. Martin Kühl Errors are values In his post “Errors are values”, Rob Pike, one of the original authors of Go, attends the common perception that one
Goの新しいerrors パッケージ xerrors - Qiita
MQTTサーバーを実装しながらGoを学ぶ - その３ errorとエラーハンドリング - bati11 の 日記
How Sentry Receives 20 Billion Events Per Month While Preparing to Handle Twice That - Sentry Tech Stack
By James Cunningham, Operations Engineer, Sentry. About Sentry Unless your engineering team is staffed by angels who commute down to the office from heaven every morning, we’re pretty confident you run into plenty of problems developing and iterating on your applications in production. Sentry provides all the tools you need to find, triage, reproduce, and fix application-level issues before your u
良いエラーメッセージの書き方 - Qiita
エラーには大抵「エラーメッセージ」が付いています。 自分は過去に、エラーメッセージの内容を雑にしてしまい後悔することがよくありました。 その経験から、良いエラーメッセージの書き方を考えました。 エラーメッセージを2つに分類する まず、エラーメッセージといっても次の2つのパターンで大きく異なってきます。 (1) ユーザーが見るエラーメッセージ (2) 開発者が見るエラーメッセージ (1) ユーザーが見るエラーメッセージ 内部実装のことは書かないようにする
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Effective Error Handling in Golang
Error, Defect, Fault, Failureの定義と解釈 - Qiita
Go1.13以後のエラーハンドリングについて語ろう / Let's talk about error handling after Go 1 13
Go Conference 2019 Spring
