Please take this in the spirit in which I’m writing it (i.e. please recognize the occupational disease of “bugs everywhere” and only mock it in moderation; I do appreciate the post itself):

- The Firefox browser on my Android tablet is close enough to a desktop one that I have no problem reading your blog post. The nag feels unnecessary, especially given it obscures part of the header. For what it’s worth, the tablet’s screen is 1600 real pixels wide @ 260 ppi, and Firefox for Android tells the CSS that the viewport is 800 “pixels” wide—if “pixels” were 1/96", then it would be somewhat below 600 “pixels”, so I don’t know where it’s getting that value from.

(And now I can’t stop thinking if I could make a thing in CSS that would look like a plain-text RFC on a desktop screen but gracefully reflow on a narrower screen.)

- The lightweight-markup parser seems to have gotten confused around the phrases “tests and whiteboarding” and “why I wasn’t a fit”.

- The HN link at the end doesn’t work (404) because you’re adding &ref=blog.webb.page to every external link and HN doesn’t appreciate extra parameters (from my earlier encounters with this kind of thing, neither does e.g. Wikipedia).

Alright, fixed the issues! The link handler didn't check for existing "?" in links but now it does and uses "&" instead for my referrer.

I made the screen size nag flush with the header. It's set to appear at 800px and below because that's when the design starts breaking. I don't have any Android devices to test what you're seeing unfortunately. A graceful reflow would be ideal! I'm sure it's possible but I don't have the energy to figure that out.

Because of the manual nature of the RFC-style formatting, Markdown doesn't wrap lines so I have to make those checks...I have a lot of posts so some fell through the cracks.

I wish I got notifications for comments.

Thank you for taking the time to let me know about these bugs, I'll check 'em out!

You’re welcome :) If you’re not afraid of making your HN addiction worse (and can tolerate some amount of jank), it’s not hard to set those up using https://hnrss.org/replies?id=NetOpWibby and an RSS-to-notifications mechanism of your choice (in my case, https://t.me/el_monitorro_bot; there are a few RSS-to-ntfy.sh daemons around as well if that’s more your thing).

NICE, never knew there was an RSS tool!