Back-end JavaScript

I’ve started my third session here at Austin Coding Academy, back-end development. It’s definitely different than front-end development, mainly with it being mostly about accessing data and making that available to your front-end viewing area. Much to learn, but it’s a new area and it will take time to adjust.

I like to organize my code first and foremost with folders. Separate directories for certain types or projects, or classes, and then having each project live separately. And then of course, there’s GitHub, a great way to back up your code and to keep track of your projects and your progress. In the actual text editor, I like to use best practices when it comes to structuring my code and when dealing with syntax. Breaking my code up into organized blocks also helps readability. Also, consistency is important, as it helps to locate code snippets easier. Some suggestions I found on the web were, to use cloud products when available. This can free up clutter on your local machine. They also mention naming projects with dashes so they’re command line friendly.

When creating a webpage I like to start with code planning. This includes what I’m trying to do, in words and in outlines and sketches. Then I’ll make sure I have the resources to host the webpage. After that I will start coding the basic structure of the webpage, while testing it along the way. After I’ve tested it and completed what I set out to do, I’ll push my code and get it up and running.

There have been many times where I can’t solve a coding problem. All of this is new to me, so it’s very common for me to be confused. My first step is to look up resources, such as my textbook or the internet. From here I can look at some examples and at the definitions for various coding methods and such. Then I can apply those concepts to my problem. To know I have the right answer, I’ll check it with various tests or with the expected solution.

There have been many non-coding problems I’ve had to solve. Some include file management and git issues. File management has always been an interesting area. It can help you, but it can be tedious too. I’ve found that having folders, but not too many, can help. Git is a great tool, but it can be complicated. Early on, I had problems with making sure I was using git correctly. The whole merging and pull and pushing concepts, it takes practice to get used to it. Then of course you have problems like personal issues and time issues. These are all best solved with being patient and taking things one step at a time.

We’ve been using Visual Studio Code in our classes, for writing code and such. I have to admit, I haven’t used any other ones really. VS code has been fine to use, in my opinion. It works for what we need and I haven’t had any major issues. It has a lot of extensions that can be installed to assist in coding and testing. It’s great for basic coding and for more robust endeavors, it’s flexible.

I’m trying to keep up with new web developments by reading about new trends and technologies as they become available. There are various blogs and news outlets that cover new coding techniques and technologies. Then of course we have our instructors at the academy that keep us in the loop about modern work trends. What technology is used, what methods and what processes are used in the workforce.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store