loader image

My Thoughts. Unfiltered. 💭

Love to get notified every time I make a post?

Subscribe to My Thoughts

Here, I share my perspectives on technology, creativity, and life’s intricate struggles, weaving insights from my standpoint as a designer. Welcome to My Thoughts — My personal canvas for thoughts that inspire, inform, and connect. 

Please enable JavaScript in your browser to complete this form.
(3 weeks ago)

Every time I make a Facebook post advocating no-code web design, some people immediately (and wrongly) interpret it as me suggesting that developers who code are irrelevant. In reality, for every successful no-code entrepreneur, there’s an army of brilliant developers you’ll never see on LinkedIn or Facebook celebrating their latest client win. Some of them are even unpaid and do it voluntarily.

While we celebrate the rise of no-code web designers making $8K/month with Elementor sites, I would like to honor and shed light on those who made all these possible. I am not talking about the WordPress + Elementor merchants like myself, I am actually referring to the software developers who wrote and maintain the codes that power these no-code tools. Without them, we probably won’t be having a no-code conversation.

1. The WordPress Core Contributors: These guys maintained the engine that powers 43% of the web. They have commited their lives to backward compatibility, security patches, and seamless updates has created the most stable foundation for millions of no-code infrastructure.

2. The Elementor Development Team: 1 in every 8-11 websites is designed with Elementor. The Elementor team didn’t just build a page builder, they re-engineered the world’s most famous visual programming language, the drag-and-drop.

Their drag-and-drop interface translates design intentions into clean, performant code that rivals hand-coded websites. The widget ecosystem that they’ve created has given non-coders superpowers. And the clean structure have helped Indie Elementor Developers like WPMET to take web development to the next level.

I eagerly anticipate the formal launch of the Elementor V4 Editor (Currently in Alpha). That will completely slap critics like the african star apple, and give Elementor even more strides. I am monitoring the progress with so much enthusiasm.

3. The Crocoblock Innovators: These people started as a small group in Ukraine in 2018. They saw the gap between static designs and dynamic web applications.

They built JetEngine, a formidable Elementor Pro companion, JetSmartFilters, and dynamic content widgets, have all made it possible for no-code creators to build sophisticated, database-driven websites that would have required full-stack development just years ago.

4. The Security Guards: These comprise the Plugin Security Researchers. They fish out and patch security vulnerabilities. has protected millions of websites from exploitation.

Software like Wordfence, Sucuri, Virus Total have contributed immensely to penetration testing and security audits that have made WordPress a trustworthy platforms, secure enough for businesses and governmental organizations like the WhiteHouse, and the NASA to bet their futures on.

To the WordPress Core Security Team: Your proactive approach to threat detection, your security hardening guidelines, and your rapid response to emerging threats have created an ecosystem where entrepreneurs can sleep peacefully, knowing their sites are almost always protected (unless they opt out of auto-update).

5. The Problem Solvers

These are the plugin developers who asked “What If?”:

What if designers could create custom post types and taxonomies visually?
What if form building didn’t require backend knowledge?
What if e-commerce could be as simple as drag-and-drop?
What if animations and interactions could be added without JavaScript?

Your “what ifs” became the tools that democratized web development.

6. The Accessibility Champions

These are the empathetic developers who code for inclusion. They have successfully ensured that no-code tools generate accessible markup code by default.

Their commitment to semantic HTML, ARIA attributes, and keyboard navigation means that when someone builds their first website with Elementor, it’s already more accessible than many hand-coded sites.

7. The Performance Engineers made it possible for visual builders to generate clean, fast-loading code.

For every web builder plugin for WordPress, there is a small segment of their user base that push the developers to prioritize performance whilst still providing enough features such as GSAP integration, etc. For example, a recent uprising among a section of we Elementor users, caused the Elementor Devs to go back to the drawing board to develop the new Elementor V4 Editor, which would soon be released in Beta. It features true class-based web development, a far more robust responsive capabilities, whilst still ensuring that performance is noticeably increased by stripping off unnecessary markups in the HTML source code.

Over the years, Elementor has put efforts in optimization by working on performance-focused feautures like lazy loading, widget-specific caching settings, DOM optimization,and image optimizations. All these to ensure that no-code doesn’t have to mean slow code.

8. The Bridge Builders: These set of devs didn’t just build tools, they build bridges.

