You’re reading the free preview.Unlock every conversation for €2.99
FreeFree previewChapter 1
Chapter 1 · Free preview
The Foundation Layer
What you will understand
- Open the terminal and run basic commands (ls, cd, mkdir, cat, grep)
- Understand what Git does and why version control is essential
- Create a branch, make commits and open a pull request
- Explain the difference between development, staging and production environments
- Choose an IDE and master the basics
Written by EduVerse for this preview; the slides below are the book’s own words.
Slides from the chapter
Each slide is a passage from the book with the figure or listing it talks about. Swipe, use the arrow keys or the buttons.
Slide 1 of 3
The Terminal: Your Gateway to Everything
1.2 · p. 23
Conversation from The Software Realm, Decoded
Chapter 1 · 1.2 The Terminal: Your Gateway to Everything · p. 23
He opens his laptop. Sees the GitHub link. Clicks "Download ZIP."
Senior developer walks by
What are you doing?
Peter
Downloading the code?
Senior developer
No, no. Open your terminal. Type git clone and paste the URL.
Peter stares at the black screen with blinking cursor. This looks like something from a 1980s movie. Why aren’t they using the normal interface with buttons and windows?
Peter
Why can’t I just download it normally?
Senior developer
You could. But then you’d miss the entire Git history, the branches, the ability to pull updates, and you’d have to manually download every time something changes. The terminal isn’t harder, it’s more powerful once you learn it.
What the book shows with it
Example from The Software Realm, Decoded
Chapter 1 · 1.2.2 The Essential Commands You'll Actually Use · p. 24
Peter learns the commands he’ll use every single day:
# Where am I?
pwd
# What's in this folder?
ls
# Go into a folder
cd Documents
# Go up one level
cd ..
# Go to home directory
cd ~Peter tries it:
pwd
/Users/peter
ls
Desktop Documents Downloads Pictures
cd Documents
pwd
/Users/peter/DocumentsThe Problem Git Solves
1.3.1 · pp. 27–28
Conversation from The Software Realm, Decoded
Chapter 1 · 1.3.1 The Problem Git Solves · pp. 27–28
Peter tries the old way first. Creates folders: my-app, my-app-backup, my-app-working-login, my-app-final-really
Senior developer walks by
What are you doing?
Peter
Making backups in case I break something?
Senior developer
Stop. Delete all those. Let me show you Git.
cd my-app
git init
git add .
git commit -m "Initial commit - app is working"Senior developer
Done. You just saved a snapshot of your entire project. Now go ahead and break things while adding profile pictures. If it goes wrong, we can time-travel back to this exact moment.
Peter
That’s it? Four commands?
Senior developer
That’s it.
Branches: Parallel Universes for Your Code
1.3.4 · pp. 30–31
Conversation from The Software Realm, Decoded
Chapter 1 · 1.3.4 Branches: Parallel Universes for Your Code · pp. 30–31
Peter’s task: "Add dark mode to the app."
Senior developer
Create a branch for it.
# Create and switch to new branch
git checkout -b dark-mode
# See all branches (* shows current branch)
git branch
# Switch back to main
git checkout main
# Delete a branch (after merging)
git branch -d dark-modeWhat just happened: Peter created a parallel universe called "dark-mode." Any changes he makes now only affect this branch. The main branch (the production version) stays untouched. Peter makes changes:
# On dark-mode branch
git add src/theme.css
git commit -m "Add dark theme colors"
git checkout main
# Look at theme.css - no dark mode colors!
git checkout dark-mode
# Now the dark mode colors are backPeter’s realization
Branches are like separate save files in a video game. I can try crazy things in one save file without messing up the main one.
What the book shows with it
Figure from The Software Realm, Decoded
Chapter 1 · 1.3.4 Branches: Parallel Universes for Your Code · p. 31
Meanwhile, his teammate creates their own branch for the payment bug. Both work in parallel.
Explore this figure
Pick one to highlight it and read what the book says about it.
Other labels in the figure (12)
Description
Git branch graph: the 'main branch' runs left to right through commits A, B, C, F and G. From B, a 'branch' labelled 'colleague’s payment fix' adds commits X and Y, which 'merge' into F; from C, a 'branch' labelled 'your dark-mode' adds commits D and E, which 'merge' into G.
Description written by EduVerse; the figure itself is from the book.
Slide 1 of 3
Try it yourself
A simulation built by EduVerse around this chapter. It runs in your browser; nothing is sent anywhere.
The full chapter
This preview shows 5 of the chapter’s 35 passages. The full chapter has:
- 6 sections
- 18 conversations
- 1 figures and tables
- 10 What They Say boxes
- 7 knowledge-check questions
Sections in this chapter
- 1.1Your Daily Command Center
- 1.2The Terminal: Your Gateway to Everything
- 1.3Git and Version Control: Time Travel for Code
- 1.4IDEs: Your Smart Code Editor
- 1.5Local Development Environment: Your Private Playground
- 1.6Peter's Takeaways: