tomtung

Ah I have "fond" memories about once spending a good week debugging this, because I was also spawning threads/sub-processes in the loop, making this a Heisenbug that caused the program to crash every hour or so...

So true. This is one reason why I really miss my Pebble watch with its physical buttons, which allowed me to perform a lot of operations by touch without looking (e.g., play/pause/forward/rewind for media control). In comparison, fiddling with the small touch screen of my Fitbit Versa is such a poor user experience.

Not to mention Pebble's "low-tech" screen was so clearly visible in direct sunlight, while I have problem clearly seeing the fancier screen of Fitbit when it's slightly bright outside.

That would probably be a popular book given how well A.G. Martinez's Chaos Monkeys has sold.

My previous employer used something very similar: either adding small features or fixing known bugs of a past build of some open source software in 1-1.5hrs. We prepared one such interview question for each supported language (C++, Python, and Java), and, to help calibration, each question consisted of a series of requirements that required progressively more complex changes.

Both interviewees and interviewers seemed to like these questions. I do hope this approach gets more adoption in the industry. It takes more time to prepare, but the high-quality signals it provides are worth the effort imo. Such questions are also harder to leak compared to typical whiteboard coding questions and thus more reusable too.

Agree. Not sure how much could be blamed on the poorly written dialogs. In contrast, for example, Witcher 3 was so engagingly written that I never minded the procedurally animated dialog scenes.

L.A. Noire from 2011(!)

The rules are more clearly depicted on page 4, with different variations depicted on the pages following that.

Looks fairly straightforward to implement. Until this is more widely available "officially", I'll probably just hack up some Chrome extension for personal use and try it out.

The article didn't shy away from the potential conflict of interest:

> Adding fuel to the mistrust, though, is the role of the EcoHealth Alliance’s Daszak. His close ties with Shi’s lab and his role as a member of the WHO mission’s international team are potentially in conflict. Critics say he can also be less than forthcoming. ...

And in his defense:

> But scientists like the University of Utah’s Goldstein, who do not collaborate with Daszak, told me that there is no evidence that Daszak “wielded disproportionate influence” in the 11-member team.

> Daszak told me in an email that his potential conflicts of interest had been declared to the WHO before he joined the mission team. ...

One method I've seen used to motivate people to move away from deprecated API is: after deprecation is announced, in addition to print a length warning message, also add a thread-sleep call, with the sleep length gradually increasing over time. Consequently, the API will remain usable for maybe months after deprecation, but eventually it will become unbearably slow to discourage any continued usage.