704 karma · joined August 8, 2010
Incidentally, I don't know why your recollection of complaints about China's atrocious human rights record skews towards the (rather few) complaints that are on HN about RMS' choice of laptop, or about the Apple/Foxconn dustup (which incidentally caught several other companies to a lesser extent), but it's not really germane to the conversation at hand.
Incidentally, the new UI for video calls makes the 'end' button the same color as the background, and it is very difficult to see.
When accounting for these things in a total comp calculation, I do it something like this:
$comp = (1 + 2 + 3 + 4 + 5) - (6 + 7 + 8)
where
[1] Salary / cost of living index for area
[2] adjusted value of health care plan
[3] adjusted expected bonuses/profit sharing
[4] retirement contributions per annum
[5] dollar value of stock options given * chance of options vesting at some worthwhile value (tricky to calculate for startups)
[6] expected hours per week over 40 * .025 * [1]
[7] estimated value of environmental and other stress
[8] cost in time, gas, stress, vehicle wear & tear, inconvenience of commuting
Now, it may well be the case that other companies that you looked at had large negative values of 6 & 7, which makes Fog Creek look great in comparison, but I think that as a profession we're screwing ourselves in the long run if we think about uncompensated overtime as the norm and working normal hours as some sort of bonus :)
If you think I'm being too pedantic, a reply rather than a mere downvote would be appreciated.
At this point you’ll have to remember that in C, arrays are represented by pointers to their first value.
No, they aren't. Arrays can _decay_ to a pointer when passed as function parameters, but arrays and pointers are different things. Between these two items, I think the author either a) is talking down to his audience more than is warranted or b) fundamentally misunderstands C.Of course, trying to take the address of a variable declared to be in the register storage class is an error, and taking the address of a variable in the normal automatic storage class typically forces it to live on the stack.
And of course, there are still languages like Haskell that have carved out a nice niche, despite their recent vintage and academic roots.
Now, for merchants this might not seem to matter, as they might be able to always convert bitcoins to a real currency immediately and never hold them long enough for depreciation to matter, but if the currency is excessively volatile there will never be a buyer at the exchange besides speculators, which prevents the currency from ever being really useful.
Now consider how the pipeline, multiple issue, hazard detection and mitigation, and out-of-order execution are implemented.
Ten million is probably an underestimate by a fair margin.