jakemal

There has to be a law about the permanence of "temporary" code.

The number of times I've picked up my phone to do something, see a notification, and completely forget what I had picked my phone up to do 5 seconds later is mind boggling.

I started pruning the notifications that I allow quite aggressively because of it, but it's still a very regular issue.

Is that the only use of the currency or just one possible use?

> It sounds more like a Ponzi scheme in a Gold farming disguise to me.

I would agree with this if the primary income stream came directly from the increase in value of Axies as the game attracted more users. From my understanding, the income comes from acquiring and selling in-game currency rather than from the Axies themselves.

Is this a bullshit job? Maybe. Ponzi scheme? I don't think so.

If people are working this bullshit job, it means that this bullshit job is better than their alternatives. I'm not convinced the existence of these kinds of games is a net-negative.

Is there an equivalent extension to open Hacker News links in an app on iOS? I'm currently using Hacker, but would be willing to switch for this feature.

Hard work is necessary but not sufficient. I agree that the essay glosses over the element of luck that is involved, but I don't think that makes the rest of what Paul is saying wrong. Even if hard work alone doesn't always lead to success, not working hard guarantees that you won't be exceptional.

Really interesting perspective. Thanks for sharing.

I'd like to know the answer to this as well. I'm not sure what I would do if I were to become financially independent before "retirement age", but it certainly wouldn't be getting a job at a BigCo. Really curious to hear the motivations behind it.

I'd bet 30% of the URLs it lengthens are rick-rolls. I did it immediately and sent it to several people on Slack.

It is not unreasonable to request that devs building on top of your platform use an API. They also aren't requiring it, they are simply suggesting it to avoid future breakages when they change the internals of how their application works.

Requiring that they maintain this compatibility would be like requiring the maintainer of an OS library to maintain the contract of a private method because my app relies on grepping their code base to parse the contents of the method.

When you don't have a defined set of public interactions with your app, every change is a breaking change.

I was going to temporarily cancel my NYT subscription because I wasn't using it enough at the time. Once I found out I had to talk to a person in order to cancel, I told them that I would never resubscribe because of it. It's infuriating that they try to use inconvenience to hold your dollars hostage. Why not just focus on making a great product?

I wonder how it compares to the average salary for an experienced hardware engineer. It may be a ~50% pay bump in 1996 vs a 10-25% bump today.