Original Summary

My wife works in the beauty industry, and her salon was unhappy with how much the booking platform took from every appointment. So I started building an alternative: SalonRadar, a booking marketplace plus the software salons run on (calendar, bookings, client history, reports, staff roles, a customer app, in three languages). Laravel + PostgreSQL. Then we went on holiday to Vietnam, and I hit a wall. Working from hotel rooms was miserable, and I didn't want to spend the trip hunched over a laptop babysitting Claude Code. So I changed how I worked. Each morning I'd write a few tickets, then go out. A loop picked them up: one agent built the change, a completely fresh agent reviewed only the ticket and the diff (never the builder's reasoning), and it merged only if the reviewer agreed. In the evening I'd check what had shipped. [X] of [Y] PRs in SalonRadar came through that loop. What I learned: The reviewer caught things I'd have missed. Writing clear tickets became the actual job. Vague ticket in, vague PR out. I named the tool after the animal I kept seeing in the rice fields: trâu, the Vietnamese water buffalo. It plows while you're somewhere else. It's now a product (trau.sh; disclosure, I built it, paid with a free trial), and I'm looking for the first 50 users. Does this workflow make sense to anyone besides me?   submitted by   /u/Deep-Security2949 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/19 03:50:54