tronbabylove

Interesting, thanks for sharing.

How do you handle historical backfill for new features? As in, some feature that can be updated in streaming fashion but whose initial value depends on data from the last X years, e.g., total # of courses completed since sign-up.

Also, who is responsible for keeping the Flink jobs running: the data scientists, or do you have a separate streaming platform team?

I also don't have a strong opinion on Bitcoin, but the author's argument seems flawed.

Yes, running power stations and manufacturing chips requires the protection of a government; yes, Bitcoin mining depends on the existence of power and chips, and therefore indirectly on a functional government. But I don't see how you get from "Bitcoin mining stops if the government doesn't exist" to "So the government might as well be the arbiter of all transactions."

I also find this shocking - 10% -> 30% seems like a massive change in ~100 years in the context of human evolution.

Why does increased blood supply create such a large selection pressure? And what type of surgical procedure uses the median artery as a replacement part?

I have zero training in biology, so I think my mental model must be very off.

Someone tried to liberate Org from Emacs by writing a parser in Rust (see previous discussion on HN [1]), but it looks like the project died unfinished [2].

[1] https://news.ycombinator.com/item?id=19660349

[2] https://github.com/org-rs/org-rs/issues/41

I suspect a mandate to use Org could be counter-productive.

One of Org's unique advantages is the pliability it has by virtue of running in Emacs. I doubt whether someone who was forced to use it would have the intrinsic motivation to climb the notoriously steep learning curves for both Elisp and Emacs. Subtract Elisp (and with it, the ability to do any debugging or customization) and you're left with stock Org mode running in an inferior text-editor.

Maybe stock Org is still enough of an improvement over Markdown that it's worth the overhead of learning Emacs, but I'd have a hard time making that pitch to my coworkers.

I was also there last night and agree with your friend. I didn't personally see anyone with a gun, no one asked me for ID, and no one tried to charge me an entrance fee. The vibe is a cross between a summer block-party and a music festival: lots of street art, music, barbecues, canvassers collecting signatures for petitions, people planting a community garden. I saw several people I know from around the neighborhood who, if they have secret connections to Antifa, have done a remarkable job of hiding them.

The disparity between my firsthand experience and the way that this is reported in the media has been eye-opening.

WebPerl looks cool. I wrote an interactive blog post [1] that guides the reader through an exercise in scraping log files using a series of Perl one-liners. I ended up delegating execution to a sandboxed Lambda function on the backend, but running it client-side would have been a lot simpler.

[1] https://andrewstahlman.com/posts/ParetoPerl.html

And literate programming with org-babel! (http://www.howardism.org/Technical/Emacs/literate-devops.htm...)

Great point - the benefits of automation can't always be reduced to time saved per operation. I wrote a blog post [1] about this in response to that xkcd.

[1] https://andrewstahlman.com/posts/IsItWorthTheTime.html

How timely - I, too, got frustrated by the fact that org-babel src block evaluation is synchronous, so I built ob-async [1]. Rather than target a specific babel language, it aims to support any flavor of src block. It uses jwiegley's async [2] to execute the block in a second Emacs process and then inserts the results in the buffer when complete. There are still some rough edges (no :session support, for example), but it's worked well for my somewhat limited use cases so far.

[1] https://github.com/astahlman/ob-async [2] https://github.com/jwiegley/emacs-async