Haikus

Reflections on software engineering, played out with Gemini

Use git flow they said
It's the very best, they said
Branch flows spaghetti

Use git flow they said
Seven release branches deep
Trunk-based was better

Pushed straight to main branch
Review time from nobody
Sprint for the exit

Skipped code review step
Tests were taking far too long
Pushed straight to main branch

Tests all passed in dev
Tests all passed in staging too
First query breaks prod

Tests all passed in dev
Why is production on fire
Close laptops and run

Fine on Mac OS
Windows trips over itself
Rescue by Docker

Git commit and wait
Pipeline runs, all tests pass green
Suspicious like few

Green build on first try
Not a single test has failed
Suspicious like few

Git found vi improved
Much to my disapproval
q-bang memory lost

X M L abounds
One change in whitespace broke prod
Legacy codebase

Merge conflict appears
Two devs touched the exact line
Time for coffee now

Marketing has lied
Feature sold before it's built
Weekend is canceled

Client opens bug
Ticket closed without a fix
Works on my machine

No tickets assigned
Refactor the whole codebase
Chaos ensues now

Why poetry?

This could be an entire article on its own, but in short: Language is used for active and some passive, thought. Wordplay and writing exercises the brain - using constraints, like a haiku, forces more work to be done, which in turn increases exercise efficiency.

Well, that sounds good anyway - maybe it's true even.