
Experience or Education?
07/05/18 • 55 min
In this episode of Building Infinite Red, we talk about the importance of education and experience when starting out in software development and how things change when you move from making your products to running your business. From books and online resources to bootcamps and higher education programs, Jamon, Ken, and Todd share their stories, insights, and opinions for every level of professional.
Show Links & Resources
Episode Transcript
TODD WERTH: Today's topic is education. I actually don't recall what this topic's about. Ken, do you recall?
KEN MILLER: Yeah. Well, it's this question that kind of comes up periodically about developers and CS degrees and that kind of thing. I think there was a Twitter thread a little while back in Jamon's feed, because Jamon's feed is the only feed that matters.
TODD: That's a fact. Yeah.
KEN: Yeah, do you remember who that was, Jamon?
JAMON HOLMGREN: Yeah. The question was, "I have 10 years experience developing sites, but I have no formal education. What are your thoughts on experience versus education? Been thinking of getting a front end development tech degree from Treehouse, but I'm not sure if it's worth the time and money." Yeah. That is a question that does come up fairy regularly.
KEN: For that specific question, I think the answer is no, it's probably not worth it, right? If you have 10 years of experience, and you're going to go take basically a practical degree, don't bother.
JAMON: Right.
KEN: But there are definitely nice things about getting a real CS degree, but getting a job is not necessarily the best reason to do it.
JAMON: Right.
KEN: If that make sense.
TODD: I would totally agree with that. Well, just to start out, the three of us, Jamon nor I have finished college, nor do we have any CS degrees. I learned to program on my own when I was a child, probably started when I was 12. And then I started programming professionally when I was about 24, and then I learned basically on the job.
Ken went to Harvard and got a CS degree there. Jamon, you are similar to me, right?
JAMON: I was pretty similar to you, yeah.
TODD: Yeah. So what I usually tell people, A, now, when I'm hiring people and I'm not representative of everyone, so it's quite a bit different, I do a cursory glance of their resume, maybe. That's less relevant to me than what they can do.
In my opinion, developers is a portfolio job, which means the work you've done is hugely more important than any kind of education.
Now, obviously if you do have a CS degree, I do find people want CS degrees, they understand some concepts that you maybe don't use day-to-day, and when they do come up, they have a much better understanding of that. Sometimes it's easier to teach them new ideas, because they have the analogy in their mind already. So it's definitely worth it.
I would say, my short answer and I'd love to expand on this further in this podcast, but my short answer is you need to learn what you need to learn in order to produce work product, which means develop software, develop websites, develop apps. And everyone has a different way of learning. For some people, school is the best way. For me, school always bored the hell out of me to be honest, and it wasn't the best way for me, but there's no exact right way for everyone. It's just however it works best for you.
JAMON: Yeah. And I think that part of this is how much access and opportunity you have, because certainly college is one fairly proven path toward gaining an opportunity to access the job market, to get enough skills that you're hireable out of the gate, and then to access the job market and actually get a little bit of exposure, whether it's through an internship or something like that.
So that plays into this as well, if your dad was a software engineer or something, and he has contacts that you can talk to and maybe get some opportunities, then maybe you don't need that, maybe you don't need to go down that road.
But there are few other factors here as well. Some of them are personal goals, like what type of programming, like Todd was saying, what type of programming you want to do, how much debt you're willing to take on, how much you can take on. And then also, in some cases, very specific cases, the prestige of the university can be a factor because it certainl...
In this episode of Building Infinite Red, we talk about the importance of education and experience when starting out in software development and how things change when you move from making your products to running your business. From books and online resources to bootcamps and higher education programs, Jamon, Ken, and Todd share their stories, insights, and opinions for every level of professional.
Show Links & Resources
Episode Transcript
TODD WERTH: Today's topic is education. I actually don't recall what this topic's about. Ken, do you recall?
KEN MILLER: Yeah. Well, it's this question that kind of comes up periodically about developers and CS degrees and that kind of thing. I think there was a Twitter thread a little while back in Jamon's feed, because Jamon's feed is the only feed that matters.
TODD: That's a fact. Yeah.
KEN: Yeah, do you remember who that was, Jamon?
JAMON HOLMGREN: Yeah. The question was, "I have 10 years experience developing sites, but I have no formal education. What are your thoughts on experience versus education? Been thinking of getting a front end development tech degree from Treehouse, but I'm not sure if it's worth the time and money." Yeah. That is a question that does come up fairy regularly.
KEN: For that specific question, I think the answer is no, it's probably not worth it, right? If you have 10 years of experience, and you're going to go take basically a practical degree, don't bother.
JAMON: Right.
KEN: But there are definitely nice things about getting a real CS degree, but getting a job is not necessarily the best reason to do it.
JAMON: Right.
KEN: If that make sense.
TODD: I would totally agree with that. Well, just to start out, the three of us, Jamon nor I have finished college, nor do we have any CS degrees. I learned to program on my own when I was a child, probably started when I was 12. And then I started programming professionally when I was about 24, and then I learned basically on the job.
Ken went to Harvard and got a CS degree there. Jamon, you are similar to me, right?
JAMON: I was pretty similar to you, yeah.
TODD: Yeah. So what I usually tell people, A, now, when I'm hiring people and I'm not representative of everyone, so it's quite a bit different, I do a cursory glance of their resume, maybe. That's less relevant to me than what they can do.
In my opinion, developers is a portfolio job, which means the work you've done is hugely more important than any kind of education.
Now, obviously if you do have a CS degree, I do find people want CS degrees, they understand some concepts that you maybe don't use day-to-day, and when they do come up, they have a much better understanding of that. Sometimes it's easier to teach them new ideas, because they have the analogy in their mind already. So it's definitely worth it.
I would say, my short answer and I'd love to expand on this further in this podcast, but my short answer is you need to learn what you need to learn in order to produce work product, which means develop software, develop websites, develop apps. And everyone has a different way of learning. For some people, school is the best way. For me, school always bored the hell out of me to be honest, and it wasn't the best way for me, but there's no exact right way for everyone. It's just however it works best for you.
JAMON: Yeah. And I think that part of this is how much access and opportunity you have, because certainly college is one fairly proven path toward gaining an opportunity to access the job market, to get enough skills that you're hireable out of the gate, and then to access the job market and actually get a little bit of exposure, whether it's through an internship or something like that.
So that plays into this as well, if your dad was a software engineer or something, and he has contacts that you can talk to and maybe get some opportunities, then maybe you don't need that, maybe you don't need to go down that road.
But there are few other factors here as well. Some of them are personal goals, like what type of programming, like Todd was saying, what type of programming you want to do, how much debt you're willing to take on, how much you can take on. And then also, in some cases, very specific cases, the prestige of the university can be a factor because it certainl...
Previous Episode

