MERN Stack Chat App #1

xensan_dev — Wed, 22 Mar 2023 20:33:34 +0000

Hello, everyone! I will be sharing this journey of coding a MERN Stack Chat App. I will be sharing code snippets, as well as, screenshots of the frontend (not finalized).
P.S. I won't be going in-depth with everything I do.

Technologies

The main language I will be using is JavaScript.
Frameworks: React(Vite), TailwindCSS, Node, Express, and MongoDB

Color Palette Generator: https://coolors.co/

Start!

Created a repository and cloned it to my local desktop.
Created a Client folder by creating a vite app and naming it client.
Created a Server folder separate from the Client folder for the backend. File Structure Make sure to keep your files organized!
Installed the following dependencies in the client-side.
Installed the following dependencies to server side.

A Quick Guide to Meaningful Commits!

xensan_dev — Wed, 22 Mar 2023 01:06:50 +0000

What are commits?

A commit is a command from Git that allows a user to save snippets of code in the order they were added/changed. Think of commits as snapshots of your code in a timeline. Commits allow a user to be able to go back to each addition/change done to the local repository and control the version afterwards.

Why are commit messages important?

Commit messages are important because it lets the current coder know what was changed during that point in the timeline.

Be specific with your commits!

Commit messages should be specific! You should be able to describe what was added/changed in your commit.

Example of a bad commit:
git commit -m "pushing fixes"

Vague
Does not help the user or the team figure out what was fixed

Example of a good commit:
git commit -m "addition function was missing a variable"

More descriptive
Identified the error and describes where it was

You can be as descriptive as you want but make sure to keep your commits short. So long as you are able to summarize and understand what was changed or added.

If you got this far thank you!

Tips before you choose to attend a coding bootcamp!

xensan_dev — Tue, 21 Mar 2023 18:22:48 +0000

Hello everyone,

My name is Xenon Santillan and I just completed my coding bootcamp on March 9. I attended a Full Stack Development Bootcamp at UC Davis Continuing and Professional Education. This is from my experience and opinion with attending these bootcamps.

These bootcamps are usually completed in 2 different time periods (Full-time and part-time). Now for these coding bootcamps, it is HIGHLY RECOMMENDED to not work or do any extracurriculars DURING the course. Is that true? In my opinion, yes. While you may have some leeway during a part-time course, you will still need to put in 20+ hours more into studying/practicing coding. AND PLEASE DO NOT MISS A CLASS. Some bootcamps will allow up to 8 absences but you will be lost if you do not pay attention to detail. Your goal isn't just to complete the bootcamp, it's to make it into the tech industry as a software engineer.

Tip #1: Do your research.
You will probably hear this from a lot of people in the tech industry, but bootcamps don't hold that great of a reputation. Yes, some are credited and are able to produce amazing software engineers, don't get me wrong; however, this is probably the top 1-10% of bootcamp graduates. Take into account that the tech industry is VERY COMPETITIVE. Many companies are looking for THE CREAM OF THE CROP bootcamp graduates.

Tip #2: Take Harvard's CS50 course on EDX
Now this is something I highly recommend for beginners. This is a FREE course you can take online ON YOUR OWN TIME. I'm not going to go in-depth with the course, but it will help to prepare you for the material in the bootcamp.

If you are choosing to go into a coding bootcamp blindly (no coding experience), please reconsider. Software Engineering is an ever-changing position.

Tip #3: Tutoring and Office Hours!
My bootcamp had office hours 30 minutes before and after each class. In this period of time you can take a professor or teacher assistant to a break out room and speak with them about your struggles with the course, things that are happening outside of class, help with projects, or even to catch up on material. PLEASE TAKE ADVANTAGE OF OFFICE HOURS.

Tutoring sessions have to be scheduled ahead of time. Here you can speak with a professor or teacher assistant 1 on 1 if you need help.

Tip #4: Commit time outside of class to practice!
This was one thing I struggled with during my bootcamp. I grew complacent just watching tutorials or reviewing bootcamp material. You need to have a knack for learning new material all the time, whether it is a new library, framework, etc. Always be curious and have fun with what you are crafting. All code is never permanent either. You can always cut code away and create more whenever so have fun with it.

Tip #5: Don't rely on others too much.
Now during these bootcamps you will have a lot of batch mates. You will have group projects to work on. You should always choose to stick with the hard working ones of course, but don't rely on them too much. You have a vision for yourself and your projects. If the group has a different vision for the project than you, you can always make a fork and change what you see fit.
(I'm not saying that your batch mates can't be trusted)

Tip #6: Figure out what works for you!
Everyone develops skills in different ways and there is not one right way to do things. What worked for me is wire framing and creating user flow charts before starting projects. I was able to visually understand how the web applications should work and how it should look. Now what works for me may be different from what works for you.

Tip #7: Find a focus.
Now this one is a little bit different. Software Engineering has a lot of branches and routes you can take. If you find a passion for something during your time learning stick with it! It can be frontend, backend, devops, etc! Figure out what you want to do or where you want to be!

Tip #8: Jot down what you learn on twitter/network!
Now this is a phase to do during and after the bootcamp. I started this blog once I completed my bootcamp so I wasn't able to show my thought process and methods. This is what a lot of companies/employers want to see. The ability you have to take in information and use it, so start early.

Tip #9: Keep working on your craft!
Once you finish the bootcamp, you may get lost on what to do next. Keep making projects and deploy them! There are a lot of FREE RESOURCES you can get from networks as well as connections! Don't be afraid to reach out to batch mates and work on professional projects together!

Tip #10: Create a community/Join a community!
This will be your safe space to grow and develop. Find people who have similar interests as you and grow along with them!

Coding Bootcamps are accelerated learning courses designed to guide you where you want to be in your career, but it doesn't stop once the bootcamp finishes. It's what you do with the skills you learn after the bootcamp that can really take you far. Keep practicing!

If you got this far, thank you!

P.S. I am not talking down on anyone's ability to learn material, so please don't take offense. Please note that I am not advocating for coding bootcamps or giving financial decisions. Coding bootcamps are a huge financial decision as well as a commitment, just like college. There are many individuals that can learn without the guidance of a coding bootcamp as well.

Slow days

xensan_dev — Tue, 21 Mar 2023 16:37:55 +0000

After working hard for an extended period of time, does it feel like there are just some days where you feel very unproductive?

My advice would be to keep pushing and to write. If you have a goal in mind, write it down that way you can always see it.

Hello Dev.to

xensan_dev — Tue, 21 Mar 2023 06:37:16 +0000

Wow, this is exciting! My first blog post! Anyways... The project I am currently working on is a MERN Stack Social Media Application that allows a user to create an account, add friends, browse a timeline/profile, and more!