skysight-inc/HackerNews huggingface dataset:
Are you positing that an enormous differential in genetic supply will result in no difference in reproductive strategy and therefore no difference in evolved psychology?

Or put another way, that everything we know about supply/demand curves and evolution is wrong?
Functionally, it's fine. The user experience is awful though.
Whuffie – how to build a reputation currency in Ethereum? (2014)
Don't take the risk.

Treat is as a lottery ticket. A good friend joined a late startup company in 1999, and in 2000 he was worth 40 million, of which he managed to cash out 10 million before the stock crashed. But that was in the days of IPOs, now the investors prefer to keep the rise in equity to themselves. So you chances of winning the lottery are much less.
While I think @coffeemug's analysis is good, I think it glosses over the core issue: money.

rethinkdb's core issue IMO was that they took VC money, which did two things:

- mandated that success had to be a home run

- gave them a fixed runway

Sure, rethinkdb made some mistakes, but I think those were successfully corrected. The problem is that those corrections were too late and they ran out of runway, and the success looked more like a triple than a home run so they couldn't go back to VC's for more.

Of course, not taking VC would have slowed things down even more, but that's fine. The primary attribute many look for when choosing a database is trust, and trust takes years to earn.

mongodb vs rethinkdb is very comparable to mysql vs postgresql, and I think the final results will turn out very similar. mysql did very well and was the leader for a long time, but today postgresql is the clear favorite.
The typical approach seems to be to consider all the visible satellites together (rather than solving for the position indicated by each constellation and averaging them).

So in practice having more satellites means that a good position measurement is possible more of the time.
> You should only go into the outer lanes to overtake traffic, and then move back in once you've passed.

Not in the US AFAIK (or does it vary by state?). My understanding and experience is that driving in the lane of your choice, and "undertaking" (overtaking on the inside) are both legal and common practice.
Except you are missing how salary works.

It is never "You create X value. We will pay you .5x" (Outside of very niche places like Trading).

99% of the world is "Oh you made X at your last job? We can pay you X + 10k.

Hence the older dev tends to make slightly more salary than the younger dev, even if the skillset was similar. And by older, I mean years of coding not physical age. If a guy was a chef for 20 years and a programmer for 3, he is the same programmer age as a 3 year out of college guy.
I starter living the dinosaur a bit more when I learned about its history

https://www.jwz.org/blog/2016/10/they-live-and-the-secret-hi...
For me personally, if I was in that position I would stick it out for however long it takes. I cannot imagine having enough liquid assets to be happy to risk $100k like that. I am also of the opinion that even if I did amass such value in equity that there's a high chance I'm going to get screwed on whatever the book value of it today is tomorrow when I actually cash out. If it's so bad that I need to run not walk out of the building then I'd have to just make peace with binning it off.

For most of us where startup equity comes with a real valuation of zero (i.e. anything but the Uber or AirBnBs of this world) - I think you're a lot better off ignoring it entirely.

> to walk away from this situation with nothing

This is where I think you are healthier having at least a market rate salary. Then you've not walked away with nothing - you've been a regular employee and happy with your lot and ready to move on.
25 lessons from a 25-year-old CEO
That's what we did, at my partnership. Except that was 1998-2006 and we only provided 5 weeks that don't roll over. I used 4 weeks one year. The rest of the years I barely got over 3. Personal choice though.
> Love for static typing is basically Stockholm's syndrome

Funny, that's sort of how I feel about my (long) time "loving" dynamic typing. Now I find it is such a relief to validate data once on the way in and completely trust it to be what it says it is thereafter. I found dynamic types required more bureaucracy (if I wanted to sleep at night) in the form of unit tests and precondition checks everywhere.

YMMV I suppose.
And the windows 10 anniversary update literally caused my computer to freeze for up to 30 seconds every time I tried to interact with the task bar.

These things happen with all companies.
Yeah, my perspective is that Mongo just positioned themselves well in their marketing. They became a default option as part of the MEAN stack.

