skysight-inc/HackerNews huggingface dataset:
I have an 18 month old daughter and I'm currently looking for work, so this question has been incredibly important.

Essentially, I see three major areas where Lauren impacts my job search:

1.) My time is significantly more important.

2.) Equity is less important.

3.) Stability is more important.

My time is significantly more important because I will only have one child and frankly, I don't want to miss her entire youth while I chase my startup dreams.

Equity is still nice, but I want to make sure that if my daughter has the kind of brain and work ethic that could get her into MIT/Ivy League, she won't have to worry about money. Consequently, I invest heavily in her education...both in an education savings plan and via making sure that she is surrounded by intellectually stimulating activities. As an example, consider daycare. It's relatively easy and affordable to put her in a daycare where the kids sit and watch television all day. It's much more expensive to have her in an environment that will use her imagination and where she is cared for by people with an education in early childcare education. Unfortunately, RSUs or stock options don't pay many bills...

Finally, stability is important because finding a new job is stressful. It's significantly more stressful when you have a little person who can't eat your hopes and dreams!

I hope this helped!
Don't you think there might be some implicit bias relying solely on a StackOverflow survey?

My source is that I know plenty of developers working in their 30s, 40s, 50s, and 60, which is anecdotal for you but reality for me.
That assumes we're the only ones in the universe. If there are others, then we are much less consequential (except to ourselves, of course).
If you're paying with cash you usually have to prepay. If you're paying with card the station does a preauth on your card (and usually a temporary hold) then does the final authorization after you finish pumping and it knows the total. Sometimes you have to pump twice if you want to go over the preauth hold amount, which is usually $50.

It's worth noting that it wasn't that way the entire time I was growing up. You would pump first then pay the cashier. It wasn't until around 2005ish that I noticed signs instructing cash customers to prepay.
Giving insurance companies more information simply reduces the scope of what they will insure. Highly predictable risk (I will be dead before I turn 150) is not really insurable. Unpredictable risk (I will be struck by lightning) is. Genetic screening just moves some unpredictables to the predictable column.

Is it fair? No clue. If it turns out that there's a genetic predisposition to being struck by lightning that modern genetic testing uncovers, then all those "struck by lightning" policies will die - they were subsidizing the highly conductive to the detriment of the non-conductive. Hope you're not highly conductive!
> Start moving across borders and you have problems

You have similar problems with bitcoin except they manifest themselves in a different part of the process, namely when you have to convert the transferred funds into local currency in order to use it for goods and service. Trying to coordinate in-person meet ups to exchange bitcoin for spendable money is inconvenient, unsafe and comes with a high markup, it's also a non-starter if you have to transfer the funds to a region with limited electricity/internet access or you're dealing with a non-technical recipient.

> Save long-term in your bank account, and inflation will eat its value away.

Bitcoin does not solve this "problem". The logic behind inflationary economic incentives aside, there is no guarantee that bitcoin's price will continue to rise, it could easily crash to half price tomorrow and recent history shows us that nobody really knows what events cause the price to swing wildly.

> Have political or religious views that run counter to an oppressive regime

As I said, not being operated by a central authority is one of the only benefits of bitcoin, however, in the case of an oppressive regime, bitcoin's usefulness begins to approach 0 since the oppressive regime could eliminate your ability to access the internet or they could just imprison or kill you.
A publisher is anyone who distributes information and brands it under their label. AT&T is not this, AT&T is more akin to the power company. If you're a neon sign maker no one can force you to make a sign that says"Irish Need Not Apply". However if you have a sign that says the above the power company can't turn off your power for it. If you put a tag on the sign that says power by acme power company, then they can shut you off.

This is because by posting on facebook or appearing on google you are implicitly now a representative of them because they're branding is all over that homepage. If you say something that facebook really disagrees with and would rather not say they have every right to not say it.

It's why Cloudflare didn't drop the Daily Stormer until after DS started to try and say the CF was on board with their views.
Don't laugh. My wife has a pair of internet-connected couch pillows. (They're white, and have LEDs inside so you can change their color with an app.)
‘Ranger Games’ Investigates a Crime and a Soldier’s Mind
That's an interesting theory. I've always played a lot of pool, and am good at math/geometry. Yet when I over-analyze a shot and think about what I'm about to attempt, I miss far more often than if I just rely on muscle memory/pattern recognition and take the shot without too much thought.

I think the understanding of angles, intersection points, transfer of energy, etc. helped me practice as a novice (as well as helped me stay interested). But to get really "good" at something, you need to work at it until most of the skills involved are almost subconscious. (Which aligns somewhat with what I recall from "Thinking fast and slow", which I thought was a great book).
You may not have to worry about somebody setting a "delete all data older and/or bigger than Y or Z" but you have to worry about someone running "DELETE FROM table" without a WHERE clause. Which is easier to prevent? The one that can be done through the same mechanism as non-destructive queries? Or the one that can only be modified through a file-system configuration, completely separate from its API?

