recommended reading

No Three-Month Course Can Teach You How to Code


Organizations such as Codecademy, the Flatiron School, and General Assembly regularly get lauded for churning out legions of seemingly qualified engineers. The latest came in a recent Wall Street Journal article headlined, “Have Liberal Arts Degree, Will Code.” Student X took Course Y and in a mere three months became an amazing developer now working for SuperStartup earning a salary far above the national average. How can you not love that story?

While these coding crash courses advertise a simple and easy path, the transition is actually a lot more complicated. Like the anecdotes in the Journal article, I too am a self-taught software engineer. And the reality is there’s no three-month course (intensive or otherwise) that can magically turn someone into a top engineer. The first 10,000 hours alone merely catch you up to your key competition for developer positions, the recent computer science grads.

Indeed, the journey usually goes a little more like this: You make the decision to become a web developer, likely because you’re not passionate about your current line of work, or think being a software engineer is cool. Next, you apply to a bunch of intensive, three-month web development classes, all of which promise to turn you into a marketable developer. In one of these course you will learn some of the basics of web development, from using the Ruby on Rails web framework to adding some extra functionality to a webview with JavaScript. At the end of three months, you’ll have gone from knowing nothing to building a website, which is real accomplishment.

Then, however, it’s time to complete your transition. You’re no longer in a “sandbox” with a planned curriculum and teacher on hand. Top companies expect you to know what a recent comp-sci graduate would know, which could include SQL vs. NoSQL databases, the time complexity of some algorithm, or how to implement binary search. As for the job placement advertised as part of these classes, those opportunities are few and far between.

While there are some excellent companies willing to hire driven and intelligent self-taught engineers, they lie in the minority. Many companies pass over candidates without a formal degree in computer science before reading on; the stigma of low experience is a hard one to break in any industry but especially in those involving technical abilities.

Before this turns into purely a precautionary tale, there are certainly words of encouragement to be shared. The amazing thing about software engineering is that these days it really is a meritocracy if you can prove you’re worth paying attention to.

Notwithstanding the tech industry’s well-documented age and gender discrimination trends in hiring, or perhaps even in spite of these, there is still a chance for anyone to be hired in these roles especially with growing pressure to keep up with rapidly evolving technologies combined with the dearth of qualified engineers.

Additionally, there is greater focus on company culture, especially within the startup scene preferred by so many fresh-faced developers. Based on your company’s culture and needs, the benefits of hiring a self-taught developer could be worth your while. Making the shift requires determination, drive and initiative—all valuable transferable skills. They also have something else over straight-up engineers: knowing what it’s like to not know the jargon, bridging the gap between an organization’s technical and non-technical employees.

But going from cold-emailing Android and iOS developers about mobile-advertising solutions to working on third party data integrations took far longer than the length of a single course. Eighteen months ago, I never could have imagined feeling this confidently legitimate in my new profession, let alone having my second full-time job as a developer be at my current employer. I owe a lot to the people, past and present, who not only took a chance on my willingness to learn, but also took the time to humor me and help me grow.

So if the curiosity is there, it’s worth it to start learning in your spare time. And if the curiosity stays and turns into passion, dive into the details, ask yourself (and anyone who will listen) the hard questions. Most importantly, be prepared to work really, really hard.

Follow Chris on Twitter @triplec1988We welcome your comments

(Image via scyther5/

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.