DEV Community


School of Code Bootcamp 4.0 Weeks 2-3

lauraashcroft14 profile image Laura Ashcroft ・Updated on ・3 min read

Week 1 went extremely quick and my brain was filled with so much new knowledge! In week 2, we moved onto advanced JavaScript to build on our existing knowledge and learn how to write functions differently.

During week 2, we moved onto :

  • Advanced functions
  • Composition
  • Immediately Invoked Function Expression
  • Refactoring
  • Destructuring
  • Methods
  • Callback Functions
  • Asynchronous JavaScript
  • JSON
  • Scope

Week 2 was building on our frontend knowledge and getting to grips with some of the more advanced parts of JavaScript. Week 3 was the real battle! πŸ‘‡

At the end of each day we've been encouraged to complete a 'daily reflection'

I've recorded what I have learnt from the lectures and what my feelings are at the end of each day. For each DEV post I'll give a brief overview of what I wrote in these reflection tasks...

Week 3 Day 1-4 Reflections

  • Persistent storage is any database that retains data even if the power is shut off to that machine.
  • C(reate) R(ead) U(pdate) D(elete)
  • Servers or databases could be on your own computer, or on different machines entirely (the "cloud"). As long as they're talking to each other, they can exist on the same machine.
  • There are relational databases and non relational databases.
  • SQL stands for Structured Query Language.
  • SQL has more 'human readable' syntax. A few examples are:
    • The * means is a wildcard and selects all information.
    • We SELECT information FROM a database WHERE a condition is present.
    • We can UPDATE users by applying SET to their new information.
    • DELETE FROM shows where we are deleting somewhere and WHERE shows what we're deleting.
  • SQL also contains operators such as =, BETWEEN, NOT BETWEEN, IN, NOT IN, LIKE, NOT LIKE, %, and - to create conditions when finding information from a database.
  • SQL can be used to navigate between different tables and select relevant information from them.
  • Node.js is a way to use JavaScript without the browser. It runs in the terminal in VS Code and is our way to backend code.
  • We can run files in node by typing 'node main.js' in the terminal.
  • Importing modules into a file uses the require("") syntax.
  • In the Pg Module, "Pool" is the active connection to the database from node.js.
  • Npm init will create a package.json file with the relevant information in.
  • Environment variables allow us to hide our credentials from GitHub without hiding the rest of our code (by putting them in the .gitignore folder).
  • Thoughts and Feelings
    This week has felt more overwhelming than the last 2 combined! We've had our introduction to the backend (node.js, SQL) and I've definitely found some parts much easier than others. The SQL Murder Mystery was way more fun than creating a server and making it listen to requests. Nervous about the hackathon but looking forward to seeing what I learn!

    Week 3 Day 5


    • Today's hackathon was difficult!
    • We git cloned a web application that had already been designed and needed to get the server to listen on the correct port.
    • We added functionality so we could get the data as needed for the front-end.
    • Turned the data into persistent storage by refactoring our code and made it interact with a database instead of an array.
    • Created a Postgres DB on Heroku, connected to it, and then interacted with it through SQL queries to allow all the same functionality as we had earlier.

    Thoughts and Feelings
    Glad I made it through the week! The intensity definitely ramped up this week but with enough notes during class and practice in the evenings, I had enough confidence with node.js to work through it systematically. I even understood why I had some of the errors that flagged up!

    End of Week 3

    Phew! I'm happy I've learned backend and have now got a knowledge of the full stack rather than just front end. Looking forward to building onto my skills and understanding the code instinctively. Definitely glad for this weekend though!

Discussion (0)

Editor guide