I expect getting the SQL autocompletion behaving decently, in all conditions, is going to take a lot of time, and a lot of trial and error.

Efficiently collecting data changes for the very low-bandwidth distributed replication scenarios.

Writing a complex thing these days, so I thought of the process. Painting came to mind, which triggered memories of and old book, and here we are.

Diving into the hashing stage of our hash-based database comparison and replication.

Copying huge databases when bandwidth is small requires creative solutions.

YAGNI (you ain't gonna need it) principle is one of my favorites.

The way you price your offering is closely related to how people perceive your company and the offering. Impacting that perception allows you to change the pricing as well.

An unexpected event pulls you down. Was can be done to prepare for this?

My first successful product was built under huge time constraints (I had just a few hours a day, mostly late night) while I was under extreme pressures. So I built a minimal things that solves the problem. Turns out I forgot about that recipe once I had a lot of time to "build things right".

With databases powering practically every business in developed countries, one would expect tooling to be state of the art. There are a ton of tools, but state of the art?

What is so special about SQL? Why is it harder to parse and analyze compared to the other mainstream languages?

Source code is just a text. Transforming that text into a structured format needed for software to understand what is written is called parsing.

For those ready to ignore all the rules and go very low-level, the ultimate performance is the ultimate reward.

Certain database engines provide sanctioned ways to notify of changes to the data. That's better than polling or manual trigger creation.

In this short series of database replication techniques, we already covered polling for changes. If we are fine with attaching triggers on our tables, we can get much better response time.

Polling for changes in a database is a simple, but inefficient form of change data capture. For many database types, though, it's the only form available.

Efficiently capturing changes on a database and mirroring those changes in another database is called change data capture.

What can a self-funded company do when competitors are much larger and infinitely better funded?

Many of us are die-hard bootstrappers, proud of shouldering everything themselves. One gets to choose a quality of life, but there is a high probability the price will be paid in tempo and reach.

To get the most out of conferences you attend, you will need to step out of your comfort zone. This is good for you in several ways.

Choosing a wrong pricing model can rob you of the success needed to bring your product to its full potential.

A little bit of due diligence goes a long way. Most startups fail and most failures are due to building the wrong thing.

Perhaps you can do better on your own. But, perhaps, it's not a wise choice.