Savadub.com

Some years back, I was filling a form on a $1.5B valuation text company which has become a unicorn as far back as 2021.

The company's service is to train and connect Software engineers with companies in the North America, and Western Europe, etc.

You know what?

Trying to submit the form on their website was showing me an error message saying "invalid email address".

Invalid email address for where? My goodness! This email is correct.

You know when you are filling a form on your mobile device, and you type the first few characters of your previously used email address, and your mobile keyboard auto-complete and you press/select the complete email address from the suggestion?

Yes, that's that's it.

But as a Developer myself, I already know what's up.

You know, I reviewed many codebases like this and checked many validation for edge cases like such.

What happened was that, their Engineers did not trim the extra spaces around the input value for the text form field.

Therefore, their app/website is seeing the extra space at the front of the email in the text box as a valid character, and their email field validation is throwing back the error.

I cleared the extra space and the form was submitted.

The point in this story is that most junior or mid-level engineers who have not been opportune to work with big firms always assume that once a company is big, then, they have the best engineers in the world, or that the engineers there can't make simple and obvious mistakes.

No. It doesn't work that way.

When you review your codes and find some small but avoidable bugs, and you are about doubting your own ability. Don't do that.

Own up the mistake, fix it, and take responsibility not to repeat such mistake another time.

If a $1.5B tech company that trains, interviews, and places Software engineers around the world can commit a subtle error of form field input validation, then it means you are not doing so bad.

And mind you, this is not making a case for irresponsibility or mediocrity. But I know you already get the point.

Code and ship responsibly.

__ If you need an experienced Software Engineer and Product Architect on your team for an amazing project, don't hesitate to send me a DM. __

Ige Fadele

__ I build and distribute quality and enterprise-grade software and digital solutions at scale. __

Software Engineers and Developers, please for God's sake, own every code you ship.

LLMs are not Compilers that will always produce binaries that do the same thing intended no matter how many times you give the same input.

Compilers are a product of many years of refinement. Also, they take in structured codes which follow already-standardized language as inputs. LLMs don't and will not.

Not now or later. As they are not designed to take such kind of input.

LLMs given the same input at different times and by different people will likely give different results at all times.

Natural language does not follow static rules like codes.

And there are more than 1000 ways to do one thing right, while there are more than 1000 ways to do same thing wrong.

Your LLM only choose one output from thousands of possible results it could produce based on the data it's trained on.

Don't forget, every code you ship is your liability.

Whatever comes up from up from it is your responsibility.

Own every single line of that code.

Inspect, verify, reactor/rewrite, own.

Take ownership, take responsibility.

Code and ship responsibly.

Have you checked our website recently?

Check it here: https://savadub.com

__ We build and distribute quality and enterprise-grade software and digital solutions at scale. __

Thinking we've all agreed that it is "Software Engineering"?

If yes.

Why are many not doing doing software as such?

There's a reason it's called Software Engineering..

However, many firms just want the software without taking the "engineering" part to heart.

We've walked away from projects and firms that refused to follow best practises and allowed software be done the way they should.

Because as an engineer in a firm with such culture, or as a leader who is outnumbered with stakeholders who do not believe in doing things the way they are meant to be for the best results...

It's just a matter of time before you burn out and get dragged into the debts which the outcomes of bad engineering related decisions caused, or even get blamed or overworked for the negative results.

It's good to ship fasts, it's good to move quickly, it's good to meet deadlines and surpass milestones, BUT at what cost?

The technical debts never go away. You will pay for it for sure.

And when the debts need to be cleared, you will pay more than you owed.

So, why not do it the right way.

This is not a shift towards absolute perfectionism. No, it's not.

It's just getting things done properly.

==> If you are an engineering agency that builds for clients.

Your clients will thank you for the quality delivery if you do it the way it's supposed to be done. Although many may never realize how much they owe you for the work until later.

And even if they never realize, that has nothing on you. Excellence compounds.

==> If you are in a firm that builds your own products, especially product-led firms.

Know that you are paying it forward. Sooner or later, the ROI will amaze you.

--------

What has been your experience with firms or teams or leaders who insist on shipping fast and clearing serious debts later, even when you know the request will lead to duct-taping the software to be released?

---------

Excellence compounds.

The more you do it, the more you can't do it in no other way.

Mediocre delivery will start irritating you.

__Working on product/software and needs help, or you are planning starting one and needs help? Send us a DM.__

Ige Fadele.

== We build and distribute quality and enterprise-grade software and digital products at scale. ==

The latest request for startups by YC (Y Combinator) for 2026 has some valuable info for builders across different economy and verticals.

_________

==> For thesis 2.

When we were building Social2Blog: stb.savadub(dot)com; our philosophy aligns with that thesis 2. (replace (dot) with . )

We understand the problem and could solve it in the most efficient way possible. So we built the tool and infrastructure and AI tool needed to get the cost down drastically.

However, we still allow those users/clients who believe they could handle the service part of the work to do it on their own while utilizing our infrastructure and tool.

_______

==> On the thesis 6.

This aligns with our philosophy for building Savv Web Framework: savv.savadub(dot)com. (replace (dot) with . )

Savv provides the best solid foundation which follow the best engineering practices needed for business websites and web apps on the PHP ecosystem.

Anyone could vibecode his interfaces, pages, etc., and drop the files in the /views/pages folder/directory, and the website will be up without any stress or configuration.

Out of the box, the website/app will have readymade PWA, SSG-feel, lightning fast and highly performant.

-----------

__Building an amazing solution that forward-driven? Let's connect. Send me us a DM__

Ige Fadele

Cutting Cloud Costs Starts with Code

Product-led businesses and those relying on cloud-based internal tools often overpay for infrastructure.

While it is tempting to tune the cloud settings first, real savings begin with the software itself.

We all know that most Cloud providers bill based on what we consume: data transfer, CPU, and RAM.

To lower the bill, you must optimize the logic.

===== Key areas to audit:

- Stack Selection: Ensure you are using the right language for the specific task; performance varies significantly across stacks.

- Data Efficiency: Minimize payload sizes between clients and APIs to reduce transfer costs.

- Process Health: Refactor long-running processes to execute more efficiently and consume fewer resources.

Seriously, we advice you optimize what you deploy before you scale the platform.

Need an engineering firm or team that has delivered high-stakes solutions to audit your system, send us a DM.