7/ If your interview process primarily measures memorization instead of architecture, debugging, problem solving, code quality, and system design, you may be selecting for good interview performers rather than good engineers.
6/ A junior developer can paste AI output.
A senior developer should be able to review it, challenge it, improve it, and explain the tradeoffs behind it.
Those are very different abilities.
5/ Can you spot bugs?
Can you identify security issues?
Can you recognize poor architecture?
Can you improve maintainability?
Can you debug production failures?
Those are engineering skills.
4/ In 2026, AI can generate code.
The valuable skill isn't typing code from memory.
The valuable skill is understanding whether that code is actually good.
3/ The expectation seemed to be that if you don't remember every Retrofit, Coroutine, or Hilt API by heart, then somehow you don't know Android.
I disagree.
1/ Just got out of an Android interview where I was expected to write a complete REST API implementation from memory in an online Kotlin playground.
No Android Studio.
No autocomplete.
No documentation.
No Gradle.
No AI.
🧵
@bumble my account got blocked due to a ID verification issue. I have mailed the customer support multiple times but no response. Please help in getting my account unlocked.
Built a small tool to take the pain out of cold job applications.
Paste a JD → local LLM parses it → tailored email drafted → sent via Gmail → logged in SQLite.
Runs on local Ollama, and is easy to retarget to any role.
https://t.co/CrXfUUzewP
LOL welcome to the future, humans. You hit the shutter button and an image is generated based on your location and weather conditions 🙃
(this is an art project but still hilarious)