In March 2023, I backed the SeeAir Tankless Dive System on Kickstarter. Compact, battery-powered underwater breathing gadget. Polished renders, a slick video, spec sheets that looked legit. $362 for the dive unit and a couple accessories. Seemed fair.
The campaign pulled in $722,178 from 2,003 backers. Estimated delivery: September 2023.
Nobody got anything. I certainly didn't.
SeeAir ran from February 28 to April 5, 2023. By late 2023, updates from the creator slowed to a trickle, then stopped. The domains see-air.com and seeair.net are now dead. The Facebook page (1,060 likes) has been quiet for over a year.
The most interesting moment came on October 14, 2023, in Kickstarter Update ...
AI can generate a lot of code. It cannot run your database responsibly.
That’s the uncomfortable truth in the current wave of vibe-coded products: frontend velocity has exploded, while backend operational maturity often hasn’t.
The result is a familiar pattern:
This is exactly where PostgreSQL Commander should live: as the operator layer that keeps AI-built apps from drifting into database chaos.
We used to think coding speed was the bottleneck. Now, for many teams, coding speed is abundant.
The bottleneck is operational coherence:
Release automation gets better the moment you stop asking AI to do the fuzzy part first.
Most iOS release work is painfully deterministic. A build either finished processing or it didn’t. Metadata is either in sync or it isn’t. Your TestFlight groups are either configured correctly or they aren’t. Apple already gives us the shape of that workflow in the App Review Guidelines, the App Review submission guidance, the TestFlight overview, and the App Store Connect API.
That’s the first thing worth automating. Not the heroic ...
You write a prompt, hit enter, and watch the console light up green. Code pours out. It feels like magic. Then you try to maintain the thing a week later, and you realize your shiny new AI agent just built a leaking bucket.
Marc Brooker nailed this dynamic on Software Engineering Radio Episode 710. AI compresses the time we spend actually typing logic. That sounds incredible, but it warps your working day.
If your old routine was spending 70% of your time typing and 30% thinking about architecture, AI completely inverts the ratio. Suddenly, you're spending half your week grading homework from a machine that hallucinated three different API ...
You write a prompt, hit enter, and watch the console light up green. Code pours out. It feels like magic. Then you try to maintain the thing a week later, and you realize your shiny new AI agent just built a leaking bucket.
Marc Brooker nailed this dynamic on Software Engineering Radio Episode 710. AI compresses the time we spend actually typing logic. That sounds incredible, but it warps your working day.
If your old routine was spending 70% of your time typing and 30% thinking about architecture, AI completely inverts the ratio. Suddenly, you're spending half your week grading homework from a machine that hallucinated three different API wrappers for the exact same service.
To survive this, you have to write a rigid specification before ...