The Practical AI Coding Publication
Hamzify exists because AI coding tools change quickly, while marketing and generic round-ups rarely explain how those tools behave during real development work.
Hamzify. The Practical AI Coding Publication.
Practical means the work actually happened
Hamzify tests tools, documents builds, examines workflows, and shares both successful and unsuccessful results. It does not exist to claim that every AI product is worth adopting.
The questions that belong here are specific: can this tool handle this task, where does it fail, how much human involvement is required, what workflow makes sense, and who should actually use it.
Testing means the tool or project was used on real work, with the version, task and limits stated. Research means a claim comes from a primary source, not from a session that never happened. Analysis is judgement on top of those two. Sample articles shipped with the site are labelled as such and are not firsthand results.
Hamza
Developer, writing Hamzify
I build software and write about doing it with AI in the loop. Hamzify is where the notes live: tool tests on real tasks, build logs from projects I actually shipped, and the workflows that survived more than one week of use.
The reason this site exists is that most writing about AI coding tools is either a launch announcement or a screenshot of something that worked once. Neither helps you decide what to open tomorrow morning. So the pieces here state what was built, how long it took, which version of which tool was used, and where the whole thing fell over.
If something here is wrong or out of date, I would genuinely like to know — corrections get published rather than quietly patched.
- Works on
- AI-assisted software development
- AI coding tools and agents
- Frontend and full-stack development
- Developer workflows and tooling
Six kinds of writing, one question
Everything on this site is a way of answering the same question: what is actually worth doing with AI when you have real work in front of you?
- Vibe Coding
Vibe coding experiments with AI coding tools
Vibe coding documented properly: AI-assisted building experiments, prompt-to-product attempts, and what breaks when you hand real work to a coding model.
- Build Logs
Build logs: shipping software with AI agents
Long-form AI build logs from real projects: stack, coding agents, decisions, mistakes, and what actually shipped.
- Workflows
AI development workflows worth stealing
Repeatable AI coding workflows for briefing agents, pair programming, reviewing generated code, testing and shipping.
- Reviews
AI coding tool reviews, tested on real work
Hands-on reviews of AI coding tools such as Cursor, Claude Code and GitHub Copilot, with a stated method, a verdict, and who should skip them.
- Comparisons
AI coding tool comparisons by use case
Side-by-side comparisons of AI coding assistants — Cursor vs GitHub Copilot and others — decided by use case rather than a single overall winner.
- Resources
AI coding resources, checklists and guides
Evergreen AI development resources: context engineering checklists, AI coding tool guides, and collections that stay useful after the next model drop.
What you can hold this site to
Tests state their method
Every review says which version was used, what was built with it and how long it ran. Without that, a verdict is just a mood.
Editorial policyMistakes get published
Corrections appear on the page with a note saying what changed and when, rather than being edited in silently.
Corrections policyMoney is disclosed
Affiliate links are marked, disclosed above the article, and have no influence on a recommendation.
Affiliate disclosure
About the current articles
11 of the 11 articles on this site are sample content shipped with the template. They exist to demonstrate the formats — reviews, comparisons, build logs, experiments, workflows — and each one carries a visible notice saying so. The timings, costs and outcomes in them are illustrative, not results from a real test, and they are meant to be replaced by genuine write-ups.
Questions are welcome
There is no comment box here, because a comment box on a static site means handing your data to a third party. Discussions happen on GitHub instead, in public, where the answers stay findable.