Hi there, I’m Sérgio.
I’m Portuguese with a European identity, who found comfort in the Finnish silence and beautiful nature. I build software, and everything that requires: software architecture, risk management, IT security management, integrations, interoperability standards, and artificial intelligence.
I started my professional journey in Lisbon, where I studied Information and Computer Engineering at Instituto Superior Técnico (Técnico Lisboa). There I became involved in student politics and student representation, which gave me a considerable head start in management and organisation related topics.
I enrolled in an exchange program that brought me to Aalto University in Finland. Here I briefly studied machine learning and data mining, and became involved in the startup scene that is desperate to find good talent. After a first failed attempt at entrepreneurship, where I learned the basics of business development and the meaning of failure, I joined other startups. In total I’ve watched and helped two startups grow from early stage towards acquisition by major industry players (Holvi by BBVA, Kaiku by Elekta).
Besides technology, I’m passionate about company culture, diversity and representation topics, sailing and the Finnish cottage and nature life.
Find me on:
2020-04-16 - Asking for feedback is the right way to receive feedback
TL,DR: When you get negative feedback you instinctively get defensive. Being defensive prevents you from integrating that feedback, and diminishes its the effectiveness. Taking control of the process by asking for feedback yourself gives you control over the situation, and allows you to prepare for and control your instinctive reactions.
2020-04-05 - Tech debt - broken windows and normalization of deviance
TL,DR: We overuse the term and we wrongly call some things “tech debt”. By overusing the term we normalize having lots of technical debt. By calling small issues “tech debt” we are opening the door for larger issues to appear. I propose a stricter definition for for the term, suggest some alternative terms, and propose that we flag issues with structured code comments.