Sonith Manakkat

Series7 parts

Software engineering, explained

Clean architecture, building apps with AI help, the forward deployed engineer role, agile in the age of AI, a two-part playbook for planning and running short AI-era delivery cycles, and a balanced look at vibe coding, explained without jargon.

Share on LinkedIn

Share

Start here

Seven articles on how software gets designed, built, planned and put to real use.

  1. Part 1 of 79 min read

    Clean Architecture in .NET Core, explained simply

    A kitchen analogy for layers, the one rule that makes the design work, a small C# example, what it does for testing, common mistakes, and when not to use it.

  2. Part 2 of 77 min read

    How I build small Android apps with AI assistance

    A first-person, honest account of designing, building, testing and preparing 24 small offline Android apps with AI tools, what the AI does well and badly, and why a human still reviews everything.

  3. Part 3 of 78 min read

    Forward Deployed Engineering explained

    What a forward deployed engineer does, where the term comes from, how the role differs from nearby roles, and how AI is making it more important.

  4. Part 4 of 712 min read

    Agile in the age of AI: shorter cycles, same discipline

    Do we still follow agile when AI writes much of the code? Yes, but compressed: shorter cycles, sharper briefs, stricter verification, and lessons fed back into the team's instruction files.

  5. Part 5 of 717 min read

    Planning short delivery cycles in the AI era: the board and the plan

    A practical playbook for planning one-to-three day delivery cycles when AI does much of the building: the board, a 30 to 45 minute planning ritual, sizing by verification effort, and a worked week.

  6. Part 6 of 711 min read

    The AI-era delivery system: roles, meetings, quality gates and release

    Part B of the playbook for short AI-assisted delivery cycles: who briefs, builds, verifies and ships, the three meetings, ready and done, quality gates, release and rollback, and sharing context with a team.

  7. Part 7 of 710 min read

    Vibe coding explained: what it is, where it works, where it breaks

    A balanced, picture-led guide to vibe coding: what the term means, a spectrum from pure vibe to careful AI-assisted engineering, where each fits, the honest limits, a safety checklist and a gate between prototype and production.

Back to all articles