Lawnmower is gonna lawn mow

Im curious as to why they picked the commit cadence they did. Why do this over the course of two years and not, say 8 months or 15 months? After committing the first patch, why did they wait x days/weeks/months to commit the second? Were they timing the commits off of release schedules, following some predetermined schedule, or something else?

When I worked at Qualcomm the inside joke was that Qualcomm is really a law firm that also employs several thousand engineers.

Thank you for the Disc Brick recommendation. A no bullshit brick-breaker type game was literally what I was looking for.

Paying it forward :) Pretty sure I heard about Disc Brick here on HN years ago (the original pre flashy highlights/colors version was my preference).

My favorite is Fark's word-changing filters and their unintended side effects. The no-no words are scanned across whitespace and reversed, and any hits get translated to the approved word. "Shit" becomes "Shiat", the N word becomes "nubian", etc

Every so often someone will find their sentence that contains something like "I will have ham or egg in my sandwich" becomes "I will have ham onaibun my sandwich"

Reminds me of Yahoo's botched e-mail filter in the early 2000s, when in an attempt to prevent Javascript exploits they automatically replaced all occurrences of a few script-related keywords with alternative terms – even in the text body of a mail and without regards to word boundaries. "eval" got replaced by "review", leading to such words as "medireview" (medieval), "reviewuation" (evaluation), "rereviewuation" (reevaluation), "prreviewent" (prevalent) and suchlike.

If you search for some of those terms, you can still find traces of them across the internet and even in some published scientific papers.

I paid ~$2k (with insurance) for 8 weeks of therapy, with one 45 minute session every weekday.

I have ADHD, major depression, and I did 8 weeks of TMS therapy last year. In the end it did help my depression some, but it isn't a night-and-day difference.

It did, however, completely change how I see myself, to the point where I feel disconnected and separate from the person in my memory. Likewise, my sense of empathy and how I few the world is completely different, for the better.

I plan to do another round this summer.

My only quibble with Zero to Production in Rust is that I assumed the title meant "this is a good book for someone who has zero knowledge of Rust". The Amazon page for it also says "Zero To Production is the ideal starting point for your journey as a Rust backend developer," further implying the reader can have zero knowledge of Rust beforehand. The book's "Who this is for" section contradicts this directly by stating (paraphrased) that this book is for someone who has already read The Rust Handbook and is familiar with the basics of Rust syntax and patterns.

"2biteencryption", name checks out

Anecdotal datapoint to add to the heap: a friend had someone show up to their first day of 100% remote work who was decidedly NOT the person that they interviewed. Obviously that was also their last day.