The first draft of my About page left out the product-engineering idea I wanted it to explain. I asked for it to return in the middle of the page, where there was room to develop it. That omission was something I had to catch by reading the sentences.
An AI coding agent helped me revise this site’s introduction, About page, work descriptions, and page metadata. Each change needed to make sense in English and Arabic.
Decide what the revision should achieve#
I wanted visitors to understand how software engineering and technical leadership fit with taking responsibility across the product cycle, using AI to help with the work. They should also be able to find an example of how I work.
The brief included boundaries: keep the site’s visual identity and diving scene, keep the writing personal, and make the two languages agree on the facts while allowing each its own phrasing.
Keep the work easy to inspect#
The main checkout already contained work on the scene. I asked for a separate Git worktree so this revision could have its own branch and preview while that work stayed in place.
The implementation collected shared identity facts in one module for page metadata and social cards. Each language kept its own prose. Articles gained visible author links to the appropriate About page.
That connected the page copy to the places where people encounter it elsewhere. If I changed the introduction alone, page descriptions and social previews could still describe my work differently.
Check the result at more than one level#
A successful build wouldn’t tell me whether an Arabic heading fitted on a phone or a work link reached an existing section. Those needed their own checks.
We checked the production build, local links and section targets, canonical URLs, author information, and links between translations. Browser review covered desktop and mobile widths in both themes. We also checked that drafts stayed out of public pages, feeds, the sitemap, and generated preview images.
I kept reviewing the writing while the agent implemented the changes. The sentences had to be accurate, sound like me, and help a visitor understand my work. That meant refining the brief as I saw how it read on the page.
What I take from this#
I haven’t measured a development-speed comparison for this revision. The scope and checks describe what we did; they don’t establish how long it would have taken another way.
The agent helped me move between writing, implementation, and verification in one project. The missing product-engineering idea was a reminder to check the result against the reason for making the change. A page can read smoothly while leaving out what I wanted to explain.