<?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 Alexander Bercow on Medium]]></title>
        <description><![CDATA[Stories by Alexander Bercow on Medium]]></description>
        <link>https://medium.com/@alexanderbercow?source=rss-ff4122bf4f23------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WNzXYkWZMlG7BQpIcjgFLA.jpeg</url>
            <title>Stories by Alexander Bercow on Medium</title>
            <link>https://medium.com/@alexanderbercow?source=rss-ff4122bf4f23------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:17:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexanderbercow/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[From Tutorials to Projects.. How do I make the leap?]]></title>
            <link>https://alexanderbercow.medium.com/from-tutorials-to-projects-how-do-i-make-the-leap-faf3b04d7dc?source=rss-ff4122bf4f23------2</link>
            <guid isPermaLink="false">https://medium.com/p/faf3b04d7dc</guid>
            <category><![CDATA[developing]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[coding-newbie]]></category>
            <dc:creator><![CDATA[Alexander Bercow]]></dc:creator>
            <pubDate>Tue, 12 Jan 2021 01:03:38 GMT</pubDate>
            <atom:updated>2021-01-12T01:05:54.613Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Tutorials to Projects.. How Do I Make the Leap?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*ANEdV7prhx4mqFGgWkuuVA.jpeg" /></figure><p>About 3 years ago, some developers at my job started an “after school coding club”. I accidentally showed up and well, immediately I was hooked.</p><p>I spent the next few months doing all the classes, tutorials, readings, videos one feasibly could without going insane. I felt pretty good about where I was but I kept running into one major road block — I don’t really know how to code without <strong>some guidance</strong>.</p><p>I’d have some project ideas but.. I wouldn’t know how to start.</p><p>Which language do I pick? What’s best? What do I start with first? How do I think about all of this at once? Everyone I ask seems to have strong, varying opinions. I only am comfortable with one language right now, do I learn something else first? I’d get stuck, give up, and go to my happy place — tutorials.</p><p>I have no formal training, I didn’t go to bootcamp, I definitely didn’t go to college for it — I went to Berklee College of Music for guitar. How do I move past this roadblock?</p><h4>Tip #1: Like your project idea</h4><p>First thing’s first, you need an idea. I’d recommend something that interests you. Sounds obvious maybe but I would keep trying to do projects that Reddit recommended or that “looked good” on job applications like a weather app or Twitter clone but problem is.. I don’t really care about the weather and Twitter already exists!</p><p>The premise is simple — if you like the idea, you’ll be more inclined to do it. In my case, I literally started my first project by just putting together a list of some things I like: music, basketball, video games, cooking, and so on. I also knew I didn’t want to “clone” something. Even if it sucked, I wanted it to be my own.</p><h4>Tip #2: Use what you know — for now</h4><p>Don’t google “best language for my blog” or whatever. You know Javascript best? Use Javascript. You feel best in Ruby? Guess what, use Ruby. You probably know more than you think!</p><p>Sure, maybe your Staff Engineer with 15 years experience wouldn’t use JS for their backend or some Medium article (not this one) you read said always do XYZ in Python or Typescript is the hot name you keep hearing, who cares. You will learn those things someday! Let’s just get something working right now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGiuMCBgJxMBH850r5LoyQ.png" /><figcaption>(no shade to this article, it’s quite good)</figcaption></figure><p>We can always go back and redo the backend in the “right” language or use different tools.</p><h4>Tip #3: Small pieces, one at a time</h4><p>Simply put — don’t overthink it. It’s hard not to get overwhelmed when you’re new.</p><p>I didn’t know nearly enough to build a full-stack app at first. I spent most of my time doing front-end work because I found it most interesting. Remember, I didn’t go to school or bootcamp. Even those who have, you may not be super comfortable with everything yet.</p><p>I found it helpful to literally sketch out everything that needed to be done. What does the front-end look like? What does this button do? How many components do I need? What API calls are made? Where are the API calls made? What would my database tables look like? How many tables do I need for what I’m doing? Breaking this into small pieces will make it easier to think about.</p><h4>Tip #4: Postman/Notebooks/Glitch</h4><p>Some actual technical advice now — don’t just open your VSCode and go nuts. I found at first with no guidance, I’d get stuck immediately. I’d make a new file or start a create-react-app project and just .. give up. It felt so big, so daunting.</p><p>One of the most helpful things I learned was to not even build anything first. Just play, have fun. Get excited about what you’re doing!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qZY5zfHRt6C4heDXCLc4HQ.png" /></figure><p>I’d use <a href="https://www.postman.com/">Postman</a> first. Get comfortable with what you’re doing. Make some API calls, what do you get back? I found this to be a fun exercise and it led me to some even more ideas I didn’t have originally — I saw that it returned some data I didn’t even think about before!</p><p>Notebooks, like <a href="https://jupyter.org/">Jupyter</a>, are another good way to get ideas down. While working on a project with a friend, we decided to just .. write some functions. Do they work? What can we do? What can’t we do? You can learn a lot just from this before worrying about if your project is setup correctly.</p><p>Lastly, I love recommending <a href="http://glitch.me/">Glitch</a>. Project setup sucks. This helps. It can be collaborative which is helpful when you’re starting like me. Get stuck? You can get help easily.</p><h4>Tip #5: Celebrate your wins!</h4><p>Imposter syndrome is real. Sometimes I’d find myself working really hard on something seemingly “easy” and get bummed out that it took me so long. That mindset really only hurts you.</p><p>So what you aren’t reinventing the wheel, you should be proud you are even this far. Celebrate yourself. The feeling of accomplishment, pride, and so on will encourage you to keep going with this project and the next. Coding is hard! Congrats, you’ve made it this far.</p><p>I hope that these 5 tips I’ve learned along the way help you. If they seemed obvious, I hope they served as reinforcement. If they are all new to you, I hope that this will inspire you to do that idea you’ve been thinking about. All in all, we’re always learning — that’s what makes coding so fun in my opinion!</p><p>Feel free to reach out for more advice or just to chat, I’m always happy to chat.</p><p>-Alexander (<a href="https://github.com/coolyoungdad">Github</a>/<a href="https://medium.com/@alexanderbercow">Medium</a>/<a href="http://bercow.biz/">Website</a>/<a href="/service/mailto:alexander@bercow.com">Email</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faf3b04d7dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>