13 contributions
What began as a series in late 2021 has somehow reached the end of 2022. Over this year, the way Buzzvil's product team works has changed even more. Change has outpaced my writing,…
I'm Whale, Buzzvil's CPO. I started this series to look back on 2021, and suddenly it is already 2022. Last year was full of experiments, reflection, and growth at Buzzvil. In this…
I'm Whale, Buzzvil's CPO. Somehow, 2021 has already flown by. For Buzzvil, it has been a year of experiments, reflection, and growth. In this series, I would like to introduce the…
TL;DR Indiscriminate use of bullet points is bad for your health. Lately, I have been seeing a lot of writing that overuses bullet points. They appear where a detailed explanation…
Read John Doerr's book on OKRs, or another well-known book on the subject, and they can seem easy to apply. You might even wonder whether the concepts of Objectives and Key Results…
Why a product perspective matters for engineers In a recent interview, someone asked what they should do to grow as an engineer. Go deeper into programming languages? Get better at…
Why container-based development environments help teams, and how to configure one with VS Code.
Why Buzzvil adopted gRPC, how it generates and publishes service libraries, and how transcoding adds HTTP/JSON support.
Buzzvil has a team called ATF, the Architecture Task Force. As the name suggests, it brings together software architects who think through—and implement—our software architecture.…
Comparing layer-based and feature-based package structures, with practical Go examples and their trade-offs.
A comparison of architectural trade-offs and the business needs behind Buzzvil’s move toward microservices.
Why architecture matters economically, how trade-offs shape its design, and why Buzzvil formed an Architecture Task Force.