Claude AI Convinced Me Not to Build an iPad App

Posted on February 9, 2026 by way0utwest

I coach volleyball and I do a lot of stat stuff on paper. I decided recently to see if I could find a way to more easily automate things. I’ve tried a few apps on the iPad, but they all have too many restrictions and they are hard to use in the heat of the moment. Paper and pencil have been simple, reliable, and they let me fix something easily.

However.

Paper takes some focus, and it’s hard to quickly summarize things. I wanted to make my own app, and Claude convinced me not to do this.

Read on.

This is part of a series of experiments with AI systems.

A Simple Prompt

I’ve been kicking this around, but I never seem to have time. Listening to podcasts, reading articles, and seeing other experiments is slowly getting me to just try things. I started with this prompt, intending to give this 10 minutes out of my day.

how hard is it to build an app for an ipad

I know some of the answers, but you can look at the image below for what Claude gave me.

2026-01_0335

I like the conversational nature of this, so I answered with this:

a simple app to track some data entry. Can you build an app for an iPad?

I was just looking for help in my thought process here and trying to scope the work. I’m sure Claude Code could knock this out, but I’m experimenting. This was Claude’s response.

2026-01_0337

That’s great news. I don’t need a native app, and in fact, that’s likely a lot of overhead registering on a store or playing the sideload game, sending updates slowly, etc. With cloud file sync, I could easily have this data available elsewhere anyway.

This is the type of advice I’d get from some friends. Others would relish the chance to build an app and make this more complex. I’ve certainly seen some other Vb coaches on FB create complex systems.

My answer:

volleyball stats. Display a list of players in a 4×3 grid, like the image. Each player’s name is customizable. A date, goal, and time can be entered. For each player, display 4 buttons: 0,1,2,3 which are used to rate a pass. There should be a real time calculation of the average pass score for a player (sum of items/ attempts). Save this to a text file with the datetime data entry was completed.

I meant to upload the image below, but forgot. For context, I print this out and then as kids pass balls, I write 0, 1, 2, 3 for each pass. After we’re done (usually xx passes or time), I quickly compute an average. You can see below, Eliza gets a 3 and Ella gets a 2.

2026-01_0334

That takes time, so I wondered what Claude would say. This is the response, which took about 5 minutes.

2026-01_0338

I downloaded the file and opened it and saw this, or most of this. I updated the player names and they’re saved in the HTML.

2026-01_0339

I can click around and it logs attempts and calculates an average in real time. If I download the data, I get a text report of what happened.

If you want to try it yourself, look in my repo: https://github.com/way0utwest/AIExperiments/tree/main/VolleyballPassingStats

I asked for a few changes, and then I asked for a log of the session. That’s the readme in the repo.

To me, this was something I’ve put off for a few years, not wanting to get caught up in a project like this when I could easily just use paper.

Now I have a new toy that I’ll use at the next practice. Plus, I’ve amazed myself at how  easy this was.

Be curious, try things, ask for help on a task or project you’ve put off. GenAI is amazing.

Other AIs

I tried this on a local Gemma3 model and it was very slow and produced a single entry box. to me, this wasn’t worth the time or effort.

I tried this in Copilot (in VS Code) with the Sonnet model, and it wanted to make me an xCode app right away with a SwiftUI. I could get it to produce something like what I got below, but it wasn’t as helpful as Claude.

Video Walkthrough

You can see some of this live in this video.

Posted in Blog | Tagged , , | 2 Comments

When SQL Server Central Went Down

Posted on February 6, 2026 by way0utwest

This is part of a few memories from the founders of SQL Server Central, celebrating 25 years of operation this month.

“The site is down.”

I got a phone call from one of the other founders around 9 am in Denver one day. At the time, I was working at a small startup, in a semi-private office with one other person. Most of the company knew I had a site on the side, and alternately cheered me on or celebrated hiccups, depending on the person.

I checked, and things were down. I had a side channel to telnet into the server, but couldn’t access things. At this time, the site was hosted on a single server, running IIS and SQL Server, in a friend’s basement. This was in 2002 or 2003, and broadband was a lot different then. No cable internet, and most other solutions were in the kbps range. I had ISDN at my house, but a friend had gotten into a trial from Sprint, giving him 3Mbps over a microwave link.

My office-mate was listening and watching. I said I was taking an early, and long, lunch. She chuckled and went back to her own tasks. I let my boss know and started driving, stressed out. After all, the site was growing, popular, and downtime could be a killer.

