Interview with Miro Samek of Quantum Leaps conducted by Leonardo Held in February 2021. Published in Portuguese in “Embarcados”.
What is Quantum Leaps?
Quantum Leaps is an embedded software company on a mission to bring “quantum leaps” in quality and productivity to embedded systems programming. The company’s flagship products are: the QP Real-Time Embedded Frameworks (RTEFs), the QM Model-Based Design (MBD) tool, and the QTools collection. These unique products enable embedded software engineers to apply modern, reactive software architecture, hierarchical state machines, model based design and automatic code generation in small embedded systems, such as ARM Cortex-M MCUs (micro-controller units).
How old were you when you first started QL?
How was your previous experience with this type of business?
Before founding Quantum Leaps, I had 15-20 years of experience in embedded software development, depending if you count my Ph.D. research. After my Ph.D. in the area of experimental nuclear physics in Germany, I worked on safety-critical embedded software at GE Medical Systems in Wisconsin (3 years). I then moved to Silicon Valley, where I worked for two startup companies specializing in GPS technologies (8 years).
Concept of Self
I saw the education section on your LinkedIn profile, and it's really outstanding. Do you believe your formal education was essential for your life as an entrepreneur?
I think that physics is a good starting point for any technical career. The pace of change nowadays is such that in college, you simply cannot know what will be needed 10, 20 years later. But physics gives you really deep understanding of the fundamentals, which you can then apply to any technical field. For example, in my career I had to quickly grasp nuances of X-ray generation and detection in medical imaging. Later, I needed to deeply understand GPS, which is a complex system. A solid background in physics helped me every time.
As far as the degree is concerned, I’m not sure that you need to go all the way to the Ph.D. level, but an advanced degree opens a lot of doors and career opportunities. It certainly helped me in this respect.
Do you believe that everybody is fit for creating and running a business?
I can only speak about the embedded software business, which to me is a craft. Consequently, starting a business in this filed is to me very much like a master of a craft setting up his or her own shop. My main point is that starting a business is a culmination of a career, not the beginning of it. It’s a destination of a long journey, from apprentice, through “journey man” to a master with his own unique “style”. In this sense I don’t think that everybody has what it takes to accomplish such a journey. But if you do have the passion, the patience, and you finally find your own unique “style”, by all means, start your own business!
What was your dream when you created QL?
The dream was actually not to start a business. The dream was only to write better software and to have more fun doing so.
Is profit a priority? What are your thoughts on the "sell fast, get rich" mentality some startups seem to have?
Profit is an important consideration to any business, not so much to “get rich fast”, but simply to survive. In my case, I had the working software product, I had published a book about it, I wrote articles, I spoke at the conferences. But I didn’t have an idea how to make money off of all this, so I couldn’t start a business. This came only after I discovered the dual-licensing business model. (Specifically, the business model called “single-vendor commercial open source”). So, to any technical person, who dreams of being their own boss, I would advise to pay attention to the business models and to the various ways of IP (intellectual property) licensing. For a successful, sustainable business, these ingredients are as important as the actual products or services.
What the idea for QL originally was and how it came to be?
Before Quantum Leaps I had only a vague sense that the embedded software I had to maintain could be designed more elegantly. The breakthrough for me was the book “Real-Time Object-Oriented Modeling (ROOM)”, which I read in the mid 1990s. I read and re-read the book several times and realized that all real-time embedded software could and should be created that way. So, my first goal became to apply this in my own software. For many reasons, I couldn’t use the big ROOM modeling toolset, so I was forced to apply the method manually and to distill it to its essence. I ended up creating a very stripped down version of the “ROOM Virtual Machine”, which was the layer of software that bridged the semantic gap between higher-level concepts like “ROOM actors” or “ROOM state machines” and the C programming language. This software layer later evolved into the QP Real-Time Embedded Frameworks. I created this with the realization that such a framework could be useful in many embedded projects and can either entirely replace, or work on top of a traditional RTOS (Real-Time Operating System).
This is perhaps the most important aspect of the Quantum Leaps story. The flagship product of the company was created and went though countless iterations a long time before the business was started. Only after seeing that the framework worked (flawlessly) inside a GPS receiver–a very challenging hard real-time environment–I had the audacity to start a business around it. I consider this my “master work” that entitled me to setting up my own shop.
Your video course on YouTube shows that you also have talent for teaching. Have you ever thought about changing businesses?
Teaching is very much a part of being a “master” of your craft. Masters always took apprentices to pass on their skills. In this sense, teaching is not a change of business. It’s the integral part of the business.
Additionally, in the embedded software field, I found out that there is no established curriculum, because our discipline falls through the cracks somewhere between EE (Electrical Engineering) and CS (Computer Science). Consequently, practicing embedded software engineers don’t have an established common understanding and terminology. Almost every term we use means different things to different people. The “Modern Embedded Systems Programming” video course on YouTube is my response to this need of establishing a curriculum and terminology of our discipline.
What tells QL apart from others?
Quantum Leaps offers unique products and different paradigm than the currently dominating approach. This might not suit every team, but if offers a choice to open-minded teams, who want to take their software development to the next level.
Work as an Entrepreneur
What kinds of hardships you went through with QL and how did you manage to surpass them?
A journey of 15-20 years is bound to hit many obstacles. But I consider myself fortunate that:
- I discovered my goal relatively early; and
- that no other business did it better ahead of Quantum Leaps.
Once I had the goal of scaling down the “ROOM method” to small, deeply embedded microcontrollers I could shape all other decisions around it. So, for example, after leaving GE I carefully chose my next employment to be at a place where they were just starting a new suitable project, as opposed to maintaining an already existing product. I was specifically looking for a “test bed” for my ideas. This was not necessarily the best paying job, but that was a good place and good team to do exactly what I needed.
Speaking of hardships, the hardest part was to keep at my thing after my “day job”. So, instead of going back to my family, I stayed long evenings and weekends after everyone left to test, iterate, and refine my framework. I then had to swap it and replace the previous version in the working project. Later, I applied the same extra effort strategy to writing my first book (“Practical Statecharts in C/C++”) about the framework.
But this is how it is. I believe that in the end only the extra effort, above and beyond your “day job”, puts you ahead.
Have you ever thought about quitting? If so, why?
Sure, I had occasional thoughts about quitting. But then, I didn’t want to keep writing the usual “spaghetti code” and keep chasing race conditions in a traditional RTOS-based deisgn for the rest of my career. Once you experience a better way of doing your job, it’s really hard to go back. So, I realized that I really had no alternatives.
Are you happy with the work you do?
Oh, yes. Definitely. Just look: a few years of extra effort have bought me already 15 years of freedom and fun doing what I like! And I’m not done yet…
Did you have any support from mentors or family?
Yes, I was fortunate to have support from my family and from the local community in the Valley. I was very positively surprised how willing some of the seasoned CEOs were to take my phone calls and answer my rookie questions about starting a company. I think this is something very special about Silicon Valley.
How did you sell the idea? Was there a market gap that you saw and fulfilled?
Actually, I did a poor job of selling my ideas (for profit). I just published a book and the code with a rather unprofessional, quasi-open licensing statement. One day, a big company called me and asked about the possibility of licensing the software “properly” for a closed-source project. Only then I realized that some businesses were willing to pay for avoiding open source licensing. This was the beginning of the dual-licensing business model.
How to choose a team? What are some of the difficulties you found working with people?
As most entrepreneurs, I was afraid of “going solo” and my first instinct was to look for partners, and so I did. But this complicated so many things right at the beginning when you don’t know about the valuation, the company stock, the allocation of shares, the “business plan”, etc. Eventually, I decided to start alone and it made my life so much simpler.
Later, I found more like-minded people, mostly through conferences, and mutual friends. But I haven’t built a traditional team. Instead the “team” largely consists of independent consultants that provide training for Quantum Leaps, for example, or help companies in projects based on Quantum Leaps software.
I still do most of the embedded software development myself, because I believe this is the only way to achieve and maintain the high conceptual integrity of the software. Good software architecture cannot be “outsourced”. Rather it must be a product of essentially a single mind of someone who deeply cares about such stuff. Embedded programming is perhaps the last software discipline, where it is still possible.
In the end, the business model of Quantum Leaps has been only possible because of the Internet. The recent pandemic shows that such loosely coupled, remote teams turn out to be more flexible, more resilient and even more motivated that “traditional” employees. It seems that more and more businesses will migrate towards this style of work.
What's in store for QL in the next 10 years? Are there any well established plans?
I hope that within the next decade we will finally see a “critical mass” of adopters of the modern way of developing embedded software. This requires a paradigm shift from the currently dominating RTOS-centered approach to new design patterns based on event-driven, autonomous components called “active objects” or “actors”. Also, we need to move up to a higher level of abstraction and the right abstractions, such as hierarchical state machines, to apply visual modeling and automatic code generation. This is exactly what Quantum Leaps is all about.
Did you do any research before starting QL?
If you mean a formal market research then no, I didn’t do it. But I knew the value of the software, because I used it in the real-life product (a complex GPS receiver at this point).
How do you search for innovation? Is innovation necessary for staying in the current market?
Yes, of course, you have to innovate to stay relevant. In case of Quantum Leaps, the main ideas for innovation come from carefully listening to the engineers who use the software in a huge variety of projects. This is one of the main benefits of having both, the open source community and commercial customers.
By listening “carefully”, I mean not accepting all feature requests as they are presented. Rather, I mean trying to understand the real needs and the underlying problems that the users of the software face. The actual solution is sometimes very different from what a customer originally suggested. All this goes really back to maintaining the high conceptual integrity of the software.
What's the biggest quality and what's the biggest flaw in QL?
I believe that the biggest quality of Quantum Leaps is the high conceptual integrity of the software. Bigger teams of constantly changing developers simply cannot create that.
The biggest flaw is the slow speed at which some requests can be implemented. For example, in embedded programming customers constantly ask for new ports (i.e., adaptations) of the Quantum Leaps software to new types of processors, real-time operating systems, and other types of third-party software. Bigger teams could obviously handle such workload faster.
Did it take long to start having a net positive financial situation?
Quantum Leaps has been profitable from the inception and has never taken any debt or external funding. This is because the company had been started with an already existing and working product.
How did you initially fund QL? Did you look for any private investors or firms like Y-Combinator?
No. Taking other people’s money limits your freedom of what you can and cannot do with your business. This was incompatible with my main goal of being truly independent.
Watching from outside, good businesses never seem to fail. Have you ever failed in business?
Not yet. The company has existed since 2005 and survived market downturns, such as the “great recession” of 2008-9. The company is flexible and has remarkably low fixed costs.
What's the biggest threat for businesses like QL?
Quantum Leaps exists because other businesses commercially license our software. The biggest threat to this is widespread disregard for intellectual property rights (software piracy and software plagiarism). Unfortunately, outsourcing of embedded software development often leads to a “lax” attitude towards license infringement. This is really unfortunate, because everybody loses when this happens. There is a reason why innovative, high-quality software like our QP frameworks have not and will not be developed in environments that routinely disregard intellectual property rights.
Do software companies have to think about ecological sustainability?
This is one of the main issues of our time. Embedded software will undoubtedly play a big role in all aspects of this, from electronic products that reduce emissions to enabling sustainable practices (e.g., robotic farming with much fewer chemicals). In all these aspects Quantum Leaps software can be very helpful. Also, the QP frameworks are ideal for low-power designs.
How do you see open-source and SaaS as a part of the shared economy?
Quantum Leaps has been built on open source, and I believe that the importance of open source will only grow in embedded systems. But to be valuable, any type of software must be actively maintained, enhanced and supported.
With so much software available from the Internet, some developers might think that they want completely “free” software (“free” as “free beer”), but they really don’t. For example, after the recent rush of acquisitions of RTOS vendors, we see a lot of the previously expensive commercial software now available on GitHub for “free”, under permissive open source licenses. But the software is effectively abandoned and no longer maintained and supported. I don’t think that many companies would like to base their products on such software anymore.
In hindsight, what would've liked to known when you first started?
I wish I knew more abut IP licensing, because this would allow me to start Quantum Leaps a few years earlier. I also wish I knew more about Internet and pay more attention to the discipline now known as SEO (search engine optimization). By this I mean not just having a nice looking website, but to design every piece of information, documentation, articles, and videos for searchability. For this you need to think backwards, starting with how you wish your information to be found and only then fleshing out the content to exactly match that searchability criteria.
Would you do something different?
Of course if I were to launch Quantum Leaps now, it will be different. But I think that the most important decisions were largely correct at the time.
Any tips for engineering students who want to follow some of your steps?
It’s really hard to give a universal advice, because everyone needs to find what they want. Actually, this is the hardest part, because once you find what you really want, you just have to do it.