Real build stories

Real work with AI, documented honestly

Builders, freelancers, and businesses share what they shipped with AI, automation, and AEO/SEO — what worked, what broke, and how they fixed it. Read their build logs, skip their mistakes, and share your own.

How Half Dev works
  1. Build

    Someone ships something with AI, automation or SEO.

  2. Break

    It goes wrong, and they say exactly how.

  3. Share

    They publish the build log, failures included.

  4. Fix

    You read it, skip the mistake, or add what worked for you.

Your turn: share what you built.How we review stories →

What really happened, including the parts that went wrong

Half Dev publishes first-hand accounts of building with AI, automation, and SEO. Most stories like this online are polished until the failures disappear. Here, a build log that admits an agent quoted the wrong price for two weeks is the point, because it saves the next person from making the same mistake.

Both formats are free to submit. Free stories carry a byline only, with no backlinks and no company promotion.

Want to know whether AI search can see your own site? Try the free checker

  • Build Log

    A full case study: the problem, the stack, what broke, and the result.

    Read Build Logs
  • Quick Win

    A single tip or fix you can read in a couple of minutes.

    Read Quick Wins

Free tool

Is your site actually visible to AI search?

Enter your domain in the box and scan everything at once: three real, rule-based scores — AEO (12 checks: schema, AI-crawler access, headings, freshness and more), SEO (11 checks: indexing, sitemap, canonical, title, alt text and more), and GEO (8 signals: llms.txt, AI bot access, entity markup, FAQ schema and more). No API cost, no signup.

See the full checklist →

Enter a URL above — free, rule-based, no API cost.

Free · rule-based · no API cost

Free checkers

Want to look at just one area? Each checker scores one part of being found by search and AI, and shows what to fix.

All tools →
Portrait of the Half Dev founder

Why Half Dev exists

I got tired of success stories that were really just advertising.

After 13 years fixing power steering systems, not writing code, I started building with AI and automation. Half Dev is where builders publish the real version: what worked, what broke, what it actually took.

More on why

Free library

Templates and prompts you can download and use.

View all →
  • n8n Workflow · JSON

    WhatsApp Lead Qualifier Agent

    Classifies inbound WhatsApp messages (booking, pricing, complaint, spam) and logs qualified leads to a sheet. Swap in your own WhatsApp + LLM credentials.

    Download
  • n8n Workflow · JSON

    Content Freshness Checker

    Weekly job that walks your published posts and emails you when one hasn't been touched in 180+ days — pairs with the freshness check in the AI-Visibility Checker.

    Download

Behind Half Dev

Real work. Real problems. Practical solutions.

Half Dev is where I document the work behind the projects: building with AI and automation, troubleshooting technical problems, testing ideas, and finding out what actually works.

I share the process, not just the polished result. That means the mistakes, the fixes, and the decisions that made a difference.

How it works

How a story gets published

Submit a story →
  1. Submit

    Write up what you built. It's free, byline only, with no backlinks or company mentions in the body.

  2. Review

    A moderator checks it against the free-tier rule and the editorial guidelines before anything goes live.

  3. Publish

    It goes live under your name. If something needs fixing later, it's corrected visibly, not edited silently.

The Half Dev approach

Build something. Learn something. Share it.

Every project teaches you something. Sometimes an idea works. Sometimes it breaks. Often, the most useful lessons come from figuring out why.

We believe those lessons are worth sharing.

Half Dev encourages builders, developers, freelancers, and business owners to document their real experiences: the challenges they face, the approaches they test, the mistakes they make, and the solutions they discover.

You don't need to have everything figured out. You just need to share something useful and be honest about what you learned.

Have something worth sharing?

Turn your experience into something another builder can learn from.

Explore publishing opportunities