About Explore
Why it exists
Explore is an interactive profile for engineers.
Johnny Butler built the first version of Explore because static CVs and polished summaries hid too much of technical work.
It became a product because the same problem kept showing up across engineers in an AI-shaped market where polished summaries are cheap, real work matters more, and Explore is already a working way to inspect that work.
From person to product
- Person: it started with Johnny trying to show technical work more honestly.
- Product: it became broader when other engineers recognized the same gap.
- Proof: today you can inspect a live profile, grounded follow-up, and explicit owner workflow.
For the delivery model behind that product, read the Dark Factory page.
Why this matters now
When polished summaries get cheaper, real work matters more.
AI makes polished summaries easier to generate. That does not remove the need for real professional signal. It raises the value of work people can actually read, question, and explore.
The problem kept showing up across excellent engineers with strong experience and good CVs who still felt pressure, uncertainty, and difficulty standing out. Explore is the product response to that reality: an interactive profile for engineers with grounded follow-up and a web-or-CLI workflow people can already inspect.
Origin
The starting point was simple: static professional summaries hide too much of the work.
Explore started with Johnny's need for a better way to present technical work than a static CV or polished LinkedIn summary. Over time that problem started to feel less personal and more widely shared.
The same issue kept showing up across engineers with strong skills, solid experience, and good CVs who still struggled to differentiate in a noisier market. Explore also became a greenfield proving ground for the Dark Factory approach, but the product reason stayed practical: build something easier to inspect than a polished summary alone and prove it with a working product.
Product pivot
The project became a product when it stopped feeling useful only for me.
The more this concern showed up around other engineers, the harder it was to treat Explore as a personal experiment. People did not only respond to the interface. They responded to the need for a better public way to show real work in a market where polished presentation is easier than ever.
That was the shift from personal tool to product. The job stopped being "show the idea" and became "make it usable for other technical professionals who want something clearer than a good summary and more useful than a vague AI-compatible claim."
Where it is now
Explore is already a working product with three clear pillars.
Interactive profile
- A public profile that shows role, experience, projects, and writing.
- A better way to show work than a static summary alone.
Grounded follow-up
- Grounded chat tied to real profile material.
- A way for visitors to ask for context instead of guessing.
Web and CLI workflow
- Update your profile on the web or via the CLI, depending on how you want to work.
- Public profiles stay open to explore, while owner-only draft and preview steps stay explicit.
Explore can also start from existing material. One practical onboarding proof is the new CV-to-Explore workflow page, which shows how a static source can become a richer interactive profile.
Why the Dark Factory matters here
Explore is both a product and a proving ground.
The Dark Factory is the operating model used to shape and ship Explore. At the same time, the product is being designed to stay clear for people, usable by agents, and trustworthy because the workflow is explicit.
That strengthens both sides. The product becomes easier to understand and trust, the Agents page has a real workflow to point at, and the delivery model has a real system to prove itself against. For the operating model itself, see /dark-factory.
What comes next
Next comes a tighter product story, then broader onboarding.
The foundation is already there. The immediate work is to make the current launch feel more obvious, more dependable, and easier to start for engineers arriving cold.
After that, the product can broaden outward with smoother onboarding and richer profile management without losing the clarity of the core idea.
Closing thought
The goal is simple: help engineers show real work more clearly.
Explore is the product expression of that idea. If the launch keeps getting clearer and more useful, it is moving in the right direction.