Engineering notes
Six long-form perspectives on system design, AI, engineering careers, cloud reliability, software craftsmanship, and trustworthy data. Practical examples, original explanatory visuals, and primary references.
System design
A good architecture explains what happens when a request is repeated, a dependency slows down, or the business changes its mind. Here is how to make those decisions visible before production makes them urgent.
9 min read · By Sohail Sharif
Published
Read article
AI & engineering
AI is changing how software gets written. The harder questions concern responsibility, verification, and the value of an engineer when generating another implementation becomes cheap.
9 min read · By Sohail Sharif
Published
Read article
Engineering careers
Job-market headlines are broad; hiring decisions are specific. A practical way to connect your experience with the problems a team needs someone to own, without inflating your resume or chasing every keyword.
9 min read · By Sohail Sharif
Published
Read article
Cloud & reliability
A green pipeline proves that its checks passed. Production readiness also needs safe identity, compatible changes, meaningful health signals, and a recovery path another engineer can actually use.
9 min read · By Sohail Sharif
Published
Read article
Software engineering
Java, C#, Python, Go, and TypeScript offer different tools. Reliable software still depends on clear contracts, correct state changes, useful tests, measured performance, and decisions another engineer can understand.
9 min read · By Sohail Sharif
Published
Read article
Data & architecture
A successful job can still publish an incomplete, duplicated, or misleading dataset. Reliable data systems need explicit meaning, temporal boundaries, reconciliation, and a safe way to correct the past.
8 min read · By Sohail Sharif
Published
Read article