skysight-inc/HackerNews huggingface dataset:
There are some ways to adjust and counteract these effects (it's an issue with every clinical trial on serious illnesses and older populations though).

A reference:
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3227332/

Sometimes, you have to trust the quality of the journal and biostatistician if you aren't able to read everything yourself.
I agree that mutability won't often bite professional programmers as you say. But as context is good to know that quite typical F# programmer has strong C# background like you. Individual features are often raised during discussions but point behind features is mind-shift (at least for me).

You don't have to remember/think/know:

-Possibility that somebody somewhere is unexpectedly effecting on you

-How to move data, it's just parameters and return values

-What object identity is

-etc.

It takes time to adapt to these constraints in a way you really don't have to think them. But as gain you can free quite a lot your mental load.

As result I feel that with F#:

-I feel significantly less stress

-It's easier to model complex system and understand/trust their behavior

-After 6-12mo I can constantly write clean and maintenable code. In contrast I am not very happy any of my C# projects after 6yr experience.

Yea yea not silver bullet but I love it.
>> Apr 23, 2014 - Almost 25 years since the Iron Curtain came down, deer roaming the Czech-German border still balk at crossing areas where electric fences one lay

https://www.dailymail.co.uk/news/article-2611585/Deer-not-cr...

I also remember a story from the US. A high-security prison was removed, its razor wire fences torn down. Years later, GPS data showed an outline of the prison. The deer were still afraid of a fence that they had never themselves seen.
Ultimately these higher-level requirements like JVM vs. .NET are the biggest factor in deciding a language. For example, my latest project need to run on Azure Functions (consumption plan, has cold-start) for cost reasons, so the deciding factor was "which language has the lowest cold start time?" If you're doing ML model design, you use Python because that's what the notebooks and libraries are written in. At any given moment, OS/cloud platform support, library availability, and desired app model has way more impact on choosing a language than design.
Two killed in accident at Antarctic research station
That's a major component and harbinger of a Dark Age, the loss of a functioning bureaucracy.
> I was really just thinking of grep and some other CLI utilities there. :)

Another technique I use is to spider a site (respectfully) and then use https://github.com/BurntSushi/ripgrep or load the spidered data into a local Elastic search.

Some of what you outline in searching other parts dovetail into handling poor access to the Internet. For folks with bad or transient access

pip install --upgrade youtube_dl

To download youtube videos (or complete playlists) for offline viewing.
Democrats in the US would be considered center right in many European countries. The highest income tax rate in Denmark is around 80%. If you want excellent public infrastructure, you need to be willing to invest into the commons (not hand it over to the private sector - there is no example I am familiar with where that has led to better outcomes in the long run).
Where does it say Linode's perform isn't good? Any source DO has better disk speed?
Your sentences should be as long or short as they need to be to communicate clearly
How can an essay like this not mention David Foster Wallace? So many of the sentences in Infinite Jest were absolute doozies.
Over 72% of network traffic is encrypted
Sorry for late response. Got answer. Almost 12.
Thanks very much for that perspective and the link.

It certainly sounds more attractive than writing everything in Javascript and using Node!

I'm interested in writing a portable, commercial 3D CAD modeling library. F# has already been used commercially for some years for 3D CAD on Windows. So F#, when compared with Ocaml, is a relatively easy sell into that market as it doesn't add another dependency.
The original paper is good.
http://www-scf.usc.edu/~csci201/lectures/Lecture11/royce1970...
Was that from Mother Night? That is an amazing book.

By pretending to be a Nazi to spy for the allies, he turned out to be very good at being a Nazi.

It's a dizzying trip around the age-old question of are we defined by what's in our hearts or by our actions, or perhaps our actions are the clearest indicator of what's in our hearts.
Tell that to Python! ;-)
I think this is reflective of two very different perspectives on diversity.

I was watching a panel on increasing diversity in investment, and there were two women with two different ideas.

One wanted to simply help encourage more people to get into investing, especially since a lot of widows, for instance, are left with large fortunes which aren't invested. Many of them give to various philanthropic causes, but not as many invest on their own.
The other was objectively angry and hostile to the two men on the panel, making numerous accusations of "sexism" (they were unfailingly polite). She had an incredibly unprofessional demeanor and simply talked about founding different investment funds where "straight white men" wouldn't be hired, but rather others who were underrepresented. Sadly, crowd seemed to approve.
Later in the talk, a "white man" dared to make a comment (actually supportive of diversity and agreeing with the first woman), and the second woman butted in, commenting that what he was saying was "benevolent racism". He was only agreeing with her and being positive.

It is unfortunate that so many people get so angry about this topic. The idea that we have to force exact proportional representation is wrong, and just as racist as excluding people. It's just excluding a different set.
Thank you.

>it would certainly be possible to share 90% or more of your core code.

