Exponential Growth: The reason I spent 7 years building tools.

It may seem silly to some that I have spent the better part of a decade building tools. After all, there are several tools out there already!

Some do this, some do that. Some do things well. Some ultimately do more harm than good.

There are hundreds of things that a software may need to work. Almost every one of these things require a large degree of redundancy to accomplish – logic that is repeated over and over, with little variations.

In the beginning, I too did this same thing: repeated my logic in varying forms across different pieces of code. Most developers do – especially in the beginning (both early in their careers and when starting a new project).

There’s nothing really fundamentally wrong with this approach – in fact it’s more cost efficient in the short term, so long as it’s a smallish one-off project ( or where the developer knows they won’t have to worry about future maintenance because it’s the clients problem ).

In recent years, there have been a slew of open-source codes offering to solve some problem or another. A lot of developers just sling together from existing code: so long as it mostly works, who cares right?

That attitude has caused (likely tens of) millions of headaches

    for you, the user, and whoever has to clean up this mess.

That’s why I’ve spent 1000s of hours developing my own ecosystem from the ground up! I don’t have to worry about this fatal flaw or that dependency issue: I attach and go!

I don’t have to spend countless hours scouring the web, comparing the pros and cons of existing “solutions”, learning to get the software to work with me (through usually vague documentation that requires going into the source code to see what’s going on).

I don’t have to do any of that!

    though I still do because it makes me a more informed developer

When you cut corners, it costs. You may even be paying full price – or several times fair market value – and it costs you even more because you are paying for one thing and receiving another!

That’s loss. Even worse, exponential loss, because you have to invest in it then either chuck the project or try to salvage it, which costs even more than you’ve already paid – possibly (and likely, depending on the severity of the damage) several times more.

Don’t lose! Win!

If it takes a developer one hour to complete a task and it takes me 15 minutes to do the same task better, that, my friends, is an exponential win.

The benefit for you also increases exponentially – it means:
    1) you’re charged less
    2) you can afford to do more
    3) you can show off your new goods faster
    4) you can do more faster

It also comes with another factor that’s harder to determine: How much will this cost me in the future?

When you’re with me from the start, you can be sure that if you decide to make changes in the future those changes will come with the same level of quality and scalability!

#[a What if I have an existing project? ]

It’s hard to gauge just how much of an increase value you’ll receive if you choose me over that other guy, but I can guarantee you this:

The difference is night and day.