01 · Community powered
Why reinvent
a perfectly good wheel?
Mike spots a useful snippet, gives it a new home, and adds three interfaces so it feels properly welcomed.
// familiar code, fresh surroundings
MikeOS · backyard edition
Simple task.
Great guy.
Infinite
pipelines.
Mike can turn a one-line fix into a pipeline that builds a pipeline that approves another pipeline. Same result. Twelve new layers. Somehow, he still has time to bring everyone brisket.
Run Mike's pipeline# Added complexity: enterprise grade. Added value: pending.
$ cat mike.config
approach: thoughtfully elaborate
code: inspired by the community
lawn: unreasonably immaculate
brisket: worth the wait
pipeline_depth: "just one more layer"
$ git status
On branch feature/abstract-the-abstraction
New dependencies:
PipelineFactoryFactory
YAMLConfigurationAdapter
approval-for-the-approval.yml
BUILD passingLAWN stripedBRISKET restingCI/CD calling itself
01 / The pipeline that builds the pipeline
one line of code. a small civilization of runners.The task: print “hello.” The solution: a parent pipeline, a child pipeline, a matrix job, and a workflow to make sure the workflow is working.
A waits for B. B waits for C. C triggers A. Mike calls it reusable architecture. The progress bar calls it home.
Ready. One line of code awaiting six layers of supervision.
○ Build the pipeline generator
○ Test the generated pipeline
○ Spawn the child pipeline
○ Child asks parent for approval
○ Approve the approval workflow
○ Deploy
02 / The Mike stack
built with care. and a few adapters.Why reinvent
02 · Backyard infrastructure
The lawn has
an architecture.
The mower is a service. The grass is a platform. The edging has a roadmap. Somehow, the yard really does look fantastic.
sudo mow --with-extra-care
03 · Low and slow
Some things deserve
the extra steps.
The software could use fewer layers. The brisket could not. Mike understands the difference. Eventually.
smoke --low --slow --feed-everyone
03 / Continuous Integration. Continuous Inception.
a pipeline with excellent family values01 · The family tree
Every pipeline
deserves a child.
Pipeline A starts Pipeline B. B starts C. C checks on A. Mike calls it a supportive engineering culture. The runners call it a loop.
A → B → C → A → B → C → A
02 · The build matrix
One burger.
108 combinations.
Three operating systems, three buns, three doneness levels, four environments. Sesame on Windows is flaky. Mike brings everyone brisket while it reruns.
matrix: [linux, windows, the_smoker]
03 · Dependency management
Approval needs
an approval.
The child needs the parent to approve it. The parent needs the child to pass first. Mike adds a third pipeline to mediate. It needs both approvals.
needs: [approval, approval_of_approval]
# Every layer adds a job. None add a feature. Occasionally, the whole thing pauses for a quick Costco run.
04 / Five meetings. One Mike.
calendar availability: theoretically infiniteHorizontal scaling / vertical calendar
He doesn't double-book.
He runs a meeting cluster.
Five meetings at the same time? That's not a conflict. That's a five-node Mike availability zone.
His calendar looks like a Tetris game someone already lost. Every invite still gets “Yep, I can make that.”
# “Sorry, I was on mute” — simultaneously, in five different calls.
10:00 · Daily standup
10:00 · Architecture sync
10:00 · Pipeline planning
10:00 · Meeting to reduce meetings
10:00 · Quick call that needs 90 minutes
[BACKGROUND JOB] Design a meeting scheduler
Presence: available
Attendance: eventually consistent
Action items: bring everyone brisket
$ calendar --find-free-slot
Next available: during another meeting.
05 · The argument ends here
A great guy.
An elaborate process.
He'll lend you his mower, help debug your code, and show up with enough food for everyone. You came to discuss the architecture. You left with leftovers.
“You can argue with his architecture. You can't argue with a guy who brought everyone brisket.”
# Try it. He's probably already made you a plate.