How Bruno Germano Builds Human-Centered Software by Listening First

From coding in Visual Basic 6 to working remotely in South America via a satellite dish on his car’s roof, Bruno Germano has had a journey that’s anything but ordinary. 

As a DevRel specialist at Azion, Bruno brings an artisan’s mindset to software development in which empathy, creativity, and human connection matter just as much as syntax and logic.

On this episode of What the Code, Bruno shares the evolution of his career from a 12-year-old skateboarder building websites to a tech leader who sees communication as the core of engineering. He explains why understanding people, not just programming languages, makes developers truly great.

Coding Is Only the Beginning

Bruno's earliest days in tech were hands-on and personal. "The only thing I know to work and to make money is working with tech. I never had a different job besides technology," he says​. But over time, he’s expanded much more than his knowledge of code.

“I spend more time talking with people, trying to investigate the problem, the real problem,” he explains. “Writing code is just a small part of my work."

That shift in mindset, from mastering syntax to also understanding people, has defined his growth as a developer.

Software Is Communication

Bruno believes great software development is rooted in communication. “Software engineer work is about communication,” he says. “And so you need to have this ability to understand what you are thinking and try to explain to another party.”

This ability to listen, translate, and clarify across stakeholders is what sets high-performing engineers apart, he argues. While developers are experts in their domain, they need to make sure they’re solving for the right problem. 

“If I ask a client, ‘How can I solve your problem?’ he would say, ‘OK, add an upload button so I can upload a document,’” Bruno says. “But if I explain that I can upload a document, edit a document, preview a document inside a browser, he says, ‘Maybe this is better.’”

Working Remotely, But Not Always From Home

Bruno has been working remotely since 2018, but that hasn’t made him any less social. In fact, he’s turned remote work into a life of connection and adventure. Recently, he and his wife drove from São Paulo to the tip of Argentina—working along the way with laptops, a cat, and a Starlink mounted on their car.

“My work is remote. It’s not working from home,” he says. “The chance to work remotely made all these things possible."

For Bruno, remote work isn’t just a benefit. It’s the foundation for living a life that blends purpose, freedom, and presence. He urges other developers to embrace community, no matter where they work from.

“Learning together, listening, learning, reading other one's posts or other one's book documentation,” he says, “is easier than just yourself, trying to take your steps alone.”

Transcript

Amit Sion:

Hello, and welcome to What the Code here at the X-Team Studio live in Sao Paulo. And I'm very excited today, I've got my first guest, which is Bruno Germano. Bruno, welcome to the show.

Bruno Germano:

Thank you, Amit. It's so good to be here. I would say it's my second time here. I went in the first season in Portuguese, and now in English. That's really cool. Thank you for having me.

Amit Sion:

Well, I appreciate you doing both episodes, and it's really neat that I saw that you have a lot of followers online, and I wanted to get a bit of an understanding of your background. Unfortunately, I don't speak Portuguese, so I couldn't understand it. So perhaps I'd love to, from the very beginning, let's start with your origin story. I'd like to get to know you a bit. Tell me how you got into tech, how you got into development and everything.

Bruno Germano:

I think, this is a funny story, because I have the feeling that I don't have any choice beside tech to work on. Because my dad used to work, is still working with technology, he is working with, right now, some ancient language called Futura, I think? I don't recall but it's a really old language. But he worked with tech since I was, I don't know, three, since I was 4. And so I grew up with a computer inside my home, inside my bedroom. I grew up connected to the internet. 

And I recall that when I was 12, 11, we used to have some magazines that come with CD-ROMs, and one of these magazines had a course for three brand-new languages, call it HTML, CSS, and JavaScript. At the time it was '98 or '97, I don't recall. But I was still in school, I was not having a formal, proper formation for start with tech. But since I have a computer at home, since I have connection to the internet, and a new course to start learning, I create my first website when I was 12. 

And then after this, I start to involve more with my studies on tech. I went for some technical course and then to the college. And I start to work, formal work, when I was 17. And so, today I am 37, it's been 20 years since then. I used to say that the only thing I know to work and to make money is working with tech. I never had a different job beside technology. Actually, I never had a different job besides coder. Always being a programmer, since my first job until today.

