When you just want to implement one or two methods … but be careful.
A bit of up-front thinking can help make our Go code cleaner and more performant.
there is a fundamental parity mismatch between SQL and imperative code.
The big thing in Unix was the realization that instead of building large monolithic systems, one could build smaller programs which could communicate with each other.
As a software engineer, I’ve learned that consistency in code is crucial for the long-term success of a project, even when it means deviating from idiomatic principles.
20 years ago: Use a fat and complex persistence framework on top of the DB, because we might switch DBs in the future…
Luca Palmieri’s book, Zero To Production in Rust is a great guide for those looking to learn Rust by building an email newsletter-sending Web service from scratch. The book is full of first-hand developer tips on how to set up one’s environment or what tools to use, and goes beyond explaining the usual steps one can find in the official documentation.
The wait is over!
Explicit > Implicit
Is this the beginning of the end of Xcode?
Idiomatic is what works for you and your team at the end of the day
You cannot trick the Go compiler, and that is a good thing.
If you are betting on PostgreSQL, pgx is the right choice.
A thought experiment with generic type parameters