skysight-inc/HackerNews huggingface dataset:
> If you've been with someone for a year, you know how bad your worst fight was. Chances are though, whatever it was is a sampling from a distribution that you've only sampled a small amount of.

But you also need to sample across different partners. How many partners do you need to sample to evaluate whether the fights you have are on the better or worse end? Then there's only so much time in life. Also you change and get more mature. I don't think I learned that much from the relationship I had at 19 than at 25 and again at 30. Choosing one partner for life, while not impossible, is pretty flawed because you never know how both of you will change over the next 10 years. Plus the general problem with us humans that we're just never content with anything for extended periods of time. The grass is always greener on the other side of the fence. By that logic, don't even start a relationship ever. Stay single, so you don't have any responsibilities. Slightly dissatisfied with your current job? Put in your two weeks notice and see where life takes you. Shouldn't be to hard to eventually get another job in tech. Moving shouldn't be an issue at all. Unemployed for a year? No problem, you got plenty of savings, since there is no nonsense like college funds for any kifds going on in life. Only that eventually you might wonder if your life might be incomplete without having raised your own kids... That green grass stuff again...
> It daunts me how much software is getting unreliable, but trying to shame people to hold them accountable is naive.

> The root of the problem is the uncontrolled complexity of modern software products.

I think there's a feedback loop between those two things, especially when it comes to government or giant corporation projects. Lack of accountability causes accidental complexity, which in turn causes a lack of accountability.

It starts with a organisation that lacks tech leadership hiring a consultancy, which then treats the project as a "flagship engagement" which means trying to make everything perfect, where perfect is used in the context of the number of future sales-pitches that will cite this one project.

As a result, there's a gap between what the organisation needs and what it gets, which adds to the amount of work required and complexity to navigate, whenever changes are required, and the overall complexity snowballs from there.

Most of the above is business-as-usual for most very expensive projects. The real danger-zone is when you get to the third iteration, six or seven years down the line, and you're forced to re-hire the first consultancy again because they're the only one with the resources to take it on; but the tech-world has moved on, so they see you as a "modernisation engagement". They simultaneously can't criticise their own bad decisions from several years prior, but at the same time they want the wider-industry to see their "transformative" power, so can't merely iterate on what's already there either.

That's how you end up with iOS apps, talking to Ruby-on-Rails APIs (which used to be the primary web-app, before that was replaced with a React frontend), reading and writing from an Oracle database which is also updated with a series of batch jobs dating back to early 2000s Java EE.

The "coal face" developers in all these situations have done the best work to their ability, and quite often achieved minor miracles in stability given the underlying complexity. The problem is always a management (or lack-of management) problem.
To a degree this is true, but they do find the abundance of some "amenities" negatively correlated with national income, some of which, like "marketplace" make more sense than others (like "hospital", at least until you consider not all hospitals are equal and the state of the art ones tend to be big...). When it comes to ATMs being more commonly depicted in lower income countries (within the sample) it's an interesting question whether that's because they actually are more common or whether they're more commonly marked on OSM because locating them is more important to people in a cash economy (cf most of the ATMs near me are unmarked)
Couldn’t dump a truckload of baking soda?
The IOTA project http://www.iota.org is a dystopian mess at the moment but ternary computing, the internet of everything, the tangle paradigm instead of blockchain and fee-less transactions are what many are dreaming of and possibly at hand even before quantum computing (therefore sooner than later).
Indeed. It's awesome that they are beating projections, but even so, the rate is far below what is needed to decarbonize the energy sector by mid-century which is what we need to keep warming below 2C.
Eh, I wouldn't exactly be a martyr for these deleted comments.

dulac91 has been "leaving Elm" starting at least six months ago, supposedly only still around to let others know of his decision.

superdisk and type_level_memes are piling on about how much Elm sucks in multiple comment threads, random examples being "Elm's BDFL is just a DFL" and "Elm is not the language for [me]. Or... anyone, apparently, since writing Elm code can be considered a liability at this point", respectively.

This sort of dismissive toxicity just begets more of it and turns off newcomers.

