Developer Portfolio

A Virtual Machine (VM) is, for me, mainly a practical way to try things out without affecting my own computer. The idea is straightforward: you run an extra computer inside your existing system. That extra computer has its own operating system, its own settings, and its own environment, while still using the hardware of your laptop or desktop.

Whatever happens inside that VM stays there. That makes it a comfortable place to learn, test, and sometimes just experiment without worrying too much about consequences.

A computer inside a computer

You can think of a VM as a sealed-off space within your current operating system. Your normal system — macOS, Windows, or Linux — keeps running as usual. Alongside it, you start a virtual machine with, for example, a Linux distribution installed.

That virtual machine behaves as if it were a real computer. It has its own memory, storage, and CPU resources, all managed in software. Because of that separation, you can change settings, install software, or break things without risking your main system.

For me, that mainly means peace of mind. If something goes wrong, I shut down the VM or delete it and start again.

Running a VM next to your desktop (for example with UTM)

On macOS, I use tools like UTM to run virtual machines. The workflow is simple: you download an installation file for an operating system, attach it to a new VM, and start it. Within minutes, you’re working inside a completely different system, running in a window next to your regular desktop.

What I like about this setup is that nothing feels permanent. You don’t replace your current system, and you don’t have to commit to anything long-term. The VM is there when you need it and gone when you don’t.

That makes it easy to try things out without overthinking the decision.

Getting to know other operating systems

One of the main reasons I use VMs is to explore different operating systems, especially Linux distributions. Fedora, Ubuntu, and many others all have slightly different approaches and design choices.

Running them in virtual machines lets you slowly get a feel for:

how each system is structured
how software is installed and managed
how the terminal works
what makes one distribution feel different from another

You don’t need to decide upfront which system is “right” for you. You just try them.

Doing things you wouldn’t do on your main system

I also use VMs for systems like Kali Linux, which comes with a lot of security and networking tools. These are not things I want installed directly on my everyday desktop, but they are interesting to explore and understand.

Inside a VM, this feels natural. It’s a contained environment where you can experiment and learn without affecting your daily workflow. Everything stays separated, which makes it easier to focus on what you’re testing instead of worrying about side effects.

How I personally use VMs

My use of virtual machines isn’t very strict or structured. Sometimes I want to check out a new operating system, sometimes I want to test a tool I’ve read about. I create a VM, use it for as long as it’s useful, and remove it when I’m done.

I actually like that nothing has to be permanent. A VM doesn’t need to be carefully maintained. It’s a place to explore, not something that has to be perfect.

Why VMs make learning easier

What virtual machines really do for me is lower the barrier to learning. You don’t have to be afraid of making mistakes. That makes experimenting feel relaxed instead of stressful. Instead of only reading about how things work, you’re inside the system, using it directly.

For beginners and curious tech enthusiasts, that’s probably the biggest advantage: you learn by doing, without putting your main computer at risk.