Urgent.News

What's breaking now, across thousands of outlets.

More in Tech

How I decide which feature to cut (notes from building Tingbase)

Every project I've shipped or tried to ship hits the same point: something has to go, and it's usually a thing I enjoyed building. I'm making Tingbase in Unity 6 and C#.

  • To cut a feature, ask what the player loses if it's gone.
  • If only slight depth or variety is lost, the feature is not essential.
  • Consider real cost of feature, not just visible tasks.

Three services and nothing to store

Originally published at eyosias.me . This is a chapter in the Ivyk8 series. Last time: I cut a flagship-platform plan down to three stateless TypeScript services and five written decisions.

  • Three stateless TypeScript services: dashboard, drive-sync-service, analytics-service
  • Report request determined by backup file, timezone, rate overrides
  • No data stored; security achieved through subtraction and network policies

I tried SKILL.state in my coding agents and stopped after four days

A friend sent me the SKILL.state paper and later asked how it worked out. This is the answer: what I built from it, the four tasks I ran, and why I stopped.

  • SKILL.state replaces chat history with explicit execution state
  • Author tested on four tasks, encountered manual fixes
  • Switched to Opus 5.5 model, benefits lessened

More from Friday 30 October →