Choose a Programming Language: Choose Git, Choose Markdown

2025-02-24

Choose a Programming Language: Choose Git, Choose Markdown

That iconic line from Trainspotting is a powerful reflection of choice- sometimes outrageous ones. In our journey in development, most of us will agonize over which flashy programming language to master (Python, JavaScript, any of the C's, or the latest trendy framework). What if theres a quieter, more foundational choice that underpins the entire journey. What if we choose Git and Markdown?

While neither strictly programming languages they lay the foundation that can drasctically improve the ability to learn, collaborate and grow in Software Development.

Git: Version Control

We've all been here at some point in our lives, creating a document for school at work (probably at 3am)deadline approaching, you've spent hours at it and then - BANG, you didn't save it, power went off, you deleted something you shouldn't have and POOF- Gone.

Git is your very onn DeLorean time machine, whisking you back to any point in time- tracking changes, safeguarding 'oops' moments and a brilliant way to collaborate with others.

Why Git Matters

1. Version Tracking Git lets you record every change like a digital library, rewinding when you make a mistake and allowing experimentation without fear of catastrophic failure. Imagine if your superpower was "CTRL+Z" for your entire project.
2. Collaboration Whilst working alone is great, at some point collaboration is inevitable. Tools like Github, GitLab, Bitbucket use Git to enable teams to work on the same codebase.
3. Disaster Recovery Accidently deleted an important file, or changed something that has broken your code and don't know what- Git like a caped superhero can restore it.

By mastering Git, it cultivates a disciplined approach to managing projects, the secret sauce regardless of the programming language.

Markdown A Simple Markup Language

Markdown may not have the complexity of full-blown word processor or the flash of HTML, but thats the charm. Its a minimalist hero for documentation, clear, concise and so straightforward a goldfish could use. Its widely used for README files, documentation, note-taking apps such as Notion and Evernote, and all my blog posts like this one are produced in Markdown.

I use markdown for all my documentation now to create proffesional, structured that are easy to maintain and read.

Why Markdown Matters

1. Simplicity Markdown strips away the fluff of normal word processors. Use a simple # for headings or - for lists and suddenly have a well presented document.
2. Portability Markdown plays nicely everywhere, writing on Github, code editor or Notepad++ and doesnt care whter Mac, PC or toaster (not yet anyway).
3. Focus on Content With the minimal syntax, you can concentrate on ideas, not formatting. Great for making and viewing notes and turning that into documentation with no fuss.

Getting Started with Git

1. Install Git
   Visit and install Git.
2. Learn Basic Commands
   • git init Initialize a new repostiory
   • git add Stage changes
   • git commit Save changes with a message
   • git push Upload changes to remote repository.
   • git pull Fetch and mege updates from remote repository.
3. Learn from Doing
   Create a small project, track your progress, and push your work to Github. Even if its just a basic README for your account.
4. Resources
   • Pro Git by Scott Chacon and Ben Straub (Free Online Book)
   • Githubs learning Lab
   • Tutorials on YouTube and Codeacademy.

Getting Started with Markdown

1. Write your first Document
   Use # for headings, - for listss [text](url) for links and theres your first document.
2. Preview your Work
   Use README in Github, Coding Editor like VS Code, online markdown editor or install package for Notepad++.
3. Explore advanced features
   Try creating tablkes, code blocks or embedded images.
4. Resources
   • The Markdown Guide
   • Tutorials on Gihub Docs
   • Apps like Typora or Dillinger

Simple Guide to Learning Git and Markdown

1. Start Small
   • Create a personal project in Github.
   • Write a README file in Markdown
2. Experiment
   • Practice branching and merging
   • Format documentation, Notes, blog/Social Media posts
3. Integrate
   • Combine Git and Markdown
   • Clone repository edit and push to Github
4. Join the Community
   • Share projects on Github
   • Contribute to opens-source

Final Thoughts

Choosing Git and Markdown might not have the flashiness of Python or JavaScript but these tools provide the foundation for everything else you build.

When someone asks you "What was your first programming language?" feel free to reply "I chose to manage my projects like a pro, I chose to communicate my ideas clearly and effectively, I chose to build a foundation, I chose Git, I chose Markdown, I chose something else."