Today I wanted to share my perfected file naming format and explain why it looks the way it does on all the files you've seen so far and will see in the future. First, l'll introduce it to you, then I'll break it down. I've also included a .pdf for easy reading and a .txt file for using as a reference in your terminal. ====== THE NAMING FORMAT: title_descriptor_YYYYMMDDtHHMM_m####.ext title_descriptor_YYYYMMDDtHHMM_p####.ext For this post it would be: theforge_my_perfected_file_naming_format_20260405t0714_m0500.txt ====== THE COMPONENTS: - title_descriptor — To represent the contents, the name should be all lowercase words, separated by underscores; no capital letters, spaces, dashes, or special characters. - YYYYMMDD — To represent the date, I use an ISO 8601 adjacent format with a 4 digit year, a 2 digit month, and a 2 digit day (the date of creation or export). - tHHMM — To represent the time, I also use an ISO 8601 adjacent format with a lowercase letter ‘t’ to indicate the start of the documented time, followed by 24-hour time, then the hour and minutes. For the UTC time offset, I use two different indicators depending on if the timezone is ahead, or behind, UTC. - m#### — To represent a time behind UTC the offset indicating character is an "m" for minus # of hours (e.g., m0500 = UTC-5). - p#### — To represent UTC or a time ahead of UTC, the offset indicating character is a "p" for plus # of hours, and standard UTC is simply “0000” (e.g., p0200 = UTC+2 and p0000 = UTC). - .ext — To represent the file type I use the corresponding file extension (e.g., .txt, .md, .pdf, .csv, etc.) at the end. If I don't know the file type, or the file’s contents will be switching file types, I just use ".ext" as a placeholder. EXAMPLES: ai_assistant_summary_20251005t1140_m0500.txt guardian_druid_builds_20251102t1745_p0200.pdf unix_cli_reference_20251001t0930_p0000.txt ====== THE MANDATORY RULES: 1. Use only lowercase letters, numbers, periods and underscores.

Hey guys, for those of you unaware, the World of Warcraft Mythic+ dungeon season is starting next week and before I dive in, I wanted to document my pre-season thoughts and perspective. So, here’s what I’m thinking about: 1. ALL BEAR, ALL NIGHT: To support my skill and mastery building as a tank and a Druid, I’ve decided that I will play the bear tank  Guardian Druid “all night” aka the whole of the Midnight expansion*. So from now on it’s ALL BEAR, ALL THE TIME! (* Only if strictly necessary, I will swap to the melee damage spec, Feral Druid, for that instance and then swap back to bear.) 2. TANK TIME: The Guardian Druid specialization is a “tank” specialization; the functional leader of the group. For all group content, the tank starts the runs, initiates all of the fights, and leads the group through the content to completion. This means that leading the group will be my responsibility for the whole expansion. This responsibility is the root of my, and many other tanks’, anxieties around the role, and the largest aspect I’m specifically tackling. 3. PRE-PULL PANIC: A personal challenge of mine is that I struggle significantly with anxiety. This adds some difficulties to my life, which includes my path to tanking mastery. Before queuing for instances, I experience significant waves of anxiety. I get anxious about everything from preparation to game mechanics to group composition and more. HOWEVER, I have made meaningful improvements in managing my anxiety recently, both in general and while tanking. What I’ve learned and practiced so far is this; I (or you) may never be able to get rid of the anxiety, but anxiety is a mental state that can be tamed and worked through. The key for working through it for me has been, first, recognizing the anxiety for what it is; second, treating my anxiety as a cognitive distortion and nothing more (easier said than done); and third, rebalancing my mentality to accept that the state is what it is and that, independent of my feelings, can be worked through with persistence and dedication.

After personally struggling with fonts for readability in various environments, I've just found what I would consider to be the perfect font; Jetbrains Mono (normal). https://www.jetbrains.com/lp/mono/ Jetbrains Mono is special because ... - Open Source and Free: Licensed under Apache 2.0. - Distinct Characters: No more confusing O or 0, or 1, i , and l. - Increased Letter Height: Enhanced x-height for much better readability - Consistent Character Widths: Uniform width of all characters. - No Character Overlap: F and t won't flow over other letters. - Massive Language Support: Supports 152 different languages! - Versatile Weights: Includes 8 clear weights, each with its own italics version. - Coding Ligatures: Includes 142 coding-specific ligatures to make logic easier to scan. - Universal Support: Works everywhere from your terminal to Word. Check it out yourself!

Hey guys, While my Linux CLI content is still currently a work in progress, I wanted to share some of the best PDF resources I've found helpful to me. Here are 10 of my favorite resources for efficient learning and troubleshooting of the Linux Command Line.

I wanted to get the ball rolling on explaining some of the work I’ve been doing with AI, so I decided to create a new series, AI For Everyday (AIFED). In this series I’ll be going over some of the helpful ways that I’ve been able to incorporate AI into my everyday life to be more informed, more efficient, and ultimately achieve better outcomes. This will be in addition to another series I am working on as an introduction into AI and various AI tools, but that is still in progress at this time. But, without further ado, AI FOR EVERYDAY #1 - Google’s NotebookLM See the attached PDF for my introduction to Google's Notebook, and a how to on how you use it yourself! https://notebooklm.google.com