peatfreak

There's an undercurrent of victim blaming here.

A lot of companies hire data scientists simply because it's "the thing to do" and they want to appear modern in the marketplace. But then these data scientists are typically left to work alone and put under pressure to "produce results" with no tangible understanding of their mission.

Sure, you could say that it's up to them to advance their own case, but if you have no support system (which is something that most people need) then it's very demoralizing. Unless part of your job is to figure out how and whether a data driven approach is even applicable, then this is can be a very depressing situation to be in.

Did you actually listen to the presentation? They explicitly addressed each of these points (except the bit about the confounding variables, admittedly).

The good examples are _always_ cherry picked.

I'd be interested in seeing other "setting up an electronics workshop" articles by other engineers.

Luke Gorrie, for example, has an article here: https://github.com/lukego/soldering

I'm really curious as to how these were done, or might plausibly have been done. Is this indicated anywhere? After working on audio signal processing for quite a few years, I'm investigating image and video rendering, and applications like this are the kind of thing I'm interested in.

This makes no sense!

The whole point of the article is to discuss Make.

It kind of makes the whole article irrelevant. Like a house of cards that is build on a foundation of Make, but when you get to the bottom there are no actual Makefiles there.

I've never seen so much disagreement about "what is Buddhism" as I have in online Buddhist communities. Everywhere I turn there is conflict, misunderstanding, and people proclaiming "this is not real Dharma, but I know what the real Dharma is".

I do however agree that a lot of folk seem to get into esoteric stuff like Tantra and Dzogchen very early before understanding basic things.

Its conclusions stand in stark contrast to the fundamentals of Buddhist practice. It's message is confusion from an author who is not accomplished in practice but writes eloquently.

Some famous Buddhist teachers are a bit like this to me. Chogyam Trungpa, for example... I can't make head or tail of the man. Sometimes I think Crazy Wisdom is great, other times I think he's been a disaster for the spread of Buddhism to the West. I raise the spectre of CTR because the article we're discussing has a Crazy Wisdom feeling for me, and that's why I like it.

I think it's unfortunate its gone to the front-page because it makes a mess of the dharma and communicates Buddhism as a mass of contradictions.

The whole Internet is a mess of contradictions regarding Buddhism. It is literally the worst place you can go to learn about what Buddhism really is, because the only way you learn properly is to trust a teacher by knowing them on some kind of personal level or teacher-student level.

For a tradition with such emphasis on sangha, practice, and lineage of teaching, it's ridiculous to submit to the thoughts of online Buddhists who you don't even know. I think this is a reason for all the disagreement; arguments are conjured up out of thin air with no reference to the actual practice of the person who says it.

I'm not saying the article is correct in all aspects, but rather that it goes beyond the trite and predictable criticisms of Western Buddhism, and for that alone it's more interesting than most articles. It raises anecdotes that I haven't much of before, it's slightly abrasive, and I like that.

I encourage more people to go out and practice the way we have the teachings preserved not in Zen, not in Tibetan but early Buddhism, where we're closest to the teacher.

This is a very Western Buddhist attitude. In the Western tradition we love to get as close as possible to the primary canonical source when learning something, possibly because Western Buddhism tends to be quite dry and academic and admits very Protestant attitudes. I think a lot of Western Buddhists have this mistaken notion that Theravadans have some monopoly on what Real Buddhism actually is.

My most recent teacher said it doesn't matter whether you start out in Zen, Pure Land, Tibetan, or Theravada, just pick one and stick with it for a while otherwise you'll get your wires crossed and end up getting a jumbled message that is inconsistent with any sect. He acknowledged the desire for people to study early Buddhism as the "purest" form of Buddhism, but he said that IF you want to study early Buddhism or Theravada, then you need to stick with it. So, much like you're saying, yes the Theravada teachings are more direct and simpler, but maybe it's not necessary to start out with this form. Maybe it is, I don't know. I'll figure it out as I go along. But I don't disagree in principle.

Personally I like the simpler, warmer approaches to Buddhism, and I do often appreciate irrational, supernatural aspects when I encounter them. I do appreciate Theravada, not because it's the purest form, but because the practitioners I've met so far seem to be a bit warmer. Plus, Theravada is a bit more like, "do this, do that, keep it simple".

I've been very curious about Zen but I notice that a lot of Zen practitioners tend to deflect real-life problems into clever Buddhist aphorisms, which is just evasive and doesn't really engage with the world. Plus I don't really love meditation that much so maybe it's not for me. I'd prefer to do active physical exercise in my limited time (and when I'm not writing on HN) because I know this benefits my mind and body more than extended sitting. On the other hand, I like Alan Watts a lot, I think he had had a much more positive influence on Western Buddhism than CTR had. So AW a good, positive advertisement for Zen.

Pure Land sounds cool because I like chanting, but I like Nichiren chanting more (plus I met a lot of cool people in Nichiren circles). Tibetan Buddhist sanghas around where I live seem to be a bit, oh I don't know, I just can't really get into it.

