- AI-Assisted Engineering – Guardrails and When Not to Use It
Secrets, destructive commands, production access, confident wrong answers and invented APIs. The settings and habits that contain each risk, and the tasks where doing it yourself is still the faster, safer choice.
- Android – Testing
What is worth testing in an Android app and where each test runs. Pure JVM tests for the rules, MockWebServer for the network, virtual time for debounces and polling, ViewModels with a test Main dispatcher, Robolectric when Android is genuinely needed, and Compose UI tests through the semantics tree.
- AI-Assisted Engineering – Customer Support Tickets
From a customer's confused message to a reproduced bug and a reply a human would send. Triage, reproduction against the real app, what never goes into a prompt, and why the reply needs your judgement more than your typing.
- AI-Assisted Engineering – Responding to Code Review
Working through review comments with the assistant: deciding which are right, answering the ones that are not, and making each fix a small, separate change. Plus using AI as a first reviewer before a human sees the PR.
- Android – Accessibility in Compose
The semantics tree is what TalkBack reads, and it is what your UI tests read too. contentDescription, mergeDescendants and the trap in it, roles and state descriptions, one adjustable control instead of three nodes, live regions, headings, and 48dp touch targets.