Mission/Vision

We, Tool Builders

We, as in we humans, are tool builders. We build tools with tools built with tools. The age of computing has taken this to a whole new level. Which tools are used can make or break software development, in terms of progress (translating into costs) but also of simply enjoying the process itself.

Love For The Craft

As they say, 'Easy reading is damn hard writing'. Building something well takes effort and to go beyond takes a vision. But that is also where my job satisfaction comes into play.

I am a solid backend developer, specializing in .NET and SQL databases. That is where I shine.

After being in the business of software engineering for over 25 years I have increasingly fostered good, clean, lean, elegant coding. Because apart from being useful, good code can read like a well-constructed story that can be aesthetically pleasing as well as functional. I like to read.

The Real World

Yes, I am mindful of budgetary and time constraints with software projects. Still, I strive for code to do more than 'just work', because I know from experience that (too much) lazy, sloppy, short-cutty code will bog down a project until it eventually can't go any further. That scenario is not just sad and frustrating, it's expensive as well.

Enduring Problems

I have seen, time and time again, the classic software engineering problems involved with combining middle-tier code with SQL databases remain unresolved in established frameworks and tools. Problems such as...

In my opinion, no industry-standard comprehensive set of .NET SQL database tools exists that addresses these issues fully in a unified manner, satisfactory and development-friendly.

What I see in the options available for .NET backend development is that too much compromises have to be made, to good coding and/or efficiency. This manifests in different ways; the 'N + 1 problem' for example. But more broadly speaking I see the problem in that the richness of relational database is left unused. The keyword being 'relational'. In my opinion tools too often reduce a database to a set of stand-alone tables, greatly diminishing the 'more than the sum of its parts' aspect of the database.

On top of that, the available tools have become bloated.

This process can not semi-haphazardly 'Jenga' on forever, not without mounting costs in performance and complexity anyway. This situation has got to get better, and not just incrementally.

My Goal

I want us to move past the current, disappointing status quo.

What I aim for, in a mix that is both 'professional' as 'personal', is to increase the quality of what is functionally needed by increasing what is enjoyably good. Thus setting the stage for a positive feedback loop.

This means staying closer to the spirit of the database, and in doing so remain much more SQL intuitive. It means honoring the richness of the relational database.

What It All Adds Up To

And so I decided to go back to the drawing board, back to a blank slate, and build from the ground up, to address those aforementioned problems responsibly once and for all. I set out to make a suite of tools I would like to use myself, and I feel that every honest coder deserves. I decided to build a unified tool set... WYSE!