[1] I didn't take them up on the offer to interview in the wake of that and so it will be forever known as "I've made a huge mistake."
192 karma · joined June 26, 2021
[1] I didn't take them up on the offer to interview in the wake of that and so it will be forever known as "I've made a huge mistake."
1. Loud refrigerators / appliances / computer fans
2. ICE engines with mechanical problems / modified exhaust
3. Smoke alarm replace-battery beeping
4. Noisy airflow (bad air gaps / glass insulation) in vehicles and rooms
5. Bad electric noise (bad AC/DC converters)
6. Emergency vehicle sirens that are too loud (I think this is a US phenomenon)
7. Television commercials that increase in volume over ordinary programming
I'm sure there are many more out there
Is there an explain plan sanitizer that is helpful for this situation?
On any HN corporate layoff post, we should expect some volume of named company FTEs or impacted folks commenting. There seems to be a pattern here that has been ebbing and flowing over the last few years.
Should this be a titled phenomenon/effect? I see at least 3 options here:
1) Named company employees do not read/post on HN (if true, is this HN content? divergent topic...)
2) Named company employees are coerced or otherwise compensated to not comment on these matters, even if they do not directly impact them
3) Named company employees do not care about this n% layoff and are withholding comment
edit: formatting
Taking a peek at the source, it's so interesting to see the a piece of history. For example, this was released in Japan in 2000, then internationally months later. As I recall, there was awareness building around the idea that vibrating controllers (here, the N64 Rumble Pak accessory) cause RSI or carpal tunnel. Since the developers shortened the rumble length outside of Japan, it looks like they were aware as well: https://github.com/nanaian/papermario-dx/blob/main/src/rumbl...
I wonder what led to this decision being made at the exclusion of the JP release.
"if it's not Boeing, I'm not going" (See '79 bumper sticker: https://www.ebay.com/itm/332131135342)
Starting to look like it might be the other way around...
If you have ever taken a commercial flight, you have seen it: the individual that needs two people to team up (or one highly capable one) and lift up or down their 40-50 lbs (~20 kg) roller from the overhead. Half the time, their help is in their party, but it slows things down.
I would estimate that this happens at least once every 4 rows on a fully occupied 6 seat wide aircraft.
Given this, forbidding passengers to bring carry ons aboard that they can't overhead lift themselves would be the only way to speed things up regardless of boarding/deboarding strategy.
Is that practical? Probably not.
Here's a paper from last year: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9321237/
Yes, it's Omicron, but 32.4% asymptomatic infection is not very rare.
Asymptomatic carriers are 75% as infectious as symptomatic individuals: https://jamanetwork.com/journals/jamanetworkopen/fullarticle...
This post finds reasonable fault with false dichotomies as "OR life" then reifies the structure of false dichotomy in the title and proposition as positivist thinking.
I think the constructive equivalent is "When life gives you lemons, make lemonade". Or at least be mindful of the false binary trap, even in your personal life...
The thing people don't realize is that speed limit advisory signs (on turns or downhills usually) are essentially mandatory for high CG vehicles - to avoid rollover risk.
To help you understand some reasons to refuse a pullout, here are the conditions that I think must be true for an RV or heavy truck to safely and practically use a pullout: (Maybe I'm missing something)
1) Vehicle is slower than the speed limit or lower than the safety speed advisory by more than 10 mph. (Yes, this is annoying for people that want to exceed the speed limit, but they can use passing lanes.)
2) Pullout must be visibly paved and clear for entry in advance of safe braking distance. (This is often a problem.)
3) The pullout must have good visibility behind it so the vehicle can safely get back up to speed from 0 after stopping. (Sometimes a problem.)
4) Traffic must be light enough such that rejoining the travel lane is feasible in less than a couple minutes. (This is often a problem.)
5) The pullout must have a safe path to return to the travel lane. (I have had to balk pullout attempts after nearing the pullout because this is not always immediately clear at a distance.)
6) Most importantly, the vehicle must not be followed either at an unsafe distance or by someone driving erratically. (I am not going to risk damage to my vehicle by braking for someone following too closely.)
edit:formatting
A lot of these SSF hotels are new and close to a quite a few ex-SoMa tech companies now in Oyster Point.
Apropos of nothing, on a 3 day trip, I did see a man, minding his own business walking, get "ride-by" assaulted by a mentally ill bicyclist in the marina. I think this fits with what I'm hearing about not prosecuting that type of thing there. Other than that event, the areas in SF I saw seemed cleaner/safer than it was pre-covid.
This means it's an 800 pound gorilla in a dev/bay friendly costume (docs? API?).
They cannot fix the financial system unless they can become Wells. That will not happen. Thus, their actions, pricing, and product development choices all point to Wells.
PayPal has this exact theme of a problem. Or lack of solving.
I am personally interrogating my response to this:
"Oh no! A trolley is heading towards 5 people who tied themselves to the track. You can pull the lever to divert it to the other track, killing 1 person who accidentally tripped onto the track instead. What do you do?"
I save the 5 over the 1. Only 15% agree with me. Why?
This is the first Absurd Trolley Problem (I think) that explained WHY a person was tied to the track.
I think the value of this hypothetical is in establishing the value of cultural relativism versus Kantian ethics.
In that framing, I'm really surprised that, on Level 27, 70% would rather send a trolley into the future to kill 5 people 100 years from now, instead of 5 people now. In almost 11K votes, this seems significant.
My view is that this provides evidence for the Bentham "hedonic calculus". (And I'm sure there are better scholars of Kant and Bentham than I that can argue for or against this.)
Here's a "political" example: Do you want to deal with problems now, or defer? 70% will defer. (I think this checks out, and is truly hedonic.)
So, I think the data, and the utilitarian approach shows: don't expect any of our societal problems (politically agnostic) to be solved any time soon.
My yearbook advisor sent yahoo mail and asked what I would like to be picked up at Starbucks for an early morning meeting the next day.
"Caramel Mocha, thank you!", I replied.
The next morning, I was surprised with an undrinkable "Caramel espresso" - an espresso with a pump of caramel syrup. I thought she had made an innocent mistake and was shocked to see there was in fact a difference between my sent text and her received text. I had no explanation.
After some years in web dev, and encountering this article, I realized that, as the precursor to javascript - the script type "mocha" was valid, so yahoo just went ahead and replaced all references to mocha with something that probably seemed innocuous to a junior developer - except it wasn't.
2021-04-07: https://github.com/evildmp/diataxis-documentation-framework/... Add license CC-BY-SA 4.0
2021-04-30: https://github.com/divio/diataxis-documentation-framework/co... Copyright change from Danielle Procida to Divio
edit: fixed link
This is front of mind for me since reading a Cloudflare blog regarding AVX-512 instructions invoking dynamic frequency scaling to manage power/thermal capacity on chip. (https://blog.cloudflare.com/on-the-dangers-of-intels-frequen...)
If this is happening on Xeons, it's probably happening on consumer dies as well, in addition to other non-obvious power/performance optimizations. Perhaps this is why Alder Lake is pumping up the TDP[1]?
A lot of the pthreads books I see are from the late 90s. Is there a more recent reference? What's the best way to write cross-platform (e.g. not Grand Central Dispatch) multithreaded apps with these new chip architectures?
"People managers" prioritize interpersonal manageability while owners / "sufficiently incentivized" / technical managers have more weighting towards competency and execution performance.
At either end of the "sociable vs competent" spectrum (a reduction for sure), an underperforming or rude colleague will invariably decrease output from ordinary team members. The impact variable must be closely monitored and responded to.
Quarterly eNPS-type feedback helps keep these cycles tight.
edit: quotes
In my next class, the teacher was talking about "Time for break" virus going around... :/
This was after the district IT wanted to suspend me for setting up a Windows 2000 domain for the yearbook lab, so I kept my mouth shut.
Alternatively, and pessimistically, is this simply a successful marketing endeavour by a digital agency?