Go's Zero Value and Practical Examples
Unlike C or uninitialized dynamic languages, Go assigns deterministic zero values to variables to avoid errors; json's `omitempty` uses the Zero Value concept.
Unlike C or uninitialized dynamic languages, Go assigns deterministic zero values to variables to avoid errors; json's `omitempty` uses the Zero Value concept.
I believe in an era where many AI models compete, Models will only get cheaper and more efficient. Let's host the right model through Ollama.
Frontend tests focus on browsers; backend tests face distributed services and state. This shows using Testcontainers to run Docker-based integration tests.
AES is the most widely used symmetric cipher—used in HTTPS/TLS, Wi‑Fi, full-disk encryption, and messaging. Understanding AES clarifies modern encryption.
Managing many site passwords is risky. FIDO (Fast IDentity Online) enables passwordless login using fingerprint or face scan.
I noticed a widely praised convention in Go testing: Table Driven Tests. I thought tests should be simple, but this pattern reflects programmers' laziness.
Notes on implementing a Set while migrating from JavaScript to Go — using maps to represent Sets since Go lacks a native Set.
Using Go 1.16's embed to include files at compile time, avoiding path/environment issues. Not suitable if files must change at runtime.
P and NP classify problems by whether they can be solved in polynomial time or nondeterministic polynomial time.
After covering what Feature Flags are, this post explains four types of Feature Flags and their differing lifecycles, dynamism, and management strategies.
I thought keeping things simple—changing code or env vars—was enough. But when incidents occur you don't have time to debug.
To better replace modules via "dependency injection" for cleaner testing. I uploaded the demo example demonstrating testing architecture through DI.
From JS to Go, I wasn't familiar with Go's approach to modularity. Although similar in places, Go's simple and opinionated design is very evident.
N+1 database query problem, its causes, and solutions: denormalization, DB-level joins ($lookup/JOIN), batch queries with assembly, and ORM/ODM eager loading.
Revisiting serialization/deserialization in Go and the origin of "Marshal", building on my earlier post about struct tags and reflect.