Sometimes you have to make your point and then leave the theater so others can enjoy the show.
An even better (or possibly the same, I'm just restating you more verbosely) recommendation would be one which gave you a mental framework to help you organize your thoughts around the situation so that you can be confident in exercising your own judgment.

Books which are good for helping lay out such a mental framework include:

- https://www.amazon.co.uk/Decisive-How-Make-Better-Decisions/...

- https://www.amazon.co.uk/Too-Good-Leave-Bad-Stay/dp/07181417...
Severance is not in the law in germany. Notice periods are, but there are some substantial differences. You can’t take on a job after having received or handed in your notice - you’re in principle still expected to work. If you just decide to not show up, that’d grounds for immediate termination.

Both sides can agree by contract to terminate the employment immediately (Aufhebungsvertrag) and those contracts often stipulate a severance, but for example they also often stipulate that any wages from jobs you take on in that period get deducted from the severance payment.
Yes.

Athens picked their Senators by lot, and we probably should consider it.
FYI: You're replying to the person who wrote the article.

That said, I do think he's raging against people pointing out Survivorship bias [1] rather than Confirmation bias. But perhaps the confusion between the two is the reason he's missing the point: the "critics" are not so much pointing out that a successful person's advice is worthless and that their success is sheer luck and that therefore you shouldn't try - it's that whatever worked for them might not work for you, and whatever did not work for them might work for you. In other words, don't expect a successful person's advice to be a magic formula, and don't be discouraged if their advice seems unattainable for you to follow.

[1] https://en.wikipedia.org/wiki/Survivorship_bias
Aren't all Millennials over 18 at this point?
GraphQL Server Tutorial with Apollo Server and Express
>It daunts me how much software is getting unreliable, but trying to shame people to hold them accountable is naive.

Has it been getting more unreliable? Software is being developed, bugs are getting fixed, new use-cases are emerging faster than anytime before.

If it seems like software is getting more reliable, maybe its just that we're relying on it more and more.
What advertisers need to know about blockchain now
No notifications on iOS safari, btw.
I work as a biostatistician and I've been tasked recently with querying large databases using SQL, in addition to analysing the data. However, my programming background is very limited and thus I'm sure my queries are very inefficient.

Could you point me to some materials/texts about how to improve querying efficiency for SQL? If it's oriented for beginners then that would be ideal.

Thanks in advance.
All career advice for women is a form of gaslighting
Nate Silver of 538
> in the fast spectrum chloride salt are better, in the thermal spectrum flourides

Would you mind expanding on this? Why?
> It's an alpha pre v1 language

Not according to the homepage. According to the homepage you should install now and it's already used in production by major companies!
Let be preface by first saying, that when this gets off the ground. There is going to be a huge learning curve. I am humble enough to say, I don't know what I don't know.

So, I will have to meet the challenges and handle them as best as I can.

That said, from what I understand. There are companies which have developed ML tools with government assistance from the UK. That can detect whether a video is terrorism.

So if you run with that thread, perhaps similar tools will be available to the other content.

I'm sure as time goes on, other complex systems will evolve to meet said challenges.
This is an interesting analysis and can only really be accurate if we assume the level of mapping and number of mappers in an area is the same from area to area. I don't think this is true.

However, its possible statistics to find the number of mappers and the level of activity in an area from OSM, so a better analysis should normalise for this too.

But! This only considers OSM from the point of view of a "hobby mapper" - the old school view of individuals going out with GPS units. Today a growing proportion mapping is contributed by governments, open data sets, batch imports, businesses and mapping teams, all of which vary by geography too.
> It daunts me too, and reminds me of the early-days of commercial flight. I hope we'll have a similar "we cannot continue like this moment".

The first citation of the words "Software Crisis" meaning the inherent difficulty of writing high-quality software in a predictable way was from a NATO conference fifty years ago: https://en.wikipedia.org/wiki/Software_crisis

It is taking a long time for good practices to be discovered and win-out, and even when obvious improvements have been made, they're not necessarily used effectively.

I suspect a large part of the reason why the software industry isn't maturing at the same speed that other industries have had to, is that in software, failure is much easier to hide.
Well, like I said, we're in the realm of a semantic debate, and I'm definitly being pedantic.

But, as I see it, records and types define only data. The former as an immutable map with pre-defined keys, the latter as a fixed set of data fields. Thus neither are an object.

Protocols define only function signatures, without data. More like interfaces. Thus it too is not an object.

Why am I being pedantic? Because data and functions are never coupled in this case. But in traditional OOP, an object groups data and methods, and are thus coupled together tightly.
Fastmail is down (again)
"Both are significant at the p=0.04 level, and fortunately I don’t think Levitt had many if any opportunities for specification mining here to artificially drive down the p value."

You guys will fall for anything, won't you?
> why can't we just by default build the reactors underground?

It would appear to carry an increased risk of hidden problems and groundwater poisoning. There might also be issues with corrosion and accessibility for maintenance.

That said, I'm not ruling it out. A lesson these new approaches to nuclear engineering is that we never figured out the right defaults the last time around. We were too focussed on making bombs and submarines.

> we already know the impacts of underground nuclear explosions

Nuclear plants should never fail by way of nuclear explosion. If this is a possibility it is a bad reactor design.
Considering this is the second time in one month, I think I will be transferring to some other provider.
Some years ago, I was bored and made this javascript version:

http://www.gibney.org/conway_s_game_of_life

When you click 'Start' and then 'BigBang', it will start from a single cell in the center. I find the resulting evolution pretty fascinating.
> I don't think we're facing any critical electricity shortage

Shortage? No. But energy could always be cheaper.
There's this book by Peter DeGrace and Leslie Hulet Stahl called Wicked Problems, Righteous Solutions. It describes all of these problems and others. It presents a number of very practical and proven solutions.

The book was published 28 years ago, in 1990.

We use words like science and engineering in conjunction with others like computer, programming, and software. And yet there's nothing scientific about how we don't learn from mistakes already made decades ago. And how we keep reinventing "engineering" best practice and call them new names.
Reiterating and showing from different angles and in various contexts = good.

Not getting to the point, or giving relevant context and precursor ideas, while dwelling on unrelated subjects = fluff.

I like my non-fiction the way I like science articles: starting with a summary, and diving into all necessary details later.
Our far-right just wants to kick out foreigners and ignore refugees and doesn't give a shit about anything else
Crucially they don't carry around mutable state by default. If you want a record with protocols to act like a stateful object you can do it, but you have to explicitly jump through hoops eg by embedding an atom in one of its fields and writing all your own getters/setters. It's not an especially pleasant or useful way to write Clojure(Script) but, as others have mentioned, it can be useful for things like achieving very high performance in certain situations.
Tổng quan về thuốc Terpin-Codein
This narrative goes back to at least '68 [1]. I guess the Democratic Party was just way ahead of the curve in the fight against Trump.

[1] https://www.theguardian.com/news/datablog/2012/may/24/robert...
This was confusing to read if you only knew about the email client Elm. In general I wish people spent more time naming things better, and reducing naming clashes.
> Every single nuclear facility is has a lot of fixed expenses to keep it running

Counterintuitively, economies of scale are more frequently found in small products which can be mass manufactured than big projects which must be custom built. This isn't an ironclad law. But neither is "nuclear must be big."

> the first few reactors are assuredly can't run at profit

"Assuredly" based on what? This article is about a commercial reactor project. One of many. Their investors have less of an interest in "advancing [their nations'] science and industrial competence" than in turning a profit.
Hiroshima lives before the bomb recreated with colorized photos
Disappointed to see the discussion here revolve around the podcast production style when the core topic of determining a world wide consensus for what is or isn’t considered ok to publish is such an impossible and simultaneously interesting problem.
I'm curious what technology is used to sense when the can is full and needs emptying?
But a political is supposed to be a "representative" of the people. Not some kind of professional wordsmith...
Thank you for this; very elaborate. I would be interested in hearing more about your experience making the shift. I have considered CTO roles but generally here in .au look for people with previous CTO experience, so it becomes very hard to demonstrate experience. I have worked with numerous CIOs in my time as a consultant on business cases and commercial performance so definitely have some proof. But again being a consultant is very different to an operational role of a CTO. Unless tech start ups are different?
I once read on Hacker News that in the future, the C-level people all need to be very strong in IT as any company or organisation nowadays is so much reliant on IT.

It's also the message of the Phoenix Project book, which I did like.

The problem I have noticed is that although management does understand their businesses, it's easy to bullshit them when it comes to IT. And they let it happen because they are not into IT and they don't grok it. They would never treat other projects like this the same way when they would totally understand it.

I especially notice that as I read what higher management layers write about projects or effort, it's high on fluffy 'visionary' words but low on actual actionable vision that would help me to make every day decisions on what to prioritise.

I believe that the simple reason why IT projects fail is because of very mundane basic things.

But those are not sexy to write about. To me it's all about:

- Why are we doing this?
- How would you define succes and failure for this project
- Who is responsible for what / contact person
- How do we work with each other and detail this
- What are the guiding principles
- How do we assure quality
- How do we assure timely delivery
- What stuff do we need, gear, licenses, etc.
- P R E P A R A T I O N - do your homework, investigate things beforehand before you make choices.

I can go on and on. And it may bore you. But I think there is actually no true complexity involved in all those failing projects.

There is not something really special to IT projects. I wonder if we do pretend there is something special to them because we ourselves want to feel important in some sense.
I always thought that is what everybody did before they quit - how wrong I was.
To get in trouble for piracy, you need to:

A) live in a country where surveillance is huge (America, UK). This simply wouldn't happen in a 3rd world country.

