The Journal · Ayman AtifSoftware engineering, field notes
Practical lessons from building software
I write about the decisions that become important after the demo works: architecture, .NET, databases, performance, AI-assisted development, Android, and the mistakes that taught me something useful.
How I Rebuilt an Excel-Like Web App After the First Architecture Failed
A relational model looked right for an Excel-like web app until formulas, version history, and undo exposed a mismatch. The rebuild used JSON documents to make spreadsheet state easier to preserve and reason about.
Read case study →-
Building Software · Case study
I Rebuilt a CRM Three Times. Here's What I Learned.
Designing for a developer instead of the users, and a Microsoft Access migration that needed record matching, ID mapping and a human review step to keep contacts and deals connected.
Read article → -
Building Software · Case study
How I Built My First AI-Powered News-to-Video System as a Junior Developer
A small startup, an automated news-to-video product, and a lot of unfamiliar ground: FFmpeg, Python, and an MVP that only planned for one user. What the rebuild taught me about research and architecture.
Read article → -
.NET · Career
The One Interview Trick That Got Me Hired as a Senior .NET Developer
Interviewers rarely care whether you know what something is. They assume you do. What they test is whether you have lived with its consequences in production. Here is the answer format that changed every interview I walked into.
Read article → -
Career · Interviews
Why You Keep Failing Senior Developer Interviews (Even With the Experience)
The rejection says “strong candidate, not quite the right fit.” You have shipped production systems for years. Seven specific, fixable reasons strong engineers give weak interview signal in the room.
Read article → -
.NET · async/await
async/await in .NET Interviews: Request Stalls and Thread Pool Blocking
The async question is not about I/O versus CPU. It is about what blocking a thread pool thread costs you under load: a hard continuation stall, or a slow latency collapse with healthy CPU and memory. The trade-off answer that sounds senior.
Read article → -
.NET · EF Core
EF Core Interview Questions: Tracking, the N+1 Problem, and IQueryable Traps
EF Core questions are database questions in disguise. Tracking overhead, N+1 that nobody wrote on purpose, and IQueryable that silently pulls a table into memory, with the production symptom and the rule for each.
Read article → -
.NET · ASP.NET Core
ASP.NET Core Interviews: Middleware Order and DI Service Lifetimes
Two questions where a small, invisible mistake produces a confusing production bug: a CORS failure that is not about CORS, a threading exception that is not about your code. The “has been burned” answer for each.
Read article → -
.NET · System design
Caching, Garbage Collection, and System Design: Three .NET Interview Answers
Three topics where the textbook answer is easy and the senior answer is a different thing entirely: cache invalidation, GC generations and the Large Object Heap, and driving requirements before the diagram.
Read article →
No articles in this category yet.