Suggestions
Beto Moreira
Engineering @ Leonardo.Ai | Co-founder & former CTO @ Good Pair Days
Beto Moreira is a software engineering professional currently working as a Team Lead at Leonardo.Ai.1 He has a strong background in technology and a diverse set of skills and experiences:
Education and Professional Background
Beto holds a degree with First Class Honours, which he completed between 2003 and 2007.1 This educational achievement suggests a strong academic foundation in his field.
Language Skills
Beto is bilingual, demonstrating:
- Full professional proficiency in English
- Native or bilingual proficiency in Portuguese1
Professional Interests
While specific details about his current role at Leonardo.Ai are limited, Beto's professional history indicates involvement in various tech-related fields. In a previous position, he was associated with GPD (Global Product Development), where he expressed excitement about ongoing projects.2
Personal Interests
Outside of his professional life, Beto appears to be an avid reader. His Goodreads profile shows that he has logged 400 books and is currently reading "The Staff Engineer's Path: A Guide for Individual Contributors Navigating Growth and Change".3 This suggests a commitment to continuous learning and professional development in the field of software engineering.
Beto Moreira's LinkedIn profile (username: betocmn) likely provides more comprehensive details about his professional experience, skills, and achievements in the software engineering field, particularly in his current role as Team Lead at Leonardo.Ai.
Highlights
Navigating past company decisions is often a journey full of questions for new team members. Why do we use two similar tools for email marketing? What prompted us to increase shipping fees 10 months back?
If they're fortunate, they'll connect directly with the decision-maker who still remembers the decision and can provide immediate answers. However, sometimes the team can only point to scattered chats across Slack and Email for some background.
In less lucky situations, the decision-maker might have left the company, leaving the reasoning behind their choices undocumented and lost. Six months later, another new employee arrives, and the cycle of questions begins anew.
Over the past three months, I talked to over 100 companies, and it’s astounding how universally acknowledged the value of a Decision Log is. Yet, in practice, very few are actually implementing it (only 3, to be precise).
I'm talking about the most basic form - A centralised place where anyone in the company can go and see a list of all major decisions and the thinking behind them.
The desire to refine decision-making is there. The first step? Establishing a reliable record of your company's past decisions to ensure inclusivity, facilitate learning, and improve efficiency.
That's what I'm currently working on, and we're launching in ten days!
Just read an old memo from the Slack team just before their Preview Release in 2013.
Here are my top 3 highlights and inspiration as I build AsyncBrain:
People had no idea they wanted Slack: Slack was solving a big problem. Teams didn’t communicate well, but they didn’t know a tool like Slack could help. And no one was actively trying to find a solution for this.
Change in human behaviour: "The best — maybe the only? — real, direct measure of innovation is change in human behaviour." The actual Slack tool wasn't that glamorous, but the impact and change it brought to companies immediately got attention.
Selling a change, not just a tool: They weren’t just selling software. They were selling better teams and a less stressful way of working.
A must-read: https://lnkd.in/gqivudfQ
