HN user

hmschreck

102 karma
Posts0
Comments53
View on HN
No posts found.

The word commonly used for this sort of thing is "ineffable" - that which cannot be put into words.

If you want to see a less "these are magical" and more "here's some science" perspective, you might like "How to Change Your Mind" by Michael Pollan. Always very down to earth, gets into some mechanics of effects, well written and engaging.

More and more research is showing that poverty has a severe impact on the brain, and left unchecked it can become nearly unbreakable.

Many of the decisions made by impoverished people are either somewhat sensible for their situation in the short-term (e.g., asking a 16 or 17 year old child to drop out and start working) or are sensible when viewed through certain forms of skewed perspectives (e.g., spending a small windfall immediately because 'that money will just be gone soon anyway'). Children of impoverished parents overwhelmingly learn these lessons, and the stress of poverty is an ever-present part of their lives, so they are often debilitated by it from the very start.

The final time I ordered from DoorDash, the driver ignored directions (which no one else had ever had issues with), didn't tell me there was something wrong with the directions I had sent him 10 minutes in until over half an hour after leaving the restaurant (my apartment is a 7 minute drive in normal traffic), and I had to call him to get him to tell me that much. He refused to listen to the directions, and when the address that I live at didn't work for him, demanded a different address. DoorDash support then demanded the same, but I told them I was not allowing an obviously irate man to come to my apartment. It took me 20 minutes to get them to assign a new driver so I could give my address.

I am never dealing with them again.

It's less a retelling and more an expression of a culmination of factors in post-war Japan. Japanese media in that era really had a lot of fear about the post-war state, especially the loss of culture, baked in.

First, there is no IQ barrier. I have several friends who, based on psychologist-administered IQ tests, are very, very close to average, who do well in the industry, usually better than me. They worked hard to get where they wanted to go. Sure, you probably can't do this work if you have an IQ under 85, but the same can be said for most any knowledge or even office job. It's not like we're unique in that regard.

Second, a "genetic bottleneck"? That absolutely reeks of genetic elitism. It implies, rather heavily, that they are genetically superior to those who cannot (or just don't) do this work.

The idea that we are special because no one understands us - finance, biotech, pharmaceuticals... No one really gets those, either.

We've had the opposite experience - it's been slow, clunky, and hard to learn/teach. Of course, seeing some of the other things the former admin/advocate for it did after she left, I'm not sure it's Grafana's fault.

200k documents per second really isn't that much for Elasticsearch. The single-instance setup we have in my small company (around 25 people total) has been sent in excess of 40k/s at times, and even then it doesn't slow down noticeably.

I'll second this one. Most of the people in my office who watch anime have all said that SEL played a part in their path in life. It's fun to watch, it has some great artwork, and it's still surprisingly relevant. Just don't expect it to make sense for a long time.

The cognitive impact of wealth has been pretty well studied, and there is already a very good population being studied for this - farmers in some places are pretty well off immediately after harvest/sale, and just before the next harvest, are usually back to a baseline state, or even struggling to pay bills again. Not only do they exhibit better long-term thinking when they are flush with cash, they tend be overall more cognitively capable.

That's the really important thing - we use websockets pretty heavily here, and users can have bizarre issues with them. With this, it does just work. It's not the best or the shiniest, but it's the easiest and the most compatible.

Someone from my local community runs a non-profit that, on paper, sounds great, and he gets a ton of these types of awards for the work he does. Except he doesn't actually do much work. I don't mean he, personally, isn't responsible for all the success his org has, I mean his org does very little of the work they purport to do. They focus on getting a few very high-profile placements per year that they can tout as successes, but overall, not many successes that are coming strictly out of this program.

Dude's also one of the types who acts like doing "so much good in the world" gives him the right to put down literally everyone else in the community.

I ended up building a transcoder within the past few months using Lambda that is handling, as of today, 500k+ videos per month and growing. This was replacing a set of EC2 instances similar to what you described.

A few caveats I ran into: 1) You are limited in how much /tmp on a Lambda instance can hold (512MB total). For the transcode I'm doing on these boxes, some of the videos are that size just to download. It will fail. I have a backup using the older method to handle these very large instances. 2) These, obviously, need a pretty decent amount of RAM to run.

But the benefits are really worth it for us. Elastic Transcoder, for our needs, was going to be >$15k/mo). Our current transcoder cost is around $400/mo. The previous, EC2-based iteration, was a step up for us, but it sometimes took a while to start. Doing it with Lambda has actually been less expensive, provided a faster experience for our customers, and was significantly easier to build than the EC2-based option.

Not bad for a project to see if I could write something in Go.

I stopped reading here:

It’s fine for the algorithm to have separate logical parts, but in a function this is a violation of the single responsibility principle.

If it's contained inside the algorithm, and never done elsewhere, then it's still following the SRP to have the algorithm as a single function. This is just someone who learned a new set of principles and over applies them.

When we talked a decade ago about "when open source wins", we were really excited for it. Now that it's happened, some people are freaking out. This is what winning looks like, though. This was the plan all along.

At my last job, I was getting paid $45k/yr and was expected to work 80-100 hours per week, on top of a 1.5 hour round-trip commute, because the other people on the team for the project were pulled to do other things that were deemed "more important", but the timeline for the project didn't shift at all, because it was also "vital".

There's a really great Usenix talk about burnout I stumbled across, and it so perfectly described what I was feeling, even down to the fact that I found myself drinking more and more each night just to be functional.

On paper, I took a pay cut at my next job, but I earned enough in overtime to more than make up for it, and I've gotten significant raises since then.

Leaving Google Fi 7 years ago

I had one bad experience, and it was so bad I nearly stopped buying from Amazon.

Product did not arrive on time, spoke to support rep.

Rep said that it was delayed because it was coming from overseas, which the tracking information easily disproved - it was coming from Illinois. Illinois is not overseas. When told this, the rep accused me of making things up, despite having the link.

The rep then said that it had been delayed because of weather in my town. I live in this town. It was sunny the entire day in question, and the day before. When I pointed this out, he flat out called me a liar.

I then asked to speak to a supervisor, because I had been lied to twice at this point. The rep immediately began stonewalling me, and for the next 45 minutes, I became increasingly impatient with his behavior, and told him that if I did not have a supervisor in the next 5 minutes, I would be ending the chat and sending the transcripts to someone else at Amazon and following up.

At this point, he made a thinly veiled threat to ban me (I have thousands of dollars of digital content tied to my account), and I immediately ended the chat and sent the entire log to anyone and everyone associated with Amazon that I could think of.

The biggest issue if we can make it non-transmissible (which we are already to that point for first-world serodiscordant couples, to a large degree) is getting it to the third world, where not only is there no money for this, but there's some pretty vile things going on that worsen the spread.

We had a developer interview here who was an Elixir zealot - and I use that word entirely purposefully. He was very adamant that we needed to rewrite our entire platform in Elixir because it was obviously better.

We ended up not hiring; he refused to touch certain technologies that make up a core part of our stack (Node being the biggest issue), and he was honestly something of a massive tool -- on our take-home thing (takes most developers maybe a few hours) he limited himself to one hour, didn't get it done, wasn't even solving the right problem, and, when he sent in his solution... "It's ok, I know you won't get it, but that's OK."

This is how the BLS U3 statistic is arrived at. The U3 is the federal-level unemployment figure that is most commonly pointed to.

The U3 specifically does not include discouraged workers, those who are underemployed, or those who simply aren't looking.

As long as we are comparing apples to apples (i.e., these figures are all indicative of the same basic data with the same restrictions), there's no issue comparing them.