We’ve had a few outages over the years, but not many. This was one of the more stressful ones as I fought traffic on I-25, trying to get from the Denver Tech Center up to Westminster. I can’t remember the weather, but I was sweating when I got to my friend’s house. This was the before-times, when remote work was a rarity. Luckily, my friend had left me a key to get into his house, where I ran into the basement. Unable to get the server to respond, I rebooted it and crossed my fingers.

I’m sure a few of you have had the stressed-out feeling of waiting for a database server to restart, hoping that it comes back up cleanly. It did this time, and I don’t remember what went wrong, but things were back up and running with no major issues. I was probably in the basement for less than 30 minutes, and I left, dreading the long drive back to the office. Almost two hours driving for a 30-minute fix.

I do remember thinking if this was going to be a regular occurrence, I might need a new job. Or a new place to host the server.

We weren’t in the basement for too long. Revenues were increasing enough that I started to look at co-location facilities. My current employer had investigated quite a few when we set up our systems, and I reached out to a few contacts. I negotiated a half-rack at some point, moving our servers to a real facility. By that time, my employer had failed, and I got an F5 firewall as part of my severance, which fronted SQL Server Central for quite a few years.

Those were the days, with lots of CLI access to remote systems and a power strip where I could cycle them off and on. Those were skills I had to learn to avoid more drives at inconvenient times.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged | Comments Off on When SQL Server Central Went Down

A New Word: Dolorblindness

Posted on February 6, 2026 by way0utwest

dolorblindness – n. the frustration that you’ll never be able to understand another person’s pain, only ever searching their face for some faint evocation of it, then rifling through your own experiences for some slapdash comparison, wishing you could tell them truthfully, “I know exactly how you feel.”

I’ve been lucky and blessed in life, with many things going my way and relatively few big obstables or painful moments. I’ve had some, but many less than a lot of people I know. I’ve also had plenty of success (by my definition) in life.

As a result, I think I run into dolorblindness regularly when I run into someone that’s had a difficult event. Losing a loved one, dealing with a health crisis, losing their job, or some other event that creates a lot of pain in individuals. I feel empathy and sadness for them, but I’m often struggling to understand the feelings because I haven’t felt them.

Most of the time.

I often won’t say that I understand because I don’t. Sometimes I do, but often I express support, offer help, or just give them a hug.

Whether you really know how someone feels or are experiencing dolorblindness, I hope you be kind, have compassion, and support those struggling in life.

From the Dictionary of Obscure Sorrows

Posted in Blog | Tagged , | Comments Off on A New Word: Dolorblindness

Expensive CPUs

Posted on February 4, 2026 by way0utwest

There have been a lot of features added to the SQL Server platform over the years. Several of these features let us perform functions that are beyond what a database has traditionally been designed to handle. SQL Server has had the ability to send emails,  execute Python/R/etc. code, and in SQL Server 2025, we can call REST endpoints.

Quite a few of these features (arguably) are more application-oriented than database-oriented. There’s nothing inherently wrong with having a server perform some of these functions, and there have been some very creative implementations using these features. I recently ran into one of these examples from Amy Abel, where she shows how to use the new REST endpoint feature to call an AI LLM to generate and send emails from your database server. That’s creative, and it’s reminiscent of the numerous examples from various experts over the years who demonstrate how these features can be used to accomplish a task.

However, these are examples. They work amazingly well with one user running a limited workload. This reminds me of many of the examples I’ve seen using the AI vector enhancement in SQL Server 2025 to create embeddings from string data using an LLM. That is interesting, but most of the examples show a trigger being used to update the encodings. Imagine users updating data and those triggers firing. Imagine a real workload and how often your users might update string data you want to use in an AI application, especially a RAG application. Think about how complex or long-running triggers in your applications now that can overload your system.

CPUs in database servers are expensive. The hardware isn’t more expensive, but the software is pricey. Standard Edition is limited to 24 or 32 cores (depending on version), and while Enterprise isn’t limited to any number of cores, the cost of each core is $$$$. Is it worth having those $$$$ cores sending emails or calling external services? Or would you be better offloading those calls to another server, like an app server, where the cost of the core is the hardware and a little .NET code running separately?

Many of us already struggle with the database server as a bottleneck for our application and workload. Scaling up our database systems is expensive and cumbersome. We struggle to get approval for larger VMs, and if we scale up in the cloud, it gets very expensive very fast. I’m not surprised that database vendors are happy to add these features as it increases the licensing cost for applications using them.

I know the majority of the cost of building applications is labor and software developers’ time. However, that’s changing with LLMs that can produce code cheaply. I keep seeing that the cost of writing code is approaching zero.

That’s not going to be true if you use LLMs trained on the example code that increases your database licensing cost. Then the cost might be higher than you expect.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged , | Comments Off on Expensive CPUs