Tips for building your first fullstack app

adinah — Sun, 24 May 2020 19:41:15 +0000

Hey world! I finished building my first fullstack application while attending a coding bootcamp this spring. I learned a lot in the process of building my app and want to share those experiences with you.

Biggest tip: Plan Ahead

First, think about which tools are best to build your app. I came into bootcamp with a little bit of background in JS, but I wanted to gain more experience with Python since I was more interested in becoming a backend engineer. My app was built with a Python/Flask backend, PostgreSQL database, and an HTML/CSS/JS frontend. Know which framework fits in with your design best. Same with databases.

While researching which tools to use, you should also research which APIs and libraries you want to use. I heavily relied on external APIs to provide data for my project. I spent a huge chunk of time reading documentation on how to use various APIs. I found some APIs have clearer documentation than others. (I plan on writing another blog post about tips for finding reliable APIs.)

I assumed one python library would work for an API I wanted to use. What I realized when I started coding was the library hadn't been updated for Python 3. I was unable to use the library for my project. Had I researched a little more thoroughly, I would've realized the library wasn't viable. My suggestion is to read articles showing examples of what kinds of queries other developers have used for the APIs you are interested in before implementing it in your project. Documentation for both APIs and libraries can be dry but having a sold base of understanding can (and will) help you further down the road if you get errors.

Second tip: Have an achievable MVP!

MVP stands for minimum viable product, a term used in Agile development. Think of 1-2 features you need your application to have to be considered done. Give yourself deadlines of when you want something to be due to hold yourself accountable. My bootcamp provided deadlines for each step of our process- I had deadlines for completing data models, my MVP, and extra features. It's okay to expand your MVP or extend your deadline. Just make sure you are giving yourself a reasonable scope to meet.

I kept a project journal throughout the process. Every day I wrote down what I was having trouble with and what strides I made (if any). My notebook is riddled with a mixture of handwritten emojis, cURL requests, and ideas on how to proceed forward. Some days I didn't make any progress. Know its okay to not have "productive" days every single day you are working on your project. Looking back on my notes, I can see what my blockers were as well as my solutions. Each step of this process is a learning curve!

Last tip: Play around in the terminal

If you are using APIs, I don't recommend trying to code directly in your IDE. Make curl requests in your terminal first. If you are using Python, utilize the python interpreter. Know your syntax is correct first before adding the code into your file. It's a lot easier to understand errors that way. First, it can help understand what you are getting back. Is the API giving you information in XML? JSON? How is the data nested? If an API is giving you a ton of information and you only need a little bit for your app, practice parsing the response in the terminal first.

I would suggest using the terminal for libraries as well. Make a couple variables in your interpretive shell. Does your data look how you want it to look? Are you getting errors?

I am really excited at the prospect of building more applications. It's amazing to get to a level of knowledge where I can think of an app idea and realize - hey, I can build that now! Do you have any tips for newcomers building their first fullstack app? Share them in the comments!

100 Days of Code: a Reflection

adinah — Thu, 10 Jan 2019 02:33:59 +0000

Hi there, my name is Adinah, and I started learning how to code last summer with challenges on freeCodeCamp. It wasn't long before I realized I loved learning how to code!! At first I thought I was progressing at a good pace, but soon decided I wanted to hold myself more accountable for my progress and began to establish learning goals.

100 Days Of Code

The best thing I did was start the 100DaysOfCode challenge, which requires a public commitment to code for at least one hour each day for 100 days & willingness to tweet about your experience with the hashtag #100DaysOfCode. I began my challenge September 5th, ending in December, and plan on doing a second round soon!

my first day of #100DaysOfCode started out establishing goals. first goal= by day 14 to complete FCC's responsive web design certification!
— adinah.js (@adinahcodes) September 6, 2018

My Goals

My first goal was to get the Responsive Web Design certification from freeCodeCamp. Luckily, I completed this goal early into my challenge.

My second goal was to obtain their Javascript Algorithms and Data Structures certificate, which I unfortunately did not finish. I have one more section to finish before starting on their projects, and in my second round of the 100 days challenge this certification will be my first goal :)

Tips for Completing the Challenge

establish tangible goals
make your goals flexible: it's okay to try something new!
thread your tweets
share your projects

My biggest tip for completing the challenge is to establish goals. Whether it is building a product landing page with Sass by day 30 or getting a certificate from Udemy by day 70-- make your goals specific. Though you should be firm in your determination and dedication, remember to be gentle with yourself if you aren't able to meet your goal in time, or even if you decide you want to focus on something different entirely.

As a beginner it can be tricky writing down goals and creating a curriculum when there seems to be so much to learn. Sometimes the hardest part about doing a project or learning something new... is actually starting it. I found myself wasting a lot of time beforehand reading reviews on what to learn when I really was just delaying diving into doing the work and discovering what I was interested in.

During my challenge, I dabbled a little bit in Java before deciding to stick with Javascript. Sure, it may set me on a detour for a bit during my #100DaysOfCode challenge, but more importantly it solidified that I definitely want to continue learning Javascript. Trying something that I later realized I didn't like isn't a waste of time; it's a great way to explore, especially in a field with so many areas to try new things. Besides, knowing what you don't want to do is just as important as knowing what you do want to do.

I recommend threading your tweets when tweeting about your #100DaysOfCode challenge. It's easier to see what you've accomplished throughout the challenge when its all in one place. For example, if you're on day 68 and feeling unmotivated you can scroll up to day 32 and realize you have learned A LOT. This always helped me feel like I was progressing.

Share your projects in your tweets. Link your CodePen or GitHub to your latest project. Sharing might seem scary but its a great opportunity to get feedback from a community that wants you to grow as a developer. Sharing your work is also a good way to show how you've progressed along the way. Discuss what new frameworks you've learned while creating your project.

If you're not currently working on a project where you can show code you've written, screenshot your answers to tutorials or share a resource that helped you learn a difficult concept. There were times when I didn't "code" much but I learned a lot reading articles on here & other sites...instead of tweeting my code those days I tweeted links to the articles.

My last tip is to break up the hour into smaller parts to make it more manageable for folks with a tight schedule. You don't need to try coding for extended periods of time in one sitting to do the challenge. 15-20 minutes of coding bursts throughout your day can work as well, and returning to a project after a bout of fresh air often helps when stuck in your work. I typically would do a lot of tutorials before my workday started (when I had the most energy) and at work between customers. Depending on your learning style, it can even be easier to digest the material if you're working in parts.

For those doing the challenge or are beginning the challenge, lets code together! I would love to interact with more beginners in their journey. If you've finished #100DaysOfCode challenge, what tips do you have to share?

DEV Community: adinah