Product mockup

“if err != nil” Developer T-Shirt (Go Edition — Dark Mode)

XS
£25.00
Sale price  £25.00 Regular price 
Skip to product information
Product mockup
1/7

“if err != nil” Developer T-Shirt (Go Edition — Dark Mode)

£25.00
Sale price  £25.00 Regular price 
Size

For developers who live in dark mode. This black unisex tee brings Go's iconic if err != nil line into your everyday setup — clean, minimal, and ready to compile with any outfit. Soft, durable, and designed for long coding sessions, it's a perfect fit for late-night debugging or coffee-powered mornings.

  • 100% combed and ring-spun cotton (Heather colors contain polyester)
  • Fabric weight: 4.2 oz./yd.² (142 g/m²)
  • Pre-shrunk fabric
  • Side-seamed construction
  • Shoulder-to-shoulder taping
  • Blank product sourced from Nicaragua, Mexico, Honduras, or the US

Disclaimer: The fabric is slightly sheer and may appear subtly see-through under certain lighting conditions.

Printed on demand — no bulk waste, just clean syntax and sustainable production.

Part of the Go collection, within Low Level & Performance.

Available in Dark Mode and Light Mode.

Review our T-Shirt size guide

Heads-up

Shipping costs vary by region, so it’s worth giving the delivery total at checkout a quick look before confirming your order. Some variants may show limited availability in certain locations—if fulfilment isn’t available in your region, our suppliers will try to ship globally from the nearest facility that can produce that specific item. When this happens, delivery costs may be higher than expected due to the increased distance.

We’re constantly reviewing suppliers and expanding fulfilment options, and new routes may open over time.

If you’d like updates when things change, you can join our mailing list at the bottom of the page.

EU Product Safety (GPSR) Compliance

Error Handling in Go: Why 'if err != nil' is Everywhere

Error Handling in Go: Why 'if err != nil' is Everywhere

Go handles errors explicitly. Every function that can fail returns an error, and you check it immediately. It's verbose, but deliberate. Understanding why this pattern exists helps you write clearer, more reliable Go code.

Read the article

You may also like