It sounds like maintaining parallel code bases in Ocaml and F# with the same basic design and file layout might work quite well for the core.
I disagree wholeheartedly.

Movie tastes are very niche and this is why Netflix makes so many weird/off stuff. But movies right now are like an "all or nothing" proposition so they have to cater to the lowest common denominator.

But if you could do variable pricing, movies could stay in the theaters longer.

Also as recently as 15 years ago there were still "Dollar Theaters" that played past hits and it was totally a fun college-type thing to do to go with your buddies so that that one friend or friends would see it.

I think it would open up a whole new market of bargain-seeking/quirky behavior where the cheaper movies would be like a cult following type of deal.
You can't really criticize it only based on those numbers, at least not without looking at similar numbers from other cohort studies with the same length.

Well, one can't criticize the quality of the study without looking how well other studies did. But even if all studies involve a massive drop-out rate, the drop-out rate still seems like something to look at in evaluating the accuracy of the study.

I mean my concern, looking from the outside, isn't relative accuracy, but absolute accuracy. Not "is it as good as other studies?" but "it is good enough that I can rely on it?"
How about kettles? A container that whistles when your water boils. The never-ending list of errors: handles that are in the wrong place, whistles that don't whistle, underside heat distribution plates that come apart, lids that become wedged tight. After the centuries we've had to perfect kettles, you'd think a reliable design could have emerged by now.
Google isn't on OCP afaik. Their hardware layer is pretty custom. Maybe you were thinking of Facebook?

Google's hardware layer is one thing; as btian mentioned, TPU also is deeply integrated with software infra e.g borg https://ai.google/research/pubs/pub43438
Sure with a half dozen fixes you get an approximation of a modern terminal. GP is talking about the console, not the shell however. The console is a character grid designed around VGA hardware, not built on streams as a proper terminal is.

CMD is another horribly-designed feeble tool compatible with COMMAND.COM, acceptable back in the eighties. Yes, its fine for running a program or two here and there if you've got low expectations. You can get work done on 640x480 too, but we don't suffer that today. ;-)

I recommend this series of posts that will explain how poor the situation has been on Windows, and how it is improving:

https://blogs.msdn.microsoft.com/commandline/2018/06/20/wind...
From a developer perspective, Windows does SSH keys just fine. You can't SSH into Windows boxes (yet apparently!) but you can SSH out of them a-ok.

Window Key, type "optional features" and install the OpenSSH client.
Two Nearly-Identical Dark Matter Studies Have Conflicting Results
To be fair any modern IDE or text editor that supports JavaScript supports JSX
Accessing that one bit can be as expensive as passing an int around.
The inconsistency of math was a trick question. It doesn't matter what probability you assign to it since if math is inconsistent, all numbers are equal!
This. Once the spaghetti code glued together to somehow work is deployed and people start using it, it's production system and next sprint will be full of new feature stories, nobody will green light a complete rewrite or redesign.
Hi Jason,

I'm familiar with the academic research in paper prototyping (for background, I have a Ph.D. in CS [HCI], have been a HCI course assistant, and published in academic HCI/design conferences).

To say that paper prototyping is the best implies a certain design philosophy, team structure, and organizational culture. It requires a certain buy-in, level of trust, and design pace that are not appropriate for all industries. There are reasons why most professional UI/UX design tools go to the pixel level, and why sketching interfaces never took off in practice.

That said, there are great benefits to paper, prototyping, and sketching skills. But there are also drawbacks which are not immediately obvious in reading the research literature or taking academic HCI classes.
Employers in a market economy have no power in the general sense to expropriate wealth. Their only power is in offering employment terms better than the next better offer. Offering the market rate for a unit of labor is not wealth expropriation. It's compensating people for exactly what their labor is worth.

Force people to pay any more than the market rate for labor, and you're artificially under-valuing investment capital, and thus disincentivizing delayed-consumption/long-term-investment. In other words, you'll be incentivizing people to save/invest less of their income than is optimal for maximum economic development, and it is economic development that is responsible for virtually all reductions in poverty and improvements in quality of life for the general population.

>>It also doesn't follow that increased incentive to invest in employers translates to higher wages for laborers — why wouldn't employers keep wages stagnant and pocket the money themselves?

Employers have to compete with each other for employees. Why else do you think wages would ever increase? I really recommend you study standard economic theories on wage growth, or the economic history of any major country, to better understand the interplay between per capita production and wages. Look at China over the last 20 years, where wages have tripled. There is no force that increases wages as much as economic growth, which hinges almost entirely on investment capital.
I agree with you, except I’d say that the ideal of Agile, the manifesto itself, responding to change, etc., is a significantly worse workflow process than Waterfall (which is also bad).

Agile prescribes so many things that are absolutely pushover, toothless concepts in the face of basic corporate bureaucracy that it really is a case where it’s the tool’s own fault that everyone uses it wrong.

