jssmith

I agree, I too found this barely readable.

Interestingly, ChatGPT was able to parse and explain it to me. I got a lot out of its presentation.

I get it. But I never would have until I built muscle memory for the keyboard shortcut.

I see JSON parse errors on occasion when using OpeanAI structured outputs that resolve upon retry. It seems it’s giving instructions to the LLM but validation is still up to the caller. Wondering if others see this too.

We've been focusing on indexing but query rewrites are probably next.

It looks like LLMs can do a pretty good job at generating ideas, particularly if you prompt them right.

After that, you have to: 1/ make sure that the SQL produces the same results, 2/ see what the query planner will actually do with it, 3/ see whether it improves performance.

As you point out, the data makes a difference, so you need production data statistics, at a minimum, to do this well.

Right. Why build another MCP server for Postgres?

There's a lot of value in just getting a database connection. But the LLMs hit limits pretty quickly when it comes to index tuning, etc.

Classical algorithms still have their place.

Confused about the new US tariffs? We built an interactive US Tariff Calculator—a simple tool to help you instantly calculate the new tariffs per country.

Fair enough. American companies (and people) definitely have a home bias. I guess to be constructive, I would suggest that perhaps there are parallels in your country.

I don't remember exactly how it broke the first time, but the cognitive overhead shows up in various places. E.g., start a new project, create a branch, then merge back to master... oh wait, it's main now? But then I'm back to an old project, or another person's project, so let me look up what name I need to be using, etc...

I want to share my own reactions to the name change since this is a really interesting topic. For context, I'm an African American, so many of my ancestors were slaves.

  - The first time it occurred to me that "master" in this context could offend anyone was when GitHub changed the name (and broke my workflow).
  - My immediate reaction was, "this change is by white people for white people," where "white" means anyone who isn't black.
  - My next reaction was, "they may be changing the name for the wrong reasons, but the change is brilliant."

Let me explain a little more. Whether motivated purely by virtue signaling or by more genuine intentions, changing the name doesn't fix any of the problems that black people face. The article explains this well.

What's powerful about this name change is that it pushes us to alter a habit, in my case one embedded deeply in my fingers, something that I do every day without realizing that I'm doing it. Thus it is a useful reminder of the implicit bias that contributes to the lack of diversity in tech. Never mind that the old name was harmless, the change brings repeated awareness to an important topic, and it reaches a the developer community in a targeted way.

So, next time you are annoyed that you have to fix a script or you accidentally type master when you needed to type main, please just take a deep breath, change the name, and remember to reflect upon whether you have are subconscious habits or biases that work against diversity in tech.

Yes, the idea is that the cloud provider should offer something like this. We intercepted system calls to simulate what it would look like.