Amit Sion:

I want to go back to that first website. I remember the first website I built, I was in university, and I was really into claymation. And I used to make all these claymation figurines and make animations. And at the time, GeoCities came out. Some people might remember GeoCities. This was 1998, and I built my website, launched it on GeoCities. And I remember only about a month after, a teacher on the other side of the world who was teaching art contacted me and said that she was showing it to her students. And that just blew my mind, the ability to create content and have it seen by someone else on the other side of the world. What was your first website that you were building there?

Bruno Germano:

This is a funny story. Me and my brother, we are really into skateboarding. When we are young, and at this time when, '95, '96, I don't recall exactly the year, we got our first digital camera. And since we are skateboarders, we start to take pictures, make some quick movies about our parties. And the problem is we were in this between worlds, when no one was expecting for digital picture, and we don't even have how to show this digital picture. We need everyone to sit around the computer and watch the pictures. And I got this idea to create a website to share our pictures. And my first website was some kind of the same relation we have with social media today. It was some kind of a blog, some kind of Instagram page, but just sharing our skateboarding pictures. The skateboard picture was bad, the website was bad, but it works for a lesson for me. And since then, I’m still working with technology.

Amit Sion:

I remember all the first websites were bad. We were all creating ones with every bit of GIFs that we could find to add it onto there, lots of JavaScript tricks that we can add on, and our code was just a complete mess. But that was the beginning, right? We put everything in and then we go, "Oh, this takes a month to load, so let's scale it all back and make it accessible,” right?

Bruno Germano:

And the connection was really bad at that time, too. You cannot add too many pictures in the same page.

Amit Sion:

So when you were learning coding, what was your first language? What got you excited about first?

Bruno Germano:

This time, it was JavaScript, but I don't want to say that I learned JavaScript at this time when I was 12, because I was more copy-and-paste codes, try to tweak some codes that I saw in the internet. But my first language that I actually learned and knew how to create some software was VB6, Visual Basic 6. And I learned this during my high school, and then I went to a course to learn better. And when I was 17, my first job was working with VB6 and Microsoft Access for database. But I know that today that Microsoft Access is not a database, but the software at this time was creating using VB6. And I loved VB6 for this time. I worked for many years with VB6 until I went to the web, like starting with apps, ASP, C#, and etc. But my first language was VB6.

Amit Sion:

VB6 was amazing. Your ability to create an application was so quick. You could insert a button, drag and drop. It was quite new in comparison to some of the other languages that were available at the time. Now it's more of a common thing to do that, but it was quite exciting as to what you were able to create. And like you said, you can put the Access database behind it, and all of a sudden, you've got a fully functioning program without the web. But it worked. So it was quite exciting to have that created.

Bruno Germano:

Yeah. We used to share one Access file between a whole LAN, and everyone in the company was using the same software connected with the same database using local area network. It was fun. But the parts I loved with VB6 at this time was debugging. Debugging VB6 at this time was so easy, and I learned a lot about how software works just debugging.

Amit Sion:

It's interesting that debugging actually has something quite intriguing about it. There's a bit of detective work behind it, right? You're trying to figure out, there's a mystery here, there's something that you need to solve. And sometimes it gets frustrating, but there's a certain element that is exciting. How do I get through here? How do I figure out? And then when you clear it out and can keep programming, keep going on, right?

Bruno Germano:

Yeah. I used to say that you are following computer steps, like computer taking one step, and you check where it goes, and then another step and you check again. And you can learn how the computer works, how the software works, how the problem is solved just watching the steps. This is really fun. Today, we have a bunch of debugging tools, but at this time, it was really difficult to do debugging.

Amit Sion:

There's something you said in there really triggered for me. There was this feeling for me with programming that it was creation. You could go from nothing and create something. I couldn't go outside and find some bricks and start building a house or anything. But on the computer, you can start with nothing there. And with your own mind and time, you can create something where nothing existed before. And I think that's part of something that creates a spark with programming, don't you think?

