Stephen Way
@stephenway.bsky.social
Feedback loops should be instant, I think
AI-generated changes should be cheap experiments, not pipeline landmines.
1) Right now, every AI-suggested refactor feels risky.
Not because the code is necessarily bad.
1) Right now, every AI-suggested refactor feels risky.
Not because the code is necessarily bad.
November 30, 2025 at 5:02 PM
AI-generated changes should be cheap experiments, not pipeline landmines.
1) Right now, every AI-suggested refactor feels risky.
Not because the code is necessarily bad.
1) Right now, every AI-suggested refactor feels risky.
Not because the code is necessarily bad.
Reproducible incidents: why epochs beat ad-hoc logs every time.
1) Most CI and infra incidents are technically “reproducible” only in theory.
1) Most CI and infra incidents are technically “reproducible” only in theory.
November 29, 2025 at 6:00 PM
Reproducible incidents: why epochs beat ad-hoc logs every time.
1) Most CI and infra incidents are technically “reproducible” only in theory.
1) Most CI and infra incidents are technically “reproducible” only in theory.
I’ve hit the founder stage where buying domains feels like collecting Beanie Babies.
Except Beanie Babies didn’t charge $79/year for .sh
Except Beanie Babies didn’t charge $79/year for .sh
November 29, 2025 at 5:03 PM
I’ve hit the founder stage where buying domains feels like collecting Beanie Babies.
Except Beanie Babies didn’t charge $79/year for .sh
Except Beanie Babies didn’t charge $79/year for .sh
Stop hitting “rerun job” and start rewinding to the exact state that passed.
1) “Rerun job” is a superstition button.
You’re not fixing anything.
1) “Rerun job” is a superstition button.
You’re not fixing anything.
November 25, 2025 at 5:03 PM
Stop hitting “rerun job” and start rewinding to the exact state that passed.
1) “Rerun job” is a superstition button.
You’re not fixing anything.
1) “Rerun job” is a superstition button.
You’re not fixing anything.
CI is slow because it guesses what changed instead of knowing.
1) Most CI pipelines don’t actually know which parts of the system a change touches.
They approximate it.
1) Most CI pipelines don’t actually know which parts of the system a change touches.
They approximate it.
November 24, 2025 at 5:04 PM
CI is slow because it guesses what changed instead of knowing.
1) Most CI pipelines don’t actually know which parts of the system a change touches.
They approximate it.
1) Most CI pipelines don’t actually know which parts of the system a change touches.
They approximate it.
99% of your pipeline didn't change. Your CI should know that.
November 21, 2025 at 5:02 PM
99% of your pipeline didn't change. Your CI should know that.
What if secrets weren’t .env files or a Vault maze, but a project-scoped encrypted notepad that syncs across dev + CI with versioning and diffing?
Would you use that?
Would you use that?
November 18, 2025 at 7:58 PM
What if secrets weren’t .env files or a Vault maze, but a project-scoped encrypted notepad that syncs across dev + CI with versioning and diffing?
Would you use that?
Would you use that?
Looks like another VSCode AI clone
November 18, 2025 at 4:57 PM
Looks like another VSCode AI clone
I’ve been measuring not just how fast things run, but how fast they begin.
Cold starts tell you what your system actually thinks of your time.
Cold starts tell you what your system actually thinks of your time.
November 11, 2025 at 7:58 PM
I’ve been measuring not just how fast things run, but how fast they begin.
Cold starts tell you what your system actually thinks of your time.
Cold starts tell you what your system actually thinks of your time.
I’ve been asking freelancers where their time actually goes.
Most expected a little admin work, but many said they lose half their week to everything except creating.
If you’re a freelancer or creative, how much of your week gets lost to admin work?
And what task drains you the most?
Most expected a little admin work, but many said they lose half their week to everything except creating.
If you’re a freelancer or creative, how much of your week gets lost to admin work?
And what task drains you the most?
November 6, 2025 at 5:18 PM
I’ve been asking freelancers where their time actually goes.
Most expected a little admin work, but many said they lose half their week to everything except creating.
If you’re a freelancer or creative, how much of your week gets lost to admin work?
And what task drains you the most?
Most expected a little admin work, but many said they lose half their week to everything except creating.
If you’re a freelancer or creative, how much of your week gets lost to admin work?
And what task drains you the most?
There’s something about GitLab CI that just feels engineered, not glued together.
I have my suspicions why, but I’m curious if you’ve used it long-term, what keeps you loyal to it?
I have my suspicions why, but I’m curious if you’ve used it long-term, what keeps you loyal to it?
November 6, 2025 at 12:48 AM
There’s something about GitLab CI that just feels engineered, not glued together.
I have my suspicions why, but I’m curious if you’ve used it long-term, what keeps you loyal to it?
I have my suspicions why, but I’m curious if you’ve used it long-term, what keeps you loyal to it?
Every DevOps team has that one forbidden folder: /var/lib/jenkins/
Nobody talks about it, nobody dares touch it, but when compliance needs a deployment audit...there it is.
Jenkins isn’t cool. It’s responsible.
Some of us run it not out of love, but because the auditors don’t understand yml
Nobody talks about it, nobody dares touch it, but when compliance needs a deployment audit...there it is.
Jenkins isn’t cool. It’s responsible.
Some of us run it not out of love, but because the auditors don’t understand yml
November 5, 2025 at 8:04 PM
Every DevOps team has that one forbidden folder: /var/lib/jenkins/
Nobody talks about it, nobody dares touch it, but when compliance needs a deployment audit...there it is.
Jenkins isn’t cool. It’s responsible.
Some of us run it not out of love, but because the auditors don’t understand yml
Nobody talks about it, nobody dares touch it, but when compliance needs a deployment audit...there it is.
Jenkins isn’t cool. It’s responsible.
Some of us run it not out of love, but because the auditors don’t understand yml
GitHub Actions: 3 minutes remaining
Me, 17 minutes later:
Me, 17 minutes later:
November 5, 2025 at 12:56 AM
GitHub Actions: 3 minutes remaining
Me, 17 minutes later:
Me, 17 minutes later:
CI/CD shouldn’t feel like booting an operating system just to run a script.
The next wave of DevOps is about pre-compute, doing work before work starts.
The next wave of DevOps is about pre-compute, doing work before work starts.
November 4, 2025 at 12:56 AM
CI/CD shouldn’t feel like booting an operating system just to run a script.
The next wave of DevOps is about pre-compute, doing work before work starts.
The next wave of DevOps is about pre-compute, doing work before work starts.
90% of DevOps is pretending you understand the YAML written by your past self.
November 3, 2025 at 3:02 AM
90% of DevOps is pretending you understand the YAML written by your past self.