Hey Kyle, quick
question…
The charge code is doing that thing again.
AssigneeK Kyle of course
SprintThe rest of his life
Estimate“Should be easy”
THE UNOFFICIAL DEPARTMENT OF KYLEEST. ONE MORE QUICK QUESTION
Now. You want to know who's fixing it?
KYLE’S
FIXING
IT.
One developer. Every ticket.
An absolutely unsustainable legend.
LIVE FROM KYLE’S BROWSER01 / ∞
Hey Kyle, quick
KYLE’S
GOT THIS.
GOT THIS.
Kyle opened another tab.
01 — SCOPE? YES.ALL ROADS LEAD TO THE SAME ASSIGNEE.
That’s a lot
for one person.
You’re RIGHT. It IS a lot.
But here’s the thing about Kyle—
Kyle just opens a tab.
It worked
yesterday.
Wonderful. Send yesterday to Kyle too.
Just add
one value.
And every place that assumed there would never be another value.
While you’re
in there…
The URL table rows. The migration. You know. All of it.
Can Kyle
jump on?
Every charge code. Every BAA. Every operating day.
02 — THE TAB SITUATIONTHERE’S ALWAYS MORE.
Ten tabs. Twelve tabs.
Fifteen tabs.
He’s going to fix this one.
Then he’s going to fix the next one.
Then a client’s going to file another one.
↶ ↻ kyle://just-one-more-ticket10 tabs
KYLE’S QUEUEEVERYTHING IS PRIORITY 1
0RESOLVED BY KYLE
10STILL KYLE’S PROBLEM
03 — THE LONG-TERM ROADMAPOWNER: KYLE
KYLE AND THE TICKETS. KYLE AND THE TABS.
A HUNDRED
YEARS.
Every charge code. Every BAA. Every operating day.
All of them. Over and over. Forever and forever.
The backlog has outlived the roadmap.
There’s Kyle.
For Kyle. You absolute legend.