DEV Community: Emmaculate Jane Akinyi Odhiambo

Not everything needs an app

Emmaculate Jane Akinyi Odhiambo — Sat, 01 Aug 2026 10:32:32 +0000

If you are making me download a whole mobile app just for me to use it twice a year, then maybe you should just go back to user Experience classes. Correct me if I'm wrong but supposed to be downloading an app so that I can maybe pay a bill or even book an appointment or maybe just viewing the menu Seriously. Don't get me wrong native apps definitely have their space like banking, fitness training, tracking apps, gaming e.tc all that, things that heavily rely on your phone's hardware but this other app's please just make a website

Cache-Aside with REDIS

Emmaculate Jane Akinyi Odhiambo — Sat, 01 Aug 2026 10:13:59 +0000

Every time you open a amazon product or you refresh the same page, do you think that amazon sends a request to the database again. If millions of people are looking at the same product wouldn't that mean 1,000+ database queries and that's extremely expensive. So how do big companies avoid that? There's something called REDIS. REDIS is an in-memory cache, an in-memory cache simply means it stores data on RAM instead of disk cache cause RAM is much faster. REDIS can return data in just a few milliseconds but here's is the most interesting part REDIS doesn't just magically know what data to store and that's where a cache strategy known as a CACHE ASIDE comes in. A user request product 15 and the application ask REDISs, do you have product 15 REDIS says no. This is something known as CACHE MISS, simply means the requested data is not in the CACHE so the application goes to the database and finds product 15 it turns it to the application. Now here's the clever part before sending the product back to the user the application first stores a copy inside REDIS this is called POPULATING THE CACHE now REDIS remembers product 15 and finally the application sends back the product to the user a few seconds later another user requests product 15 again the application asks REDIS and this time REDIS replies product 15 is there. This is called CACHE HIT, it simply means that the requested data is in the cache so the application returns the product immediately and the database is never touched and that is why cache responses are so much faster.

Now let's imagine the product price changes from maybe 999 to 899 but remember the cache stills remember the former price. The cache contains stale data, Stale data simply means that the cache has outdated information. To fix this after updating the database the application deletes the product from REDIS and this is called CACHE INVALIDATION not because the data was bad but simply because it was incorrect data so now when another customer comes in and requests product 15, the application ask REDIS but remember the product was deleted so what will REDIS say, i don't have this product another cache miss so what does the application do, the application goes to the database because the product is unavailable here and then it goes to the database it finds the updated product 15 with the updated price so now it stores a copy in REDIS and then sends a response back to the user with the updated price. From that point on everybody receives the latest data directly from REDIS and remember REDIS is at the CACHE, CACHE aside is the cashing strategy. There are several caching strategies, CACHE aside is just one of the most common but it's not the only one.

Next time we'll explore different caching strategies and why CACHE aside is not used by some companies at all

Many believe AI can write code, fix bugs, build features, and eventually replace software engineers. The reality is different. AI is an incredible co-pilot, but it doesn't understand users, business goals, or the trade-offs behind building great software.

Emmaculate Jane Akinyi Odhiambo — Wed, 15 Jul 2026 19:11:38 +0000

AI Won't Replace Great Engineers—It Will Amplify Them

Emmaculate Jane Akinyi Odhiambo — Wed, 15 Jul 2026 19:07:05 +0000

I came across this image today, and it perfectly captures one of the biggest misconceptions about AI in software development.

People often think AI can:

Write code.
Fix bugs.
Build entire features.
Replace software engineers.

The reality is different.

AI is an incredible coding partner, but it doesn't understand your users, your business goals, or the trade-offs that make a product successful. Those are still engineering decisions.

As developers, we are responsible for:

Breaking complex problems into manageable pieces.
Designing scalable and maintainable solutions.
Understanding context and user needs.
Testing edge cases and ensuring quality.
Collaborating with teams and stakeholders.
Taking ownership when things go wrong.

AI helps us move faster by handling repetitive tasks, generating boilerplate code, explaining unfamiliar concepts, and speeding up debugging. But shipping valuable software still requires human judgment.

I've found that the best results come when engineers and AI work together—not when one tries to replace the other.

The future belongs to developers who know how to think, not just how to type code.

AI is a multiplier. Your engineering mindset is the advantage.

💬 Discussion: What's one way AI has made you a better developer without replacing your role?

DEVCommunity #SoftwareEngineering #AI #Programming #Developers #Coding #ProductDevelopment #Tech #MachineLearning #BuildInPublic

Being a Full-stack Developer

Emmaculate Jane Akinyi Odhiambo — Fri, 05 Jun 2026 11:55:45 +0000

Let's be honest about what "Full-Stack" actually requires. 🧵

That fancy title covers FOUR completely different disciplines:

