Software architecture · Go · Distributed systems

Calvin Lobo

Backend engineer. I build systems that scale, and write about the decisions behind them.

Scroll
Philosophy

How I approach engineering

Technical leadership means scaling teams and products by investing in teams, architecture, processes, people and communication.

  1. 01

    Gladiator over spectator

    Don’t just critique and bring ideas, execute and drive results.

  2. 02

    Principles over playbooks

    I have a deep curiosity to ask tough questions and search for answers.

  3. 03

    Momentum over speed

    Balance short-term gain for longer term success. Find the best path to deliver value.

  4. 04

    Ideas over egos

    I don’t always have the best ideas, and that’s okay.

Calvin Lobo
About me

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 →
NewestOct 1, 2022 · 9 min read

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()
}

Prefer a feed reader? Subscribe via RSS