Tag archive
Introduction to Go Interfaces Go interfaces, at first glance, might seem like a familiar...
Why Go functions should take abstract inputs and return concrete types, where the rule breaks, and the testing payoff it buys you.
One line of Go turns a silent runtime interface break into a build error. Where to put var _ Iface = (*T)(nil) so it actually helps.
Most developers memorize: "One interface, many forms." Unfortunately, that definition is so...
Technical Reconstruction: Interfaces, Traits, and Dynamic Method Dispatch Main Thesis:...
How to do DI in Go without Wire or Dig. Interfaces, constructors, wiring in main.go — and why a DI framework is often the wrong answer to a real design problem.
Your function returns nil. Your caller checks for nil. The check fails. Welcome to typed-nil interfaces in Go.
Introduction to the Repository Pattern in Go As a seasoned blogger stepping into the Go...
The Go "accept interfaces, return structs" convention explained through a concrete ClaudeGate code review case. When to apply it — and when leaving things as-is is the right call.
How XR systems are moving manipulation from interfaces into perception itself — why attention is becoming programmable.
Why we are moving from interfaces to perception — and from communication to synchronization.
Understanding the Most Common TFT Interfaces Used with STM32 MCUs TFT displays are a...