Skip to content

What we did and what the assistant did

A plain list of who did what in building this site: the taste, the pictures and the corrections on our side, the building, the matching and the checking on the assistant's.

3 min read

A human hand and a hand made of gold sparks together arranging dark glass tablets on a wooden desk.

3 min read

Here is the whole split, as plainly as we can put it. This site was built by us together with an AI coding assistant, and we think you should know which part was whose.

What is an AI coding assistant?

An AI coding assistant is a program you give instructions in everyday words, and it does work for you, such as writing text or code. It does not know what is true or right for your project, so a person gives the instructions and reads what comes back.

Key points

  • Our part: the ideas, the taste, the pictures, the corrections and the decisions about what to publish.
  • The assistant’s part: building and rebuilding pages, matching them to the picture, running the checks and drafting text.
  • In the first three days the project history shows more than 80 saved changes.
  • We decide what goes out under the BotKB name.

What we did

  • We brought the first ideas, with Gemini (opens in a new tab) and Claude (opens in a new tab), and we said so when we were not happy. That is the first story.
  • We made the pictures. The main picture on the home page and the covers of these stories all came from long conversations with meta.ai (opens in a new tab). When we wanted a more technical look, with dark glass tablets and gold icons, we chose it over the construction site of the first picture.
  • We chose the direction. One picture set the colors for the whole site, as we tell in One picture changed the whole site.
  • We corrected the facts. The audits of our case studies were read by the person who built the projects, and wrong lines were fixed.
  • We decided what not to publish, and what to remove. We took out a blog we had started, because it held one made-up example post.

What the assistant did

  • It built and rebuilt the pages. In the first three days our project history, the dated list of every change we saved, shows more than 80 changes, from the first tabs to the error pages in both languages.
  • It matched everything to the picture: colors, shadows, shared headers and footers, and the words of the pages.
  • It ran the checks: the page checker, the check that both languages have the same pieces of site text, and the audits of our case studies.
  • It drafted text, including these stories, from our notes and from the history of the work.

What is a project history?

A project’s files are kept in a repository, a folder that also records every change. Each time someone saves a set of changes with a short note, that is called a commit, so the history reads like a diary with dates. We use it to see what we did and when.

Where we checked each other

The checks went both ways. The audits caught things we had remembered wrong. We corrected claims that the code alone could not settle. The fact-checking story tells how that works.

Why we say it

An AI assistant makes a site like this quick to build; the choices, the facts and the words that go out under the BotKB name stay with us. We review what the assistant writes, and we decide what stays.

Read next

We were not happy with the first designThis site started with ideas from Gemini and Claude, and a lot of movement. We were not happy with it. Here is what we built first and what we threw away.One picture changed the whole siteWe brought one picture, and the colors, the mood and the words of every page followed it. A story about taste, and about letting an assistant do the matching.

Got something to build? Let's talk.

No sales pitch. Tell us what your business needs and we'll tell you straight how we'd tackle it, or whether you need it at all.

6 stories about BotKB.com

All 6 stories

We were not happy with the first designThis site started with ideas from Gemini and Claude, and a lot of movement. We were not happy with it. Here is what we built first and what we threw away.One picture changed the whole siteWe brought one picture, and the colors, the mood and the words of every page followed it. A story about taste, and about letting an assistant do the matching.A calm site that is also lightWe wanted this site to feel rich without feeling heavy. Here is how we kept the motion gentle and the pages light, and what a page checker said when we ran it on 28 October.Hebrew and English as equalsEvery page of this site exists in English and in Hebrew, read left to right and right to left. Here is what that meant for the fonts, the layout, the error page and the way we check our words.We fact-checked our own case studiesBefore our case studies went live, we checked every claim against the real code and the live sites. Some of our first wording was wrong. Here is what changed.What we did and what the assistant didYou are reading this story. A plain list of who did what in building this site: the taste, the pictures and the corrections on our side, the building, the matching and the checking on the assistant's.
Accessibility menu

Keyboard shortcuts

Open accessibility menuAlt+A
Accessibility statement

These settings are saved on your device only and are used to adjust the display. They do not change the site content and send no information to any server.