Forem: Little Coding Things Blog

Why Every Developer Should Still Know curl in 2026

Little Coding Things Blog — Wed, 18 Mar 2026 11:00:46 +0000

In 2026, with AI-powered IDEs writing your fetch calls, Postman generating collections from a description, and copilots auto-completing your entire API integration layer — you might wonder: do I still need to learn **curl?

Yes. Absolutely. And here's why.

What is curl?

curl (Client URL) is a command-line tool for transferring data using network protocols — most commonly HTTP and HTTPS. It has been around since 1998, ships on virtually every Unix-based system, and is available on Windows. It requires no GUI, no account, no setup. You open a terminal and you run it.

That simplicity is precisely why it remains irreplaceable.

The AI Argument — and Why It Doesn't Replace curl

👉 Continue reading the full guide on Little Coding Things

💡 Enjoyed this? Follow @lilCodingThings for more coding tips and tutorials!

How to install Git on MacOS

Little Coding Things Blog — Thu, 05 Feb 2026 11:48:43 +0000

Originally published on Little Coding Things

So, you’re new to macOS and ready to set up Git? Great choice! Git is one of the essential tools for developers, and installing it should be one of the first steps in your journey. Don’t worry—it’s easier than you think. Let’s get started!

If you’ve never worked with Git before, think of it as a timeline for your files. It’s a tool used to keep track of every change you make, so you can jump backward in time if you break something or experiment freely without losing your original work.

It’s not just for programmers — writers, researchers, and designers also use Git to track versions of their work. Installing Git on your Mac now will save you a lot of headaches later.

Although there’s a small learning curve at first, you’ll quickly find that once you’ve used Git for a while, you can’t imagine working without it — you’ll wonder how you ever managed before.

Check if Git is already installed

If you’re just setting up your Mac, it’s unlikely that Git is already installed. macOS doesn’t come with a fully functional Git by default. Instead, it includes a placeholder located at /usr/bin/git. This placeholder acts as a link to the actual Git version, which gets installed with Xcode or the Command Line Tools.

To check, open your terminal and type:

git --version

If you see something like

No developer tools were found, requesting install

it means that macOS detected that you tried to use a command line developer tool — git in this case – but the Xcode Command Line Tools are not installed on your system.

From here, you have two main choices for installing Git on your Mac — Apple’s Xcode Command Line Tools or the Homebrew package manager. Both will get the job done, but they have different strengths.

Xcode Command Line Tools is quick and easy if you just want to start using Git right away, but the version it installs is maintained by Apple and might not always be the latest.
Homebrew, on the other hand, gives you more control and makes it simple to update Git whenever a new release comes out. If you plan to keep working with Git regularly, I suggest going with Homebrew for its flexibility and ease of maintenance.

Install Git on Mac using Xcode

Xcode is one of the quickest ways to install Git on your system. Since Xcode Command Line tools include Git in the package, to use Git all you need to do is type the following command in your terminal

xcode-select --install

When the pop-up appears, click Install. Make sure you’re connected to the internet.

Once the installation finishes, confirm it by typing:

git --version

You should now see something like:

git version 2.39.5 (Apple Git-154)

Install Git on Mac using Homebrew

Another popular way to install Git on macOS, apart from using Xcode Command Line Tools, is by using Homebrew.

This method is often preferred by developers who want more control over the Git version or are already using Homebrew for managing other software.

To install Git using Homebrew, run the following command

brew install git

Running this command will display some logs related to the Git installation, such as:

....
==> Installing git
==> Pouring git--2.47.1.arm64_sequoia.bottle.tar.gz
==> Caveats
The Tcl/Tk GUIs (e.g. gitk, git-gui) are now in the `git-gui` formula.
Subversion interoperability (git-svn) is now in the `git-svn` formula.

zsh completions and functions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> Summary
🍺 /opt/homebrew/Cellar/git/2.47.1: 1,685 files, 54.4MB
==> Running `brew cleanup git`...
....

Once the installation process is complete, you can verify that Git was installed successfully by typing:

git --version

You should see

git version 2.39.5 (Apple Git-154)

With Git successfully installed, you’re now ready to dive into your development journey and take full control of your projects!

🛠 Extra Tip: When installing via Homebrew, you can easily update Git later by running:

brew update && brew upgrade git

This ensures you’re always on the latest stable release without waiting for Apple updates. It also makes switching between different Git versions simple, which is useful for testing or specific project needs.