Bruno Germano:

Yeah. I share the same thing. I love to have these moments in my life that I have one idea and I come to this kind of spark, maybe I can solve this with code. And then I go to computer, start a blank page, actually a blank page in my IDE, in my editor, and start coding. And I start to learn about my problem, I start to create solutions. I have this feeling that I'm almost artisan, like I see a brute material, and then I start to work on this. And I have some significant product at the end. 

And this brute thing is my own thinking or some problem that I see in the world. And this is really fun. I have the same feeling, that this is amazing to have this power to create things, just you and your computer, maybe your keyboard, I don't know. Maybe you were talking with computer using your voice, but just you and your keyboard can create amazing things.

Amit Sion:

Well, going back to where you started, where you were thinking, "Oh, I want to do programming." What is the difference between what you thought you'd be doing with programming versus what you actually do? How is the gap, or is it quite similar?

Bruno Germano:

Oh, really cool question. Because when I start to study and working with code, I was thinking that I need to deliver code to solve problems. I need to create software to make money. And today, I have a different feeling that the code, like writing code, is just a small part of the work. I spend more time talking with people trying to investigate the problem, the real problem that my client is facing or the user is facing. And this critical thinking, this investigation, take more time from me than actually writing code. Writing code is just a small part of my work. 

And I used to say—this week, I had a thing on my work that it could be solved with a quick conversation. And we were trying to writing code to deliver some solution, to deliver some features, and I was writing code. Another co-worker for me was trying to solve the same problem, creating more code.And if we just talk at the start of the week, try to manage and engage in the efforts, we can solve this really quick. 

And so I would say, answer your question now, at the start, I think I need to learn all the syntaxes, I need to learn all the patterns. I need to learn all the code that exists, all the language. I need to understand fully this language that I want to work. And right now, I’m thinking that I can know part of this technical part, but if I really understand how the people works, how the conversation in the workplace works, how the client, customer, and engineering—how this conversation between clients and engineering works—I think this will make my work and my delivery better than learning a bunch of technologies, new technologies, fancy technology, or really learning about all the language that I can learn. I think people is more important in software than coding, I think, today.

Amit Sion:

I like what you said there, the importance of communication skills to be a good programmer. At X-Team, when we look for good developers to present to our clients, yes, we look to see what experience they have, what technologies they've learned, all that sort of stuff. That's one element of it. It's almost like that's only half the story. 

The other half is the person, what are their communication skills? And I don't mean, do they have good English, that they can be understood. But are they good listeners? Do they have empathy? When they challenge a problem, are they going to be challenging in a respectful way? If they disagree with something, would they sit quietly because they're too timid, or are they going to put it forward because they want to do it better? And also, are they invested into it? Because that's something that you said there about that understanding of what the client actually wants because you want their success, right? So that element is so important. All those human skills are necessary for a person to be an amazing developer for the client.

Bruno Germano:

Learning the code, know how to code, know how to create software, you want just one of the tools you need to use during your day-by-day work with software. I used to say I'm hired to write code, but I spend more time not writing code, like in meetings, in conversations, in documentations. But if you're thinking, if you abstract the code, like the technical part, the whole software engineer work is about communication. When we are writing code, we are communicating to the computer how we want them to repeat the solution, how we want the computer to execute what we are expecting. When we are talking with my manager, I was talking how we can solve a problem in a better way. When I was talking with customer or with a client, I'm trying to understand the problem and trying to propose solutions for them before I code.

And so, I think the software development work is about communication, communication with computer, communication between different computer. If you're thinking cloud, we have a bunch of computers working for one software work. And behind a screen, behind a software screen when you are using a software, there are many people that work in there. Designers, copywriters, developers, I don't know, manager, and et cetera. And all these people need to communicate to each other. And I think the work of software development is communicating. And so, you need to have this ability to understand what you are thinking and try to explain to another party. Maybe it's a computer, maybe it's a person, maybe it's a client, but you need to explain what you are thinking, what you are proposing, how you want to solve the problem, and et cetera.

