Robert Feranec, computer board designer and educator 

Welcome to Tech Explorations Podcast episode 9. I'm Peter Dalmaris, and in this episode, my guest is Robert Feranec. Robert is the founder of FEDEVEL Academy. He is well-known for his YouTube channel and his online courses on schematic design and PCB layout, where he teaches hardware design. Robert specializes in advanced digital development, with a focus on high-speed processor and motherboard design. He regularly posts on his well-curated blog, teaches on Udemy, and runs the Hardware Design Help Forum.

Robert creates content about electronics, Altium Designer, Cadence Allegro, and shares hardware design tips and tricks. In this interview, we cover a range of topics and explore Robert's journey as an engineer. If you design printed circuit boards, you'll find a lot of valuable insights in this episode.

Peter: Robert, great to finally have you on the Tech Explorations Podcast. How are you today?

Robert: I'm very well, Peter. How are you?

Peter: Pretty good! It's almost spring here, but today it started raining heavily.

Robert: Yes, it’s quite cold here as well. I’ve got my short sleeves on because I expected it to be warmer, but I had to bring out the heavier clothes again. How is it for you?

Peter: Well, it’s summer here, and it’s not as hot as California, but I’m really enjoying being back in Europe.

Peter: I’ve wanted to have you on the podcast for a while because you design motherboards and PCBs, something I’m very passionate about. Could you tell us how you got started with that?

Robert: After I finished university, I had a great opportunity to start designing products. I always wanted to design a motherboard—something running an operating system like Linux. Initially, I didn't know much about the different types of motherboards, such as x86 or ARM, but I learned a lot through a project where I had to figure out how to make it work. That’s where it all started.

Peter: Now you teach others how to design motherboards and complex PCBs. Can you tell us more about how you transitioned from designing boards to teaching?

Robert: After 8 to 10 years of designing boards and gaining experience, I received a lot of questions from people asking how to design these complex systems. I started writing a blog and making videos to share what I had learned. I realized that most of the knowledge wasn’t difficult—it just required someone to explain it clearly.

Peter: Were you still in university when you got that first job designing motherboards?

Robert: Yes, I was working on my master’s degree and had a project for a company. It wasn’t anything exciting—my first board was a keyboard design. But even from that simple project, I learned a lot. There were random interrupts caused by crosstalk, and that was my first experience with subtle design issues.

Peter: It’s amazing how even simple projects can teach you so much. Was it a team effort?

Robert: Yes, we were a small team of engineers. We split the project into different parts. One engineer worked on the DSP board, another on the microcontroller board, and I worked on the keyboard and some software. We had no real practical experience, so we learned a lot through trial and error.

Peter: That resonates with me. When I finished university, I felt like I didn’t know how to build products either. My first job involved building software, and I had to learn on the job. It’s a similar experience to yours—learning by doing.

Peter: After building that first keyboard PCB, how did things evolve for you? Did you take on more complex projects?

Robert: Yes, after finishing that project, I stayed at university to work on a larger project during my PhD. I then received a job offer from a company in 2003, where I worked on hardware for Internet calls using VoIP. At that time, it was a completely new technology.

Peter: I remember those early days of Internet telephony. How did that project go?

Robert: We designed both USB phones and Ethernet-connected phones, but the problem was that the Internet wasn’t fast enough back then, and the project didn’t succeed in the long term. However, because we built that initial platform, we started designing other boards for different clients, and I gained a lot of experience from those projects.

Peter: It sounds like that experience gave you exposure to a variety of projects, which helped you grow as a designer. When did you move into motherboard design?

Robert: Around 2004-2005, we started designing an in-car entertainment system—a screen to replace the traditional car radio. It was ahead of its time, but it led me to design my first x86 motherboard, which was a big step in my career.

Peter: That’s incredible. So, how did your career evolve from there?

Robert: After spending several years in the UK, I realized I wanted more freedom. I decided to move back to Slovakia, where living was more affordable, and started freelancing. I quickly found out that freelancing had its limits, especially in terms of financial security and work-life balance. That’s when I transitioned into teaching online courses.

Peter: How did you get started with teaching?

Robert: I started by writing a blog to promote myself and attract clients. Eventually, people started asking if they could pay for courses, so I created my first course. It worked well, and I realized that online teaching could provide a more sustainable and scalable income.

Peter: So, you went from freelancing to creating courses. What was the biggest challenge in making that transition?

Robert: The biggest challenge was getting enough visibility. I had to build a reputation and prove that I could offer valuable knowledge. But once I released my first course and saw its success, I knew I was on the right path.

Peter: That’s a great story. Let’s switch gears a bit and talk about some of the technical aspects of motherboard design. What are the top three challenges you face when designing high-density, high-speed PCBs?

Robert: One of the biggest challenges is proper layout. For example, when I designed my first processor module, I didn’t consider how difficult it would be to route the final 1% of the board. I ended up having to delete half of the layout and start over. Another challenge is managing crosstalk, especially in high-speed designs. The stackup of the PCB is critical, as well as ensuring the ground plane is close to signal layers.

Peter: Do you prefer manual routing or using an auto-router?

Robert: I’ve tried using auto-routers, but they don’t handle complex designs well. I once spent a week setting up an auto-router, only to find that it couldn’t finish the board. Manual routing gives you more control over signal integrity and ensures the board will be stable and reliable in the long term.

Peter: That makes sense. Before we wrap up, can you share your advice for PCB designers just starting out?

Robert: My best advice is to study the design guides provided by chip manufacturers. They explain exactly how to route the signals and design the board to ensure stability. Also, choose chips with good documentation—it will save you a lot of time and headaches later on.

Peter: That’s fantastic advice, Robert. Thank you so much for being on the podcast today. How can people find you online?

Robert: You can reach me via email at [email protected], or find me on LinkedIn, YouTube, and my blog. I post a lot of helpful videos and tutorials for hardware design engineers.

Peter: Thank you, Robert! It was a pleasure talking to you.

This concludes episode 9 of the Tech Explorations Podcast. You can find links to Robert's resources and contact information on our website, techexplorations.com. Subscribe to our podcast on iTunes, and we’ll see you next time!