Marco, so you're working as a Software Architect. What brought you to IT in general? Tell me your story.
Oh, well, when I was a kid, I got my first computer from an uncle and an aunt (Carlos and Lucy). They were kind enough to give me a computer. It had three gigabytes of disk memory and just a few megabytes of RAM. It was my first ever computer, and I got so interested in it. I started playing with it and using it every day, learning how to take advantage of it. I used it as a tool to improve on my homework and later on in university.
By the time I got to work, I was already very proficient with the computer, had advanced Excel skills, and everything needed to perform on a job. So, I decided to learn more and more about computers every chance I got. That first computer was the initial call – it sparked my curiosity and passion for IT.
Do you remember the model of your first computer? I'm curious because it's such a unique detail about everyone's tech journey. Our first computers often leave a lasting impression, sparking our interest in technology. What was yours like?
That's a good question! I think it was an old Windows Clone PC. It was quite bulky and had that classic beige color. I remember it had a floppy disk drive and ran on Windows 95. Back then, everything seemed so magical and complex. It's amazing how far technology has come since those days. I remember the chip. It was a Celeron II or something like that. Celeron doesn't exist anymore. It was Intel-based, and it was a clone that my uncle had built. He was also in software. He's also a software architect, and yeah, he assembled it and gave it to me with the Celeron II. It had a very slow processor, but it was enough to ignite my interest in technology.
Very interesting. What was your first programming project?
Yes, when I started learning programming, there was a little turtle that you had to move around and draw with by giving it commands. You would give it sentences, code sentences, and the turtle would move a certain number of pixels to the right, then up, and so on. The turtle would move and draw something based on the commands. My homework and projects involved drawing something interesting or whatever I wanted. That was my first encounter with coding. I remember I made a landscape or something like that. My God, those were exciting times! And that was in the 90s, around 1996 or 1997, I was like eight years old.
Absolutely! Hm, what I really like about being in a small company is that we're empowered to deal directly with our own customers. So, you have to be able to do a little bit of everything—whether it's sales, presentations, coding, databases, or infrastructure. You need to be quite knowledgeable in a variety of areas to function well on client projects. This versatility is key, and it's something I admire about my coworkers—they're all pretty knowledgeable across the board. It really defines our culture, and that's what I enjoy the most. I get to mix things up, like having presentations in July in Tennessee at KSCOPE, where we showcase the latest and greatest we’ve done this year, proof of concepts, and more. Good stuff. That's what I love about our culture.
I agree with that. When we talk about your job as a software architect, is it primarily focused on coding and programming, or does it encompass a broader scope?
Yeah, being a software architect is quite broad. It involves designing the architecture of the software, not just programming and not just applications. It encompasses database design, infrastructure, and more. Imagine it like building a whole house where you're responsible for plumbing, electricity, and every single detail. As an architect, you need to have knowledge across all these areas. Of course, you have a team of designers and specialists to support you, but understanding everything is crucial to making it all work.
Okay, let's discuss the latest project you've been involved in. What are you particularly proud of? You can share details about your most recent project or perhaps highlight one of your proudest achievements
Okay, yes. So currently, I have several active clients, most of whom I support ongoingly, and I take pride in this work because it requires continuous maintenance and readiness to tackle unforeseen challenges. However, the project I'm particularly proud of right now involves a client in the medical industry. They're developing modules and tests for respiratory illnesses where a single DNA sample can identify various types of flu — A, B, RSV, ECS SE2, COVID, and more. It's cutting-edge technology, and they're building machines to conduct these tests.
My role in this project is overseeing the team that connects the iPad to the machine, then integrates with an API, which in turn communicates with an application managing patient data, operator controls, and analytics of test results. I'm the lead architect for the Operator Portal application, and in the past month alone, I've developed approximately 80 new screens. The client has been impressed with our team's efficiency and collaboration.
I particularly enjoy working alongside Erik Espinoza, who handles the API, and Jason Canada, responsible for the database. Together, we form what Jerry aptly calls a 'team of A-players,' working swiftly and effectively. I'm incredibly proud of the progress we've made on this project, which promises significant success and potential future opportunities with this major client.
Over the past few years, we've encountered various challenges and gained valuable experience as a team. In my view, the most crucial factor for success is maintaining open and clear communication — both within the team and with external stakeholders like clients and upper management.
Effective communication means not just sharing information but ensuring it reaches the right channels and is understood. It's about being proactive in communication, ensuring everyone is informed and engaged. We've learned from past experiences where communication breakdowns occurred despite our efforts. Now, on our current project, we prioritize daily meetings and utilize multiple communication channels.
Personally, I have direct lines of communication with the CEO and clients, which facilitates transparency and alignment. This open communication approach is fundamental to our current success and ensures that everyone is on the same page.
I agree. What mistakes do you think are unacceptable when colleagues work together on a project?
Sometimes a team member might disappear and then reappear later in the project with their ideas not properly communicated. By that point, everything may have evolved into a state where reversing changes isn't possible anymore. This could even occur with a team leader, causing disruptions that are hard to recover from. It's definitely something teams strive to avoid.
With the rapid integration of AI in our lives and digital landscape, do you believe your job could be replaced by AI? If so, in what time frame do you foresee this happening?
I love that question. I have a master's in artificial intelligence, so I hope not. If anything, I aim to create models that could potentially replace my role in the future. At our company, we've embraced AI wholeheartedly, pioneering its integration. During conferences last year, we showcased numerous AI applications already implemented by our clients, positioning us well ahead of competitors.
I believe AI is best suited to replace repetitive tasks that don't effectively utilize human capabilities. For example, we've developed a system that automates purchase order identification, linking it with items, PO numbers, and vendor details. This frees up our accountants' time, allowing them to focus on more critical tasks. Ultimately, AI enhances efficiency and enables humans to engage in more impactful work.
If your computer could talk, what do you think it would say to you first thing in the morning?
Oh, well, I'm a big coffee lover, so my computer would probably ask, 'Have you had your cafecito?' It's a little Spanish term for 'coffee,' kind of like coffee CTO! 😂
Haha, well, here's a fun fact about me. I'm actually internationally certified to roast coffee at two out of three levels. I'm pretty handy at making my own brew, which everyone in the office knows because I always have my coffee on hand. They might not realize it, but I'm a bit of a coffee snob! I pursued this certification purely as a hobby—I enjoy exploring the intricacies of coffee roasting and even bought my own roaster to experiment with.
I first got into it during a vacation in Guatemala, where I took classes and exams for the certification. It was a bit unexpected, but it's been a fun journey. Now, I enjoy collaborating with local coffee shops, roasting beans together. It's a passion of mine, completely separate from my professional life.
Oh, besides tech, I mainly play the guitar. I used to be in a band for 10 years when I was younger. I also enjoy playing video games and tennis — I was on the university tennis team for my engineering group. Those are my main hobbies, I would say.
Marco Pereira is a seasoned Software Architect at Viscosity North America, specializing in Oracle APEX and JavaScript. His expertise extends through SQL and Python, with a strong foundation in comprehensive software development, particularly in crafting robust solutions using Oracle technologies.