Amit Sion:

So many of the elements that you mentioned there are very human, and it makes me think of this challenge that people put forward to us. When I explain to people, "Oh we're X-Team, we provide developers." And they say, "Oh, aren't you worried about AI? Isn't AI going to make it all disappear?" And so much of what you said there was human, right? I think that there's elements that AI is amazing for, and it's helping us to elevate, but I don't fear it. I don't see it as something that will take away any of the importance. I think it'll just make us able to deliver even more to the client. How do you see it?

Bruno Germano:

Hey, machines, if you are listening to this conversation, I'm on your side. This is just a joke, but I'm using AI all the day that I'm working. I use AI multiple days during my work day. I'm using inside my editor, inside my IDE. I use for searching, I use for learning things. Sometimes I have difficulty to understand the documentation, I upload the documentation in LLM, and I can understand better. And so, AI is just again a tool. I think this is a huge tool, we can elevate our skills, we can learn faster, we can deliver code faster because AI is completing my code when I was writing. But I have the same feeling/ I'm not afraid. Because AI is just a mathematical model, it's like statistics. If you had a chance to learn about the statistics, you can understand better how the AI models work.

They don't know exactly what they are doing, but because of a pattern of a bunch of documents, bunch of code, bunch of learning the AI had, the AI can suggest the next word, and the next word, and the next word. And in that way he can, I don't know if “he” is, it can create a whole page of code. But AI is learning from our knowledge. We create that code, we create that document. And we as humans, developers, and people, scientists, et cetera, we are creating this content that AI is learning. And so, we are just repeating the same problems, or the same solutions, or the same invest of time to create something that already exists or something that was solved before.

And I think I had the feeling that AI is a great co-worker to have by our side, that knows all the problems that was solved before. But if we are facing a new problem, if you are facing a new product, if you are facing a new client, AI will have difficulty to understand exactly what you are requesting or what you are expecting from the AI. But you have the knowledge to use AI to create this new solution. And this new solution will be used for clients and make money, et cetera.

Amit Sion:

That's such a great differentiation that AI is wonderful for being able to reflect on all the history, all that's been done before in a way that it can do with all the machine learning, all the processing, and all that. But when it's something new, there's such benefit to being human, right?

Bruno Germano:

I agree with this statement. If it's something new, humans have a bunch of advantage on this because we can create things that never exist inside our minds. I'm not telling about code, or tech, et cetera. Inside our minds, we already create the solution. We already see this working. And this imagination or this creation thing, I think, is a big difference. But every time I say this, I say with some mathematical models again, we can give a feeling that AI is also creating things. Because AI is mixing different patterns or different solutions in the new one. And if you're thinking that solution A exists and solution B exists. But when we are mixing and merging together, we have a third solution, AI is able to do that and is able to create this.

But I think the big difference between creating solution using AI or using people, we want to understand the other part, we want to engage with the other part. We want to create a solution for the other part, we want to solve the client's problem. The AI doesn't matter, the AI don't have feeling, don't have this feeling to create the solution. AI just answer a question or just answer a prompt. I think that's the difference. We want to do this for the other person.

Amit Sion:

Well, it comes back to your point before about the thing that excites you is that desire to solve a problem for a client, something that they're trying to achieve. And you are not just getting a prompt to do something, but you're invested into what they're trying to achieve and wanting to figure out the solution to that.

Bruno Germano:

Yeah. And sometimes the client doesn't know exactly what he wants.

Amit Sion:

True.

Bruno Germano:

And this happens often. Like me and my wife, we are building a house, and this is a really, really cool moment for me to talk about this because I am the client now. I am the client who creates a request for the architect to build a house. And sometimes, maybe because I'm into software engineer, maybe because I'm into problem solving, I suggest the solution, not the problem. I suggest, "Oh, we need to have, I don't know, a window here because I want to see the woods." But the engineer, they have more experience. They know why there is no window in there. But every time that I propose a solution, I am afraid to have this same relationship between my clients. They are proposing what I need to do and not expecting a solution. And then I need to do this exercise to not propose a solution.

