Changing stuff and seeing what happens. If you change two things the universe will let the problem be fixed, because that leaves you uncertain which thing fixed the problem.
The ol Heisenburg’s Uncertainty fix
The guy who wrote this is gone
I’ve gotten about 1,000 alert emails in the last 8 hours because of this
The trick is to be the guy who is gone
Guys who are here hate this one trick!
I retired about a year ago, so the left-most book on the middle row is about me.
That one is my aspiration too. Is retirement as great as it seems?
I’m enjoying it a lot so far. I haven’t missed working at all.
congrats wisened/enrichend early retirement one.
I have a mention in forward with a note being “the only documention left was a series of desperate sounding emails that the documentation was still on the now quarenteened work computers and something about a README”
THIS HAS HAPPENED TWICE TO ME, like I appreciate my bosses and PMs being chill and not wanting to overwork me on my way out but seriously guys I needed to hand this off to someone and put it somewhere. shrug
I asked people to take handover for a full month before I left and nobody cared. On my last day they kept asking if they could call me with questions. I said only if they had their credit cards ready because I wasn’t going to work for free.
100% like can you message me? Sure. Will I help or hell respond? Probally not tbh. Work, chores, and hobbies keep me busy enough.
blaming the user, it’s not necessarily their fault, but gaslighting worked for Apple so why can’t it work for me.
I’m going through Rustlings so Trying Stuff Until it Works
I’m definitely writing useless git commit messages
For work, I at least include the Jira ticket id
For personal stuff, it’s sweeping features stuffed into one commit that barely describes what was changed
“Fixed stuff”
…
“Fixed for real this time”What was the git flag to basically rewrite history again?
I’ve definitely been guilty of this, but if I can redo my changes in narrative form before I push I bet I won’t have to.
git rebase -i
Forcing myself to write in the format of Conventional Commits has helped me a lot to write better commit messages.
Looking at the website, Conventional Commits seems a little verbose for ny tastes but it probably helps actually communicate the changes so everyone is on the same page. Thanks for the tip!
Edit: Spelling
I’m 100% the frog :)
Ain’t nothing wrong with that.
Forgetting how your own code works over here
It’s probably going to be a kitten sort of day; I’m stress testing and trying to address the pain points (which so far is mostly on all the other services outside my code that can’t keep up; not a bad place to be).
Nobody going to admit to being the pigeon? Because that’s me.
I’m sorta like the pigeon but more just a vague understanding of the last critical thing that was asked of me.
Mine is not in the list.
“Click here and there, because no documentation…”I just picked up the latest version of “Copying and Pasting”. This edition discusses copying and pasting from various AIs. Looking forward to digging in
Glad to see they keep it up to date.
Customer facing, so I think I wrote the one with the cat…
Blaming the user. Always
I’m the user
Came here to post this.
