In Part 1, I laid out the catalyst (the 2026 U.S. midterm elections), the broadcasting industry's structural backdrop, and E.W. Scripps' operational positioning - its local station footprint, ION's must-carry reach, the OTA/sports pivot, and the secular headwinds it's running against.

The operational story is decent. But none of it matters if the capital structure can't survive long enough for it to play out.

Security analysis, especially of the 'cigar-butt' variety (as Buffett would describe) has always been an interest of mine. Taking a cue from Michael Burry's old MSN MoneyCentral articles, I'd like to elucidate on my own theses, in order for me to reinforce my own arguments and build a track record of my performance going forward.

For no particular reason whatsoever, I recently found myself dusting off an old repository, InterviewPracticeQuestions and thought it a good exercise to restructure it along the latest C++ and CMake principles.

Having recently returned to dynamically-typed languages, I've found myself stumbling a little without the safety net of type-checking. Yet, I'm not convinced on the principles of duck-typing either.

For a discipline supposedly rooted in rationale and logic, it's surprising there isn't a greater emphasis placed on decision theory. All too often, critical decisions are led by heuristics rather than formal methods.

This might appear a little left-field, but it's always surprised me how the morphology of the Irish language lends itself to programming constructs.

I decided to do a short write-up about my approach to writing a good program. I'd recently finished reading Clean Code by "Uncle Bob" and I felt evangelised to put what I learnt into action.