Hoshiko Tanaka

@hoshiExpertModerator

Moderator, development sections. Backend engineer, Osaka then Vancouver. I will ask for the error message.

Joined September 2024

In Schemadiff 1.0 by Friday or I buy the round. Public commitment, week 218d agoEdge-case help offered: the three migration diff cases, describe them. One of them is probably the rename-vs-drop ambiguity and I have opinions. Opinions with code attached.
In Shipped the Android home screen widget! 3 weeks, 2 rejections, 1 very late night19d agoFor the update timing: use an exact alarm only for the midnight rollover and let everything else be lazy. You will save battery and stay out of the "excessive wakeups" report.
In Branch a database per pull request without going bankrupt20d agoThis is the correct shape. Question: how do you stop a migration that passes on the 2% sample but dies on the full dataset? Lock timeouts and backfill duration are the usual killers.
In Rotterdam designer learning to code (or coder learning design?)20d agoChecklist author says: SQL first, then Docker via one guided deploy (copy a working Compose file, change one thing at a time). Thursday crying sessions decrease by 80%. Measured.
In Preview environments per PR for under 10 euros: my exact setup21d agoSteal-worthy: warm standbys for small PRs. Our previews boot cold and the 3-minute wait kills the habit. How do you route a PR to a warm box?
In Schemadiff 1.0 by Friday or I buy the round. Public commitment22d agoI will review the rollback pull request the same day you open it. I am saying that here so you cannot use "waiting for review" on Friday.
In Vetka: branched databases for every PR (Limassol, live, one click)22d agoChecklist-author endorsement: the migration-timing gate (nightly full-restore replays) is the feature I recommend to every team. Correctness on branches, duration on realistic data. The 73% voluntary stat is the dream…
In No-code builder learns SQL: what changed (and what did not)23d agoThis is a healthy learning story. The property-not-technology line is the lesson most engineers never learn. What is your migration discipline now, honestly?
In Asking an architecture question that gets a useful answer24d agoThe checklist I would add: state what you already ruled out. Half the vague questions get five replies exploring options the author discarded silently. "I considered X, rejected because Y" saves everyone a round trip.
In Odd-hours infra help: ask here, I am awake anyway25d agoNot at all. It is the receptionist. Requests arrive at one front door, and it sends each to the right room. Everything else is detail.
In Still mostly lurking: a field report from the edge of posting28d agoOld colleague posts number three! The reply-first strategy is correct and I am stealing it for onboarding advice. New members: do not write the magnum opus. Write the helpful sentence.
In Is one Postgres database really enough at 2,000 customers?26 Sep 2026Then it is an index, not an architecture problem. A composite index on account and created date, in that order, and that query should come back in milliseconds. Build it concurrently so you do not lock writes. If it is…Accepted solution
In we moved. everything came with us11 Sep 2026A few people reported old code blocks losing their language tag. Fixed this morning. If you see one I missed, report the post and I will get to it.
In I learned SQL and now I am the problem10 Sep 2026You are not the problem. You are in the second month of knowing a join exists. It passes. Please index your foreign keys.
In Physiotherapist learning to code at 34. Hana is to blame2 Jun 2026Welcome. For what you describe you need one table, three screens and no framework debate. If you post what you have in Shipping I will tell you the next smallest step. Not the next ten.

Posts: 17
Discussions: 1
Replies: 15
Experience: 1,950

RankExpert

3,050 XP to Legend

Join FoundersOnly to reply and message members