The article has the following near the end:

"To see more real-world examples of makefiles, see my [World Atlas](https://github.com/mbostock/world-atlas) and [U.S. Atlas](https://github.com/topojson/us-atlas) projects, which contain makefiles for generating TopoJSON from Natural Earth, the National Atlas, the Census Bureau, and other sources."

I checked those repositories because the descriptions of the makefiles sound interesting, but I couldn't find the makefiles. Am I looking wrong?

I'm currently working with the AWS SDK Python documentation and it's a hot pile of garbage from all points of view (UX, info architecture, technical detail, etc.).

I agree that pretty much all AWS documentation is woeful, and it's a travesty that the service is so expensive yet its documentation is so poor. I would gladly dump AWS and never use it again, as I hate paying top-dollar to decipher the AWS doc team's mistakes (not to mention that they are unresponsive to bug reports and feedback).

My point was made more in jest, and supposed to point out the irony of the communities' changing expectations of what documentation should be like. I predict that in a few years we'll be circling back to prioritizing writing software documentation well. (Kind of like how everybody was hating on XML for the past 20 years and it's now having a renaissance because it actually does what it's supposed to well very well.)

It makes me sad that many people will use this as an opportunity to write off Buddhist practices.

This would be a huge misunderstanding of the article. I read the whole article, and I found it to be positively re-affirming of Buddhism. Unfortunately the submission title is potentially misleading and possibly even clickbaity.

It's a very good article. I've read many critiques of Western Buddhism and they can mostly get a bit samey after a while. However -- after the first few paragraphs, which are admittedly pretty run-of-the-mill -- this article elevates itself to a much more interesting level. It also raises solutions, anecdotes, and references that go way beyond what you normally hear.

Homebrew is an awful system, it's the exact opposite of what should be held up as an example of a well engineered "packaging system". It's not even a proper package management system anyway, and there are far, far better systems for Mac OS X. The whole "dump everything into /usr/local" is absolutely insane, and it's depressing that the development community on OS X has fallen for it.

I never knew about MiroTalk before, so I'm happy to see this post. How does it compare with Jitsi, for example?

wasting time looking up the manuals

God forbid!

Ooh, I've never heard of FizzBuzzBang before, but this seems like such a natural (and surprisingly interesting) extension. Thanks for mentioning it. I'm going to check it out.

Interesting to see so many folks here running Exim. It's my favorite MTA primarily because I find it understandable, it has excellent documentation, and I'm used to it as it used to be Debian's default MTA. I get a lot of folks telling me not to use it due its history of security issues, and recommending something else instead, like a qmail derivative. I'm not sure how I feel about this.

a) I Co-run the Data Science Weekly newsletter.

Is the newsletter still running? I looked at the archive on the website and I didn't see anything more recent than April 2022.

Thanks for the information!! I just checked my copy, and it is indeed the Buss translation. I was reading it for several week a few months ago, and I ended up putting it down, just because it just wasn't happening for me and I couldn't figure out why.

Very recently I discovered that I need glasses (for the first time in my life). My eyes went from perfect to downhill very quickly. I'm now trying to get used to wearing reading glasses. This is especially important with a book like this, which has a tiny font. Now I know why I was feeling uncomfortable and getting headaches :-)

How does the Penguin translation stack up? It's the only one I can easily find.

For software, a programmer literally owns the means of production, so all programmers are bourgeoise?

No, they are not. Marxist analysis doesn't really map to information technology in service economies in the classical way. The principles of analysis still apply in today's society, but first you have to recast class definitions and class relationships in a meaningful way. There's a nice (but idiosyncratic) book called "The Relevance of the Communist Manifesto" that explains this, but it won't make sense unless you already have a basic grip on orthodox Marxism.

Does anybody know how this works? As somebody with a serious interest in signal processing, machine learning, and audio, I'm genuinely interested. Have Adobe published anything about the technology behind this?

This sounds interesting to me, especially as somebody who was exactly zero interest in learning anything other than regular JS (i.e., no TypeScript, CoffeeScript, or any other JS-extension languages). Is this some kind of pattern, and do you know of any examples that show this?

Incidentally, the underclass that many on the modern left focus on were pejoratively considered “lumpen-proletariat”.

This is absolutely correct in terms of orthodox Marxist theory. It's interesting how "lumpenproletariat" has been whitewashed out of modern Marxist analysis. You just don't hear this term anymore.

I've been using Debian for 20-25 years and it never gets straightforward.

What a revolting attitude.

Thank you for this comment, I only wish it was at a higher level up in this thread.

The number of ignorant comments in this thread is astounding. All this criticism feels like it was written by back-seat drivers who have no clue about the complexities of language design or compiler implementation.

Oh, the arrogance and the irony.

I like his music a lot, but I do get tired of nerds constantly fawning all over him.

Which laptop has the best keyboard? This is a huge deciding factor for me.

I've had Thinkpads with beautiful, solid keyboards and they are joy to use. But they tend to be pretty old models and I want to try to update if possible.