DEV Community: Kimberley Madoya

Why Every Developer Needs a Strong Test Suite (Even If You Hate Writing Tests)

Kimberley Madoya — Sat, 20 Jun 2026 12:23:23 +0000

I used to think tests were a waste of time.

"Ship fast, fix later" was my motto. Until I spent three painful weeks debugging a production issue that a simple test would have caught in 30 seconds.

That was the day I became a believer.

The Harsh Reality Most Solo Developers Ignore

If you're a freelancer or indie hacker building real products for clients, here’s what happens without good tests:

You make a "small change" and something unrelated breaks
Clients find bugs you should have caught
Refactoring becomes terrifying
You lose sleep before every deployment
Your reputation slowly takes hits

A solid test suite changes all of that.

What a Test Suite Actually Gives You

Confidence to Move Fast

You can refactor, add features, or upgrade dependencies without fear.
Living Documentation

Your tests explain how the system should behave — better than comments ever could.
Early Bug Detection

Catch issues before they reach the client or production.
Better Architecture

Writing testable code forces you to write cleaner, more modular code.
Professional Credibility

When clients or senior devs review your code, a good test suite immediately signals seriousness.

The Test Suite Pyramid I Actually Use

Unit Tests (70%) → Test individual functions and components
Integration Tests (20%) → Test how different parts work together (API + DB)
End-to-End Tests (10%) → Critical user flows (login → checkout → etc.)

I don't aim for 100% coverage. I aim for high-value coverage — especially around business logic and critical paths.

Final Thought

Writing tests feels slow at first.

But it compounds. Every month you have tests, you move faster and sleep better.

The developers who ship reliable software consistently aren't necessarily the smartest — they're usually the ones who learned to respect testing.

Have you built a strong test suite habit yet? Or are you still in the "I'll test it manually" phase?

Drop your experience below. Let's talk.

From Blank Terminal to Shipping a Real Client Project: My First Year of Coding

Kimberley Madoya — Tue, 09 Jun 2026 18:22:37 +0000

Exactly one year ago, my terminal was a blank slate. I started where almost everyone does , wrestling with HTML, CSS, and JavaScript, trying to understand the web pixel by pixel.

What began as curiosity quickly turned into a full obsession. I went from building simple static pages to diving deep into full-stack development. Here’s what that intense first year of constant building, breaking things, and shipping real projects has looked like.

The Leap into Modern Frameworks

Once vanilla JavaScript started feeling limiting, I jumped into React. Component-based thinking completely changed how I approached interfaces. Then came Next.js — it bridged client-side beauty with server-side power and pushed me into a true full-stack mindset.

The Ultimate Test: Lynvista Safaris

The biggest challenge was building lynvistasafaris.com, a live travel booking platform for a real client. This project forced me far beyond tutorials and into real engineering problems.

I had to implement:

Payment infrastructure from scratch with Daraja API (M-Pesa STK pushes) and Paystack for international transactions.
A robust database layer using Drizzle ORM + MySQL.
Custom business logic, including a multi-currency pricing system with special validation rules for currencies like GBP.

It was messy , many late nights debugging webhooks, schema mismatches, and edge cases , but shipping it taught me more than any course ever could.

What One Year Taught Me

Syntax is just a tool. The real skill is learning how to break down complex problems, debug effectively, and keep iterating even when things break in production.

I’m incredibly proud of the progress I’ve made in 365 days (402 contributions later), but I know I’m still at the very beginning. For the next phase, I’m focused on shipping more projects, writing about the crazy bugs I encounter, and deepening my architectural and full-stack skills.

If you want to see what I’m building right now, check out my GitHub.