I wonder if Rethink somehow piggybacked on React or Angular in the same way...
These questions are still from the perspective of someone with money, education, and options. Imagine you're talking to someone below the poverty line, not your friend with a comfortable but unsatisfying job.

> Willing to move for the job?

Sure, how? What if I have no money and no credit? You're asking me to come up with a down payment on an apartment, transportation to another city, some kind of rental van or moving service, and a landlord who will take someone like me.

> Willing to work in a related field until you can get into your first choice?

Related field? I can't get anything above a minimum wage job. My "first choice" would be literally any job with predictable pay and hours.

> Willing to switch jobs 3 times in the first 5 years?

I'm working three jobs right now so my family can eat.

Again, this is not a contrived example. Millions of people live like this.
12 excellent non-US cities for software engineers
There's a lot of advice to value your options at $0. I'm curious how people do the math when considering moving from a big company with RSUs that are liquid at vest to a startup (doesn't have to be a unicorn). Big company RSUs can be a big part of your annual total compensation. Do thinking about a "fair market salary" do folks consider that their base + risk adjusted RSUs? Seems like the best advice I've seen here that might be applicable would be to negotiate down equity in favor of base comp. especially if you consider that equity will likely be granted as bonuses during your tenure.
This reads like a Faustian bargain. I've seen this sort of stuff happen over and over to my colleagues, it was worst in the late '90s and early '00s. As much as I wanted to work for a startup once in my life, I learned that the only way to do "startup" is if you are the founder. Practically everyone else is along for the ride.

The US used to have a steady IPO market but that has dried up in recent years. I have read that 2017 might brighten things a bit, but we'll see.
Operations will not keep Apple alive. I mean Jobs was a genius in knowing what people want, but he wasn't good at knowing how to replace himself. It's outside his abilities just like it's Cook's abilities to be creative or to know what people want. Operations people are good for operations, and nothing else. And usually hated by many people in the company for the policies they force on the company in order to improve the bottom line.
> As the mailing list software should use its own domain for the bounce addresses, the mailing list operator can set up SPF to authorize the mailing list server as an outbound server for that domain just fine

This will make SPF pass but it has no effect on the DMARC result. For DMARC to use the SPF result, the envelope FROM needs to be aligned with the header From. Pretty much every mailing list already does what you've described but it doesn't help with DMARC.

> As for DKIM, you simply should not modify the message

Many mailing lists modify every message to add a footer with unsubscribe information. Others only modify some messages when necessary such as to convert HTML messages to plain-text, to strip attachments, to wrap lines to 72 characters etc.
If you keep on following every hype-train yea you will get over complicated software development.
I hope my finished writing is as good as your draft.
Unless it was considered worth the effort to try and see if they could just jeopardize the system financially. For example, nation states have the capability to compromize industrial operations with specific viruses. If a uranium enrichment centrifuge can be targeted I don't think any system can be guaranteed to be infection free.
Confusing, especially with "Moz" being one of the bigger players in the SEO space. Google "moz://a", you're going to get mostly stuff about Moz.

Good luck dethroning an industry leader in SEO at... SEO.
I agree with most of your comments. I think as a fairly new profession we are still finding our feet when it comes to best practices. I don't think there is one system that will work across the board for all trades. I mean I would think it took longer than 30-40 years to work out the best way to plumb, wire a house etc.

Sometimes when estimating work, I think how long would the same project take to build 5, 10, 15 years ago. It's not often that time spent coding today is any quicker than before.

Arguably we get better quality software now with unit tests, better compilers and better tooling. Perhaps I've just got some massive rose tinted glasses on!.
Maybe he's too busy closing down Gitmo right?
Goodness. Seriously? Another notes "app"? Longevity exists in ASCII text (UTF-8 if you must be a Modernist). Portability exists in simple plain text files. Privacy exists in keeping them on your own blankety-blank drive and backing up your own files somewhere that isn't a fluffy cloud. Or back them up there if you want.

Oh, now someone will say, but what about photos and images? What about "clippings" from the web? Images are to be in a properly tagged image library. And a dozen software solutions have already solved that. Documents are PDFs or TIFFs or JPGs or.... something like that. Put them in, gasp, a "folder" ("directory" for geeks) and call it something like "documents".

I don't know what "notes" people are so desperate to save, but if they are your own ramblings... plain-text. If they are writings, make a folder called "writings". Use markdown or ReStructured Text if you must, but trust me, the "must" is your must. No one else cares. It will all burn eventually.

Plain text will still be here as it has been for four decades. Your app, OneNote, EverNote, NoteyNote, and all the rest will all burn. Or be hacked. Or stolen. Or not be backwards-compatible with whatever new NiftyNote comes along.

Plain-text. Stop making these. The problem was solved 40 years ago. Solve something else. Maybe Cancer. Maybe how to install Windows 10 in 3 minutes or less. Maybe public transportation.

But for all our sakes, no more Notes apps. You are actually accomplishing the opposite of what you set out to achieve - further distracting people from an ancient standard which works Just Fine For Almost Everyone.

By the way, if you are That Guy (you the reader) who thinks your special (said with a lisp) notes deserve better than Plain Text, you probably are wrong.

Same with To-Do list apps. Plain-text. Just write down your tasks - and then go do them. Stop prioritizing, colorizing, making 'sub-tasks', attaching deadlines, putting time estimates, "sharing" them with others (oh for the love of all things holy, stop sharing anything), and adding javascrap drag and drop junk to it. Either buy Microsoft Project and use that or use Plain Text. There is no in-between - just clutter. Lots and lots of clutter.
> This implies that Citadel is buying the stock before selling it to you.

Large firms do this business as usual. They maintain inventory and sell it to their customers directly, while still reporting the trade to the market audit trail. This is usually done by the private brokerage side of the firm executing all trades through the public investment side, and the investment side just executes the trade against the house inventory instead of a third party buyer/seller in the market.
>Why would a user's password have an extra character on the end anyway?

That seems the strangest of them all: "If the login fails, try stripping a character off the end and see if that matches". I can understand the "First character inadvertently capitalized one" somewhat, but the CAPS LOCK thing seems unforgivable. I just did that yesterday with Apple and it simple suggested to me caps lock might be on. If your test for that is (password didn't match AND all alpha characters in the submission are capital letters) you don't even need to store a second hash for it.

I know there will always be trade-offs between security and UX but, if this image is accurate, that seems like going too far in favor of usability. No matter how small, multiplying the numerator in the probability of matching a password is a dangerous decision.
It's not a best programming language fight. In my experiences in the industry, an enormous of amount of technical debt and operational inefficiency is accrued when someone ignorant of how machines and processors actually work (SIMD, cache, pipelines, threading, etc) is in a leadership position to dictate the toolset for solving problems.

This wasn't a noticeable issue until about a decade ago. But it is now and it continues to get worse IMO. The "programming language" bit is just one of its symptoms when the root cause is ignorance of practical computer architecture.

That said, the mentality of throwing all big data problems at Hadoop clusters with 4 year-old GPUs and flaky 10 gB interconnect (many of which could be solved faster on one.big.modern.and.cheaper.machine(tm)) is working wonders for my Amazon stock so maybe I should just shut up and get rich?
I wrote a BitTorrent client that specifically only downloads the parts you need to perform some operation: https://github.com/anacrolix/torrent
IMO, the amount of vacation you're actually permitted to take culturally is completely orthogonal to the vacation policy. I've worked in places with a fixed # of vacation days where it was absolutely unacceptable to actually take those days.
Amazon patent hints at self-driving car plans
Now, that is a valid concern. So far the first I read. Maybe some countries in Europe also wanted to see Snowden catched.
I should clarify, the logotype “mozilla” and not necessarily the dino logomark. The original is more legible, less cryptic.

They also based their new typeface Fira Sans off that original logotype, which is what they use to brand Firefox. So they also fragment that brand association.
We have a few tie-ins too, but only for Bitbucket stuff like feature branches and occationally Confluence.

What's a better alternative to Jira though?
Whats the over/under on Scott Forestall coming back in a Job-ish way to help "win" back mindshare?
When the second generation won't exist for half a decade, I don't think the old rules are still in effect.
> Russia but unlikely because they have no competing system.

Russian GLONASS had full constellation in 1995, then during late 90s it had breakages, but was fully restored by 2011 again.

EU Galileo has full constellation planed for 2020.
I'd add a few things:

- You probably won't have a 10 year horizon if you are joining a company that is now a unicorn. You likely will if you found a company that later becomes one.

- Sarbanes-Oxley is a big villian here. It pushes the cost of legal compliance through the roof for public companies, forcing companies to delay IPOs until revenue is higher. In addition to delaying liquidity events, it prevents small traders from owning stock in companies that are ramping from ~100m valuation to ~1b, which is why there are so many unicorns now. This hurts normal investors big time, and helps people with access to private markets. (source: friendly neighborhood VC)

- the article doesn't go into AMT, where the IRS forces you to knowingly overpay tax when you exercise ISOs, then (slowly) pays it back over the years.
Swedish supermarkets replace sticky labels with laser marking
Threading can be preserved when creating a new message as long as the mailing software re-uses the same: 'message-id', 'references', 'in-reply-to' and 'thread-index' headers.
That's not entirely true. DHT is generally the most effective, but PEX and trackers help a lot when there aren't many seeds, or there's a lot of noise on the DHT.
Early proposal for Type Classes in C#
>but I have the impression that they mostly exist to burn through the millions they get from Google

Isn't the money from Yahoo now?
To be fair, there are only 3 signatures for the forEach() method, the reason that section is so noisy is because it's followed by forEachEntry(), forEachKey(), and forEachValue(), each of which has two signatures. You technically don't need those other methods, but they are convenient to have. I find "map.forEachValue(1, Foo::bar)" to be more clear than "map.forEach(1, (_, v) -> Foo.bar(v))".

Manual composition can get ugly if the argument is used multiple times, especially if the function is non trivial. Say something like

map.forEach(1, Expensive::func, x -> x * x)

which would naively manually compose to

map.forEach(1, (k, v) -> Expensive.func(k, v) * Expensive.func(k, v))

which is going to be less efficient, doubly bad if that function has side effects, and noisy on top of it. You could assign the value to a local variable inside the lambda, which gives you

map.forEach(1, (k, v) -> { int x = Expensive.func(k, v); return x * x; })

which fixes the efficiency and correctness problems, but is a bit too verbose for me. There's probably other situations, that was just the first one I thought of.

Honestly, though, it all comes down to taste and the situation. I personally would use manual composition excepting circumstances like my example above.
Google is reportedly bringing Android One phones to the US
What about browser's (says Chrome) auto update feature? Security theater too?
While I like that idea (paid extras to deal with pain points), it puts developers of the base product in a weird position. They are incentivized to ignore user complaints on one codebase, as that's a business driver on the other codebase.

Nothing new, just a strange place to be in.
We citizens have very little say in the machinery. That is the biggest problem we face these days. Regular people have no agency at all and there is a sneering elite that runs things from the coasts who believe everyone else is a sheep to be sheared for them.
You are incorrect, but I can see why you would be confused, since so many people pick the left lane to go slow in. I think they imagine themselves to be some sort of force for good, slowing down all those evil speeders.

Here's a summary of the law, by state.
http://www.mit.edu/~jfc/right.html
As others have mentioned, it will be difficult to work your way out of this if you're working more than 60 hours a week.

I've seen quite a few employers who have health insurance that covers stress leave. You might qualify, since what you're experiencing is often the result of long term chronic stress.

How amenable your employer would be to this is another question - if they've seen what you're capable of,and they know how difficult it is to find a capable developer and bring them up to speed on the company's product, they might be open to giving you a month to recharge.

Even if it's not covered by insurance, perhaps an unpaid month off is something you could negotiate? Again, it's very dependent on the employer. I've seen it work, though - and in most cases, the employee almost didn't ask because they'd convinced themselves it would be impossible, but the employer didn't see it as a big deal.

I've been in the position you're in - where you're just staring at the screen, unsure of what to do next. I found it helpful to take steps to restore my creative abilities - I'd lost touch with them after spending years just focusing on code. Being great at writing code is useful when you know what to do, but all the programming skill in the world doesn't help when you can't envision what to do next.

I found The Artist's Way[1] helpful here. Some people like it, others don't. I suggest reading some reviews on Goodreads ahead of time to develop an understanding of whether or not it would be a good book for you. A newer book along the same lines with a slightly different approach is Let the Elephants Run[2].

At the end of the day, your approach to getting past burnout is going to be a personal one. Things that have worked for others may or may not work for you. Keep in mind that many of us have been where you are, and we've been able to work through it and become productive again. You can (and will), too.

Just remember that you didn't get into your current state over the course of a few days; it's been a long, slow grind that has worn you down over the course of years. That doesn't mean it'll take you years to get better, but it does probably mean it would be helpful to treat this as a recovery process that will start small and show progressive gains over time.

(Amazon links, but no affiliate codes or anything dodgy like that (: )
[1]https://www.amazon.com/Artists-Way-25th-Anniversary-ebook/dp...
[2]https://www.amazon.com/Let-Elephants-Run-Creativity-Everythi...
A part of their success was timing. When they came out I didnt know of anything else that could allow you to store JSON objects and do queries on them. Just that ability was a big deal. I believe the mainstream alternatives was to serialize your JSON object and store it in a text field.
What's surprising to me is there wasn't a way to get the ride data other than paying somebody to scrape it.
It might be easy for the US to shoot down satellites, but so it might be for Europe.

The whole point of this story is that the USA wants to be able to act without Europe possibly having a say. That Europe agreed was wrong, I think.
It has always baffled me the way founders treat employees and investors so vastly asymmetric. Ive been involved in rounds close enough to see how just the "hint" of a potential investment and all the numbers, financials, cap tables are sent in one big email to their analyst, while some early employees (who controversially have worked just as hard as the founders) have no clue who owns what and whats going on.
I get it without money we can't build anything, but without good employees everything else is multiplied by 0. The math in the article is unique to the U.S but I think the "essence" behind it is quite universal.

What stops founders from offering a company wide "vested Share vs. Cash" with an equal cap for everyone on each new round ?
For e.g founders planning to sell 10% of their own share while raising round in the so called "Take money off table", all employees get the 'right' to exercise the same option, hence instead of dilution to the new value its straight selling the value they created ? what are the arguments against this ? For the investors its the same, and if the cap of how much of the vested % you get to sell is kept realistically low it should not risk decreasing the value of the private stock.

while i agree with Jaymzcampbell as an employee you're better off with dropping the "hope" the paper value of what you own means anything, however its contradicting to the popular piece of employee incentive tool that is quite essential in acquiring& keeping good talent.
Compiler that regularly crashes. Dev environment that regularly crashes, behaves strangely and is full of bugs. Really long compile times.
I thought I could exercise my options 5 years after sign date, regardless of liquidation. Have I misunderstood or do I have some special deal?
Compliance cost.
They are codes for FOIA exemptions. http://www.foiadvocates.com/exemptions.html
also Chase.com
Interestingly, that's not legal in California. Vacation is a form of earned income, and must accrue and be paid out at separation. (You can cap accruals, but vacation accrued must be paid, and can't expire.)
Mozilla's minimalist new logo just leaked
Software is getting less reliable as well.