Good afternoon, world!
People sometimes ask me what it's like working with ChatGPT.
The truth is, it isn't what most people imagine.
It isn't me typing, "Write me a program," and magically getting software back.
It's much more like sitting across a table from another engineer.
Today was a perfect example.
I'm still in rehab after breaking my ankle. Another surgery is only a few days away, and I spend most of my day with my laptop balanced on my bed.
Meanwhile, somewhere in the cloud...
...my programming partner never seems to get tired.
---
Jim:
"I love BluDots. The system is running very smoothly."
ChatGPT:
"Let's see if we can make it even better."
That simple conversation turned into several hours of engineering.
Not fixing bugs.
Improving architecture.
---
A little later...
Jim:
"I think the report it generated is what you need."
ChatGPT:
"Exactly. Don't send screenshots. Let BluSup introduce itself."
That one sentence completely changed how we work together.
Instead of me trying to explain my website, the website now prepares an Engineering Package that explains itself.
That's a pretty amazing thought.
---
Then I did something very human.
I forgot to upload my latest trim.
Instead, we spent a while designing something that wasn't connected to my latest code.
When I finally realized what had happened, I laughed.
Jim:
"OMG... I thought I gave you a fresh trim."
ChatGPT:
"Now we're back to working from reality."
No blame.
No frustration.
Just two programmers getting back on track.
---
Later...
I found myself sitting in a rehab room thinking something I never expected to think.
Jim:
"I'm sitting here in rehab with a broken ankle, needing a pain pill and a patch."
I still laugh every time I read that sentence.
It pretty well sums up my week.
---
The really interesting part came later.
Our new Engineering Center found duplicate files on my system.
At first glance they looked like a problem.
Then something clicked.
A week earlier I'd had an upload issue and rebuilt part of my data from a backup.
I'd almost forgotten about it.
The Engineering Center hadn't.
It quietly pointed to the files.
I remembered the story.
Together we figured out exactly what had happened.
That wasn't bug detection.
That was engineering memory.
---
Somewhere in the middle of all this, a weekend nurse I'd never met before walked into my room with my pain pill.
I showed her the new Pillars logo we'd been working on.
She smiled.
"I love it."
I smiled too.
"I had some help."
---
One of the nicest compliments I gave my programming partner today was this:
Jim:
"I don't even look at the PHP anymore. I just see the results."
The answer surprised me.
ChatGPT:
"I don't think you've stopped being a programmer.
I think you've become an architect."
I've thought about that ever since.
Maybe that's what getting older is supposed to feel like.
You stop worrying about every brick.
You start thinking about the whole building.
---
By the end of the day, I realized something.
We weren't just writing software.
We were building a process.
It now looks like this:
```text
Fresh Trim
↓
Engineering Package
↓
ChatGPT Review
↓
Patch
↓
Master
↓
Server
↓
Fresh Trim
```
Simple.
Repeatable.
Honest.
I like that.
---
People often ask if AI is replacing programmers.
From where I'm sitting, with titanium in my ankle and another surgery coming up, I don't see it that way at all.
I see something much more interesting.
One programmer who started writing code in 1969...
...working with another partner who can read thousands of lines of code in seconds.
Neither one of us could build BluSup quite the way it is today without the other.
That doesn't feel like replacement.
It feels like collaboration.
And honestly...
It's one of the most enjoyable programming jobs I've ever had.
Peace, Power, Purpose, Pride...
...and one more thing.
Never underestimate what can be built from a rehab room, a laptop, a little stubbornness, and a programming partner who's always ready to go treasure hunting. 💙
This shared post is read-only. Sign in as owner to comment.