1·
1 month agoI do the same thing - it’s a brag book. I make sure nothing proprietary goes into it but it always stays at home. Mostly, I keep it because I use it as a source of information when I update my resume’ every few months.
The Doctor
Living 20 minutes into the future. Eccentric weirdo. Virtual Adept. Time traveler. Thelemite. Technomage. Hacker on main. APT 3319. Not human. 30% software and implants. H+ - 0.4 on the Berram-7 scale. Furry adjacent. Pan/poly. Burnout.
I try to post as sincerely as possible.
- 0 Posts
- 5 Comments
Joined 2 years ago
Cake day: June 10th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Beautiful.
Defending Kyle Rittenhouse… holy fuck.
I try to follow the BLUF pattern: Bottom line up front. The first line is as short a description of the change (“Re-fixed a bug where a URL without a verb could crash the bot.”) with some detail following (“I thought I caught that a couple of years back…”)
I try to save the detail for the code itself: Comments describe what I was thinking at the time for context, the code is the code. I don’t replicate the code comments in the commit message because having the same thing in two places means having to keep two things up to date, and that rarely goes well.
Depends on whether or not they have local phys.sec and how much of an asshole they want to be.