How I approach engineering
Technical leadership means scaling teams and products by investing in teams, architecture, processes, people and communication.
- 01
Gladiator over spectator
Don’t just critique and bring ideas, execute and drive results.
- 02
Principles over playbooks
I have a deep curiosity to ask tough questions and search for answers.
- 03
Momentum over speed
Balance short-term gain for longer term success. Find the best path to deliver value.
- 04
Ideas over egos
I don’t always have the best ideas, and that’s okay.

Calvin Lobo
Backend engineer focused on software architecture, scalability and developer efficiency. Outside of work: electric guitar, home renovation and time outdoors.
Latest writing
All posts →Testing complex workflows in Go
A testify/suite style that keeps sophisticated fixtures, mocks, edge cases and complex outputs readable as the test cases multiply.
Read the article →// Before every test, fresh mocks and fixtures
func (s *CollectorSuite) SetupTest() {
s.mocks = Mocks{}
s.fix = Fixtures{input: happyPath()}
s.expect = Expectations{}
}
func (s *CollectorSuite) TestRateLimited() {
s.mocks.ListUGC(Fail)
s.run()
}Advanced Go Error Handling Made Simple
Go handles errors explicitly. Here is how to carry richer context through your errors without giving up that simplicity.
Defusing an ElasticSearch Mapping Explosion with Slots
When user-defined fields threaten to blow up your index mapping, a fixed set of reusable slots keeps it under control.
Reducing System Load With Event Folding
Collapsing bursts of redundant events into a single unit of work, and the maths behind how much load it saves.
Building a Comfortable Dev Environment
The tools, aliases and habits that make the daily grind of git, docker, kubectl and friends feel effortless.
Prefer a feed reader? Subscribe via RSS