Voices

What people wrote about my work, in their own words, on the platform where they wrote it.

5 voices on Medium · Show all

mayfair-workroom

Runs https://mayfair-workroom.com/ (interiors business, per own comment)

On Medium

Really enjoyed this. The process feels clear, practical, and honest about where AI coding helps and where the hard work still stays manual. I liked the focus on context, structure, and discipline before speed. I run https://mayfair-workroom.com/ , so my work is in interiors, not software, but the same idea applies. Good results come from a strong foundation, clear planning, and careful execution. This was a smart read.

S M Faidarul Alam

On Medium

This is an exceptionally well-documented, battle-hardened methodology. What sets this piece apart is the maturity of perspective: the clear delineation between being a "junior developer using AI" versus becoming a "product architect directing AI teams." The three-phase framework—Context Engineering, Build, and Production—provides a much-needed antidote to the "vibe coding" chaos that often dominates discussions about AI-assisted development.

The emphasis on Phase One as the non-negotiable foundation is the most valuable insight. Framing documentation not as overhead but as the primary driver of agent efficiency reframes the developer's role from implementer to system designer. I particularly appreciate the honest accounting of the debugging phase; acknowledging that agentic testing still carries significant friction (token costs, login walls) adds credibility that a purely promotional take would lack. This is a practical, real-world guide for anyone serious about scaling their output without sacrificing production-grade discipline.

Ehsan Yazdanparast

On Medium

The image of two capable agents and one person carrying messages between them is uncomfortably accurate. I have done that same copy and paste loop between tools, and it feels productive until you notice a whole evening has disappeared. I also liked that you spent years on the question of who owns a message before you tried to make the setup easy for someone who never opens a terminal. That order is rare, and it usually shows later in the quality of the tool.

Tejas Sharma

On Medium

been building something like this too. the graph view is where it gets interesting. around 30 to 40 sources in, you start seeing clusters you didn't plan for. connections between things you read months apart that you never consciously linked.