Atypical Journey: From Anonymous Silence to CTO Stage (on Buser)
My path from software engineer to Chief Technology Officer (CTO) at Buser, with some reflections on what I'm learning in the process
While the path to the position of Chief Technology Officer (CTO) may seem similar to many, each story is uniquely extraordinary, colored by the unique combination of experiences, struggles and intensive learning. In “Invisible Learning”, John Seely Brown and David Thomas discuss how learning is often an invisible path, rooted not only in formalities, but also deeply woven into the fabric of our life experiences. This is my story within Buser.
From Anonymity to Center Stage
I joined Buser, not as CTO, but as a member of the software engineering team. Previously, I had been CTO at several companies and was enjoying the relative obscurity of this more reserved role, shying away from the limelight that usually accompanies the CTO function.
In one of my first one-to-one conversations with Tony Lampada - Buser’s CTO at the time - he expressed his desire to return to the engineering team, sharing his dissatisfaction with the CTO position. This is a relatively common move in technology, as described by Michael Lopp in Managing Humans. In response, I referred him to three other potential candidates, emphasizing that I wasn’t interested.
was enjoying my moment of “anonymity” and didn’t want to return to center stage (the CTO is constantly in the spotlight), it’s worth reading this blogpost (sorry for being in pt-BR).
Continue reading the text here