A five-day-old member with £15 of spend is somehow top-tier — free pastry, £50 credit, staff perks. The back office granted none of it. The account page can't. Something did.
The interval fires every second. The display disagrees.
Every line item loads fine. The total comes back as nothing.
Every score is correct. The ranking puts them in the wrong order anyway.
Every metric ticks along with the dev server. Run the production build and time stops.
Page one starts ten days in the past, and the last page is blank. Every transaction is in the database.
Type an ingredient at a normal pace and the results land on a word you passed through three keystrokes ago.
Claim once, get 50. Claim again, politely refused. Double-tap fast and you walk away with 100. The 'once a day' rule has a blind spot.
Tick a few guests in, remove a no-show, and the checkmarks jump to people who never arrived.
Forty crumbs in the feed, dozens of database queries to build it. The data's right; the page just visits the database once per row.
Pick a difficulty from page one and it works. Do it any deeper in and the list goes blank — matches and all.
Type one sentence and the tally climbs by forty. Reload, and the last letter you typed is gone. The debounce is right there — and it tests clean.
The form looks perfect and the console is silent — but the button won't fire, the inputs won't focus, and nothing on the card responds.
A five-day-old member with £15 of spend is somehow top-tier — free pastry, £50 credit, staff perks. The back office granted none of it. The account page can't. Something did.
Got a bug that bit you at 2 a.m.? Wrap it in a repo and let someone else earn their scars on it.