<p>I thought I'd take a moment today to talk about what it takes to make it as a lowly web
developer :)</p>

<h3>Disclaimer</h3>
<p>First thing I should mention may be hard to hear, but if you find you have to force
yourself to code month after month and nothing clicks: it may not be for you. I've
worked with many people who were natural programmers, they get a huge kick out of
solving little problems, and if you don't have this I want to encourage you to look
elsewhere. If you aren't losing sleep dreaming about code and fantasizing about some
cool architecture, odds are it's not for you.</p>
<p>However bad this sounds, this is also just as beautiful: you don't need anything but
passion and hours invested to succeed. Your natural talent will put you ahead of thousands,
unwilling to lose sleep over some problem, vying for these high income jobs.</p>
<h3>How do I get a gig?</h3>
<p>A lot of people, I believe, feel like they need some certifications or other kind of
approval from someone else to code or do their own project. Just. start. doing. it!
You love some song? Make a website about it and learn about positioning elements on a page.</p>
<p>You have to do project after project, solving as many problems as you can with code.
Put those projects on github. Host them via Heroku or some-such.</p>
<p>Show people the awesome stuff you're making. Go to meet ups. Make presentations about
them. Get good at talking about things, it's OK to be passionate. Make beautiful things.
Make something take 100s of requests per second. Make a really nice landing page. Learn
what you're good at and do more of that, stay away from things you hate doing -- to a point.</p>
<h3>You only get ahead by doing things right</h3>
<p>One pitfall people fall into is making every project as quickly as possible. I've found it
helped me pickup necessary skills to force myself to apply them one-by-one to each new project.
The skills you <em>need</em> to do web dev may be:</p>
<ul>
<li>Git</li>
<li>Logging</li>
<li>*nix command line (how do find a file? how do I tell which binary is running when I run
some command? where <em>am</em> I?)</li>
<li>HTML/CSS</li>
<li>JS</li>
<li>Python</li>
<li>Regex</li>
<li>Testing frontend (no idea what libs to use now, mocha? karma?)</li>
<li>Testing backend (pytest, pytest-xdist)</li>
<li>Asynchronously handling something</li>
<li>Persisting information (database, file storage)</li>
<li>Docker containers</li>
<li>Docker swarm to manage it</li>
<li>It is nucking futs how many things you have to learn...! Keep adding as often as you can.</li>
</ul>
<h3>People will notice you</h3>
<p>At my company all it takes to get in the door is passion and hours. If you have a github
full of web dev projects, python automation tools, etc. we're going to fit together nicely,
for the most part. We may have to fine tune some things like CI/CD, code style, etc.
minutia -- but we'll gladly do this for the right people.</p>
<h3>Don't give up!</h3>
<p>It might take 50 tries to find a company with the right mindset to fit in a greenhorn,
but with Upwork-and-friends it's a global market place and only a matter of time for
someone to recognize your talent. Take some shit salaries to get your foot in the door,
if you have to. $15/hr is great to start at, I did.</p>
<h3>In conclusion...</h3>
<p>This was brief but tldr anyway: work hard, put your work out there, talk to lots of folks,
and <em>force</em> yourself to pickup valuable skills that are annoying to learn.</p>
<p>If you think you have what it takes to work with us, please feel free to shoot
us a message <a href="mailto:hello@ckcollab.com">hello@ckcollab.com</a> — thanks!</p>

How do I get a web dev gig?