Bridges between technical possibility and creative vision.
Between complex code and simple interfaces.
Between the developer shortage and business needs.

Their APIs, hooks, and extensible architectures mean that when no-code hits its limits, there’s always a path forward.

Zapier, n8n, Make. Thank you.

You have created the perfect symbiosis for web automations to extend beyond writing cron jobs, and beyond the limits of WordPress functions. You have empowered non-coders while keeping the door open for developers to extend and enhance.

Coders are the Real MVPs, not no-coders. While no-code web designers and entrepreneurs showcase their success stories, the coders are already debugging compatibility issues across thousands of hosting environments in preparation for the next no-code software version.

They must also write documentation that turns confusion into clarity. They responding to support tickets in the WordPress Plugin Support community at odd hours, and they refactor legacy code to support new features.

This post is a “Thank You note” that’s long overdue. The no-code revolution didn’t happen because coding became irrelevant. It happened because brilliant developers made their expertise accessible to everyone else.

You’ve proven that the highest form of technical skill isn’t writing complex code but abstracting the complexities, so others can focus on solving the real-life problems.

Every success story in the no-code space is built on your shoulders. Every entrepreneur who escaped the traditional gatekeeping of web development owes their freedom to your code.

The future of web development isn’t no-code vs. code. It’s the beautiful collaboration between those who build the tools and those who use them to build their dreams.

These are my thoughts!

What’s your Reaction?
0
0
4
0
0
(1 month ago)

Let’s be honest, owning a car in Nigeria is a different flex on its own, but I have always overanalyzed the inconveniences and cons of owning one, even before I got mine.

Guess what? It manifested on me.

As a creative designer who mostly works from home, I never had the need to purchase a car, except for one reason: Family.

At the time, I had two kids and a wife, so owning a car would ease both casual and mission-critical movements such as when I urgently had to drive my wife to the maternity hospital in the middle of the night.

I was rightly nudged to get a car, so I sold one of my side projects which I no longer had interest in running for about $4,000 USD, and spent nearly all of the money on acquiring my first car.

I got the car, parked it in my compound, and started taking driving lessons in a licensed driving school, meaning that I bought the car before I even learnt how to drive.

The car was a Nigerian-used Toyota Corolla CE 2004. I was escorted to the lot by my dad, who also assisted in inspecting it. It was such an accomplishing moment. Even though it was a 20-year old car, I could see the glee in my dad’s eyes as I finalized payments with the dealer.

I observed the peeling steering wheel and the split-open airbag, but “it’s a Toyota, it can be fixed”… Which I eventually did. I was also excited about the prospects of driving a car around the streets which I used to trek on.

For the first few weeks, things were smooth, but I did some quick interior revamps. I quickly fixed the airbags, and replaced the steering wheel. A simple steering wheel replacement procedure eventually turned out to be a two-day work and that’s due to rust, which made it impossible to separate the wheel from the steering column. I was told I need to replace that too, which I did.

I also installed an android-powered touchscreen infotainment in place of the old-school FM Radio module.

But the honeymoon phase started going away. The first thing I noticed was the car randomly tripping off while in motion. But each time I start it, it starts and I would normally be able to continue with my journey. According to the auto-electrician, he said it was a fuse issue. I paid him to get it sorted, but the issue persists, although now less frequently. I was ultimately able to get rid of this problem after paying for a full fuse box revamp, and I think that solved the problem.

Since then, it’s been one issue or the other. Below are a list of expensive problems I have had to deal with since I started using the car;

  1. Fixed its Engine thrice
  2. Replaced fuel pump
  3. Replaced Two Brake Drums
  4. Repaired its Gear Box
  5. Fixed its kick starter
  6. Replaced the rectifier in the alternator because the alternator randomly fails to charge the battery.
  7. Fixed wiring issues related to fuel delivery.
  8. Replaced all sorts of sensors on it, from Shock sensor to O2 Sensor.
  9. Replaced the coils
  10. Fixed the windshied water spray mechanism
  11. Tyres (2 Sets)
  12. Catalytic Converter

And here I things I purchased to customize and reflect my love for the car

  1. An Android-powered infotainment screen
  2. Pairs of custom windshied vinyl stickers
  3. Sporty boot spoiler
  4. Sporty front grille