B) Own the actual content-distributing site (piratebay, etc). That's who litigators / law enforcement go after the most.

C) If you don't own the site, you need to download ungodly amounts of content illegally. I'm talking 1000s of Gigabytes worth of content every month.

D) Actually be worth the cost of a legal trial, meaning you have to respond to the email/notice, have the money to pay them, and be downloading so much they're somehow losing money.

If you don't tick 100% of these boxes you will almost never be caught. Piracy isn't a big deal on an individual basis because people who do it were never going to buy the content even if they got forced to. If anything, they're doing your product a favour by checking it out and probably buying it in the future. Or it's a warning sign that you need to get your shit off of HBO and onto a more accessible platform. So nah, this lawsuit will change nothing. All it does is take away point C of the above list.

Now, can you be kicked off the internet for this new law? I don't know the ins and outs but the reason i see that not happening is because ISPs would lose a huge amount of customers and would lobby against that hard, among reasons stated in the article. Anyway don't panic, the internet is still a wild west and nothing is going to change that anytime soon.
I see you have never had to desl with radioactive material and activated tools in private companies.

It is not a pretty sight. But hey, keep advertising nuclear. How much do they pay you?
User squats on over 100 names on Rusts package manager
A good ELI5 analogy is the Pythagoras' theorem [1]. Its taught here (NL) at school at around age 12, so its not quite ELI5 but closest I can think of.

