Amateurish and ersatz "thoughtful thinking aloud" is just the latest reason I can't stand listening to radio, and now prefer podcasts.
Pause and ponder all you want, Abumrad, Krulwich, Koenig et. al. I have set my player (Podcast Addict, among others) to skip silence and play at 1.2-2.0x speed, so that gormless pauses and ponderous exposition are now scarcely noticeable.
The connection to HN, IMHO, is this: Louis CK is extraordinarily creative and committed to his art and craft, attributes demanded of entrepreneurs. He sometimes figuratively "hacks" viewer's brains with clever, surprising, insightful works, even when he gets parts wrong. It's the kind of accomplishment I think we can aspire to. We want our code, or our hardware, or our bare idea, to change minds, to inspire discussion, and even to disrupt lazy convention.
Oh, and the topic of this episode is not at all removed from women in tech, and how to "get it" and treat people well, regardless of age, size, shape, gender, religion, etc; these are perennial HN topics, if I'm not mistaken.
Three years ago I just went for Bose QC-15s (in-canal earbuds weren't an option for me, but might be for you, to change-up 'phones throughout the day. Most are isolating, some are noise-cancelling).
Aside from the noise-canceling, the QC-15 feature I like best after 3 years of semi-daily use is that the cable disconnects smoothly from the headset when stressed, like when you suddenly stand up while forgetting to take off the 'phones. I bought a spare cable, anticipating breakage, but I've never needed it.
These are personal, "pro-sumer" headphones, which are definitely not built to take years of daily recording studio rough-and-tumble step-on, sit-on, throw-around abuse. I've never sat on or stepped on my QC-15s, so I don't know how they'd be affected.
These headphones offer pretty good battery life (I get 40 hours, because I don't crank them loud) and soft circumaural earpads. But even with the light earpad pressure on my big head, I "run hot", so the heat and sweat build-up sometimes bothers me. This is true of all "sealing" headphones. I got some relief with my earpad covers made of stretchy t-shirt fabric. Eyeglass wearers will feel pressure on the frames; I don't know any way around it.
Sound quality is fine for me with good bass and clarity; the sound stage is so quiet it's initially a bit spooky. They're quiet enough and sensitive enough to reveal sonic source faults like my laptop's hisses and crosstalk. I don't know how durable they are against overload: I suspect fairly robust, because the speakers are driven by the 1.5V-powered internal amplifier, not the source (mixer, guitar amp, etc). But I also don't know how protected they are against input signal level over their maximum rated 9 Vrms (http://www.bose.no/NO/no/Images/owners-guide_QuietComfort_15...).
The noise canceling is excellent for my most frequent uses (office, home & planes), and very good for my second-most-frequent uses (public transit, walking). QC-15s do not block people whistling and tiny dogs yapping; I really wish Bose would allow selectable algorithms or firmware updating; I'd pay $50 for that feature.
The earpieces rotate to fold flatter in one's backpack, messenger bag or briefcase (I often roll up the cord and stow it in an earpiece compartment).
I've looked the competition to the QC-15s over the years, but I haven't been moved to switch because the features and performance keeps me satisfied. I might switch if mine broke or were stolen, and some other brand offered cable quick-disconnect and useful selectable algorithms.
The difference (with tax and/or shipping) between your target price point and $300 isn't huge.
Though it was posted 2 years and 3 months ago, and the article states that the bug was fixed, to me, the interesting parts were tracking down the versions of git that were affected, and demonstrating the need for more rigorous regression test cases in build --test.
IMHO you have a comfortable cushion, and some time to make careful, thoughtful decisions. Some professional financial planning could set you up to relieve yourself of some worries. Having done phase 1 (acquiring retirement money), you can take some time and assess what you love in life, or to explore what that means. Phase 2 might be family, or it might be personal growth, or it might be an adventure, or investing, or maybe as simple as a soul-searing eye-widening scary-ass meeting with either Paul Graham or Mark Cuban. Something to consider. Short term, though, the sincere, hopeful recommendations by others here that you look into discreet professional counseling to break your logjam and apparent depression, and to help you make your way from phase 1 to whatever your next phase is, are not wrong. You might need the therapy after meeting with Graham or Cuban. Best wishes for your breakthrough.
This is interesting in the context of https://news.ycombinator.com/item?id=6712717 "Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?" - the feature copying usually goes the other way.
But indirectly, this functionality could exist in a Javascript widget/gadget/script that users who do not wish to see spoilers can install themselves, into their registered account's settings. The installation process is usually very simple, a small copy/paste into a configuration file.
I think that no direct modifications to articles to accommodate the script would be allowed; this includes special templates, <!-- hidden comments-->, or even the existing benign {{anchor}} template (usually used to mark HTML URL#link targets), if it's used to mark text {{anchor|spoiler}} for the script.
So the script has to be smart and dependent only the article text itself. It could selectively activate on articles in any category containing the words Television or Film, on sections named Plot or Synopsis, and simply collapse (autohide), or redact (blackout) any paragraphs which contain proper names, or keywords present in a list (die, dead, death, kill, wed, wedd*, marry, married, etc.)
A good starting point would be the text selection and redaction functionality as shown in the ProseSize.js script, which also presents a "Page size" link in the left navigation bar and, when clicked, instantly styles all the eligible article text background in yellow. Our widget could just use black.
I leave it to Javascript and CSS wizards to go further.
I just got a forced update with no way to cancel. But I haven't gone to OldApps to see how far back to go so that A) forced updates don't happen and B) the API and apps still work reliably. Don't know which version at which those two criteria are satisfied.
"The Desktop API was created in 2004 and it doesn’t support mobile application development." So what?
Desktop users built Skype with their Skype-to-phone and phone-to-Skype (Skype Number) subscription money. We want what we paid for: Skype API, and whatever apps and devices are supported by it.
Mobile will necessarily have different apps and devices with some (perhaps) overlap. Developers should be courted to redeploy their apps to a Mobile API if they like, and if their customers want. Microsoft should leave Desktop alone, rather than dumbing it down and damaging ongoing Desktop product value.
Microsoft has been perennially wrong about product value. This is just one more bold misstep.
If what you know has been published in a way which meets enwp.org/WP:Reliable_sources then it can be used in articles. Unpublished material can't be used, because it can't be independently verified by anyone - see enwp.org/WP:V
Self-published material might be usable under certain circumstances, if you're already an established expert in your field (per independent reviews, or citations by others) - see enwp.org/WP:SPS