Fears and Anxieties of Running a Business
In this episode of Building Infinite Red, Jamon, Ken, and Todd touch on the fears, anxieties, and struggles of running a business. They share stories and thoughts on starting a business, managing stress, how success and failure impact focus, the difference between venture capital and other sources of funding, fear of missing out, and the importance of knowing what you stand for.
Show Links & Resources
Episode Transcript
TODD WERTH: So I thought a good topic today, one of the reasons because I'm personally interested actually, hear what Jamon has to say and Ken has to say, and of course I'm sure they're interested to hear what I have to say. But the topic is when you start a new business or you're an entrepreneur doing multiple businesses, or anything of that particular area. What are some of the biggest fears, anxieties, apprehensions, that you might have you know before the process, during the process, whenever? I find this very fascinating, because I imagine a lot of people, well maybe some people who are listening are experiencing these right now and A) it'd be great to hear someone else express the same thing so they know that they're not alone in this, and B) it's kind of interesting to think about yourself. It kind of, it's not something you typically sit down and think about, so if you two don't mind, that'd be a really interesting subject for today.
KEN MILLER: Sounds good.
JAMON HOLMGREN: Yeah. Well I think back to when I started by business. It was 2005, and I was working for a home builder at the time, so I had a, you know, decent job. It was an office job. I was doing I think cad design and marketing for this builder. Not really doing programming. But I decided that one of the things that ... well I had, prior to this time, I had thought, you know I'd be really nice to own my own business at some point. It'd be something that I would aspire to. And I think that part of that was my dad owning his own business and knowing a lot of entrepreneurs kind of played into that. I thought it would be an interesting thing. I've always been a little bit independent. Want to kind of set my own course.
So I started thinking about doing this and talking with my wife, and at the time I had a six month old baby. That was my first kid, my son, who is now 13 years old. Around actually this time of year is when I decided that I was going to do this. What helped was an opportunity that came up. So the apprehension of how do I get my first customer was sort of already taken care of. My uncle had a bunch of work that he needed done, and he asked me if I wanted to do it kind of on the side, or as a business, and that gave me the confidence to pull the trigger and say, let's so this. Because I had a built-in customer right away. But I do remember the first month sending my bill over to him, and it was only eleven hundred dollars, and that was all I had earned that whole month was eleven hundred dollars. And that was a wake up call to me that, hey I can't just expect the money to come in, and that was definitely ... I sat up and noticed.
TODD: Yeah, that's really interesting. So when you started ClearSight, that was your first company, correct? At that time?
JAMON: That's right. Yeah, ClearSight. There were other points along the way where I was sort of I got kind of gut-punched. Many times along the way. One was when ... my first business was doing websites, but it was also doing CAD designs, so I had essentially two business, and the CAD design part of it, you know designing homes, designing remodels, those sort of things eventually dried up, because remember that was during 2008, 2009 the housing recession kind of came along and that impacted the designers first, because we were the first ones in the process. People stopped taking money, equity out of their homes to do remodels. They just stopped doing it. So basically the whole market dried up.
I remember my uncle told me, "I don't have any work to send you anymore." And I had a few accounts myself, but they were pretty slow too. And I kind of sat at home for a few days and felt sorry for myself. But in typical Jamon fashion, I was like, well I guess it's time to go do this myself, so I went out and literally started knocking on doors at offices and stuff and handing out my business card. Wasn't too successful at that, but it was at least doing something, and then things turned around eventually.
TODD: Since you had a new baby at home, and obviously you're married, and you're trying to support them.
JAMON: Right.
TODD: Did...
Next Episode

