jokull

I think poster overfits the postgres wiki advise. The thing is, most timestamps are not "UTC". That's only when you want to print an epoch value human readable you need some timezone and UTC is the most neutral. That doesn't mean you should opt for zoned timestamps in columns.

Because of this overfitting OP lands on exactly the wrong advice. Unfortunately the quoted line is "Even Postgres Wiki says: Don't use timestamp without time zone" but wiki says "Don't use timestamp (without time zone) *to store UTC times*".

Good feedback - I condensed the webpage

Yes - not seen it this red though.

Keep in mind that a lot of vibe-coded software is flying under the radar because it’s being built to replace SaaS and bring workflows in-house. We often judge success by public launches or ARR, but the real "killer app" for this methodology right now is internal tooling for small teams. For example, instead of spending developer bandwidth integrating Salesforce into first-party data, teams are increasingly just vibe-coding a bespoke CRM or CMS as an appendage to their existing database. It’s complex software (state, auth, heavy logic), but it will never be on Product Hunt because it's purely for internal utility. The success metric here isn't "did we get 10k users," it's "did we avoid a $50k contract and weeks of integration hell."

Link to your wife's work?

libsql (from turso) is also working on this - the more the merrier

I just use cloudflare tunnels (cloudflared) - don't have to install any certificates, it's all handled by cloudflare. Yes, it exposes globally, but that's often convenient to share a link to my dev with colleagues. And it has been fast enough. Downside is that you need internet connectivity.