DEV Community: Agunechemba Ekene

The Most Beautiful “Ugly” Gift in Tech: Happy Birthday Jean-Baptiste Kempf

Agunechemba Ekene — Mon, 30 Mar 2026 14:59:11 +0000

Happy Birthday to Jean-Baptiste Kempf, the man who looked at the flashy, over-designed world of media players and decided to give us a traffic cone instead.

As we celebrate the founder of VLC today, let’s address the elephant in the room: VLC is objectively ugly. As Android Police recently reminded us, the interface looks like a time capsule from 2001. It’s gray, it’s clunky, and the menus are a labyrinth of technical jargon. In an era of sleek “Glassmorphism” and “Material You,” VLC remains stubbornly, unapologetically bland.

But here’s the twist: We wouldn’t have it any other way.

While other players “look” premium but choke on a basic MKV file or demand a subscription for 4K playback, Jean-Baptiste’s creation just works. It doesn’t care about your aesthetic preferences; it only cares about your codecs. It is the rugged Swiss Army knife in a world of gold-plated butter knives.

We don’t open VLC to look at the UI. We open it to make the UI disappear so we can actually watch our content.

So, Jean-Baptiste, thank you for focusing on the engine rather than the paint job. Today, we’re raising a glass (and a traffic cone) to the greatest piece of “ugly” software ever written.

The Flute and the Code: Why Many Programmers Are Becoming Unoka

Agunechemba Ekene — Sat, 21 Mar 2026 14:44:36 +0000

In the book Things Fall Apart, Chinua Achebe’s Unoka was easy to dismiss. He sat in his hut playing his beautiful flute while other men farmed yams and went to war. He died in debt, carried to the Evil Forest.

But Unoka is alive today. He is writing code.

Walk into any tech company. You will find brilliant programmers who love the craft the way Unoka loved music. They stay up perfecting elegant functions no user will ever notice. They refactor code that already worked. They argue about tabs versus spaces with the passion of warriors.

But ask them to talk to a user. They grimace. Ask them to understand the business problem. They say it is not their job. Ask them to step away from the terminal and face the messy reality of why people actually need what they are building. They retreat into abstraction. They have become Unoka, sitting in a modern hut, playing a digital flute.

There is nothing wrong with loving your craft. The problem is when the craft becomes an escape from responsibility. Unoka said he hated the sight of blood. He said farming was not his gift. He played his flute instead. But when the lean season came, he begged for yams. When his family needed protection, he had no title. The flute did not save him.

Today, programmers say, “I just want to write clean code.” But code does not exist in a vacuum. Code solves problems. It runs businesses. It pays salaries. It serves people. When a programmer refuses to engage with anything beyond syntax, they are refusing the very reason their craft exists.

Achebe did not romanticize Unoka. He showed us a man who chose beauty over responsibility and paid the price. The flute was not evil. But playing it while the world demanded something else was a slow kind of death. Programmers today make the same choice. They choose the elegance of abstraction over the messiness of reality. They measure themselves by cleverness rather than impact. And like Unoka, they become irrelevant.

Love the code. But let it serve life. Talk to users. Understand the problem. Write beautiful software that actually helps someone. Engage with reality instead of hiding from it. Unoka’s music could have meant something if he had played it in service to his community instead of in escape from it. Your code can mean something too.

Rest in peace, Chinua Achebe. Your stories still speak.

The Man Every Open Source Community Should Worship: Happy Birthday Richard Stallman

Agunechemba Ekene — Mon, 16 Mar 2026 07:01:43 +0000

If you’ve ever typed a line of code in a free editor, hosted a project on GitHub, or used a Linux-based OS, you owe a debt to Richard Stallman.

While others saw software as a commodity, Stallman saw it as a moral battlefield. In 1983, he launched the GNU Project, not just to build an operating system, but to declare independence from proprietary giants. He gave us the GPL (General Public License)—the legal “shield” that ensures free software stays free.

He didn’t just invent tools like GCC or Emacs; he invented the very idea of digital freedom. Stallman taught us that users should control the program, not the other way around.

We don’t just use his code; we live in the ecosystem of liberty he built.

Happy Birthday Richard Stallman

JavaScript Optional Chaining: The Complete Guide