Regardless, it's a different paradigm with different "don't do that" behaviors that you need to know about.

In Kafka, if you want the persistent, append-only, write-ahead log to not delete stuff, then configure the retention period to keep things forever.
^ Agreed with above -- when I've discussed this with my more privacy-minded friends they always raise a concern about their data getting into the hands of insurance companies down the road, and having their premiums affected. Data security would be something I'd think quite a bit about, but I like the sound of what you're offering.
I don't disagree that it's overhyped, it's just the most recognizable example for me to mention.

> reducing the burden on the bottleneck. That's it, nothing more.

That's precisely it though. By reducing the burden of the bottleneck on the greater traffic network, it localizes the congestion to a smaller area and reduces the disruption the rest of the traffic network has to feel. Overall improving congestion, even if locally the congestion still occurs.

> What the zipper merge is really good at isn't improving flow, it is improving space efficiency.

This is based on the human execution of a zipper merge. Ideally, the continuing lane of traffic will be going at a consistent speed with enough space between vehicles to allow the merging traffic to merge without causing a disruption in the flow of traffic. Theoretically you'd get this benefit from merging earlier as well, but as you mentioned the space efficiency causes cascading impacts to other aspects of the traffic network.

That being said, I only mentioned that as a recognizable example. However, a lot of congestion isn't due to a specific trigger such as a lane ending. It's due to bad human driving habits, and suboptimal human reactions to that behavior. Which create phantom traffic jams[1][2]. Self-driving cars will drive more consistently than human drivers, introducing a level of calm in a sea of inconsistent human reactions. Effectively buffering traffic in a way that will improve overall traffic flow, even before we have majority adoption of self-driving cars.

[1] http://topyaps.com/how-traffic-jams-are-created

[2] http://imgur.com/gallery/CIhYAiv
I've seen "out of paper, cashier has receipt" before. Never seen "out of paper, too bad, no receipt for you" before.
>>> It's more mainstream than the $NEW-AWESOME-JAVASCRIPT-FRAMEWORK.

This sentence doesn't make any sense.

"Mainstream" means used alot - widespread acceptance.

Lisp is #33 on Tiobe after Cobol, Foxpro, Fortran and Ada. How you can compare that to the takeup of the latest JS nframeworks I don't really understand.

https://www.tiobe.com/tiobe-index/

21	SAS	1.372%

22	Dart	1.306%

23	D	1.103%

24	Transact-SQL	1.075%

25	ABAP	1.065%

26	COBOL	1.055%

27	(Visual) FoxPro	0.932%

28	Scala	0.923%

29	Fortran	0.879%

30	Ada	0.787%

31	Crystal	0.756%

32	Erlang	0.733%

33	Lisp	0.690%

34	Awk	0.662%

35	Lua	0.648%
It's just too easy. I never programmed a thing until after I had graduated college and yet when I did start running into times where I wanted a little script or program, it was always less than 100 lines in python to set it up.
Ah cool, I didn't notice that. And I must admit, I am not familiar with how an AST works. My application makes a lot of HTTP requests and is full of async operations. How would it handle this? It wouldn't be able to run most of the code because all of the data is missing...
Well... for a language to succeed long-term, it needs to be either significantly better than the alternatives (at some particular kind of use), or else it needs to be entrenched in existing code.

When C began to spread, it was significantly better than alternatives for writing operating systems and associated tools on commodity hardware. Part of that "better" was cost - cost of the machines it ran on, cost of buying a compiler, and cost of implementing a compiler. (The mistake the anti-C people make in saying "but other languages were so much better!" is that they forget that cost was part of "better".)

C became entrenched in Unix and, later, Windows. But it didn't start entrenched. It started by being better.

If Lisp were significantly better, with everything considered, it should have won by now. I mean, yes, there are a lot of people chasing the current hotness. But the programming profession is not made up entirely of fools and sheep. Better languages get noticed, get used, acquire momentum. (Note well, however, that "better" again is "better with all things considered" - it doesn't equate to "better" as defined by theorists who about how much better their language is, even though it's a little-used language.)
Prioritize, especially when everything is a priority
I understand where you're coming from and agree to a large extent, but I think your hypothetical person's characterization of infix as a "basic capability" is a bit off. It's antithetical to Lisp's design to make use of infix notation. As far as Forth goes, I would say the same thing.
UNIX had a weak design. It won not because it was good, but because it ran on more computers. There are many other OSes of that time period that had superior designs.

The Lisp Machine had way better composition primitives than UNIX's pipes passing plain text around.
> Public transit generally doesn't reduce congestion, but rather provide an alternative to it.

