Leet code is dead 💀
Software engineering is dead 💀
Writing code is dead 💀
Writing tests is dead 💀
Reviewing code is dead 💀
Reading tech books is dead 💀
LLD is dead 💀
Tech X is just a funeral home with Wi-Fi at this point.
Give it time, developers will extend their app support to Duo and we can all calm down, can’t say the same for the hardware issues am seeing for a $2,000 phone😖
Added Duo support to EkAyu app, please do check the app out.
apps.apple.com/us/app/ekayu-…
I tried taking screenshots of pic from the XCode 27.1 RC of iPhone duo and all i get is a dark screen is that a bug???
Medical reports lost in your camera roll or paper bundle stacks?
I built EkAyu with my friend @NirajTiwari_ to keep your family’s health records organised, private and easy to find.
Free on iPhone & iPad. Download 👇
apps.apple.com/us/app/ekayu-…
My buddy was irritated with one issue that he was having, and he and I had been working for a month to build something.
It was fun, it was learning, and it was having a good sense of accomplishment in solving a real problem in daily life.
More to come
You are a good developer till the time these agents don’t start hallucinating in a codebase you have either vibe-coded or have no clue what the AI coded till now.
Good day 🌻
What skills are you using for SwiftUI project? Is there any repo you can point at or any of your personal recommendations?
As AI usage increases in the IT sector, junior devs who once took 6–7 years to become senior developers will now skip mid-level, senior, and tech lead becoming solution architects in 2 years and CTOs in 3
Temporary hacks quietly become permanent technical debt.
Even when a language or framework adds native support for a feature, codebases almost always keep the old workarounds anyway.
The feature ships, but the cleanup never happens.
AI can accelerate implementation. It cannot replace engineering judgment.
And no, a lengthy skill or spec file doesn’t solve that problem.
Lessons I’ve learned building software with AI
codecat15.medium.com/lessons…
WWDC26 brought some serious SwiftUI upgrades 👀
I broke down 5 changes iOS devs should know:
• Toolbar APIs
• Document API
• Reordering
• Swipe Actions
• Performance + Data Flow
Bookmark this if you build with SwiftUI.
🧵👇
The Performance & Data Flow updates are worth paying attention to.
AsyncImage caching, lazy @-State initialization, ContentBuilder, and Xcode 27 build-time improvements can impact real production apps.
That’s the full breakdown.
Follow @codecat15 for more SwiftUI, iOS, and Apple developer content.
Repost this for another iOS dev catching up on WWDC26 🚀
#SwiftUI #iOSDev #WWDC26
The way some accounts post these days is truly exhausting & immature.
- AI will make your job obsolete
- Did you know what just happened?
- Someone just crashed the real estate industry
Appreciate progress without turning every update into fear-mongering for engagement & like.
Code that works sequentially is not automatically safe concurrently.
Here’s how shared state breaks your Swift code and how actors fix it. 🧵👇
youtu.be/Eiu53Kr6Ejs
In the AI era, everyone writes async/await.
Very few understand system behavior.
This video accidentally became a lesson on system correctness and the silent blunders that happen when critical thinking is ignored.
youtu.be/IS_ZNXKFj4I?si=y0c6…











