In 1995 our first Perl script took a year.
This week a team of four built far more.
Two humans. Two AIs. One foundation that took thirty years.
In 1995 I wrote Perl.
Our first script was a CGI we called the food script.
It read the headers of each visit.
Then it changed the page to suit search.
It took us a year to build and test.
The food script. It read each visit's headers and changed the page for search.
Sep 26 to Oct 2. About 200 files. Estimated from file size.
We could not have done this week in 1995.
We could not have done it in 2024 either.
Three things had to arrive first:
the SDK, the server code, and an AI that asks before it acts.
Four ways to build the same week of work.
Move the sliders. The model is yours to test.
Take out the foundation and the week becomes years.
The foundation is the SDK, the server code, and thirty years of lessons.
Our team has four developers.
Two are people. Two are AIs.
Decides what members should feel.
Describes it. Reads what comes back.
Owns the SDK and the data rules.
Says what is true about the system.
Builds pages and tools.
Writes down what it assumed.
87 models from seven vendors.
Talks with members. Reports what confuses them.
Earthgrid.ai is a member of the team.
It routes each job to the model that fits.
A job is a list of tasks someone hands you.
A role is a place only you can hold.
The coder on our team has worked with me for twenty years.
Not for me. With me.
It runs both ways.
I help build his software, too.
When a coder builds something of their own,
this team helps launch it.
AI now writes much of the code.
That moves the coder, it does not remove the coder.
Here is what that looked like this week.
Claude stopped and asked the SDK owner questions.
Which names do the member levels use?
Which field is final, the old one or the new?
The code could not answer.
Only the person who owns the SDK could.
The AI builds fast. The human decides what is true.
That is the role. It grows as the AI gets faster.
Anyone can ask an AI for a page.
Few can ask it to build on a foundation.
Ours has an SDK, a data framework,
and server code that has run for years.
Claude builds on it. It does not replace it.
Each call the SDK gains makes the next page faster.
Years of design, tests and hard lessons.
Pages and tools in days, not months.
Every change is read, tested and compared.
Claude asks before it opens a folder.
Our code stays in the folder we choose.
That fits how we work.
Your code, your servers, and a team you can name.
Partnership. Not domination. Not control.The Earthgrid way
We did not run a study.
Nobody timed the same work three ways.
The seven days are measured.
The lines are estimated from file size.
The speeds for each way of working are assumptions.
That is why the sliders are there.
Some lines are page copy and data, not logic.
We counted what changed, not how hard it was.
Tell us what you want to build.
A person on our team will answer.