yes it does: http://i.imgur.com/RDHyKBh.gif
> I'd sacrifice my life for my son, but I could give a shit about my great great great great great great great great great great grandson.

That makes sense from a "maximizing your descendants" point of view--maybe.

Assuming a normal sized family losing your son knocks out from 25 to 100% of your living descendants.

Assuming that your descendants on average have average sized families then by the time you have a great^10 grandson you should have a large number of living descendants. Losing one barely makes a dent.

On the other hand, it's hard to imagine a scenario where you could take an action now that would greatly affect (positively or negatively) a great^10 grandson without similarly affecting hundreds of your other great^10 grandchildren.
Today's Issue of Week in Ethereum News
Well "only reacting now" might be a stretch. A few years back they elimintated 40 year mortgages putting them back to 25 years and adjusted the loan requirements.

Canada isn't facing a housing bubble as much as they are facing a debt bubble. Most of the recent household debt that has been record breaking year after year has been with credit cards, autos and lines of credit.
Some people submit their DNA but switch up their gender so as to theoretically nullify the results for a potential future data breach. (Insurance providers being one concern here.)

Does anyone know if/how 23andme addresses this, or do they care?
Because if your genes didn't historically result in an organism with a drive to propagate itself, your genes would have a significantly higher likelihood of dying out in an ancestor generation.

If you do not have that drive, then it is natural to cull yourself.
Strictly speaking wouldn't that be mercantilism?

But I get your point, just substitute any of the human catastrophes of the nineteenth century.
According to TIOBE, in 1987 only C was more popular than Lisp. Thirty years later, C is #2 and Lisp is #31. Lisp was mainstream and for some reason other languages overtook it. I think it's a good question.
Imagine the shock when our descendents wake up on Jan 1 2118 and all their systems are accidentially running on a 100 year old JVM :)
Co-founder of Standard here. I agree. Our goal is to use this technology to streamline our lives, not to invade privacy. We don't do any biometrics or facial recognition, and we don't send video to the cloud for central storage. We have a fully on-prem solution. The only need for Internet is to push out updates to the local system.
> Without the humans, the universe is empty.

Max Tegmark adds a twist to that statement: without consciousness (subjective experience), the universe is pointless.
I don't even disagree on the infix math point, really. I do find it awkward that it makes up a small fraction of what you actually do in most programs. Seems odd that such a minorly applicable point holds such high regard.

Sadly, I assert that this being the main irritation of LISP is one more of fashion than it is of actual applicability. Sad, because I do have pride in our communities to want them to be above fashion. Most people that "hate" LISP have never written a single line of it, ever. Nor will they ever do so.
Wild African Dogs use Sneezing as “an act of democracy”
I think underlying many of these discussions is a fundamental question:

"If not all cultures and values are equally successful in modern society, should we (as a society) encourage people to adopt a more successful values, or should we adapt society to make all cultures and values equally successful?"

(edit: obviously I have biases, but I tried to phase this in a way that masked my biases. If there's a more neutral way to phrase this, I'd be interested in hearing it)
Once you are dead you won't enjoy it and you won't care, so there is no reason to prefer life to death by that criterion.
Yes, it's actually quite interesting! It's a recurrent observation that we have inside the team with our own voices. Friends of the person usually better appreciate the quality of his/her digital voice. You can also observe these reactions to some extent on twitter: https://twitter.com/LyrebirdAi

Other interesting observation are the sentences that people generate for the first time with their digital voice...
And they won't need as much space for backing/driving- especially if they can communicate with each other- a car that is blocked in could signal the other cars that it needs out, and they could move to make space for it to get out.
I was just looking at that same list. I'm surprised Lua is that low considering how many applications embed it.
Maybe no society that suits our instincts can scale like that? Perhaps we are just meant to live in thirty-strong groups.
Jumpy water bugs
An Update on Information Operations on Facebook
Doesn't natural suffering of creatures far outweigh anything humans experience or inflict? Plus, we've made life better for countless animals through domestication.
Prediction: In the future Flat UI will be perceived similarly as bad retro "80s sci-fi" (like "Hackerman" from Kung Fury wearing a dataglove, etc), in the same sense that it will only have a "nostalgia" aesthetic, not because it was any good.

Once we move past this madness, after a while we'll look back and see it for the unusable "mystery meat navigation" (remember that from the early 2000s web?) that it was. Trying too hard to look "clean".

In as far as Flat UI was usable, it's because of its ubiquity and that after a while we had to get used to it and somehow managed to obtain a somewhat common UI vocabulary.

Like the "hamburger menu", completely unintuitive until you learn what it means. I'm afraid we're gonna be stuck with that one for a while. It was supposed to depict a super-stylized drop-down menu, right? Except that some menus are now a grid of icons.