The car, which was supposed to be a convenience, quickly turned into the biggest productivity guzzler I’ve ever known. It ended up becoming the most demanding client I’ve ever had. Could it be due to dishonest and poor mechanics? Almost certainly, could it be due to its mileage? Maybe.

But one thing is for sure; My most productive moments were when I had no car. I did not have to worry about Federal Road Safety Commision officers on the road sides, Fire extinguisher expiring in the boot without my knowledge, fixing appointments with mechanics, panelbeaters, gear masters, and auto-electricians instead of building websites and creating designs, car stalling in the middle of nowhere, dealing with dubious mechanics, and worrying about flood water. The list goes on and on.

I was comming back from work when my car started smelling like burnt oil. When I checked, it was oil leaking from one of the spark plugs. My car kept stalling every five minutes under the heavy rain. As I got close to my house, it totally stopped working. It cranks faintly and won’t start.

I called one of the mechanics I have previously worked with to come check it. He fixed it and I was able to drive it home. The mechanic came the following morning to try to get the issue permanently fixed, and got me to spend over 100K on that day. After he was done fixing it, the car was worse than before. It kept shaking vigorously while working, especially when I apply brakes when the gear is in Drive.

That was the last straw that broke the camel’s back. I decided to abandon the car and focus on myself.

I still love my Corolla 2004 because it taught me so much about how cars work, but sometimes, you have to use logic and not emotions.

I haven’t felt the urge to get it repaired for the umpteeth time, since I am always working from home 98% of the time.

I am not eager to buy another car because the truth remains that you are still likely to run into a bad mechanic that would ruin everything for both you and your car.

I hate owning cars at this point in my life, but I can’t talk enough about how much I do to incompetent mechanics and technicians who exist to worsen every situation.

A naija used car can either be a tool or a trap. For me, it became the latter until I reclaimed my time. My lovely 2004 Corolla is now enjoying a well-deserved rest. And me? I’m back to hiting my big strides like I used to. I now have the concentration to focus on work that matters, release more course videos for my students, and hit targeted deadlines for clients’ projects

I’ll buy another car once I find a rightly priced and dependable workhorse I can count on all the time and I believe that my experience would be valuable in assessing my next one.

Thanks for reading!

    What’s your Reaction?
    7
    8
    30
    3
    7
    (2 months ago)

    Learning web development used to be fun until around 2015/2016, when the curse, known as JavaScript frameworks, and framework-esque frontend libraries like ReactJS began gaining traction.

    Google had earlier created AngularJS in 2009 and released it in 2010, but in 2016, Google released a complete rewrite of the AngularJS Framework. This led to breaking changes and a complete approach to how things are done. There was no backward compatibility and developers had to relearn a lot of fundamental concepts in order to keep up with this new change.

    Fastforward to the year 2025, we now have over a hundred of these JS Frameworks and Frontend Libraries.

    Web development stopped being about building websites to solve actual problems, but started being about chasing frameworks to solve the problem the previous version of a framework introduced.

    You know the saddest part? These changes are often breaking changes, and are not cross-compatible with the legacy versions of the same Framework. Another sad aspect is the very short duration between these updates.

    A new JavaScript tool drops. It’s smaller, faster, and claims to fix everything that came before it. Devs rush in. Blogs are written. Tutorials go live. Talks are given. And companies? They hesitate because they have real users and production apps that need to stay up.

    Before you know it, the same tool that promised simplicity increasingly becomes more complex, grows in dependencies, and breaking changes starts to creep in.

    It starts looking like the exact thing it tried to replace. The hype fades. Another one enters the scene. The cycle repeats.

    Even Vue, which I once thought was the sane alternative, eventually gave in. Vue 3 brought a new API, broke a lot of things from Vue 2, and made teams rewrite or relearn just to keep up. And that’s if the libraries their project depended on even survives the upgrade.

    Developers now spend more time jumping from one tool to the next than building real things. They know a bit of everything and master nothing. The focus has shifted from solving actual problems to keeping up appearances in a fast-moving ecosystem.

    We don’t need more frameworks. Lets learn a thing or two from the evolution of HTML, CSS and Vanilla Javascript.

    If that sounds boring, maybe boring is what we need.

    Javascript Frameworks were a curse to website development.

    What’s your Reaction?
    0
    5
    1
    2
    2
    What’s your Reaction?
    0
    0
    1
    0
    0