Phyllux TechLearn · free
One change, then a note
Git tracks changes to files in a folder. For a solo operator on Windows, Git provides a history of what you changed and why. You do not need branches, pull requests, or collaboration features. You need a record of your work.
Install Git for Windows from the official site. During installation, accept the defaults unless you have specific preferences. Git installs a command line tool and integrates with Windows Explorer. After installation, you can right click a folder and open Git Bash, a terminal window where Git commands work.
Create a folder for your project. Put your files in it. Open Git Bash in that folder. Type "git init" and press enter. This creates a hidden .git folder that stores the history. Your folder is now a Git repository.
Make a change to a file. Save it. Go back to Git Bash. Type "git status" to see what changed. Git shows modified files in red. Type "git add ." to stage all changes. The period means everything in the current folder. Type "git status" again. Modified files now appear in green, ready to commit.
Save the snapshot with a message about why. The usual form puts a short flag for the message on the same line. Read that line before you press Enter. The message should say why, in your own words.
The message should explain why you made the change, not just what you changed. "Fixed bug" is weak. "Added check for empty file before processing" is better. Future you, reading the history, needs to understand the reasoning.
Work in small steps. Make one change, test it, commit it with a message. Make another change, test it, commit it. This creates a detailed history. If something breaks, you can look back through commits to find when it broke and what changed.
To see your history, type "git log". Git shows commits in reverse chronological order, most recent first. Each commit has a long identifier, your name, the date, and your message. Press q to exit the log view.
If you need to see what changed in a commit, type "git show" followed by the first seven characters of the commit identifier. Git displays the exact lines added and removed.
Python runs scripts that automate tasks. A Python script is a text file with a .py extension containing instructions. Python reads the file and executes the instructions line by line.
Before you run any Python script, read it. Open the .py file in a text editor. Understand what it does. Look for file operations: does it read files, write files, delete files? Look for network operations: does it connect to websites or services? Look for system commands: does it execute other programs?
If you do not understand what a script does, do not run it. If a script came from someone you do not know, be especially cautious. Malicious scripts can delete files, steal data, or install malware. Reading the script first is not paranoia. It is basic caution.
When you write your own Python scripts, include log lines. A log line prints information about what the script is doing. Use the print function to output messages. "Processing file: " followed by the filename tells you what the script is working on. "Completed successfully" or "Error: could not open file" tells you the outcome.
Logging helps when something goes wrong. You can see where the script stopped or what it was doing when it failed. Logging also confirms that the script ran correctly when everything works.
Build a way back into your scripts. Before modifying files, consider making copies. Before deleting data, confirm it exists elsewhere. Before overwriting a database, back it up. Automated tasks save time but can cause damage quickly if they malfunction.
Use full paths in your scripts. A full path specifies the complete location of a file: C:\Users\YourName\Documents\data.csv. A relative path like "data.csv" depends on where you run the script from. Full paths eliminate ambiguity. The script works the same way regardless of your current directory.
Do not run commands from strangers. If someone online suggests running a Python one liner or a PowerShell command, stop. Understand what it does before you execute it. Copy it into a text editor. Break it down. Research unfamiliar functions. Only run it if you understand and trust it.
This is not a bootcamp. You will not complete exercises, earn points, or receive a certificate. This is practical instruction for specific tasks: tracking your changes with Git, automating work with Python. You learn enough to use the tools safely and effectively, not enough to claim expertise.
Git and Python both have extensive capabilities beyond what is covered here. You can learn more as you need more. Start with simple use cases. Track changes to a single project folder. Write scripts that process files in predictable ways. Build competence through practice with real work, not through tutorials disconnected from your actual needs.
When something goes wrong, Git lets you recover. The log is the way back you can read tonight. Restoring an old snapshot is a further command. Do not run it until you have read what it does, because it can set your latest work aside. Frequent notes in the log are what make that later step possible.
Python errors tell you what failed. Read the error message. It specifies the line number and the type of error. Go to that line in your script. Check for typos, missing quotes, incorrect indentation, or wrong variable names. Fix the error and run the script again. Error messages are information, not punishment.
Both Git and Python reward consistent use. Commit after every meaningful change. Write scripts for repetitive tasks. Over time, you build a history of your work and a collection of tools that save time. The investment is small. The return compounds.
Extra cuts
One folder. One change. A sentence about why. That is the whole habit. You can learn more later. You do not need a certificate to keep the history.
If a command from a stranger includes a path you do not recognize, do not run it. Paste it into a note, read it, and ask what each word does.
A local model pass
Novelmate Studio on this PC wrote a further pass. In the folder, read git status, then git log. The commit message says why the change happened. Open a Python file in Notepad and read it before you run it. A double click can start a script. Reading it first is the step.