254 karma · joined January 24, 2021
This is an attitude more than anything I'd say, the "follow the calendar" mentality doesn't have to apply to you unless you choose so.
This shouldn't surprise you neither, but that depends on your null hypothesis ;)
> It is a PoC built in my own time cause I don't have time/money or a project.
That sounds like a complain, which might motivate others not to listen to you ;)
If your only or main KPI ignores the social consequences , then you're doing it
> Despite de social consequences.
But I get your point, it's a well known school of thought based on selfishness, I'd guess.
Despite the social consequences.
It's a function of debugging time which is a function of the programmer's skills. I almost certainly fall into the Python subset though :/
There's limited offer because it's a rare skill, not sure what you mean by "not because of my skills" since your skills are rare hence valuable to the market.
> Thankfully for my mortgage, that hasn't happened yet and probably won't happen soon.
The keyword is "hopefully". This already happened to physicists with nuclear power if I recall my history lectures.
An option to buy something at a certain price isn't the same as just getting the something. As mentioned in the article, ceo compensation consists usually of stock + options (et al.) tied to performance targets.
> In effect, isn't this the same as later VCs reallocating the cap table in favour of the founders (and against earlier investor and employees)?
Sort of, that's the point of the article. Apparently, new founders take on too much early financing.
It's not that they don't understand, it's that non-technical people often proactively avoid carefully reading the few lines of relevant documentation. That's something a technical person can tell from the second the non-technical tries to ask a question.
> When monetary incentives and non-developer input inform product decisions, "it's in the docs" just doesn't cut it.
Obviously, you have the right to ask any question if you're paying for someone's time: you become a "client". Otherwise, yes please read the docs.
The technical problem is solvable, but the security and transparency (to the public) are harder to get, specially the security aspect since blockchain technology could potentially help dealing with transparency.
Not if there are laws to keep electricity price within a range. In places like Canada electricity is not necessarily traded in public for-profit markets, and must by law stay below inflation. I agree that in can be a problem in (most of?) the US.
> I really wonder what happens to Bitcoin (or any PoW coin) when it no longer becomes economical to mine new coins.
That might be the equilibrium price, the electricity/production cost. Isn't the pow algorithm smart enough to keep rewarding at least above electricity cost?
Sure, but JavaScript was already there, so I don't look at it as a MSFT idea event though I agree it's technically a msft product.
Edit: typo
That's the key indeed. I think I get it now! Anyway, the simple thing would be counting btc if btc is confiscated and counting cars if cars are confiscated. Then I don't see how it could blow up, but I guess it just can't be that simple.
> but there is nothing that stops you from modifying or hacking it to your heart's content if you are able to.
Are you sure? I haven't read the terms, but that might be quite against their rules. Rules that you probably adhere to by using their product, but I'm not a legal expert.
If it was a car that they confiscated, would they still have the car or would they also need to buy the car today? I am honestly curious as to how this makes any legal sense.