⬅️ Tip of the Apache Iceberg 🧭 Networks, Security, and an Easier EV ➡️

Zettelkasten End of Year for 2023

by Jay Cuthrell

This week we take a look at what I learned this year and my Zettelkasten that powers this newsletter and blog archives.

As with my last update a year ago, if you are reading this, I’d like to thank you for your patience as I explored new content formats this year. I am also pleased to share that the Fudge Sunday newsletter remains a free newsletter. 🆓

This year I paid all fees that enable the Fudge Sunday newsletter to be hosted and delivered to your inbox — but if you unsubscribe it only means my costs might go down a bit. If you are only reading this on my website, feel free to subscribe. 🎟️

If you are concerned about me putting referral links or interstitial banner ads in the content, there is no need to worry. Late last year, I was approached by an advertiser but the “Links From Our Sponsor” section was a very short experiment. 🤓

Further, I’ve removed all forms of tracking after experiments with Buttondown click tracking, Google Analytics, LinkedIn Creator Analytics, and now focus primarily on FQDN claims with Google Search Console (i.e. Google Webmaster services). Specifically, for LinkedIn Analytics, I shared my findings over the year in an 11-part series of posts as a LinkedIn Creator.

Getting Informed

While avoiding listicles, I do intend to continue this series of zettlekasten updates in the last week of the year.

How The Sausage Is Made

I’ve had a few emails from the readership this year who are amazed I have published the Fudge Sunday newsletter for so long without missing a week.

Jay, how do you find time to make Fudge Sunday every week?

To be clear, not every Fudge Sunday newsletter is going to be a +2500 words magnum opus… and I will experiment… but getting to around 500-1000 words each week seems to be the sweet spot for me at least. Will I go over or under sometimes? Sure.

How To Fudge Sunday for 2023

This year I’ve experimented with serval workflows and landed on what works best for me. I’ll share the basic 10-step process here:

  1. My stack begins with my public GitHub repository and during the week on my Apple MacBook Air M1 (2020) local machine, I keep a file open in Obsidian as either a daily note from my newsletter readings, Slack Save for Later list, etc. that I can also update from my iPhone 13 mini in Obsidian as well 🔖 📖
  2. On my Apple MacBook Air M1 (2020) local machine, I use Microsoft Visual Studio Code with a few extensions 🪜my Microsoft Visual Studio Code Extensions list
    • Do these extensions play well together? Honestly, I don’t know but they provided me utility at some point. 🤷‍♂️
    • I should probably clean these out and see what I miss in 2024. YMMV. 🧹
  3. After a few years of toil with Revue (Ughh…), Substack (Ughh…), Gatsby (Ughh…), etc. I have fully embraced POSSE again and adopted Eleventy thanks to the wonderful Eleventy Excellent 😍
  4. Each week I add a new markdown file in posts/ to create a newsletter 📝
    • I update frontmatter with the appropriate title, description, date, and tags. 📝
    • I use common snippets for my post structure. 📝
    • I preview using npm start and visit http://localhost:8080 on my local machine. 👀
    • I save the markdown file and preview edits along the way. 💾
    • I turn on MacOS accessibility to “read on screen” at 2x speed to catch things Grammarly misses. 👂
    • I save the final version. ✅
    • Anecdotally, I always seem to miss something because the power of git is no substitute for the humility required to be a writer who acknowledges the value of an editor. 😬
  5. Commit to GitHub 🎉
  6. Await automated build at Netlify 🤖
  7. Await (or manually refresh) RSS to Email powered by Buttondown 🤖
    • My current process is 95% automated and 5% sweating the final details before I launch to thousands of subscribers. 🤔
    • When I refresh the RSS to Email, I am presented with a “Draft” in Buttondown. 🤓
    • I do a quick scan to make sure that what I intended is being imported as expected. 🧐
    • I hit send and hope for no unsubscribes as Buttondown handles delivery. 🤣
  8. As of December 2023, I’ve manually replicated my Buttondown email newsletter as a LinkedIn Newsletter 🔁
    • I copy the content of the first delivered email I receive to my test email account. 📥
    • I paste the content into the LinkedIn Newsletters WYSIWYG form. 😕
    • I create a quick and dirty Canva image that conforms to LinkedIn Newsletter formatting. 🖼️example of the LinkedIn Newsletter WYSIWYG form
    • I send to another ~800 subscribers that are on LinkedIn that may prefer the ease of notification and email delivery. 🚚
  9. Monitor my inbox for replies and make any typo corrections then commit back to GitHub 📝
  10. Await Sunday night automated GitHub Actions ⏰

Favorites

In keeping with the yearly Zettlekasten post tradition, a common email reply from my readership this year was as follows:

Jay, where do you come up with this stuff?

For background, at least once a year I get this question or a similarly worded version of this question. For 2023, I reached the point where I was reading ~100 newsletters but recently pruned all Substack newsletters.

I still use Obsidian and briefly flirted with using Drafts. My Safari Reading List has been tamed for 2023 after seeing just how much I had backlogged in 2022.

My startup Safari browser page is an empty page now. I’ve completely exited from using Twitter/X (including blocking t.co and related cruft with pihole).

My goal is to experiment again with Kagi Search more in 2024 in addition to continued use of DuckDuckGo. I believe that Google Search, Bing Search, and similar are still useful in certain situations if you release all cookies, VPN, or use an anonymization service to get the gist of what others might be seeing vs. your increasingly hyper-targeted assumption profile that weighs heavily upon your IP address as a basis for customized results.

What will my predictions be next week in my first newsletter for 2024?

Until then… Place your bets!

Disclosure

I am linking to my disclosure.


p.s. As I’ve gotten older, I have come to appreciate getting snail mail. If you have time to drop me a postcard that would be amazing.


View this page on GitHub.

⬅️ Tip of the Apache Iceberg 🧭 Networks, Security, and an Easier EV ➡️
Share and discuss on LinkedIn or HN