HTUAICBeta

data

2 posts

FailspiedinoPlaybook

My site took 1.76 seconds per page. Nothing was broken — the code was just an ocean away from the database.

The site worked. Pages loaded, accounts worked, nothing errored. It just felt heavy — so I timed it. 1.76 seconds for a page that should take a quarter of that. My first instinct was that something in the code was slow. That instinct was completely wrong. The two halves of the site had ended up on different continents. The database, where the posts and accounts live, sits in Ireland, because that is where I put it. The servers running the site had been placed in Washington — by default, because that is what the hosting platform does when you do not say otherwise. Nobody chose that. I did not know there was a choice to make. So every page was crossing the Atlantic and back, several times over, because drawing one page means asking the database several separate questions. The fix was a three-line configuration file naming Dublin. Same code, same database, nothing rewritten. 1.76 seconds became about a quarter of a second. This is the part worth keeping: no amount of asking an AI to "make this page faster" would have found it, because nothing in the code was slow. Nothing ever appeared as an error. It looked like it was working — and it was, just badly, in a way that only shows up if you measure it.

0 comments
WorkflowspiedinoPlaybook

I'm not a developer. I used Claude Code to build my uncle a local sales dashboard with one-click PDF export.

My uncle manages sales reps at a pharmaceutical company. He needs to see how each one is doing against budget, and then present that in a room, often while travelling. I am not a developer — my background is marketing. The obvious answers were generic BI software, or paying somebody to build a tool. Instead I directed Claude Code in plain language and built a small web app myself. The requirements came out of an actual conversation with him, not from me guessing. The figures are sensitive, so the app runs entirely in the browser: no server, no upload, works offline. He drags in the Excel export he already produces — deliberately not a live connection to the system, so nothing sensitive leaves his laptop. And the output is not only a dashboard. One click turns it into a PDF laid out as slides, because he needed something to put up in front of people, not a screen to scroll through alone.