How Frameworks and Libraries Changed the Way I Build Software

Knowing how to code is not enough you need to learn how to deliver more value with less

Back in college, I used to think that a “real” programmer built everything from scratch.

If you didn’t write every line of code yourself, it somehow didn’t count.

That, I believed, was what proved mastery.

But once I joined a professional development team, that belief quickly disappeared.

In the real world, time is money.

The longer it takes to build something, the more it costs — not just in hours, but in missed opportunities.

The goal isn’t to reinvent the wheel. It’s to deliver value efficiently.

Frameworks Don’t Make You Less of a Developer

Using frameworks and libraries doesn’t mean you don’t understand technology — it means you know how to leverage it.

You’re standing on the shoulders of those who’ve already solved the same problems, so you can move faster and focus on what truly matters.

Of course, understanding what’s happening under the hood is still important.

That knowledge helps you debug, optimize, and maintain your applications when things inevitably go wrong.

My First Encounter with Frameworks

In my early days as a developer, I worked with Angular, Ionic, and the Slim Microframework.

Before frameworks like Angular, we used to manipulate the DOM manually with plain JavaScript — a tedious, repetitive process that made codebases messy and hard to maintain.

Then came jQuery, which simplified DOM manipulation but still required us to manage everything by hand.

Modern frameworks like Angular, React, and Vue changed the game completely.

They abstracted away low-level DOM operations and introduced declarative programming — a mindset shift where we define what the UI should look like, not how to build it step by step.

Now, when the state changes, the UI updates automatically.

Without these frameworks, it would be much harder to build highly interactive web applications. Time that should be spent developing important features would instead be consumed by managing DOM manipulation — something that can be eliminated in the first place.

Building Once, Deploying Everywhere

Another example of a framework that sped up our development is Ionic.

It opened my eyes to hybrid app development.

Instead of writing separate codebases for iOS (Swift), Android (Kotlin/Java), and the web (JavaScript), we could build a single application that runs on all platforms.

From a business perspective, that meant faster delivery and lower costs — without sacrificing user experience.

Without Ionic, we would need to build multiple versions of the same application for different platforms.

Of course, there are many other frameworks and libraries you can use aside from the ones mentioned here to speed up solution delivery. Don’t hesitate to take advantage of them.

The Takeaway

Frameworks and libraries aren’t shortcuts — they’re accelerators.

They let developers focus on problem-solving rather than rebuilding solutions that already exist.

Looking back, frameworks didn’t make me less of a developer — they made me a more efficient one.

And that’s what real-world engineering is all about: building smarter, not slower.