Business Successes and Failures
In this episode of Building Infinite Red, Jamon, Ken, and Todd answer a question from the podcast channel in the Infinite Red Slack Community about what they have learned and observed from businesses over the years who have succeeded or failed.
Episode Transcript
CHRIS MARTIN: We had someone reach out on the podcast channel with an idea for an episode. He said: "You three must have watched a lot of businesses starting up/establishing themselves and subsequently succeeding or failing. What have you learned or observed from those businesses? In your view, what made them successful or otherwise?"
KEN MILLER: That is a great question. The first thing I would say is no one, literally no one can predict which company is going to succeed, especially like in a big way. The startups that we have been part of in our careers or, have worked for as clients, the ones that are trying to hit it big, there's no one who can predict that.
That said, we do see mistakes, we do see things that will hinder success or prevent it. One of the big ones I would say is having the wrong amount of money. That doesn't necessarily mean having to little although, that's by far the most common version, but sometimes having too much. I've seen startups that had so much money that they just wasted it and never had any discipline, and they crashed and burned.
So, having too much money surprisingly, can be a problem. Having too little is much more common, you don't hear about it as much, because they tend to fizzle in a very quiet way. There's a fairly frequent thing that we will encounter which is the self-funded entrepreneur who comes to us and says, "Hey, can you do this for $50,000?" The answer is almost always no. Any interesting app is likely to be more than $50,000. But more than that, if your only source of funding is your own life savings, or yours and your parents' life savings, that's a big red flag. Because it means that you have no room to move or develop or anything. If all you have is $50,000 to spend, and it's your life savings, and you want to build the business. I'm not saying don't do it. But what I am saying is you need to use that $50,000 to validate your idea more than you need to build an app or a website or whatever it is that you're looking for.
That can take a lot of forms, right? But take that $50,000, quit your job if you have a job, go interview customers, go do things that don't cost money that let you validate your idea. And then you can go find people who can help you. We are famously bootstrapped here, and the reason that we're able to do that is because consulting is a very easy thing to do the first one. Because it's just you, and you go out and get a contract and you grow from there.
A lot of businesses, that's not true. And if you need investors, because your idea has enough going on that you have to build something, then use the money you have to start that process rather than blow it all on an app that then can't grow because you've run out of money, Todd.
TODD WERTH: If the kind of business you want to build is $10,000 to actually build it, and then $50,000 is a great amount of money because then you can build it and iterate on it and have extra funds. The problem is something like an app that typically costs $100,000 or more is not only do you need the initial cost of it, you need all the capital to run that business and modifying and really adapt it to what you find the market actually wants.
That being said, there's nothing wrong with starting out bootstrapping. However, it is a little bit of a red flag if you haven't convinced anyone other than your mother to give you money for your idea, because if you can't convince one person, it's going to be hard to convince all the users to give you money to use for said business.
JAMON HOLMGREN: To play off of what Ken said earlier, I think that a lot of it is you want enough money that you're not making decisions based on fear, basing it on desperation. But you also don't want to be in a position where you just don't care. Where who cares if you blow this money because it's not your money and whatever. You need to have some level of skin in the game, so to speak.
KEN: Yeah, I would say that the ideal that we look for is whatever budget we think we need to build the most focused version of your app, we would love to see that you have two, three times that total somewhere. Not because we want to spend it for you, but because you're going to need it for something. And it's a measure of your health as a startup.
Even more ideal than that is, you have that much in hand, and you know what you're going to do to get more when you need it.
JAMON: Moving beyond the financial side of it. Another thing that I've observed in my 13 years of doing consulting work i...
If you like this episode you’ll love
Episode Comments
Generate a badge
Get a badge for your website that links back to this episode
<a href="https://goodpods.com/podcasts/building-infinite-red-63424/experience-or-education-3328634"> <img src="https://storage.googleapis.com/goodpods-images-bucket/badges/generic-badge-1.svg" alt="listen to experience or education? on goodpods" style="width: 225px" /> </a>
Copy