1️⃣ FrontEnd — HTML, CSS, JS + React/Vue/Angular
2️⃣ BackEnd — Node, Python, PHP + API design + Redis
3️⃣ Database — SQL (PostgreSQL/MySQL) + NoSQL + Message queues
4️⃣ DevOps — Docker, Kubernetes, AWS + CI/CD pipelines

That's not one skill. That's four careers in one job description.

So here's my advice:

→ Don't panic looking at the full list
→ Don't skip fundamentals to chase frameworks
→ Don't call yourself full-stack until you've shipped something real at each layer

Start with Frontend (HTML → CSS → JS → one framework).
Then Backend (one language, REST APIs, one database).
Then learn DevOps when you have something worth deploying.

The roadmap is real. The shortcut is not.

Save this. Come back to it in 6 months. You'll be surprised how far you've moved.

FullStackDeveloper #TechCareer #LearnToCode #BackEnd #FrontEnd #Database #DevOps

Who is a full-Stack Developer

Emmaculate Jane Akinyi Odhiambo — Fri, 05 Jun 2026 11:50:10 +0000

🚀 Everyone wants to be a "Full-Stack Developer" — but what does that actually mean?

Here's the honest breakdown:

💻 FrontEnd — What users SEE
→ Start with HTML, CSS & JavaScript (the holy trinity)
→ Then pick a framework: React, Vue, or Angular
→ Polish it with Material UI or Bootstrap

⚙️ BackEnd — What makes things WORK
→ Choose your language: Node.js, Python, PHP, or Ruby
→ Learn how APIs and server logic connect everything
→ Redis for caching — because speed matters

🗄️ DataBase — Where data LIVES
→ SQL first (MySQL, PostgreSQL) — this is non-negotiable
→ Then explore NoSQL: MongoDB, Cassandra, Elasticsearch
→ Message queues (Kafka, RabbitMQ) for scalable systems

☁️ DevOps — How code gets DEPLOYED
→ Learn Docker before Kubernetes
→ Pick a cloud: AWS, Azure, or GCP
→ Automate with Ansible, Chef, or Jenkins

The biggest mistake most developers make?
Trying to learn ALL of this at once.

Here's what actually works:
✅ Master one layer completely
✅ Build a real project with it
✅ Then move to the next layer

You don't need every tool on this list.
You need DEPTH in a few, and awareness of the rest.

That's what separates a real full-stack engineer from someone who just watched tutorials.

Which layer are you currently working on? Drop it below 👇

FullStack #WebDevelopment #Programming #SoftwareEngineering #DevOps #CareerGro

Productivity Booster

Emmaculate Jane Akinyi Odhiambo — Tue, 02 Jun 2026 08:49:38 +0000

Here are 5 simple things I started doing that completely changed my productivity:

The 20-Minute Rule for Being Stuck
If I cannot solve a bug or configuration error within 20 minutes, I stop guessing. I force myself to look at the official documentation, search the DEV Community, or ask a colleague. This saves hours of aimless troubleshooting.
Writing Down the Goal Before Coding
Before typing a single line of code, I write down exactly what I am trying to build in plain text. Having a clear roadmap prevents feature creep and keeps my pull requests small and focused.
Turning Off Non-Urgent Notifications
Context switching is a productivity killer. I close my email client and mute general chat channels for two blocks of 90 minutes each day. The uninterrupted focus allows me to enter a state of deep flow.
Reading Code, Not Just Writing It
Every week, I spend 30 minutes reading open-source repositories or pulling up code written by senior engineers on my team. Seeing how others structure their solutions expands my perspective.
Committing Small, Committing Often
Instead of waiting until the end of the day to make one massive commit, I commit every time a small sub-task works. It serves as a safety net and makes my Git history clean and easy to follow.

Simple Habits

Emmaculate Jane Akinyi Odhiambo — Tue, 26 May 2026 05:37:21 +0000

We often think that becoming a better software engineer requires mastering complex frameworks or algorithms. However, I found that the biggest improvements in my workflow came from tiny, daily habits.

Why go is great for beginners

Emmaculate Jane Akinyi Odhiambo — Mon, 18 May 2026 12:23:38 +0000

Go is one of the easiest programming languages for beginners to learn.

It has simple syntax, fast performance, and strong support for building modern applications. Many developers use Go for web development, APIs, and backend systems.

One thing beginners enjoy about Go is its readability. The code is clean and easier to understand compared to many other languages.

Go also helps developers learn important programming concepts like functions, loops, structs, and concurrency in a simple way.

If you are starting your programming journey, Go is a great language to explore.

I’m a software developer currently exploring Go, and I wanted my first project to be simple, fun, and practical. So I built a CLI tool that converts plain text into ASCII art—something like turning “Hello” into stylized text using characters.

Emmaculate Jane Akinyi Odhiambo — Wed, 06 May 2026 07:20:51 +0000