SwiftUI dismiss bugs that eat an afternoon:
❌ Done in a sheet does nothing
❌ Done closes the sheet and the screen behind it
❌ The UI test stays green
Same cause: dismiss read in the wrong view.
12 cases like this, free beta:
👉 https://t.co/59DQinGc2X
New book: Engineering Software with Coding Agents.
How to work with Claude Code and Codex so you keep context between sessions, keep agents inside clear limits, and know what was tested before it ships.
20% off for 3 days.
https://t.co/D2RDw57Oyk
"We have decided to move forward with other candidates."
That same email goes to the engineer whose CV got skipped in six seconds, and to the one who lost a close final round.
Same words. Completely different problems.
Your security scanner passed. Did it scan anything?
Test the check with an unsafe fixture before trusting the green tick.
Security is a Feature v2.0: a practical developer's guide, FREE.
https://t.co/D5nrQxy5p4
Many companies run your CV through software before a person reads it.
If it can't read your experience, it doesn't matter how good you are.
I built a free scanner that shows what it reads and what to fix first. Score out of 100, runs in your browser.
If you are a senior mobile engineer and want staff, this is the book you need.
Altitude shows you how staff engineers think about the whole system behind the app, from the API to the server, the data and the failures.
Second edition. 481 pages.
Your rate limiter passes every unit test.
Now deploy it behind four API servers.
Each server allows 100 requests per second.
Does your system enforce a global limit of 100?
Or have you accidentally built a 400-request limit?
Passing the coding challenge and designing the production system are two different problems.