<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv" -->

---
title: Go's error handling doesn't sit right with me | daily.dev
description: A critique of Go's error handling pattern, where every fallible call requires a 3-line `if err != nil` block that clutters the main logic flow. The author...
canonical: https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Go's error handling doesn't sit right with me | daily.dev
og:description: A critique of Go's error handling pattern, where every fallible call requires a 3-line `if err != nil` block that clutters the main logic flow. The author...
og:url: https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv
og:image: https://api.daily.dev/og/posts/gX5SmoTJV.png
og:image:alt: Go's error handling doesn't sit right with me
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Go's error handling doesn't sit right with me

**[Drew DeVault](https://daily.dev/sources/drewdevault)** · 4 min read · 0 upvotes · 0 comments

## Summary

A critique of Go's error handling pattern, where every fallible call requires a 3-line `if err != nil` block that clutters the main logic flow. The author draws a comparison to assembly language, where a single conditional jump instruction (e.g., `jp nz, errorHandler`) achieves the same result in one line, allowing a single shared error handler for an entire procedure. The conclusion is that while Go's philosophy of returning errors rather than throwing exceptions is sound, the verbosity of its implementation makes code harder to read and more tedious to write.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://drewdevault.com/2014/06/07/Why-Go-error-handling-doesnt-sit-right-with-me.html>

## Similar posts on daily.dev

- [How to Handle Errors in Go](https://daily.dev/posts/how-to-handle-errors-in-go-tlpqkl2og) · JetBrains · 25 upvotes · 1 comments
- [Best Practices for Secure Error Handling in Go](https://daily.dev/posts/best-practices-for-secure-error-handling-in-go-4zsml2ahs) · JetBrains · 3 upvotes · 1 comments
- [Go proposal: Type-safe error checking](https://daily.dev/posts/go-proposal-type-safe-error-checking-u4b58mpwl) · Anton Zhiyanov · 70 upvotes · 5 comments
- [The Second Great Error Model Convergence](https://daily.dev/posts/the-second-great-error-model-convergence-e6ligcvol) · matklad · 0 upvotes · 0 comments

---

Tags: [#golang](https://daily.dev/tags/golang), [#assembly](https://daily.dev/tags/assembly)

[View this post on daily.dev](https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Go's error handling doesn't sit right with me","url":"https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv"},"datePublished":"2026-03-31T12:27:57.560Z","dateModified":"2026-03-31T12:34:01.862Z","description":"A critique of Go's error handling pattern, where every fallible call requires a 3-line `if err != nil` block that clutters the main logic flow. The author...","image":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","thumbnailUrl":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","isAccessibleForFree":true,"articleSection":"Drew DeVault","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Drew DeVault","logo":"https://media.daily.dev/image/upload/s--BGhGBu0U--/f_auto,q_auto/v1774960025/logos/drewdevault?_a=BAMAMiWQ0","url":"https://daily.dev/sources/drewdevault"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/go-s-error-handling-doesn-t-sit-right-with-me-gx5smotjv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"golang,assembly","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Drew DeVault","item":"https://daily.dev/sources/drewdevault"},{"@type":"ListItem","position":3,"name":"Go's error handling doesn't sit right with me"}]}
```

