Nothing here yet.
Nothing here yet.
May 11 · 10 min read · The problem with one storage solution Most React Native apps store everything in AsyncStorage. Tokens, user data, preferences, session state. All in one place, all in plain text. AsyncStorage is a key-value store backed by SQLite (iOS) or SharedPrefe...
Join discussion
May 4 · 14 min read · Why MSW over manual mocks Most React Native projects mock their API layer with jest.fn(). You mock fetch or your Axios instance, define what it returns, and test against that. It works. Until it doesn't. The problem: you're testing your code's intera...
Join discussion
Apr 27 · 8 min read · The hiring panel will never see the app That was the constraint I kept forgetting. I built a whole interview tool with wizards, timers, auto-save, keyboard shortcuts, colour-coded scores. The hiring panel gets none of that. They get a 7-page PDF atta...
Join discussion
Apr 20 · 8 min read · The test nobody finishes Most take-home tech tests fail before the candidate writes a single line of code. They clone the repo. They run npm install. Something breaks. 45 minutes later, they're debugging a Ruby version mismatch, a missing CocoaPod, o...
Join discussion
Apr 13 · 7 min read · The problem with "is this a 3 or a 4?" When I started building the hiring process for my squad, I knew I wanted a structured scorecard from day one. I wrote about the tech test itself in an earlier post. The test worked. The scoring didn't. At least,...
Join discussion
