HN user

grangerg

88 karma
Posts1
Comments38
View on HN

Someone on another Amazon related thread mentioned that 50% leave after 2 years and 80% leave after 4.

If you do the math on their TC to see how it actually works out from month to month, it makes sense. Unless you get more RSU's, you take a huge hit in pay, unless you weren't cashing in on them to make ends meet.

Perhaps tell them the story of the 10x carpenter.

Obviously, the one who uses the most wood wins! ;) If told right, they should easily figure out why LoC is a horrible metric.

Even without rDNS, they're almost certain to know of at least one DNS name that goes with the IP address you're connecting to. Even if not, they can label/categorize/group it by ISP and/or approximate location.

I used to wonder the same about Chrome. Try using a Chromebook with less than 4GiB RAM. You can handle 2 simultaneous tabs/apps---if you choose them well. It's due to this behavior alone that I never consider Chromebooks; by the time you find one with enough RAM to handle Chrome, you're in the price range of a "real" laptop.

Project Ideas 4 years ago

Remember back in the day when we used to use the word "algorithm", instead of "AI"?

Those are similar to my own thoughts. I like also having them talk about their favorite recent achievements.

I can quickly train a person to have knowledge in some domain,

This part I have a little bit of trouble with. If you have a trivial domain, sure. In my experience domain knowledge takes a while to truly get your head wrapped around. But I expect that's why there's always other things that people do in an interview.

Any sources on that bit about chronic ibuprofen usage? I'm aware of the GI issues (stomach lining actually), and not the others. I'm a long chronic user (daily for years now), and appear to have a reliable mitigation for the GI problems, so I'd love to know more about the other stuff you mentioned.

^THIS^

...And what comes when people are under the cloak of anonymity, or otherwise feel there will be no negative consequences to whatever they choose to do.

My opinion is that it's rooted in the anonymity people feel on the 'Net. There are no, if little consequences to being a jerk online---not nearly like in "real life".

The other problem I see is that a person says what they feel in the moment---and then they move on. But the (emotionally charged) comment from that moment lives on, potentially for years. The "energy" doesn't dissipate with time like it does in "real life".

I think he touched on that in the article. The masses are trusting the centralized API, not the blockchain. His NFT exists in the chain, but not the API, so it effectively doesn't exist in the eyes of the market.

I'm in a similar boat with the "Google Now" feed on Android. When I say "not interested", it fails to note that as expected, and I see the same news "story" pop up (usually different sites, but occasionally the exact same site!). It's likely related to the fact that it almost NEVER gets the subject/topic correct, so I can never use that option.

There was a time I thought I'd trained it to stop telling me about what celebrity said or wore what, but those are creeping back into my feed.

Both meeting A and B start at 2pm and end at 3pm.

After you're done with that corner case, you may find it better to determine if they don't overlap and negate that.

I read the title and first expected some satire like this:

Imagine you're being taken on a "backstage tour" of the Internet. They open the door, turn on the lights, and as the distinct odor of decay and the chaotic scene of confusion and disarray greet you, you hear the guide blurt out, "Ah, crap! Who made this mess?! I swear it was presentable just a little bit ago! Well, good luck getting ME to clean this up! OK folks, we're outta here!"

And THAT is AWS in "plain English".

It depends on what you're after.

I'm very comfortable in SQL, and would prefer to write my queries. But our team has grown, and we've found that developers say they know SQL, but they really don't. In general, I've found that it's not the syntax that messes people up. There's a significant mental "jump" between the usual procedural coding paradigm and the "set based" paradigm offered by SQL. Some people just never catch on.

So we're going to start using an ORM (Entity Framework Core 2) so that the "mere mortal" developers can pitch in. I know there's a way to run raw SQL, so I know that when we find spots where the ORM fails, we can just rewrite it with some good SQL if we decide that's best.

But maybe that'll never happen? We've been trying to do simpler SQL stuff as of late so that the heavier lifting in the system is done by the application/client instead of the database (bottleneck). As the database sees simpler, less unique queries, more stay in the plan cache, indexes are more reliably hit as expected, and performance increases.

Exactly. We canceled Hulu ages ago. Look! I can pay for Hulu, and get the exact same service as people that get it for free---but on something other than a browser!

Canceling "cable" was a bit jarring at first, but I don't miss it anymore. It was kind of like trying to stop watching the show "24". The show had its hold until I missed the subsequent episode, then it was gone; I didn't care anymore.