Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why a Working App Can Still Have the Wrong Database Schema

AI-generated database schemas—the structures that define what information a database stores and how that information relates—can look convincing. If the data saves without problems and the code runs, does that mean the design is good? Here are five examples of AI-suggested designs I reviewed and changed while building a real service. 1. Creating a statistics table without asking if it is needed…

When building a service, the very first thing to check in the database schema is whether it is truly necessary. The AI may generate a statistics table suggesting a date-by-date structure for subscriber count, video count, and total views. However, it is essential to ask if collecting this data is required for the service's current analysis.

If the service can retrieve subscriber changes for specific dates from an external API, there is no need to store that data separately. This oversight avoided in the initial design prevents unnecessary storage and potential confusion later.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Terminal recordings, reimagined

"I'll remember!" Famous last words. You spend two hours chasing a bug, hardening a server or deploying a service. The veteran in you knows you should document the steps as you go.

  • Trecs records terminal activity, preserving commands, outputs, and visuals
  • User-friendly interface allows easy navigation and search within recordings
  • Open-source (AGPLv3) and statically linked, available for various platforms

My Snapchat scraper returned 0 results for a day and still said "SUCCEEDED"

On Monday I checked my Snapchat Spotlight scraper and it looked fine. Green status, run finished in five seconds, exit code 0. The dataset was empty.

  • Snapchat's website layout changed, breaking the scraper
  • Data moved to HTML of pages, streamed as React Server Components
  • User discovered method to extract JSON video data from HTML

A Token Swap Is a Distributed Systems Problem Wearing a Simple UI

TronSeven — Non-Custodial Token Swaps on TRON Network Swap TRC-20 tokens on TRON with self-custody and open-source smart contracts. Low fees, verifiable on TRONSCAN.

  • Token swap is complex distributed systems problem with financial stakes.
  • Users must connect wallet, identify token contract, authorize operation.
  • Model swap as state machine with preparation, quotation, authorization stages.

More from Tuesday 17 November →