About

About This Site

Practical guides for developers and builders learning to work with AI.

Last reviewed: Aug 5 2026


Author and editorial responsibility

C. Leijon writes, reviews, and is editorially responsible for AI Programming Manual. He has worked in web and systems development for more than 20 years and also holds a degree in political science. Corrections and source challenges are handled by the same named person rather than an anonymous content team.

Why This Site Exists

AI Programming Manual exists because I wanted the resource I couldn't find: structured, practical, honest guidance on building software with AI. Not marketing, not theory — just clear explanations of what works, what doesn't, and where the real trade-offs are.

The site covers two audiences:

Both groups are figuring out the same thing from different directions: how to work effectively with AI as a building tool.

How This Site Was Built

This entire site — the design, the guides, the tutorials, the articles — was built by me working with Claude over about six weeks of evening and weekend sessions. It started as a translation of a Swedish manual I'd written, then grew into the 40+ page resource it is now.

I made every editorial decision: what to cover, in what order, for which audience. Claude did the heavy lifting on drafting, HTML generation, and maintaining consistency across dozens of pages. The process involved hundreds of conversational exchanges, constant iteration, and a fair amount of restructuring when early decisions turned out to be wrong.

The full story — what worked, what went wrong, and what I'd do differently — is in How This Site Was Built: A Developer and AI, Start to Finish. It's the most honest account I can give of what AI-assisted development actually looks like on a real project.

What You'll Find

Editorial Approach

Sister sites, separate audiences

AI Programming Manual is one of six sites edited by C. Leijon. Its five sister sites share editorial infrastructure and research where appropriate, but they are not interchangeable translations:

Get in Touch

Found an error? Have a topic suggestion? Want to say hello? Use the Contact page. Content corrections are especially welcome — accuracy matters more than pride.