This will show your username, email, and other configuration details. These can be changed at any time if you switch accounts or need to adjust your settings.

Next Steps with Git
Installing Git is just the beginning. The next step is learning a few key commands that will make you productive right away. Start with:

git init – Create a new repository in the current folder.
git add <filename> – Stage files you want to include in your next commit.
git commit -m "message" – Save your staged changes with a short description.
git status – Check what’s been modified, staged, or committed.
git log – View a history of all commits in the repository. Once you’re comfortable with these, try creating a branch with git branch and switching to it using git checkout . Branching is one of Git’s most powerful features, letting you work on new ideas without touching your main project until you’re ready.

As you explore these commands, remember that consistent practice is the fastest way to build confidence and skill with Git. And if you want to take things a step further, tools like Husky pre-commit hooks can help automate checks and streamline your workflow as you grow.

How to Install NPM on MacOS

Little Coding Things Blog — Sun, 01 Feb 2026 14:30:27 +0000

Installing Node.js and npm (Node Package Manager) on your Mac is super simple. With these tools, you can manage Javascript packages, create powerful web applications, and dive deep into modern web development. Start by following these steps:

Step 1: Verify that npm is installed

Open your terminal and type

node -v
npm -v

If you see version numbers (e.g., v16.13.0 for Node.js and 8.1.0 for npm), they’re already installed.
If you see errors or no versions, continue to the next step.

👉 Continue reading the full guide on Little Coding Things, we’ll
walk you through installing Node.js with Homebrew, verifying everything works, and keeping npm updated.

How to install Homebrew — MacOS for beginners

Little Coding Things Blog — Fri, 30 Jan 2026 17:15:23 +0000

Originally published on Little Coding Things

If you are making your first steps on macOS, you may have never heard of Homebrew before. Homebrew is a powerful package manager, similar to npm if you’ve worked with it before. It allows you to easily install, update, and remove software packages directly from your terminal, making it an incredibly handy tool for developers. In this post, you’ll find a step-by-step guide to install Homebrew on MacOS.

Why is it essential to install Homebrew?

Homebrew is widely regarded as the most popular package manager for macOS. It’s the go-to choice for developers and power users because of its simplicity and active community support.

Homebrew lets you easily get the tools and libraries you need for development or daily tasks, from developer tools like Git and Node.js to simple everyday utilities. It saves time by skipping the trouble of manual downloads and setup. It’s simple, fast, and perfect for customizing your Mac.

If you haven’t used a tool like Homebrew before, don’t overlook it — it could completely transform the way you manage software on your Mac.

Check if Homebrew is already installed

Just to make sure you haven’t already installed Homebrew in the past, let’s check it out. Open your terminal and type:

brew help

If you have it installed, you should see something like

Example usage:
  brew search TEXT|/REGEX/
  brew info [FORMULA|CASK...]
  brew install FORMULA|CASK...
  brew update
  brew upgrade [FORMULA|CASK...
....

otherwise, you will get the following result

command not found: brew

How to install Homebrew

Ready to install Homebrew? Here’s everything you need to know. Open your terminal (Cmd + Space and type “Terminal“) and type

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Oh, you say! What is this command? Let me explain. This command asks bash (which is a command-line shell language commonly used in macOS and Linux) to execute a script.

Here’s how it works:

/bin/bash: specifies the bash shell, ensuring the command is executed using bash, even if your default shell is something else (like zsh).
-c: This flag tells bash to execute the command provided in quotes.
$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh): This part fetches the Homebrew installation script directly from GitHub using curl (a tool for transferring data).

In simple terms, this command downloads the Homebrew installer script from GitHub and immediately runs it using bash to set up Homebrew on your system.

You will be asked for your super user password:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Checking for `sudo` access (which may request your password)...

Password:

After typing your password, you’ll see a message prompting you to press ENTER to proceed with the installation. Simply press ENTER, and the installation will continue.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Checking for `sudo` access (which may request your password)...

Password:

==> This script will install:
/opt/homebrew/bin/brew
/opt/homebrew/share/doc/homebrew
....
/opt/homebrew
==> The following new directories will be created:
/opt/homebrew/bin
/opt/homebrew/etc
/opt/homebrew/include
....
/opt/homebrew/Frameworks

Press RETURN/ENTER to continue or any other key to abort:

Wait for the installation process to complete — it may take a few minutes. Once it’s done, you’ll see the message “Installation successful!”. However, to ensure everything was installed correctly, let’s verify it by typing the following command in the terminal:

