<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam Hill on Medium]]></title>
        <description><![CDATA[Stories by Adam Hill on Medium]]></description>
        <link>https://medium.com/@adamvhill?source=rss-c5153d19c15------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*w2tUB5dkjGaGKe8OzWI25g.jpeg</url>
            <title>Stories by Adam Hill on Medium</title>
            <link>https://medium.com/@adamvhill?source=rss-c5153d19c15------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:51:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamvhill/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Should you attend a code school or code camp?]]></title>
            <link>https://adamvhill.medium.com/should-you-attend-a-code-school-or-code-camp-a1eac865603d?source=rss-c5153d19c15------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1eac865603d</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[learn-to-code]]></category>
            <category><![CDATA[general-assembly]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Adam Hill]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 19:49:04 GMT</pubDate>
            <atom:updated>2021-02-12T22:47:07.693Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*YulCmAWFsbCOvuNT.jpg" /></figure><p>Code schools are increasingly popular, and why wouldn’t they be? Software development is a growing field and has been in higher demand for the last few decades. There is a lack of software developers in the US, and the pay is excellent. After all, developers start at $130,000 a year at Facebook, right? (They do)</p><p>So it’s enticing to look at a code school and think that in 12 weeks, you can get an entry-level software development job. For around $10k, you can completely switch your career in a few months. It’s a wonderful proposition.</p><p>But should you do it? I cannot answer that question (spoiler), but I can provide some guidance from my experience.</p><h3>A little background on my experience</h3><p>I’m in my late 30’s. I have an undergrad degree in business and have worked with startups and small technology companies for my whole career.</p><p>I went through a code school myself, about six years ago, that focused on backend development (Ruby code, Rails framework). While there, I built an app that we used at my day job for 2+ years.</p><p>I learned a lot, and I enjoyed it. I wasn’t sure if I was looking for a career change at the time, and I didn’t pivot into a career in software development. I did go on to work with software developers and have hired more than a hundred developers in the years since for various companies.</p><p>I’ve recruited experienced developers with 20 years of experience, developers fresh out of college, and developers who got their start in a code school. These are the lessons I’ve learned from hiring and working with these various groups.</p><h3>What code schools do (and do not) provide</h3><p>In some ways, code schools are far ahead of university degree programs. Most universities teach things that you won’t use on the job. It’s hard for university classes to change at the pace that software development does in the real world. So their curriculum is years behind the marketplace.</p><p>On the other hand, code schools teach the practical things you need to accomplish your tasks in the real world. They tend to focus on a specific technology and teach the practical things you need to know to get started.</p><p>So, code schools are the way to go, right? Not so fast.</p><h3>What code schools don’t teach</h3><h4>First Principles, or a Developer Mindset</h4><p>The concept of “First Principles” is a bit difficult to explain. And, as a non-developer, any explanation I attempt will invariably be wrong. But I’ll give it a shot anyway.</p><p>Good developers don’t just know the HOW. They also seek to understand the WHY. Knowing the principles behind the code gives you a deeper understanding of the problem you’re trying to solve. It leads to better solutions that hold up over a longer time. It leads to code that not only solves the problem, but solves it in a better way, improves the code, and gives the code base a better chance for future iteration.</p><p>Let me try to explain this with an analogy.</p><p>You’re building a house, and you’re tasked with keeping it warm during the winter. Easy, you know how to do that, you buy ten space heaters and fill the house with them. Does this solve the problem? Yes, with a space heater in every room, the house is definitely warm. You’ve solved the problem. The house has a good chance of burning down, and the space heaters use a ton of electricity, but that wasn’t the problem you were presented with.</p><p>Now, if you understood first principles, you would take a different approach. You would start with the problem and look at the causes. Houses lose heat in the winter because of poor insulation, so you insulate the walls and put in energy-efficient windows. You also install a radiant heating system because the house already has gas. You know that a radiator and a well-insulated home will last.</p><p>Both solutions solve the problem, the house is warm in the winter, but the first ignores the causes and uses the simplest possible solution. This is the difference between an understanding of first principles and a lack thereof.</p><h4>Experience working with a team</h4><p>Yes, you will do team projects in both a code school and at a university. But you typically will not learn the complexities of code reviews, push and pull requests, or best practices of modern version-control systems.</p><p>Your code is built in the way that you learned, and that’s fine. But your code hasn’t been integrated into larger systems and intermingled with other developers’ code. If it has, it’s likely been a part of a system designed and built by others with your same level of experience.</p><p>This is true regardless of the source of your coding education.</p><h4>Ability to learn</h4><p>Neither code schools, nor universities, really teach this. But it’s the #1 thing I’ve looked for in hiring developers over the years. Do you have the drive, and the ability, to learn and improve on your own.</p><p>Yes, you had the initiative to join a code school, but how much have you learned outside the context of that school’s program?</p><p>Every code school I’m aware of will have you work on a project. That project is not your resume and doesn’t show me that you’ve gained the ability to learn. It shows me that you followed instructions and completed your code school.</p><p>The questions I typically ask to dig into this:</p><ul><li>Did you learn something entirely on your own?</li><li>Did your code school teach you javascript, and you took it upon yourself to learn a javascript framework not taught in your classes?</li><li>Did you work on a personal or team project outside of the context of the school itself?</li><li>What’s the thing you’re learning now that you’ve left your code school?</li></ul><p>These are the questions I have asked junior developers, both code school grads, university grads, and the purely self-taught developer. I find these answers to be critical markers of the potential success of a new hire.</p><h3>Should you attend a code school?</h3><p>Despite the issues I mentioned above, I am a big believer in code schools. There are many excellent schools, and some bad ones for sure. One of the biggest is General Assembly, but my personal favorite that I recommend is <a href="https://lddy.no/udim">Tech Talent South</a>*.</p><p>If you’re looking for a career change, it can be an excellent opportunity. It will be faster than learning on your own, and it will likely be better than learning with a purely online/self-paced system. But it is important to understand what code schools can and cannot teach you and what you may lack as a developer coming out of the school.</p><p>You should make sure you’re prepared to commit to learning outside of the code school curriculum. Development is constantly changing, and becoming a developer means committing to continually learning. Joining a code school can be a suitable catalyst, but it is not the end of the process.</p><p>As I mentioned, I went to a code school to learn without intending on changing my career. It was a lot of work, but I enjoyed it immensely. It has added value to my career and has given me some insight into my colleagues’ work.</p><p><em>*Disclosure, I have no stake in Tech Talent South. I’ve met the founder and much of the team in the past and have hired their students. The link above is an affiliate link that provides you with a discount, but you can visit them directly at </em><a href="https://www.techtalentsouth.com/"><em>https://www.techtalentsouth.com </em></a><em>.</em></p><p><em>Originally published at </em><a href="https://www.nolane.us/post/should-you-attend-a-code-school-or-code-camp"><em>https://www.nolane.us</em></a><em> on February 3, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1eac865603d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup Fundraising Basics]]></title>
            <link>https://adamvhill.medium.com/startup-fundraising-basics-6ea29982b8de?source=rss-c5153d19c15------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ea29982b8de</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Adam Hill]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 21:31:27 GMT</pubDate>
            <atom:updated>2018-03-21T21:31:27.818Z</atom:updated>
            <content:encoded><![CDATA[<p>Most entrepreneurs, if they’ve raised capital, have struggled to raise at one point or another. Let’s face it, fundraising is HARD. You’re setting out for a task that you’ve probably never attempted before, reaching out to investors that you’ve never met or, if you’ve been building a good network, you’ve only met casually. Asking for money is uncomfortable for most people, even if it’s money for something in which you genuinely believe.</p><p>But, it’s not insurmountable. Thousands of people raise millions of dollars every year. In 2017, there were over 13,000 seed/angel deals done with an average value of around $1 million. If we dig further into the angel deal space, the deal size gets smaller. Nationally, Angel groups invest a median amount of just $120k per deal at an average pre-money valuation of $3.5M. It’s important to note that the deal size is typically much higher, it’s just that the contribution from angel groups isn’t the total investment. The takeaway here is that, if you’re looking to raise $500k or more, you probably won’t find that all from one angel group.</p><p>So, if you’re raising for the first time, here are some things to keep in mind:</p><h4><strong>It takes time</strong></h4><p>Maybe the most obvious point here, but entrepreneurs frequently underestimate the amount of time and energy required to raise capital. You can be so enamored with your idea that you are taken aback that every investor doesn’t jump at the chance to throw money at you. The platitudes are that raising capital is a full-time job (or can be) and that it will take six months or longer. The actual timeline is so unique that estimates and averages are almost worthless to the individual. The best advice on a timeline is to figure out your runway (how long can you last without cash), and that gives you your deadline. You have to raise before you’re broke. I would personally feel much better with an eight-month timeline than a two-month timeline.</p><h4><strong>You are more important than your idea</strong></h4><p>You and your team are far more important than the strength of your idea. Yes, ideas matter, but it’s in the execution that ideas become valuable. Overstating the importance of this is difficult. Investors look for entrepreneurs that can execute on those good ideas. If you cannot demonstrate your ability to build a team, create your product/service, sell to customers, build a user base, etc. your ideas are worthless.</p><p>Every entrepreneur thinks they can execute on their idea, the only way to prove this is to have experience in a previous company or to have traction.</p><h4><strong>Traction is the key to successful fundraising</strong></h4><p>Your ability to execute is proven by the traction you already have. So many entrepreneurs think they have to raise money right away, and some of them do, but raising before you have reasonable traction will kill your ability to find investors. If you’re trying to build an app that’s dependent on a large user base to be successful, but you’ve only developed a user base of 5,000 (and only 500 of them are active) you are far from proving anything. When you go to a potential investor, the familiar refrain is “come back when you have X number of users.” Why do they say that? They’re not trying to be difficult; they just want to see a demonstration of your ability to succeed.</p><p>This reality can be difficult for entrepreneurs and leads to a sort of chicken and egg problem. You need capital to build/market your product. Without that capital how will you get the traction that you need to prove your value to an investor? It is the fundamental challenge you’ll face early in the fundraising process. Entrepreneurs who want (or need) to raise cash before they’re ready will almost always fail. There are a handful of solutions here:</p><ul><li>If you’re fortunate, you’ll have the capital to personally grow the business to the point where you can raise an external round.</li><li>Pre-seed or the “family, friends and fools” round. The implication being that those are the only people who would give you money.</li><li>Bootstrap, the often overused term, really just means hustling to figure it out until you’re able to raise cash. Build your idea on the side, learn to code so you can build your app yourself, etc.</li></ul><h4><strong>Some businesses never get funded</strong></h4><p>It’s common sense that you can fail at raising capital, but many entrepreneurs don’t want to go there. It’s important to think about your business from the investors perspective and ask “why would I invest in this company?” Removing the bias you have for the business you’re building is almost impossible, but it’s essential. It can help you learn when to give up and move on to the next idea.</p><p><em>References:<br>Chrunchbase Global VC Report: </em><a href="https://news.crunchbase.com/news/q4-2017-global-report-vc-sets-annual-records-back-strong-late-stage-results/"><em>https://news.crunchbase.com/news/q4-2017-global-report-vc-sets-annual-records-back-strong-late-stage-results/</em></a><em><br>Halo Report: </em><a href="https://www.angelresourceinstitute.org/media/upload/full-report-2017haloreport.pdf"><em>https://www.angelresourceinstitute.org/media/upload/full-report-2017haloreport.pdf</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ea29982b8de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>