Start Over Coder

Start Over Coder

By Start Over CoderTechnology
Download on the App Store

Start Over Coder episodes

  • 045: Improving Naming Conventions

    The more you write code, the more you realize the importance of choosing good names for your functions and variables. In this episode I discuss a few best practices I’ve picked up so far.

    As a newbie to writing code, it’s just about getting the darn code to work. Lots of questions take priority: What is a function? What is this var I keep seeing everywhere? Did I miss a semicolon AGAIN!? Thinking about how to name functions, variables, or elements takes a back seat.

    But the more you read code, and especially the more you read your own code from the past, it’s easy to see just how important it is to name things well. It’s probably the most important thing you can do to make your code readable.

    Here are some tips I’ve picked up so far about naming conventions:

    1. Be specific with names so that the name describes what is actually happening. Example: name a function calculateAge() instead of just calculate(), which is too vague.
    2. Don’t use similar names. My terrible bad example was when I called a button “item-reward” and on the same page called a form “reward-item.” This is the epitome of confusing when you go back and read your code after a few weeks away.
    3. Don’t use initials, single letters, or numbers as names. It’s harder to understand and nearly impossible to search. Brevity does not always win over clarity!

      4. Basically when reading through your code, the reader should be told a story: a sequence of actions that makes sense to human understanding.

      To improve your own style of naming things I can recommend:

      1. Read other people’s code, both good and bad. You’ll get best practices from the good, and can see what not to do from the bad!
      2. Read books about best practices. I can recommend Clean Code by Robert C Martin.
      3. Ask other developers to review your code and offer suggestions for improvement.
      4. Do the time test: read your own code a few weeks or months after you’ve put it down. After some time away you’ll see rather quickly where improvements could be made, as well as how clear or confusing it is.


        5. This episode was originally published 5 December, 2017.

        13 min
      5. 043: Node/Express Project - Progress Report

        For some info on what it takes to build an app from scratch, here’s a progress update on the app I introduced in episode 35.

        The main updates:

        Goal #1 is shipping a minimum viable product (MVP). Since my initial plans got a bit complicated, I took a new approach and simplified the basic functionality of the app. I can always go back and add more robust features later?for now I’d like to get a good foundation completed.

        I also aimed to pick up a new skill by using a new front end framework, Semantic UI to style the site.

        In the testing stage, I found a bug! So researching some possible fixes, including the Mongoose queries written in my Express routes, and using AJAX requests to update small portions of the page.

        I’ll do at least one more update on the app before wrapping it up! In the meantime…


        This episode was originally published 21 November, 2017.

        11 min
      7. 042: Should I Quit My Job?

        Quitting a well-paying, decent job to become a programmer is a big decision. This episode is all about the pros & cons.

        Although the initial impetus to pursue a coding career was very reactive to a bad situation, I truly threw myself into—and got excited about—pursuing a career as a developer. But as the sting of a bad work situation wore off, all of the great things about the job I’d be leaving came more into the forefront. Not to mention the stories out there about non-diverse, workaholic workplaces in tech. Is this really a good decision?

        No answers guaranteed in this episode, but here’s a glimpse into the thought process involved with leaving one career for another.

        Show Links:
        • Learn more about Effective Altruism
        • Learn more about 80,000 Hours - lots of great research on choosing a career for personal fulfillment AND the greater good of the Earth. You can also learn about them in this TED talk.


          • This episode was originally published 14 November, 2017.

          13 min
        • 041: Discoveries! Coding Solo Podcast & Millennial Money Diaries Blog

          This week I share two more great (and free!) resources for learning to code. The Coding Solo podcast is an entertaining UK perspective on working as a freelance software developer. And check out the Millennial Money Diaries blog for another perspective on starting a programming career with a view on personal finance!

          UPDATE FROM THE FUTURE:  The Millennial Money Diaries Blog no longer exists 😩

          Show Links:
          • The Coding Solo Podcast
          • Millennial Money Diaries Blog
          • MMD - awesome coding bootcamp post
          • MMD - Jing’s investing journey post
          • MMD - Prerequisites to Being Good With Money
          • MMD - This Story Will Make You Plan For Retirement
            • More in the Discoveries! series:
            • Ep 18: Learn To Code With Me Podcast & Free Lynda.com
            • Ep 64: Financial Toolbelt & Second Career Devs Podcast
            • Ep 73: Chingu & uMatrix


              • This episode was originally published 7 November, 2017.

              9 min

            About Start Over Coder

            From the publisher's feed

            A podcast about learning to be a web developer and pursuing financial independence.