And when I say that the client doesn't know exactly what is this problem, because they are requesting the solution and not claiming for the problem. We are the experts to solve problems. We are the experts that know technology, that know clouds, that know computers to solve that problem. I think if I ask for a client, how can I solve your problem, he would say, "OK, add upload button so I can upload a document." But if I explain that I can upload a document, edit a document, preview a document inside a browser, he say, "Maybe this is better." 

Because I am the expert who knows how to solve a problem. I am the expert who knows how the technology works. This challenge to understand what exactly your client's claiming, what exactly is the problem of your client, is really a difference between, I would say, good developers and not-so-good developers. Because you need to investigate, you need to invest time, you need to listen, you need to have empathy, you need to have bunch of human feelings to create that solution. It's not like, listen for a prompt and propose a solution.

Amit Sion:

I'm sure that's been a big part of your journey and your maturity as a developer, being able to listen and not just build straight away. What would you say is, in your perspective, what is the difference between you as a developer at the beginning versus now? What are the attributes that have matured and improved over the years?

Bruno Germano:

I don't know exactly when this has happened, but it was between the year '21 and year '20. But I've always been these people that like to talk, like to meet people, like to be on a stage, like to be on camera. I had rock bands before. I have my YouTube channel for six years. I like to talk with people, I like people to see me. And in a workplace, in an office, I've always been this person who knows everyone, who knows the children's name of each party in my team. And so, I like to engage with people, I like to talk with people. 

During my career, I start to understand, talk with more experienced people than me in my workplace, that some things that I was thinking that was important, like learning everything about our language, was not so important. When you actually solve a problem for your client, this is important. You don't need to know the algo of each function you are writing, but if your client have a problem, solve it in the best way, cheaper away, fastest way is better than know exactly the algo of each function you are writing. But I learned this talking with people, talking with people with more experience than me, people with more years in tech than me. 

When I talk office and when I talk like this workplace, I go back in time and remember actually the office I was working. And I've been working remotely since 2018. I've been working for foreign companies remotely from Brazil six years. And this place doesn't exist anymore. It is not a physical place anymore. But I think now people watching this and, "Oh, I'm working remotely alone inside my home." But we have a big window for the world today, it's a really, really big window today. Call it your screens, you can watch YouTube videos, you can talk with different people on Instagram, you can send WhatsApp messages, Telegram messages, for almost every person in the world. And you can do that in your work, in your company, in the company that you are working. 

But I think today is harder to elevate this kind of skills since we are apart, I would say. Everyone is in a different place. But I can remember when I was a young developer, I was so immature. I used to remove some cables or put some tapes in the LAN cable so the people lost the connection. But when you remove, you don't see the tape, the transparent tape. But I remember one time when I was, don't know, 20, 21, really young—I'm close to my 40s today—I removed the laptop battery from my manager. At this time, the laptop, we had this, I don't know, this key downside when you can remove the battery to replace the battery. And since the laptop was connected to power, the laptop’s still working but I removed the battery. We were just planning to see my manager come back to the work and lost the laptop's power. And then he grabs the laptop, remove the power, and go to a client meeting. And he went to a client meeting without a battery.

Amit Sion:

Oh no.

Bruno Germano:

And then I was doing this just for laughs, just for jokes. But when he was back he say, "Who did this?" And then I need to blame me because I don't want to blame any other person in the office. And we had a long conversation about ownership, about responsibilities in the work. I didn't know his agenda, I didn't know he would have a client meeting after I removed the battery. But I learned that at the time, each one have his own responsibility. And maybe you don’t understand fully right now, but you—I did understand fully the responsibility of my manager to go to a client meeting with a battery. But at the time, I understand that each person is part of a big plan, a big engaged plan, that we would deliver a software at the end.