... and in Chrome the menu is three vertical dots, because ummm it makes people turn their head while thinking "...", I guess. (I was looking at Firefox when I described the hamburger menu).

At least the gear-icon for config/settings makes some sense.
This is exciting I've been following you guys since at least May. How do you plan on getting the voices out of the uncanny valley?
Well, it also makes people less likely to own homes, and I'm not really convinced you couldn't have a relatively cautious system that still had long, federally backed mortgage terms or tax deductions or even relatively low down payment options. The big crash was preceded by lots of outright fraud.
Dang. It was an AMP link and I must have cut the entire first half on accident.

Link: https://www.theregister.co.uk/2017/09/05/flat_uis_designs_ar...
There's not just one reason for it.

Kafka lets dependent consumers transform that data into whatever model is appropriate for their use case. There's no one-size-fits-all E-R model for data for all use cases.

It's not just working around db migrations. It's also providing you with the ability to model the data as many ways as you require. How else would you do it, materialized views? How often are they materialized? Regular views? How performant are they?

There are many benefits to this approach, and a lot of them require a different way of thinking. It's a different paradigm.
And the question below that is, who's "we"?
A big problem with your site is it links to stuff as if its significant/important/real. Nearly every single variant I followed through on was basically bogus. An intronic variant with like 50% of the population having it.... Literally doesn't matter how many GWAS studies have associated that with a greater risk of breast cancer. The risk difference by definition is nothing. Its meaningless to state clearly on your site "breast cancer". You might want to avoid ethical/legal grey areas. But who is your site aimed at? It has none of the information a scientist would want, or a clinician would want... But does have misleading absolutist linking of variants with papers and diseases?
Realistically, if he weren't opting to be as terse as possible, this could be rewritten as:

var state;
if (typeof behavior.init === "function") {
state = behavior.init();
} else {
state = {};
}

I do enjoy terse ternary operations but they can get very ugly very quickly. I often stick if/else if I'm writing code for others. As far as choosing another language, write Python that gets executed on Chrome without further trans/compilation and I'll happily consider it.
The Trophy Woman of Ready Player One
5x seems extreme, but I'll certainly grant you 2x on the freeways.

But if you put twice, or worse 5x, as many cars on the freeways, that'll just jam up the urban core even worse than it already is. And self-driving cars are probably less efficient than human-driven cars in the urban core simply because they're much less aggressive in their interactions with pedestrians and cyclists. This is a good thing, but it will increase congestion.

Efficiency improvements can only add increase capacity by a fixed percentage. The massive improvements in cost ($0 in labour!) and convenience will cause usage to increase by orders of magnitude, IMO.
As a day-to-day developer, but one who wants to learn as much as I can outside of my domain, you are spot on.

I generally work in an OO language (C# specifically) and have long wanted to get into functional programming. I am finally making headway, but after false starts in lisp (racket, clojure) ultimately I am using F#. Partially, admittedly, due to the .NET aspect (its even shipped as part of default dotnet core) but also because of the lack of parenthesis.

One of the reasons to go functional was to get away from the excessive syntax and formality of a C-based language, and replacing every curly bracket with 20 parenthesis (minor hyperbole) doesn't achieve that for me.
What we would do is have a single aggregate representing the entire state of a micro-service. For instance, for the "Orders" micro-service, it would contain all orders in the system, with events such as OrderCreated, OrderPaymentReceived, OrderShipped, OrderCancelled, and so on.

Then, we would have a materialized view that would be a single C# immutable object (canonically called `State`) that contains a dictionary of every order, and maybe a few indices (such as "identifiers of orders currently waiting to be shipped out" or "list of orders by customer"). Everything fits in memory, so every query is simply a bit of C# code that traverses the in-memory graph of objectd rooted at the `State`.

A command emits events, which are then applied by the system to create a new `State` from the previous one. Events emitted by other instances of the application are also fetched by the system every so often, and you can request a "force catch-up" to guarantee that the `State` you access takes into account all events appended so far (so that you're certain to see the results of your actions, even if the load balancer bounces you from one instance to another).

Here's what we use: https://github.com/Lokad/AzureEventStore
These issues certainly keep me awake at night. I'm really glad that we have laws like GINA that protect us from having our medical insurance change due to genetic testing. I hope that congress preserves these protections, and further applies them to other forms of insurance (like life insurance).

This nonprofit of mine was born out of a lifetime of dealing with a rather serious medical issue. With full genome sequencing, I was able to finally diagnose myself as having a rather severe mitochondrial disorder. I've been worried that knowledge of the mutation would affect my medical care, but I finally reminded myself that the mutation was already making me quite ill to begin with! The biochemical concerns are now much more worrisome than the hypothetical insurance or discrimination concerns. I've grown relieved in the realization that finally knowing whats up will likely do more good than bad.