Gemma For Dummies: I Knew Nothing. Now I'm Running AI on My Laptop.

Aditthya SS Varma — Sun, 24 May 2026 15:54:17 +0000

I saw the Gemma 4 challenge on dev.to. I wanted to participate. I had absolutely no idea where to start.

I opened the challenge page and the first thing I saw was "run a Gemma 4 model locally." I stared at that sentence for a while.

What does running locally even mean?

I genuinely thought AI only lived on big servers somewhere. You type, it thinks, it replies. I never questioned how it worked. It just worked.

So I started asking basic questions. Really basic ones.

"What is running locally?"
"What happens if I don't have enough RAM?"
"Why can't I just use my laptop as a server for everyone?"

And slowly — question by question — it started making sense.

This post is everything I learned. Written for the version of me that existed a few days ago.

What Does "Running Locally" Mean?

When you use ChatGPT, your message goes to the internet, reaches a server far away, gets processed, and comes back. You are using someone else's computer.

Running locally means the AI runs on YOUR computer. No internet. No monthly fees. No one else's server. Just your laptop doing the thinking.

That's the whole concept. I overcomplicated it in my head for no reason.

What Is Gemma 4?

It's an AI model made by Google — and they've made it free to download and run yourself.

It comes in different sizes:

Model	Size	Good for
E2B	~2 GB	Phones, edge devices
E4B	~4 GB	Most laptops
31B	~20 GB	Powerful desktop/server

Bigger = smarter but slower and needs more memory.

For a regular laptop — start with E4B.

My Setup

I'm on Windows with 8 GB RAM and an Nvidia GPU with 4 GB VRAM.

Someone told me to open my terminal and type:

nvidia-smi

I had no idea what that would show. I typed it, hit Enter, and got:

NVIDIA-SMI 566.07    Driver Version: 566.07    CUDA Version: 12.7

I didn't fully understand it. But apparently that's good — your GPU is ready.

CUDA is what lets your Nvidia GPU talk to AI software. Ollama — the tool we use to run Gemma — automatically uses your GPU to make things faster. Part of the model loads into GPU memory, part into RAM. Your graphics card starts doing AI inference.

That felt genuinely cool.

How To Run Gemma 4 (3 Steps)

Step 1: Download Ollama from ollama.com/download

Normal installer. Install it like any app.

Step 2: Open your terminal and type:

ollama run gemma3:4b

It downloads the model and opens a chat. Done.

Step 3: Talk to it.

>>> What is photosynthesis?
>>> Write me a Python function to sort a list
>>> You are a helpful doctor. Answer my health questions simply.

No internet. No API key. No cost. The AI is running on your machine.

The Question That Changed How I Thought About This

At some point I asked — "Why can't I just use my laptop as a server and let everyone access it?"

The answer was obvious once I heard it:

Your laptop needs to be on 24/7
Home internet isn't designed for incoming traffic
10 users at once will crash it
And most importantly — you've solved nothing for people with no internet That last point took me somewhere unexpected.

The Thing That Really Excited Me

Imagine a village with no reliable internet.

A chatbot that calls a cloud API is useless there. Signal drops — chatbot dies.

But a small cheap device running Gemma E2B locally, sitting in a community center or clinic? Zero internet needed. The AI lives physically in that location. People connect through local WiFi and get answers.

This is why Google built the small models. E2B runs on hardware that costs $80-300. Not everyone has cloud internet. Gemma 4 was designed with that reality in mind.

That's when "running locally" stopped feeling like a developer trick and started feeling like something with real impact.

When To Use the API Instead

For an app real users access over the internet — don't run it on your laptop. Use the Gemma API.

The easiest way is OpenRouter — one account, one API key, free access to Gemma 4. No setup headaches.

The simple rule:

Local Ollama = learning and experimenting
API = building and deploying

That's It

A few days ago I didn't know what a model was. I didn't know what CUDA meant. I didn't know why RAM mattered.

Now Gemma 4 is running on my laptop and I actually understand why.

The learning curve looked steep from the outside. It really wasn't.

Download Ollama. Run one command. See it work. Everything else follows.

Total beginner? Drop a comment — happy to help you get it running.

Building something with Gemma for offline or rural communities? I'd love to hear about it.

OpenClaw for dummies

Aditthya SS Varma — Sun, 26 Apr 2026 18:11:24 +0000

The first time I heard about OpenClaw, I closed the tab.

Someone shared the name in my group. I Googled it, looked at the docs for about two minutes, had no idea what I was reading, and gave up. Not for me. Moving on.

Then the internet had other plans.

Over the next few days, OpenClaw kept showing up. YouTube channels I watch started making videos about it. Tech newsletters mentioned it. My feed was full of people building things with it and acting like it was obvious. I kept scrolling past — but something stuck. If so many people were talking about it, maybe I quit too early.

So I opened the tab again. Same docs. Same words I didn't understand. But this time I kept going. And what I found surprised me — it was not that hard. Once something clicked, it actually felt kind of fun.

This post is for anyone who closed that tab.

The thing nobody tells beginners

Learning something new is always a little uncomfortable. But with most tools, you at least know what you don't know. OpenClaw is trickier. The docs use words like skills, workflows, and agents — and if you've never seen them before, they don't mean much.

That's not your fault. It just means the guide was written for someone who already had a head start.

What helped me was to stop reading and ask one simple question: what's the smallest thing I can try right now? Not the full picture. Not the perfect setup. Just — what can I do today?

That one question made everything feel lighter.

What OpenClaw actually is (no jargon)

Here's the simplest way I can explain it: your AI is smart, but it's stuck in a box. It can't see your calendar, your notes, or your files. OpenClaw lets you open that box and connect your AI to the stuff that actually matters in your day.

A "skill" is just a way of teaching your AI to do something specific. Want it to look at your tasks every morning and tell you what to focus on? That's a skill. Want it to write emails the way you would? Also a skill.

The thing that made it click for me: building a skill is not like writing code. It's more like writing detailed instructions for a new assistant on their first day. If you've ever written a good prompt and got a great result, you already know how to think about this.

It's easier than it looks

What I'd tell myself on day one

Start with a problem, not a feature. Think of one small, annoying thing you do every week. Start there. That's your first skill.

Your first try will not be great. That's fine. Mine was messy and too complicated. But I learned more from building it badly than from reading docs for an hour. Make something. Fix it later.

The community is really helpful. People share what they built, talk about what went wrong, and answer basic questions without making you feel silly.

Don't wait until you feel ready. That feeling comes from doing, not reading. Just start.

DEV Community: Aditthya SS Varma