I’ve seen Waterfall used successfully. Not often, but on a few defense research projects it was great.

I have never once seen or heard of any Agile process anywhere actually working with any degree of success.

I’ve heard plenty of people indulging some No True Scotsman nonsense about how a “real” Agile process can succeed, and then proceeding to write a diatribe about their “real Agile” workplace that is clearly so fucked with dysfunction that the person writing can’t even realize they are only shipping software in spite of Agile and not the least bit because of it. But I’ve never ever seen or heard of it actually causing success, not across any of the countless blog posts or anecdata on HN, and not across 6 different jobs at companies of various ages, sizes and capitalization levels all using Agile withvarying degrees of formality, pragmatism, Agile coaching and consulting, etc.

None of it made any difference. Agile just hinders people. It is not capable of doing otherwise.

Now, having said all that, I do agree that for processes that can work, processes that are not overly prescriptive, let different teams do things different ways at different times based on different goals or different personnel, let teams ignore the customer when needed, enforce long-term planning when needed, do pure research with no time boxing when needed, etc., then for those kinds of common sense, non-Agile processes, we have to change the incentives so that people are aligned to care about the objective truth and objective outcomes required to get the job done.
I'm just a dumb worker, but I would like business owners to be forced to do their absolute best to avoid making dangerous collapsing staircases.

I don't know how it would work, I guess they'd have to pay for more insurance.

But it seems that the way it is now, everyone has to pay for their ability to move fast and break things.

Just throwing ideas around, my economics knowledge is rudimentary at best.
Note that there is also ongoing work to bring the native compilation to Scala[1].

[1] http://www.scala-native.org/
It's not the CPU cycle but lag that makes me feel like I'm on a laptop from 15 years ago.
Umm..things like standard library strings, futures, threads, memory management via shared_ptr, unique_ptr, RAII etc are also other great reasons to use C++. Every time I attempt to code in C, its like my hands and legs are cut-off. I suppose some folks enjoy this.
It is not normal English for a "b" at the end of a word to get assimilated into the "s" at the start of the word.

