Unleashed
Manager is taking four tickets out of my sprint.
Good. I've been asking for this.
"We want you unleashed."
I hit pause on the youtube video playing on the second monitor. ASMR. Productivity stuff.
"Fun yeast..?
"Unleashed."
"Yes," I say. "I want me unleashed too."
Unleashed is probably the wrong word. We don't want too much freedom. We mostly want me in one document for two weeks.
But yes. Unleashed.
I am fixing the page lifecycle. Old timers. Old listeners. New hot components touching old gross components. I've drawn this several times.
Nemesis is inheriting my tickets.
Happy to grab these he says.
Oh? Grab? Fine. Temporary custody.
Meeting ends. I decline standup. Block three hours. Set Slack to focus. Get water. Large glass. Full to the top, which is dangerous near laptop but communicates commitment to myself and my quest.
Open document.
Page Lifecycle
I type:
A page owns anything that should stop when the page ends.
Good. Very clean. I'm not totally sure what i mean by this, but it's powerful.
Does a page end though? Technically navigation starts before teardown. End is conceptually-
Slack notification.
Focus mode allows. Nemesis has a PR up for ticket #1.
Already??
Eight lines. Removes the old listener before attaching the new one.
Sure. Obvious fix if you know where the listener is. I knew where it was.
Need to test away and back. Fresh load won't reproduce it. Everybody tests fresh load because fresh load is easier. Blank state. No ancestors. No... baggage.
I comment.
Make sure you test navigating away and back. Fresh load won't reproduce it.
Yep, covered in the recording.
Recording? Fudge.
I watch.
Away. Back. Click. One event.
His cursor circles the button before clicking. yes that's the button man. Click it.
He clicks it.
One event.
I watch again because maybe the recording loops at navigation. It does not. Continuous clock in menu bar. 11:17 to 11:18. Hard to fake unless he edited the clock, which would be insane.
Approve.
Back to document. It's fine. This is more important. Leadership notices these types of things.
A page owns anything that should stop when the page ends.
Stop when the page ends is almost the same phrase twice. Should stop when it stops. What am i saying? Child sentence.
Delete.
Type Resources must have an explicit lifecycle owner.
Resources. Too cloud.
Delete.
Slack.
Do you want me to remove you as the default reviewer for these tickets? Trying to keep these off your plate.
Remove me?
Um, from my own tickets? no?
I know he means as reviewer. Sentence clearly says reviewer. Still don't like seeing remove + you + tickets in that order.
Probably keep me for context.
Three dots.
Sure. Didn't want to interrupt your focus time.
You're not interrupting.
Immediate. Too immediate.
He merges the PR.
I check another ticket. Waiting on a browser screenshot.
Actually three replies are collapsed under the original report. Tiny 3 replies link. Gray. Could be anything in there. Thanks. Pleasantry. Additional evidence apparently.
Nemesis has opened them.
Found it. Browser and console are both in the second attachment.
I open the attachment.
He's right. Browser version. Console. URL. Everything.
I saw this ticket last week. I did not click 3 replies because the ticket said waiting on screenshot and I believed it. The ticket lied. Well. Became stale. Lying requires intent. Jira doesn't have intent probably. It feels like it does though.
Nemesis messages me.
Got the rest covered. Go build the thing.
The thing?
I have explained the thing using diagrams. This is more than a thing.
I react 👍. Close Slack completely.
Document.
Title. Blank page.
Water gone. I don't remember drinking it. Did I pour it out? No. Why would I pour it out. I drank the water. Fine.
I pat my pants in the crotch area instinctly looking for a spill. Dry.
I type:
Every long-lived resource needs exactly one owner.
Exactly one.
What about shared session state.
I reopen Slack. Just in case of a fire..
Nemesis is typing in the channel.
I wait to see what he says.