And I think I just told this story just to illustrate that it was not easy to learn all these skills. It was not just talking with people. Sometimes I make big mistakes, and you learn by your mistakes. And so, at the end, you need to make mistakes. You don't need to remove the battery of the laptop of your boss. But you need to make mistakes to learn. You need to talk with people to learn. It's really harder to learn alone. Learning together, listening, learning, reading other one's posts or other one's book documentation, is easier than just yourself, trying to take your steps alone.

Amit Sion:

I completely agree. I absolutely learned from my achievements and my successes, but from my mistakes and my failures, I really learned because—

Bruno Germano:

It's quicker.

Amit Sion:

Oh my goodness, the pain you feel wanting to avoid that pain again. It's like the whole thing of you touch fire, it burns your finger, you don't want to ever do that again. That pain is good for us. We need it. It's a gift because it allows us to level up, to mature, to know what not to do, which is just as important as what to do. 

There was something you said there before about, you've been working remote for a long time. And I'm very curious, for you as someone who does really enjoy that communication, that engagement with people, how do you find that work? Because for us, X-Team has been remote from the beginning, from 2006, always been remote. And for that time, for so many years before remote became a common thing, it was great because a lot of developers who are introverted like that, and they like the ability to just work from home. But for yourself who is quite extroverted, quite communicative, and all that, how do you find working remote aligning with your social behavior?

Bruno Germano:

I learned that I can have bunch of different relationships with people that's not working with me. At this time, I was so invested in working, in learning, and develop my career that I don't have this vision that I can have deep relationships with different persons beside my work. And then I— still extroverted, still this talking person—but now I go to a gym, now I go to a bar, now I go to parties, now I go to a park close by and meet a person doing the same routine I'm doing, and et cetera. 

But I still have this lack of connection in work, because we don't have this watercooler talk, we don't have this coffee talk. And even when we use some tech tricks to do that—like in the company I'm working today, we have this Slack channel called Watercooler Chat. And a random bot make a random suggestion every week so you can meet different persons. And I did this bunch of time, more than 20 times, I don't know. And it's different. The connection is different.

So I feel this pain, I feel this disconnection, but I'm trying to fill this need with different things. But I am not saying that I want to go back to office. I love to work remotely. This creates a bunch of opportunities for me. But we cannot have it all. We cannot have all these things in the same place, in the same position. But things that I tried before to solve this. I don't do this for a while, I think more than a year, but it was like calling some friends that's not working with me. Maybe not working with technology, they are working with different things. And we managed to go everyone to a cowork and spend one day, two days working together, talking together, having lunch together, just to have this connection again.

But today, I feel empowered to choose the people who I want to work with, even if they are not working in the same company, in the same industry. But I can choose. I can call friends, I can call, I don't know, people who I want to connect and say, "Hey, I have this two seats in the coworking, what do you think about, go there and spend the day working together?" And we don't need to work in the same company to do that today. But to be honest, I don't do that for a while. Maybe more than a year. But I did this before a bunch of times.

Amit Sion:

I think it's great that you hold onto that human connection, that human interaction that is so important to many of us. But something that's really neat in the way that you do it is that you're not just working from home. We have this principle of working remote can be working from anywhere. And I did see on your Instagram that you were recently traveling, but that wasn't just vacation. You were working through that, weren't you?

Bruno Germano:

Yeah. I love to use this statement that my work is remote. It's not working from home. I don't need to be at home to work. For sure, I have pretty good setup here. I love to work from home. But I also can work from anywhere else who has connection. I can bring my laptop and work. And recently, me and my wife, we took a long road trip to the end of the world. We are living in São Paulo. We grab our car, it was me, her, our cat, our laptops, and we put a Starlink at the top of the car, and we drove until the world's end, until Ushuaia in Argentina. It was an amazing trip. This was one of the things I was planning for a long time to do, meet some places that I'm afraid that I cannot meet later. We meet some glaciers, we meet some snow mountains, we met some places that are really wild and so different from our reality.

