We often romanticize youth when it comes to startups and that can certainly be debated, but I want to talk about an aspect of youth that is not as obvious on the surface - ignorance.
With domain experience we learn to intuitively know what is worth our time and how to accomplish our jobs in a way that we know to be effective. Over the years we learn what doesn’t work and what is just a waste of time. Along with this many people end up in the cliché situation of “we have always done it this way” or “that will never work”.
But things change; technology changes; possibilities change and it becomes very easy for the experienced among us to not realize it.
Coming from an electrical engineering perspective about 8 years ago I was not well engrossed in the history and standard techniques of software development. In my ignorance I began to believe that it would be possible to create a generalized solution to most crud apps and internal tools used in many businesses. I was told by those who had been around a lot longer and been traditionally taught that this was a foolish thought that had been attempted and failed many times before. So I began to work towards this goal building an application as a side project that I believed would solve this problem.
I then had an opportunity to work at a university that needed an internal portal developed - not quite what I was building and they had very specific backwards compatibility needs. I was given a one year contract to work on the problem - but I still wanted this general solution.
I began to merge some of the system I was building on the side into a customizable widget within this portal, and then moved more and more functionality to it until in the end I had what we called a microApp. The software began being internally adopted for new internal apps, then it began being used to port other applications into it because it was easier to maintain. In the end I was given permission to design from the ground up around the microApp system and my boss joined me.
We ended up with what would now be considered to be a low code development system that includes applications and workflows with built in version management, SSO, a secure data proxy, and much more that is used to build and manage the bulk of the IT infrastructure. The application was released by the university as an open source project https://github.com/EscherLabs/Graphene.
My current endeavor is derived from this effort to pull out the developers favorite feature (the microApp form builder) and flesh out the capabilities around that for other developers as a stand alone product.
The bottom line is that it would not exist if I had known that it was not possible. I don’t think that it’s a coincidence that many of the scientific and mathematical breakthroughs seem to be made by those still early in their careers before they have solid beliefs. So I encourage you to keep your mind open as well and I certainly try to do so myself.
Inspiring story and so true.
I believe it’s the same for building MVPs. It’s easier to build one if you’re still inexperienced and ignorant about all the software design patterns and user experience good practices out there. You just build towards your goal (the MVP) instead of worrying about how you’re building.
I’m an experienced developer but I was ignorant about the space I was entering. By accident I only researched a subsection of the market and wasn’t aware of the big players so I felt confident I could make a difference. Only after releasing and revenue growing did I find out about a couple serious competitors. Had I found out before I might’ve decided against pursuing it in the first place. But I didn’t and now I’ve taken my piece of the pie.
Very nice, and congratulations on getting your piece!
I think it's an important part of the story that you were actively working for a customer of your services/product.
Without that reality-check, it's very easy to build things nobody actually wants that sounds good on paper/in your own head.
If this story had happened the other way around - you spent 2 years building a microApps framework in isolation and then tried to sell it to a university as an off-the-shelf solution - I doubt it would've worked.
Not trying to belittle your story, I just think I'd frame it more as:
Yes. Ignorance is a wonderful opportunity, because the world is still open and full of possibility!
That is a very good point. Also when you are young you tend to have fewer responsibilities and less to lose. I interviewed an entrepreneur that created his first company in his teens and end up having a lot of success but I don't think that he would do it now that he is older...
That's so true, as we get older we definitely accumulate resistance to vulnerability and exposure when it comes to our stability
Ignorance or perhaps thinking from first principles? We cannot think from 1st principles in our every day life or we wouldn’t get much done and rely on common practices. But for topics that really may make a change in your life, ignoring common practices is highly advisable.
That’s not to say you should jump into anything just because you think differently about it, but you are better off doing tests, getting data and thinking on your own.
Yeah, thats probably a more accurate interpretation - it just becomes harder to do once you are deeply engrained in a knowledge area.
So true! We all solve the same problem in different ways, based on how we interpret cause and effect, and the skills we have.
Combining the work of 10 people solving the same problem in their own unique way can lead to new, well-rounded solutions that change everything :)
This comment was deleted 4 years ago.
This comment was deleted 3 years ago.
I rarely comment but I almost always appreciate your comments and posts and would like to read your take in its entirety. So...repost it! And let's see how it does in the current IH culture.
This comment was deleted 3 years ago.
This comment was deleted 2 years ago.