Regulalar Expression

Juma Evans — Wed, 13 May 2026 01:47:34 +0000

Mastering Regular Expressions in JavaScript: From Basics to Real-World Validation

At first glance, a regex pattern looks like a cat walked across your keyboard,a chaotic string of slashes, brackets, and symbols. However, once you decode the syntax, it becomes one of the most powerful tools in your developer toolkit.
Below is the break down of how regex works in JavaScript and build a robust pattern to validate something we use every day: email addresses.

What is a Regular Expression anyways?

A Regular Expression is an object that describes a pattern of characters. In JavaScript, you can create them in two ways:

Literal Notation: /pattern/flags
Constructor: new RegExp('pattern', 'flags') ### The Core Building Blocks Before we tackle the email login, we need to understand the "alphabet" of regex:
Character Classes:
- \d: Matches any digit (0-9).
- \w: Matches any alphanumeric character (letters, numbers, and underscores).
- \s: Matches whitespace (spaces, tabs).
- .: The wildcard—matches any character except a newline.
Quantifiers:
- +: Matches 1 or more of the preceding element.
- *: Matches 0 or more.
- {n,m}: Matches between n and m times.
Anchors:
- ^: Forces the match to start at the beginning of the string.
- $: Forces the match to end at the end of the string. ### Deep Dive: Validating an Email Address When we log in to a platform, the first line of defense is ensuring the input actually looks like an email. Let’s build a regex for a standard email like zone01.recode@company.co.ke. #### 1. The Local Part (zone01 .recode) We want to allow letters, numbers, dots, and underscores.
Pattern: ^[a-zA-Z0-9._%+-]+
Explanation: We start at the beginning (^) and allow a set of characters inside the square brackets. The + ensures there is at least one character. #### 2. The "@" Symbol We just need the literal character.
Pattern: @ #### 3. The Domain (company) Similar to the local part, but usually without the special symbols.
Pattern: [a-zA-Z0-9.-]+ #### 4. The TLD (.co.ke or .com) We need a literal dot, followed by letters. Since a dot . is a wildcard in regex, we must escape it with a backslash ..
Pattern: .[a-zA-Z]{2,}$
Explanation: This looks for a dot and at least two letters at the very end of the string ($). #### Putting it all together:

const emailRegex = /^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/;

const testEmail = "dev_user123@zone01.edu";
console.log(emailRegex.test(testEmail)); // Output: true

Common Use Cases in Web Apps

Beyond login forms, regex is used everywhere in full-stack development:

Password Strength: Checking for at least one capital letter, one number, and one special character.
URL Parsing: Extracting slugs or IDs from a browser's address bar.
Data Scrubbing: Removing formatting from phone numbers (e.g., changing +254 712-345-678 to 254712345678).
Search and Replace: Swapping specific words across a whole document using the global /g flag. ### Helpful Methods in JavaScript To use your patterns, you’ll mostly use these two methods:
regex.test(string): Returns true or false. Perfect for form validation.
string.match(regex): Returns an array of matches. Great for extracting information from a large block of text. > Pro Tip: Use tools like RegEx101 to test your patterns in real-time before putting them into your code. It provides a "flavor" setting—make sure to select ECMAScript (JavaScript). > ### Conclusion Regex might feel like a steep climb, but it is a "learn once, use everywhere" skill. Whether you are working on a Go backend or a JavaScript frontend, the logic remains largely the same. Keep practicing by trying to validate other common inputs like phone numbers or postal codes!

Docker Unlocked: What I Wish I Knew earlier.

Juma Evans — Wed, 18 Feb 2026 20:20:02 +0000

When I first heard about Docker, I thought it was something extremely complex that only senior developers used.

Until recently, that is. When I finally started learning Docker, I found out how amazing it is, and I want to share what I've learned.
If you're just starting out, this is for you.

So…
1. What Is Docker?
Docker is a tool that lets you package your application with everything it needs to run:-dependencies, libraries, system tools, and your code;into something called a container.
2. What Problem Does Docker Solve?
Think of it like this:
"It works on my machine" stops being an excuse.
With Docker, if it works inside the container, it works everywhere.
Before Docker, this is what used to happen:
Developer X runs the application successfully.
Developer Y tries to run it, and it breaks.

Developer X tells Developer Y: “But it works on my machine!”

Why?
Different environments:

° Different operating systems
° Different versions of NODE or Go or Python
° Different installed dependencies

Docker solves this by creating a consistent environment that travels with your application.

3. What Is a Container?
A container is like a lightweight, portable box for your application.
But unlike a full virtual machine:

° It starts fast—usually in seconds
° It uses fewer resources
° It's easy to share and move around

How It Works:

You define how your application should run in a file called a Dockerfile (a blueprint for your environment).
Docker uses that file to build an image (a snapshot of your app and everything it needs).
Then that image runs as a container (the live, running version of your application).

When I first installed Docker, created my Dockerfile, built an image, and it actually worked…
I felt like I unlocked a new level in development 😂.
That was the moment I realized:
This is how real-world applications are deployed.

Why Every Beginner Should Learn Docker
Here is why I believe Docker is worth learning early:

It Makes You Think Like a Backend Engineer You begin to understand: ° Ports and how applications communicate ° Services and how they connect ° Environment configurations ° How production setups differ from local development
It Improves Your Project Structure You naturally start organizing your apps better when you know they'll run in containers.

🛠 Things That Confused Me at First
To be honest:
° Images vs. Containers: I couldn't keep them straight. (Think of an image as a recipe and a container as the actual cooked meal.)
° Dockerfile syntax: It looked scary at first glance.
° Ports: Mapping ports from the container to my computer didn't make sense initially.

But after building just one simple container for a Go app, everything started connecting.

What Next?
Now that I understand the basics, I plan to:

° Containerize my Go projects
° Learn Docker Compose (for running multiple containers)
° Understand how containers are used in production

One step at a time.

Summary
Imagine you bake a cake 🍰 at home.
You pack:
°The cake
°The ingredients list
°The exact oven settings
°The instructions

Then you put everything inside one box.
Now, no matter where that box goes, Nairobi, Kisumu, or New York, anyone can open it and get the exact same cake.
That is exactly what Docker does.

It puts:
. Your app
. The tools it needs
. The correct settings
Inside one “box” called a container.
So instead of saying:
“It works on my machine.”
You can confidently say:
“It works everywhere.”

DEV Community: Juma Evans

Regulalar Expression

Mastering Regular Expressions in JavaScript: From Basics to Real-World Validation

What is a Regular Expression anyways?

Common Use Cases in Web Apps

Docker Unlocked: What I Wish I Knew earlier.