And we were planning this for, for sure, a long time. I recall before I was married—I've been married for 13 years—before I was marrying my wife, I was telling her that I want to go to Perito Moreno, one of the glaciers we met, with her because I'm afraid that this is melting, and we cannot have a chance to meet. But I've been invested in this trip for more than a year, like creating planes, creating routes, preparing the car, preparing ourselves. We need to have some idea what we were facing. We went from 40 Celsius degree to minus-3 in the same trip in 30 days. 

But the chance to work remotely makes all these things possible. I think could be harder to have 30 days straight for a vacation. Even in Brazil, that our laws say that you need to give your employees 30 days of vacation per year, it's really difficult to have the whole 30 days straight. You need to split this in two vacations during the year, et cetera. But working remotely, I have more advantage of the time zone because I'm working for a company in Mountain Time, and so we have four hours difference. And so I start to work four hours before they can start every day. And so, if it is 8 a.m. here, it's 4 a.m. for them. And so I use this small advantage of the time zone to drive during all these four hours. And so instead of start work 8 a.m, I start to work at noon. And so I use this four hours to drive during my trip.

So we leave from São Paulo during a Saturday, we drove the whole day. And Sunday, we drove for a whole day. And we were at Argentina already. And during the working days, we drove only four hours. During the morning, we woke up 4 a.m., 5 a.m., prepare ourselves, prepare the car, and drove for four hours, maybe five hours sometimes. And when we found a good place to spend the night, we stopped by, having lunch, work a lot. And actually, the work took more time, like to stop the work. Instead of stop work 5 p.m., 6 p.m., I was stopping the work 8 p.m., 9 p.m. sometimes. But it was a good effort to have this experience to work and, I don't know, meet the world. I would not say it's a vacation because it was not a vacation, but we had the chance to meet the world and not stopping to work.

Amit Sion:

Well, what you're doing is, you're not working, waiting for a vacation. What you're doing is you're living your life. And I think that's just beautiful. Because you don't want to be in that position that you are, 90% of your time when you're working, you're just waiting for that vacation to come. You are experiencing it every day. And Bruno, I got to say, you're an inspiration to how you're living your life and that's just beautiful. 

Thank you very much for this conversation. I've really enjoyed it. I've enjoyed getting to know you. I think that you really have a great positive attitude to development, to technology, to battling through the evolution of the tech space that we've got right now. But also how to learn and understand what your client's needs are and how to do it in a beautiful way, that you giving the best version of yourself to your work. So thank you so much for being on What the Code today. I've really enjoyed this conversation.

Bruno Germano:

I really enjoyed, too. Thank you for having me. It was really cool to recall these stories and tell for a new person. And it's cool for seeing you understand all my experiences, and it was cool for me to remember these good timings and et cetera. And I have just one final question: Was this an interview for a job? Because I can apply for X-Team today.

Amit Sion:

Oh, welcome to X-Team. You would be an amazing X-Teamer, you're exactly what we look for to come on board. X-Team.com, sign up, we'll have you. Our clients would love you. You are the epitome of what we search for.

Bruno Germano:

Thank you.

Amit Sion:

So we'd be delighted with that.

Bruno Germano:

This was my first time being interviewed, beside a job interview, in English, I would say. I had a bunch of other interviews in Portuguese, but in English, this is the first interview I had that's not a job interview.

Amit Sion:

Well, you smashed it. Can you please share with us your social media or your links so that people know where to find you, Bruno?

Bruno Germano:

Good. If you want to follow me, you can find me in every social network by @egermano. It's like my electronic version, egermano. You can find me on Instagram, Twitter, I don't know, Mastodon. YouTube, for sure. YouTube is my most active social network. You can find all my videos there, but my videos are in Portuguese. I don't know if you learn Portuguese, but you can watch. No, right now, YouTube had this new feature for auto-translating. You can listen in different language automatically using AI.

Amit Sion:

And now you've got this great content in English that we can add to it, as well.

Bruno Germano:

Yeah, yeah. This is the first content in English. I create content in English before, but was so short that I remove it.

Amit Sion:

Awesome. Well, thank you, Bruno. Really enjoyed this.

Bruno Germano:

Thank you, Amit. It was really nice to meet you. It was really nice to be part of this. Thank you.