brew help

If it was successfully installed, you should see the following response.

Example usage:
  brew search TEXT|/REGEX/
  brew info [FORMULA|CASK...]
  brew install FORMULA|CASK...
....

Homebrew doesn’t work after installing it

If you’ve already followed all the steps described to install Homebrew but see a “command not found” error when running, e.g., brew help it typically means that the Homebrew binary is not properly added to your system’s PATH.

To resolve the issue, revisit the logs from the Homebrew installation script. At the end of the script, you’ll typically find specific instructions for finalizing the installation.

Warning: /opt/homebrew/bin is not in your PATH.
Instructions on how to configure your shell for Homebrew
can be found in the 'Next steps' section below.
==> Installation successful!
...
...
...
==> Next steps:
- Run these commands in your terminal to add Homebrew to your PATH:
echo >> /Users//.zprofile
echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> /Users//.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

copy the last part of the Homebrew installation instructions — starting from the command that begins with echo — and paste it into your terminal. This command typically adds Homebrew to your system’s PATH.

By now, you should have Homebrew installed on your system successfully.

Congratulations! This is just the first small step on your exciting journey to mastering powerful tools and workflows as you grow your skills.If you’re exploring ways to automate parts of your development workflow next, you might find Git tools like Husky pre-commit hooks especially helpful.

How Do New Blogs Build Authority These Days?

Little Coding Things Blog — Fri, 30 Jan 2026 17:06:19 +0000

Lately, we’ve been thinking a lot about authority.

At littlecodingthings.com, we’ve been around for about a year+ now. We’re still early, still learning, and still figuring out what “doing this right” even means. And honestly, in today’s AI-heavy world, writing content can feel unexpectedly challenging. There’s more content than ever, answers are everywhere, and sometimes it feels like the internet has already covered every topic from every angle.

One thing we want to be clear about though: we’re not using AI to generate our content. We use it for brainstorming, tightening up wording, or improving syntax — but the ideas, experiences, and opinions are still very much human. The actual content comes from learning, building, breaking things, and writing about it afterward.

After a year of publishing, the question that keeps coming back is still the same: how do new blogs build authority now?

How do you earn real backlinks in a world where content is cheap, automated, and often impersonal? What actually moves the needle when you don’t want to play growth games or churn out content just to fill space?

We don’t have answers. We’re trying to focus on small, thoughtful posts. The details you only notice when you’re actually doing the work.

If you’ve been through this phase, or you’re in it right now, we’d love to hear how you approached it. What helped you build trust? What surprised you? And how does writing feel for you now that AI is everywhere?

We’re still learning in public, one year in, and hoping that asking better questions is part of building something that lasts.

Am I Too Old to Learn Coding?

Little Coding Things Blog — Fri, 02 Jan 2026 18:34:52 +0000

Originally published on Little Coding Things

I have to say, this is a question I’ve been hearing for a long time since I got into the web development world. It’s a very common question, so please don’t feel like you’re alone when asking it. Many people are in your shoes and wonder the exact same thing.

This question is probably not just about coding, but about change in general. Deep down, the question might not be “Am I too old to learn coding?” but rather “Am I too old to change?” Let’s explore this together.

For those of you looking for a TLDR answer: No! You are not too old!

But I’m quite sure that doesn’t fully convince you — so let me explain.

My Late Start in Web Development

Here’s a short story about me, just so you know we might have been walking a similar path.

I’m not 100% a tech person. I didn’t study Computer Science or anything related when I finished school. I started working in a completely different field — sales in supermarket goods. At some point, I went on to take an MSc in Information Systems, a program designed for non-tech people. It had no coding lessons related to web development.

I discovered web development while browsing sites like Coursera and edX — and I loved it. I was in my mid-30s at the time, and I asked myself the same question: Am I too old to learn coding? Let me tell you what I found out.

By the way, I’ve been working as a web developer for the past 7 years. So yes — there are success stories out there, and yours can definitely be one of them too!

You’re Not Starting from Zero

This is 100% true — you’re not starting from zero. You might be thinking, “But I have no experience with programming. How can that be true?” Well, even if you’re new to coding, programming is about more than just writing code.

While you’ll focus on technical skills when learning for a job, that’s only part of what you’ll need to succeed in tech. Like any job, being a good developer also depends on other important skills, such as:

👉 Continue reading the full story on Little Coding Things