HN user

HaseebQ

651 karma

https://github.com/Haseeb-Qureshi

Posts31
Comments14
View on HN
en.wikipedia.org 6y ago

Mathematical Coincidences from the Physical World

HaseebQ
2pts0
nakamoto.com 6y ago

Introduction to Cryptocurrency (Course)

HaseebQ
1pts0
medium.com 6y ago

Breaking Mimblewimble's Privacy Model

HaseebQ
4pts0
developer.valvesoftware.com 7y ago

Latency Compensating Methods in Client/Server In-Game Protocol Design (2001)

HaseebQ
87pts14
kottke.org 7y ago

Slow TV

HaseebQ
1pts0
en.wikipedia.org 7y ago

Nicolas Bourbaki – Wikipedia

HaseebQ
1pts0
en.wikipedia.org 7y ago

List of Internet phenomena – Wikipedia

HaseebQ
1pts0
en.wikipedia.org 7y ago

“The world wonders”

HaseebQ
1pts0
github.com 8y ago

Yoichi Hirai resigns as Ethereum EIP Reviewer over conscientious objection

HaseebQ
2pts0
medium.com 8y ago

The authoritative guide to blockchain development

HaseebQ
4pts0
www.softmachines.org 8y ago

Technological Innovation in the Linear Age

HaseebQ
2pts0
en.wikipedia.org 8y ago

Wirth's Law – Wikipedia

HaseebQ
3pts2
hackernoon.com 8y ago

Bitcoin is not trustless

HaseebQ
3pts0
www.royalfork.org 8y ago

Layman's Guide to Elliptic-Curve Digital Signatures (2014)

HaseebQ
194pts21
medium.com 8y ago

Anti-Growth Hacking

HaseebQ
2pts0
www.youtube.com 8y ago

That time I used Ruby to crack my Reddit password – RubyConf 2017

HaseebQ
3pts0
hackernoon.com 8y ago

We already know Blockchain's killer apps

HaseebQ
1pts0
www.youtube.com 8y ago

[video] Let's Build a Blockchain – A Mini-Cryptocurrency in Ruby

HaseebQ
1pts0
medium.com 8y ago

Frontrunning Bancor in 150 Lines of Python with the Ethereum API

HaseebQ
4pts0
stackoverflow.com 8y ago

What Is the Rationale for IEEE-754 NaN = NaN?

HaseebQ
1pts1
en.wikipedia.org 9y ago

True name

HaseebQ
2pts0
medium.freecodecamp.org 9y ago

A hacker stole $31M of Ether – how it happened, and what it means for Ethereum

HaseebQ
520pts414
www.youtube.com 9y ago

Why Software Engineers Disagree About Everything (Railsconf 2017)

HaseebQ
4pts0
haseebq.com 9y ago

The time I had to crack my own Reddit password (kinda)

HaseebQ
1pts0
softwareengineeringdaily.com 9y ago

Cloudbleed and SHA-1 Collision with Max Burkhardt [Podcast]

HaseebQ
1pts0
softwareengineeringdaily.com 9y ago

Debugging Stories

HaseebQ
1pts0
medium.freecodecamp.com 9y ago

How Not to Bomb Your Offer Negotiation

HaseebQ
4pts0
blog.interviewing.io 10y ago

We built voice modulation to mask gender in technical interviews

HaseebQ
331pts351
news.ycombinator.com 10y ago

Ask HN: What's the name for an app which someone uses purely for utility?

HaseebQ
1pts0
qz.com 10y ago

Google, Amazon, and Facebook's secrets to hiring the best people (satire)

HaseebQ
8pts2

The thinking at the time was: how can someone under the age of 35 ever have enough accomplishments to be elected president? They believed that would only happen if they were the child of a famous person or former president.

The Constitution was largely written as a departure from the monarchical British system. By not allowing presidential candidates younger than 35, this would prevent hereditary transmission of the presidency. Past 35, a candidate is more likely to stand on their own merits rather than their family or connections.

https://constitutioncenter.org/blog/why-does-a-presidential-...

This is a totally misleading calculation for the largest currencies. It's literally quoting the spot price for what's available on NiceHash and then dividing by the fraction you'd have of the total hash rate.

In reality, as you continued buying up hashing power, the price of the remaining hashing power would go up precipitously. This is basic supply and demand.

I've noticed this is an unfortunately common trope on HN.

"If they actually cared about X, they'd Y!"

I think what you mean to say is: "If they really cared about X, and only X, and had no political/financial/strategic impediments, they'd do Y! Therefore they clearly don't care about X."

Let's not have the perfect be the enemy of the good. This is a good thing, let's encourage more of it, yeah?

I grant your point, but disagree with your framing of the problem.

I think a good analogy here is to compare to American settlers. You're going to have a few waves: the explorers who move into totally uncharted territory and take on significant risk by using smart contracts. These are kinda crazy people who love the innovation, and I'd argue this is the majority of people in the space right now.

Eventually there will be the settlers, who start finding early uses for this technology that can significantly lower costs. Basically collecting on low-hanging fruit. J.P. Morgan, many finance companies, some savvy governments will step in to capitalize on easy wins.

Then there will be the long tail of normal uses. By the time the average company invests in smart contracts, there will be very well-understood battle-tested templates and toolchains for creating smart contracts, as well as consulting firms that are specialized in writing them for you with provable security guarantees.

Right now it's early. Your average company should not use smart contracts, that's a no-brainer. But someday the economics are going to make it a no-brainer for certain things, like incorporation, or issuing shares, or doing payroll, or complying with import/export regulations, or doing corporate taxes, or whatever it is that ends up more efficient through blockchains.

Hey, author here. I tried to write this article to be accessible to people with little background in security and cryptography (hence its publication on FreeCodeCamp), and to be friendly to non-developers. I took a few liberties with the crypto explanations (like calling a private key to a "secret password") in the hopes of making things more understandable for a general audience. Definitely didn't use rigorous language in just about anything here. :)

Completely disagree. Even if you're maximizing for donations, any reasonable analysis would still have to privilege your own well-being as a giver. Lowering your burnout/regression rate from 25% to 5% by giving yourself a higher quality of life seems like one of the best investments you can make.

You don't need to expend wads of cash. But you don't need to be destitute as a software engineer to give effectively.

I see where you're coming from, and I think there are things negotiation does well.

Negotiation allows a company to offer more (or less) than a standard wage when a candidate genuinely offers more or less value for the same position. Economically, that seems like a good thing, and I consider that the principal virtue of negotiation.

But the downside is that negotiation enables candidates who are better at negotiating to command stronger offers (because they're more charismatic, or courageous, or just better studied in the practice of negotiating). That's clearly arbitrary. Negotiating skill is an axis that's mostly orthogonal to the value a candidate brings to a company. Here the public sector's system of having fixed, publicly known wages for positions is a good one. Candidates who are good at negotiating make just as much as candidates who are bad at it.

The question then boils down to how much of the variation in negotiated offers can be attributed to variation value as opposed to variation in negotiating skills.

I suspect it's weighted toward the latter. But if you think it's mostly toward the former, then I think it's sensible to claim that negotiation is mostly a good thing.