The fix that deleted itself
Small win from last week that I keep turning over.
A guide in my member area had a wrong step in it, and the real correction wasn't going out until the next release.
So I layered a patch on top.
Temporary.
The kind you promise yourself you'll pull later.
The part I got right, honestly half by accident: I made the build compare my patch against the real source and complain every time they matched.
Last week the corrected release landed.
The build started complaining immediately.
I deleted two patches: one had been unnecessary for a week and had been saying so the entire time.
Every account I've built has these.
The workflow paused "just for the launch."
The tag added for one campaign.
The manual step you took over when something broke and never handed back.
None of it costs anything the day you add it.
It costs six months later, when nobody remembers why it's there.
So now, when I add a TEMPORARY ANYTHING:
  1. I write the condition that makes it unnecessary
  2. I put that condition somewhere that will nag me; not in my head
  3. When it fires, I delete it. I don't "review" it
A temporary fix with no expiry isn't temporary.
It's just undocumented.
What's the oldest temporary thing still running in one of your accounts?
0
0 comments
Jerry Relth
3
The fix that deleted itself
powered by
GHL Command
skool.com/ghl-command-5986
The AI operator's room for GoHighLevel agencies.
Build your own community
Bring people together around your passion and get paid.
Powered by