[1] https://en.wikipedia.org/wiki/Pythagorean_theorem
Most successful companies have to execute perfectly AND have an some of those extrinsic factors, such as family money, personal connections, good timing, or dumb luck. There's nothing wrong with acknowledging that. It doesn't make the successful founders bad or less worthy to give advice, it helps explain the conditions necessary for success.

Anyone receiving advice should be aware of the prerequisites to that advice.
React vs. Vue: Programming Experience
This seems true, however the following quote is worth mentioning:

“The market can remain irrational longer than you can remain solvent.”

https://quoteinvestigator.com/2011/08/09/remain-solvent/
I'm not sure I see the reason reality and laws must be made to match. I don't see that as something that is inherently all that valuable (if at all), and certainly not to the degree that it's worth doing whatever is easiest regardless of costs to make it happen.
I started reading Homo Deus yesterday, I'm only about 50 pages in but enjoying it so far. I haven't noticed much doom and gloom in it yet, in fact the first few sections are about the positives of the modern age (advances in medicine, eradication of famine, etc).
But only really two phone operating systems to choose from and many reasons why you are stuck with an iPhone (I have one for work, many friends have one so they can use iMessage, group think, etc.).

I think the book analogy is a poor one, sorry!
Note that axioms are usually added, removing is weird. As such i see it mostly the other way around: there is a classical fragment inside constructive logic (this should not contradict what you said tho). In constructive logic, for a proposition `P \in Set` the proposition "P is in the classical fragment" is `dec(P) := P \/ P -> 0` (`0` being the empty type). As such we can define the set of classical propositions: `CL := exists P \in Set, dec(P)`, eg couples of sets together with either an element of it or a function that maps its elements to an inexistent thing (absurdity).

LEM is not wrong, it's just not always true. You must be familiar with the fact that AC is not provable in ZF, as such isn't LEM kinda philosophically wrong for AC? Not forcing LEM to be true is useful to have a better (more generic) understanding of complicated things. In general restricting logics (eg linear logic, constructive logic, etc) is only making them more powerful: we are able to express more propositions and we can internally (or externally as in linear logic with `!`) define the fragment for which the old axioms were valid. Pure languages enable explicit talk about computation, linear languages enable explicit talk about memory. Restriction are about increasing expressivity and most of we time we build them in the way that they retain the same proof-theoretic power.
Signalling and train control systems typically have two independent implementations - full stack: hardware, os, software, different development teams.

I guess you'd need three separate implementations to achive some redundancy when you can't just slam the emergency brakes if the systems disagree.

(... For some reason, I find it higly demotivating that another team is doing the exact same thing. Maybe I just want to be a snowflake...)
If you look closely, Netflix shows a ‘this tv show contains product placement’ sometimes. This will probably become a lot more common, and it’s not blockable either. I’m ok with subtle versions of it (a laptop on a desk that shows the Dell logo), but there’s also very blatant ways to do it. In Designated Survivor, there’s a scene where one of the protagonists stands in front of her car, starts it with the Ford™ app (panning inside shot of the Ford that shows it starting/booting), she and the passenger get in, talk for 5 minutes and then drive away. It was extremely shoe-horned.
A boring response, but have you studied stats? Knowing stats and a bit of SQL is enough to get you pretty far with a lot of problems. I'd consider those skills an important pre-requisite to more advanced tools and techniques.
This analysis seems much too statistical and superficial. If your partner and you are fighting more than you think is manageable, you need to make a change. That is your prerogative. You can treat them differently, you can try to find out when and why you get into fights, you can change jobs, you can change partner. All of these choices will have an enormous impact on your quality of life, and the dynamics between you.

Your outlook makes it sound like you have as little effect over your own relationship as you do over the stock market.
What about vsts?
ETextbooks improve learning and raise grades
Link to code for those of us on a phone?

Edit: found it https://github.com/isaacsanders/game_of_life-elixir