Agunechemba Ekene — Sat, 14 Mar 2026 14:21:10 +0000

Optional Chaining (?.) is a JavaScript operator that allows you to safely access deeply nested object properties without throwing an error if an intermediate property doesn't exist. Instead of crashing your application, it gracefully returns undefined.

Think of it as a protective guard that checks each step of your property access path and says, "If anything here is null or undefined, I'll stop and return undefined instead of causing an error."

How Optional Chaining Works

When JavaScript encounters the ?. operator, it performs what's called short-circuit evaluation. This means:

JavaScript checks the value immediately before the ?.
If that value is null or undefined, it immediately stops and returns undefined
If that value exists, it continues to access whatever comes after the ?.

This happens at each step of your chain, making it safe to write expressions like user.contact?.phone without worrying about whether contact exists.

Understanding Nullish Values

In JavaScript, "nullish" specifically means null or undefined. This is different from "falsy" values like 0, "", false, or NaN. The distinction is crucial because:

Falsy values are often valid data (like volume set to 0)
Nullish values represent the absence of any value

The Difference Between ?? and ||

This is where many developers get confused. The logical OR operator (||) returns the right-hand value when the left-hand value is falsy. The nullish coalescing operator (??) returns the right-hand value only when the left-hand value is nullish.

This means || will replace valid falsy values with your default, while ?? preserves them. When you're setting defaults for missing data, you almost always want ?? because you only want to replace values that are truly absent, not values that happen to be false, zero, or empty.

When to Use Optional Chaining

APIs rarely return exactly what you expect. Fields might be missing, null, or undefined. Optional chaining lets you safely navigate through API responses without constant checking.
Form data, URL parameters, and other user-provided information often have unpredictable structures.
Applications often have complex configuration with optional sections. Optional chaining makes it easy to read these configurations safely.
Elements you're looking for might not exist on the page. Optional chaining prevents those dreaded "cannot read property of null" errors.

When NOT to Use Optional Chaining

If your application absolutely needs certain data to function, optional chaining might hide underlying problems. Let the error happen so you know something's wrong.
While optional chaining is fast, it does add conditional checks. In tight loops or performance-sensitive code, manual checks might be more appropriate.
If you're working with objects you control and know the structure of, optional chaining is unnecessary overhead.

Happy Birthday Linus Torvalds: The Father Of Modern Computers

Agunechemba Ekene — Sun, 28 Dec 2025 11:53:38 +0000

Happy Birthday Linus Torvalds: The Father Of Modern Computers | 合

agunechemba.name.ng

Linus Torvalds is the kind of person who works quietly while the world runs loudly. He created Linux, the software that helps power phones, computers, servers, and even the internet itself. But what makes Linus special is not just what he built—it’s how he keeps taking care of it. Year after year, he continues to work, guide, review, and improve Linux, even when he doesn’t have to. That kind of dedication is rare.

When people visit his GitHub page, they see a calendar full of green boxes. Each box stands for a day. A green box means Linus did some work that day on GitHub.

Light green means a little work, darker green means more work, and very dark green means a very busy day. What’s amazing is how often those boxes are green. It shows that Linus doesn’t work only when he feels inspired. He works because it’s part of who he is.

Now here’s something important: the days that are not green don’t mean Linus stopped working. Many times, he is busy working on software outside GitHub—thinking deeply, reviewing code in other systems, planning future changes, or solving problems that don’t show up on that calendar. So even when a box is dark, the work may still be happening. Some of the most important effort is invisible.

And now comes the twist 🎂

Today is Linus Torvalds’ birthday.

That means this green calendar is not just a work chart—it’s a life chart. Each green box is like a small candle, showing days he gave his time and focus to something bigger than himself.

Each dark box is a reminder that rest, thinking, and quiet work matter too. A birthday is not about doing more today; it’s about looking back and realizing how far steady steps have carried you.

If Linus were to unwrap a gift today, it wouldn’t be noise or praise. It would be the knowledge that his consistency—both seen and unseen—has helped millions of people learn, build, and dream.

His birthday teaches us something simple and powerful: showing up, little by little, can change the world.

Happy Birthday, Linus. Your life’s work is written not just in code, but in habits. 🎉💚