DEV Community

Cover image for 27. Classroom cravings fulfilled (Day 25)
Manoj Kumar
Manoj Kumar

Posted on • Originally published at emanoj.hashnode.dev

27. Classroom cravings fulfilled (Day 25)

Happy Friday!

Today was a coding adventure! Here's the breakdown:

What I conquered:

Hangout at the Coding Camp: Spent 3.5 hours at the support hub, diving into Responsiveness and SCSS for specific pages. It was enlightening!

Git Mastery: Nailed the Git SSH setup on my second computer, making the magic happen—fetch, pull, tweak, and push back changes seamlessly.

Assignment Clarification: Got a crystal clear understanding of the submission requirements. No more head-scratching!

Face-to-Face Tutor Time:

I've been living the work-from-home dream for the last 2 years, juggling a 9-5 job, launching my projects, and diving into courses like coding. The WFH vibe is fantastic, saving me time, money, and giving me family moments. But when it comes to serious studying, I miss the classic classroom setup. My schooling and university days were internet-free zones, and diving into online courses initially felt like a wild goose chase. That's why the hybrid model of my coding course appealed to me—flexible online study but with invaluable one-on-one support. Today, meeting the tutor face-to-face felt like a game-changer. Their guidance didn't just clear doubts; it ignited a coding fire in me!

GitHub on Two Machines:

Freedom to code, anywhere! That's the dream. But to make it real, I needed to sync my GitHub across devices. Yesterday, I prepped my old laptop, only to realize the missing link—the SSH setup. My tutor pointed it out today.

So, the main commands I used to get all these setups were:

  • git remote add origin
  • git fetch origin
  • git pull origin main

The important principle in setting this all up was knowing the following:

  1. Computer 1 has a local repository 1
  2. Computer 2 had a local repository 2
  3. Both these local repositories have a remote repository as their remote origin

So, you also have to add the remote repository to local repository 2 on computer 2 using the command git remote add

Changing your global User name on Git

Also, learned another thing today - If you don't want your name to appear on the GitHub commits, you can change that also.

NOTE - This username is not the GitHub username but the username used by Git to associate Commits with an identity.

The command to use is:
git config --global user.name "Earth Water"

Now, when you push your commits to GitHub, the identity of the person who pushed it across will be shown as "Earth Water".

You can read more about changing user names for commits here on GitHub Docs.

Today was a day where coding met guidance and possibilities expanded. Excited for what's next! And that's all I have for you today. Friday (10:50 pm!) is almost done and I am now preparing for a 15-20 hours of study this weekend!

Top comments (0)