(Note also that when you say "rubs", the "b" is not getting assimilated - it's the "s" that is getting assimilated into a voiced "z")
The ability to wield the power of the Internet to answer questions, not just optimizing a shopping cart, but the ability to answer deep questions is a needed and important skill.

I have zero issue if someone wants to optimize themselves, even with no other end other than "optimal".
Many worldwide oppose more migration – both into and out of their countries
I once wrote a program to send data for free anywhere in the world, by dialing another machine and then hanging up. The remote machine's modem would say RING. With the right excruciatingly adjusted and slow timing you could send binary data insanely slowly. Start bit, then 8 data bits, maybe check bit, something like that. Let's just say it never took off. Something on the order of 0.1 baud.
GUI is something you can't easily copy and paste which is s real killer. And with options spread all over with 3 level depth of more "options" is getting old quick.
There is always an option to switch to OCaml instead. Especially these days it gets more and more attention to improve Windows support.
No they aren't. DuckDuckGo does add some of their own stuff in there. Ending up with different results. You can verify.
I had a Chinese coworker give it up because it was too difficult. I read it again for fun (and 'cause I decided I ought to complete the hardcover collection I keep porting around as I move) last year, first time doing so since I was a child (maybe a young teen was the last time?), it has a lot of weird Britishisms that I suspect my 5th grade teacher had to explain to us when she read it to the class.
You run browserless?

Gotta say, your customer support is top notch. I asked a question on a Saturday evening and got a response 15 mins later. I was stunned!
I just can't get over the verbosity of PowerShell.

With all the "do 1 thing well" utilities glued by bash, it just feels real effective.
Every tester should make this test.
I didn't say the book is the best actionable UI advice, I said http://refactoringui.com is, whose content is free. All I said about the book is that it's available if you seem to like all the other content. I made no comment about how good the book is, as I haven't bought it, but I think it's fair to assume it's an extension of the rest of their work.
Only if they try to open source visual studio (not the code) which is choking themselves by putting a barrier to entry for their own platform with not so cheap pricing model.
15 -years- is a LONG time for a study. I'm not sure about the dropout rates, but it is a real statistical issue. I'm just not sure there's anything that can reasonably be done about it. You'd have to have something like federally mandated participation / continued participation. That's also very unlikely to pass ethics boards.

BTW, it would also be an issue if the subjects were compensated to the point that they differed from the actual population at large.

Fundamentally having more respect for doing things right, the right way, over the /long/ term, including the STEM fields, would be a 'good thing' for any society, but particularly western ones (where often the bad/evil antagonist is based on science or a cold lack of emotions; but the protagonist is based mostly on emotion and feeling instead of logic).
The amount of the deductible was just an example, but irrelevant to my point because it doesn't change the end result significantly. Why would it, given the economics? For a $100 deductible, I'm quoted $593/year. $3400/$593 = 5.7 years, so the answer is basically the same.

The non-collisions aren't relevant because I quoted the price of my collision premium only and not comprehensive or liability. That was on purpose, to be consistent with the topic of "hitting things" and with the sort of fender bender I was talking about.

Profit is not very large relative to premiums, so "breaking even" is a reasonable simplification. For example Progressive (not my insurer, just the 10-K I was able to find the quickest) made about 6%.

Not at fault accidents are some other companies "at fault" accidents, so counting them is double counting and would inflate my estimate.

All I'm saying is that, without false precision, evidence suggests people hit things every 5-10 years on average. Having an accident every year or never in a lifetime is not normal.
A timely video from Barrons:

https://twitter.com/barronsonline/status/1070391112475557889
I’m surprised Reagent’s ratoms weren’t an inspiration. They give you a lot of Hooks functionality largely through Clojure’s native atom.
I haven't actually used C#, or any .NET language, since before 7 came out. Based on what I've seen as a sideline observer, though, it looks to me like C#'s pattern matching and destructuring are just syntacitc sugar, and therefore still significantly weaker than what F# has. I don't think you can get to the level of type safety that F#'s pattern matching provides without F#-style algebraic data types.

The reason is that a set of algebraic types in F# is effectively bundle of types that are collectively sealed. In C#, you can really only seal the terminal classes in a cluster of types, which means that anyone else can come along and add a new class to the type at a later date, after the initial module is compiled, possibly even at run time. That undercuts your ability to ensure that a branching statement is airtight.

I believe C# also still lacks active patterns, which are a pretty killer feature if you're looking to do data-oriented programming.
Specify Created/Last Modified Dates in ICS Using Aspose.Email for .NET 18.11
Yep, that was pretty much my point :). I think it’s a dangerous precedent to follow (bad practice), but I’ve certainly been guilty of it on occasion.
Author of that book here, I swear to god had nothing to do with this thread, just stumbled upon it myself perusing HN. Wish I could prove it somehow :(
I thought Fastmail offered (as much as is possible) “secure” email, but it says in their blog post that they routinely hand entire mailboxes over to law enforcement.

On the top hit they say they host everything in New Jersey, USA (with backups in seattle) but later say they are only governed by Australian law and don’t respond to US court orders: https://www.fastmail.com/help/ourservice/security.html

Caveat emptor, I guess.
"Everyone indents anyway. So why need braces?"

I don't indent. I let the editor do it based on braces.
This is more true for some products than others.

I worked on one product which involved a massive store of XML documents and a suite of somewhat complicated serializations and transformations. It was the right architecture for the project, for sure. And it was definitely the fundamental gene of the product; all of the product's design had to flow from this XML-heavy information architecture and backend.

But most of the products I've seen are not so unique. For the vast majority of web products out there, simple CRUD apps backed by a relational database, I don't think the information architecture needs to be front and center in product design conversations. People can make assumptions about this kind of app and they usually won't be too far off the mark.
Now we need to train UNIX admins how to do it without bash.

SSH alone doesn't seem any good without all the UNIX tools.
Years ago, Google announced they'd join OCP. I'd be surprised if even half the fleet made the transition, given how much mileage they like to get out of old hardware.

Besides, for special toys like TPU pods it's not clear that they would value adhering to OCP standards above anything else.
> I have never once seen or heard of any Agile process anywhere actually working with any degree of success.

I ran a team were we shipped (firmware!) every 3 weeks.

After the first year of tracking all our numbers we were able to hit our estimates within a few hours +/- for the entire team.

3 week sprints, 2 weeks writing code, 1 week testing and bug fixing.

It wasn't perfect, and learning how to do it was painful, but once we got going it worked great.

We didn't adhere strongly to any one guiding principle, but being able to use sprints to align work across multiple teams, and as a planning mechanism for management was incredibly useful.

"Our breakdown of that feature means it'll take 3 sprints in total, the last of those sprints the work is split across 2 devs, if one of those devs gets reassigned it'll take 4 sprints."

Being forced to actually plan work out, and then being held accountable for the hours, meant that over time we got good at estimating, and knowing how far to break work down. There is of course a trade off between gains from breaking work down, and time spent doing the breakdown! Several months were rather painful when we went too far one way, and then inevitably the next few months swung too far in the other direction.

But in the end? Yeah it all worked out. We figured out what length of sprint worked for us, what type of estimation system to use, and how much work to put into our planning sessions.

FWIW one of the huge benefit of doing the work breakdowns is being able to see opportunities to parallelize work, and also to see natural stopping points.

My team was lucky to have someone almost full-time dedicated to managing our workflow, without that the entire process wouldn't have been tenable. The tools just suck up too much time.