DEV Community: Muffakir Ibn Hamid

From Web Development to DevOps: Why I’m Shifting My Tech Stack in 2025 ?

Muffakir Ibn Hamid — Thu, 17 Apr 2025 07:42:18 +0000

The tech world is obsessed with churning out full-stack developers. Build a React app! Deploy with Next.js! Optimize your Lighthouse score! And while that’s all great, I’ve realized something: I don’t just want to make websites—I want to understand how the machine actually works.

That’s why I’m diving into DevOps.

This isn’t some career panic move. It’s a curiosity move. Learning DevOps has been like peeling back the layers of the internet and finding a world of Linux commands, Bash scripts, and infrastructure magic—things that make me feel like I’ve unlocked a secret level in the tech game. Meanwhile, my old life as a web dev mostly involved arguing with CSS and pretending I understood Webpack configurations.

But here’s the thing: For me, coding was never just about landing a job. It’s about figuring stuff out. It’s about that rush when a stubborn server finally obeys your commands, or when your automation script actually works on the first try (okay, maybe the fifth try).

So consider this my public accountability post. It is April 2025—one year from today—I will be a competent DevOps engineer. Maybe I’ll even build something useful. Or at least write a Terraform config that doesn’t give me nightmares.

I’ll leave you with wisdom from the man who inspired this whole journey:

“Talk is cheap. Show me the code."
— Linus Torvalds (the patron saint of grumpy geniuses)

See you in the cloud. ☁️

My Linkedin
X/Twitter

How a Linux System boots | Entire Process

Muffakir Ibn Hamid — Mon, 14 Apr 2025 09:16:20 +0000

Hey Devs!
If you're interested in learning Linux or exploring fields like DevOps, this article is the perfect boost for your journey.

We will be covering the entire thing in crystal clear and a step-by-step process.

So Let's Begin:

The Initial Checkup (BIOS/UEFI)
BIOS, also called the Basic Input Output System, or UEFI (modern version of BIOS), is the first software that runs when you power on the system.

Its core functionality:

Checks if all hardware is working like RAM, CPU, Keyboard, Mouse, etc. This process is also called POST (Power-On Self Test).

Finds a bootable device (HDD, SSD, USB, etc.)

Loads the bootloader from that device. (You might have seen options like this while installing an OS)

Bootloader (GRUB in Linux)
GRUB: GRand Unified Bootloader. It loads the Linux Kernel into memory.

Its core functionality:

Shows a boot menu (helps in dual boot)

Loads the Linux kernel

Passes control to the kernel

Linux Kernel (Brain of a System)
You might have gotten confused by reading the word “kernel” several times. Well, the kernel is basically a glue between the hardware and applications in a system. It is the core part of Linux and it manages everything.

Its core functionality:

Detects your hardware (keyboard, display, USB, etc.)

Loads drivers and modules

Mounts the root filesystem

Starts the first user-space process – init (now it's systemd)

init / systemd – The Service Starter
It is the first process (PID 1) started by the kernel.

Its core functionality:

It reads configuration to start services like:

Networking
SSH
Logging
Web server, database, etc.

Runlevel / Target – Boot Mode
Once Linux has started the kernel and systemd, it needs to decide what kind of environment to bring you into, such as:

Text-only mode

Graphical desktop

Single-user recovery mode

Login Prompt – Final Use
This is the final stage where all services are started:

A CLI login (tty terminal)

Or a GUI login screen (if graphical.target is set)

This is the full tutorial on how a Linux system works and boots.
This article was written by Muffakir Ibn Hamid.

I joined dev.to!

Muffakir Ibn Hamid — Sun, 05 Jan 2025 15:05:06 +0000

Hey everyone!
I’m Muffakir, a 17-year-old frontend developer from India. Since childhood, I’ve been passionate about all things tech. My journey started in 9th grade when I began learning Python. From there, I transitioned into Android development (using Kotlin) and eventually found my true calling as a frontend developer.

Today, on January 5, 2024, I joined dev.to—a platform I discovered through ChatGPT. My goal is to land a job before starting college, and I’m excited to see where this journey takes me!

I’ll be sharing updates here regularly as I grow and learn.

Cheers!
Muffakir