PostgreSQL in action with Opensearch (2026-10-23)

• PostgreSQL in action with Opensearch
• How to run PostgreSQL in Docker
• From the SQL Server Central Blogs - Power BI Fun With Travels
• From the SQL Server Central Blogs - The flight recorder: Replaying what an AI agent did on my SQL Server
• Delta Lake: The Definitive Guide: Modern Data Lakehouse Architectures with Data Lakes

• DML Trigger Types

Choose the Second One

I wonder if any of you have ever tried this. When faced with a problem, think of a solution using whatever comes to mind. For most of us in the data space, this is a SQL-based solution, hopefully a set-based on for MSSQL. For Oracle, you might approach things differently. In any case, solve the problem.

Then force yourself to imagine that you weren't allowed to implement the first idea for some reason. No funding, no time, whatever the reason, you can't implement it. Maybe it's your team hates your ideas and just won't approve the PR.

Now, come up with a second idea. Something new and different. This might be harder in the data space with SQL than in application programming (C#, Java, etc.), but the idea is expressed in A Philosophy of Software Design by John Ousterhout. It's how he has often taught his software design course at Stanford. His approach is to force students to think more deeply about their design, and he often finds that they build a better system the second time.

Hard to do, but arguably a good idea. He talks about this in this podcast with the Pragmatic Engineer, and how many smart people underperform when building their software. He says it doesn't necessarily take more time to do this twice, which I am skeptical of. This might be easier for students, but in the real world, is it even practical? Often we're not working on very hard problems; we're working to implement something that needs to get done, and often isn't that well-defined. In fact, many of the things I find developers are asked to build things that either aren't well thought through or are relatively trivial. There might not be a good second solution for a lot of vague ideas whose value is unclear.

I do think that often we go down a path that quickly becomes complex. Engineers will start to overcomplicate things, so perhaps slowing down, spending a short period of time thinking of a second solution, debating another approach with others is worth a little time. Maybe you wouldn't implement it, but at least think it through and game out the approach with pseudocode.

I haven't run into anyone who approaches software this way on a regular basis, but if you do it, let me know. If you think it's a good idea, maybe it's worth trying at the beginning of the next sprint when you tackle a new design requirement.

Steve Jones - SSC Editor

Join the debate, and respond to today's editorial on the forums

sabyda from SQLServerCentral

Learn about using Opensearch with PostgreSQL to improve performance and quickly return results to your users.

Additional Articles from SimpleTalk

Get PostgreSQL running in Docker in minutes with this step-by-step setup guide. Learn to pull the image and run a container

Steve Jones - SSC Editor from The Voice of the DBA

I’m back from a great vacation. I had the chance to visit two new countries (for me and my wife) and many new cities as we cruised around the...

BLOB EATER from All About SQL

“What exactly did it do on my server?” is the first question a DBA should ask about any AI agent. AgentDBA answers it from its own records: every decision...

Site Owners from SQLServerCentral

Ready to simplify the process of building data lakehouses and data pipelines at scale? In this practical guide, learn how Delta Lake is helping data engineers, data scientists, and data analysts overcome key data reliability challenges with modern data engineering and management techniques.

Today's question (by Steve Jones - SSC Editor):

Think you know the answer? Click here, and find out if you are right.

Here's a few of the new posts today on the forums. To see more, visit the forums.