skysight-inc/HackerNews huggingface dataset:
An urgent care is largely for things where you would see your primary care physician, but they are closed, on vacation, or don't have appointments available (urgent cares usually can do more treatment and diagnosis on site than your PCP, but your PCP would screen and refer) without excessive delay.

An ER is largely for “I might imminently die if this issue isn't addressed”. Not necessarily an imminently life threatening condition, but symptoms that suggest that might reasonably be the case.

For doubtful cases, if your primary care physician (usually, their medical group) has a 24-hour nurse advice line, it's good to call them (both for direction, and often because they need to authorize urgent care, so calling them first avoids delays.)
You vastly overestimate the forces required. Pumping water, let alone a less viscous organic fluid at a few mLs per minute through nominally 100micron pipe is fairly routine. You wouldn't even need 100psi to move a few mL/tube: plenty to absorb the heat output from a fraction of a processor layer.
Audio: Download Sola Allyson Songs and Latest Albums
I was working for people who were suing them, so mainly it created problems in discovery. Compelling testimony of non-citizens/non-residents was a lot harder, I gather.
I think the X1 Carbon is a better machine. Lighter, larger, non-reflective screen. Much better keyboard. The trade off is max 2k resolution, but I prefer it over the Dell's screen which is too reflective.
> If you program with the same mindset of F# in C# then the differences are not super quantifiable.

I think they are. F# defaults to immutable stuff. Everytime you write anything in C# and forget the word "readonly", you're opening the door for a race condition.
Also F# is much more succinct, things that take dozens of lines in C# are just one line in F#, take a look at this quick guide I wrote: https://github.com/knocte/csharp2fsharp
I didn't read that as victim blaming. Maybe it's a little callous but I don't think the commenter is trying to shift the blame or responsibility from the companies to the author; instead I read it as trying to change expectations about the level of empathy and humanity the author will receive.

> If only they had been studying the blade instead.

Uh, what?
Under the Bayesian school of thought, probability represents our degree of belief and is ultimately subjective. There is no a priori reason I can't assign a probability to the existence of God, since the probability reflects my belief about God's existence. Evidence lets us update our beliefs, and therefore our probabilities.

While I have no issue at all with assigning a probability to the inconsistency mathematics, the value I'd assign varies with the branch and mathematics. For Zermelo–Fraenkel set theory, for example, I'd assign a probability very very very close to 0, but not equal to zero (because to be equal to zero, I'd need a proof).
I don't understand why I'm being downvoted. I follow one of the authors on Twitter (Steve Schoger) and I think his design tips are fantastic. I haven't purchased the book (yet) as I think it's a bit spendy, but I have so much admiration for Steve and Adam, so I'm sharing here.
I used to think that prototyping on a paper is expensive since paper is non-reusable. Then I proceeded to prototype on an expensive tablet.

Funny looking back at it now.
Yes, it happens in secret vs open but I'm talking about all open stuff. It just isn't sexy when control systems engineers do it.
Who else initially thought this was going to be about TOR?
Self-driving cars and advertisement
If you're applying blind to places, then you're going to be facing the entire field of other people applying blind and you're going to be at a structural disadvantage as you noticed.

The key is that you're far along enough in your career that you should never be applying blind. Always try to get a warm intro and always try and schedule an informal meeting with the hiring manager before you go through the formal interview process. That way, they're not just reading pages of user research, they're seeing how that user research affects your process & how you think about problems.

Almost nobody who is currently being hired to work on big wicked problems are getting there by throwing their resume into a pile so the process isn't designed to see those people out. The way to get those jobs is to be the only person they were ever even considering for that job.
I probably don't need to use bitmaps as maps at all, really; Text files would work just as well. But using System.Drawing cross platform in .net core was an education in itself, so I think worth it :)
This is a cohort study conducted over 15 years. 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.

I tend to ascribe some value to "It was published in the peer-reviewed British Medical Journal."

Additional thought: Especially because it is essentially supporting the null hypothesis.
How old is the cat?
That would be your own fault for using immature libraries that don't offer stable versions with security and bug fixes. Unfortunately that's most of the npm library and a growing problem in other ecosystems.
The “New T-Mobile” is the least worst option
This is the plot of Chinatown https://en.wikipedia.org/wiki/Chinatown_(1974_film)
A Maverick Builds a New Supercomputer in a PC World (1998)
Its mentioned in the paper: "However, recruitment to and
retention in cognitive ageing studies is also affected
by self selection to volunteer among better educated
individuals who are ageing well, which is also true of
our study. Thus, the findings might be biased towards
those individuals with higher cognitive performance."
yes! when they are missing I spend too much time guessing at implied meaning. if makes me uncomfortable, like reading long text in a sans serif font
Seems to me that even if it didn't slow down the "rate" of mental decline, starting from a higher point because of "brain training" for want of a better term would still be good, no?
While those are nice things, they don't really bite me in the C# world. There's a lot of fuss about it in the F# world, but it really isn't that big of a problem in my experience. I do like the robustness of it, but in practical terms... it's only a minor point in F#s favor
I attribute the titles being a mess because of the 'newness' of the web/tech era and the specific design challenges.

There is a design pyramid which unfortunately build on top of each other for the majority of business use cases:

Graphic Designer -> UI Designer -> UX Designer -> Product Design -> Service Design

These are the levels of the pyramid at which the design process revolves around, depending on the need, for most products or services:

Visuals -> Web -> Experience -> Product -> Service

The narrative of it closely mirrors the history of many orgs:

Visuals: Hey our website looks like a database written by engineers, maybe we can make it pretty?

UI -> hey, we really need it to look like it belongs on the web, not just a RISD grad's art project, let's get someone who understands web design

UX -> okay, now our site looks like every other site. But no one uses it because it's still just a database with lipstick. Let's get some experience designers in here to make it better.

Product -> Okay, now our site has some nice experiences... but they are all disjointed and random and don't account for business needs... Let's get some product designers in here.

Service -> Okay, our product now is pretty cohesive and quite good... but there's a whole realm of things we have to do outside our product (Customer Service, service processes) that suck and are bringing the user experience down as a whole. Let's get some service designers in here...

In my opinion, this is the way most businesses think about design.
I moved directly from Python to OCaml and I have to say, I’ve never been happier. Special shout outs to Jane Street, as their open source software is really solid and a pleasure to use. The community is small but really smart. Overall I think F# and OCaml really nailed the programming language design sweet spot of powerful and practical.
The NYC subway is a poor example, since its funding is dependant on the conservative (but not for much longer) state government.
Another great reason to install ublock origin, privacy badger, and to put facebook and the gang in different browser instance / container
Thank you for clarifying. Obviously I only have a shallow understanding of what the hell I'm talking about. :)

I have been evaluating TimescaleDB and my company currently uses Splunk, ES, and Prometheus. I'm going to be giving Loki a go this weekend for our k8s cluster.

Your explanation here really helped clarify some things I've only explored a bit.
Fun fact: In a round-about way you can estimate how much revenue these products are generating for Stripe if you measure the transaction fees against the reported numbers.
That card seems to "only" be $6,000 on Amazon. [1] Methinks Dell is adding a bit of markup?

1: https://amazon.com/dp/B076P84525
5 Key Differences Between MySQL and TiDB for Scaling in the Cloud
Actually subs are the reason that the horizontal/vertical rule needs to exist-otherwise we could just use two separate pieces of bread as the rule. A sub is stacked vertically whereas a hot dog is nestled horizontally.
Reminds me of an interesting century-old maneuver ... government-created, corporate owned ... when the US created RCA after WW1 by using a 'national security' argument to force British-owned 'American Marconi' to sell to US citizens.

Which, to me, explains a lot about how RCA later treated later radio and TV pioneers.
> I once went to the ER for something. When I walked in, I went to a desk, where a person asked me some questions and directed me down a corridor to an urgent care facility on the same premises.

I've had that happen as a Kaiser patient at a Kaiser hospital, but not seen it otherwise. As I understand, it's rare because:

(1) colocated ER and UC are rare,
(2) even when they are present, they may be distinct businesses such that one cannot rely on the other,
(3) ER mandates create liability if a person needs medical stabilization and is turned away without seeing a doctor on-duty in the ER.

Where they occur, I think it is because the urgent care is actually legally conjoined to the ER, such that the cross-referral from triage is still within the ER from a regulatory standpoint.
I guess you say this because you don't really do multi-threading that much or haven't had the urge about parallelising your work yet ;)
> Are you talking about C?

Yeah, the "C abstract machine" that most C-like languages rely on by the fact of relying on libraries like libc.

> Because it doesn’t actually define anything in this case.

To be clear, when I said expect, I meant expect. These languages expect invalid dereferences to fault—i.e. to cause control flow to be taken out of the program's hands. Which is to say, they expect a generated dereferencing instruction that returns to have put the system into a valid state.

But in practice, what that means is that compilers just expect dereferences to always be valid (because any dereference that returns is valid.) So they don't have to generate any check for null before doing a dereference; and they don't have to worry about having any way to represent the result of a null dereference.

Another way to say that is that dereferencing null pointers is implicit undefined behavior. There's no part of the spec that covers what would happen if you dereferenced a null pointer, because in the model as the spec lays it out, dereferencing is a happy, clean little operation that never goes wrong. (i.e. "The MMU might cause a CPU fault? Who cares! My program didn't cause that fault; it was the MMU's choice to decline to read from $0. Other MMUs could totally allow that, and then LEA would be defined for the entire domain.") Same goes for reading from unmapped regions—"it's the MMU's fault; it could have just as well returned 0, after all."

> I’m sure that in these cases the compiler doesn’t literally insert checks

Yep, you're right. Again, it's because this is what these languages expect. It's not quite the same as undefined behavior; it's that the "C abstract-machine evaluation model" was defined to assume that architectures will always have their IDIV-equivalent instruction fault if invalid. If it returns a flagged value on some arch instead, that's something the C evaluation model is not prepared to deal with.

(Technically, I believe that you'd say that a C compiler "cannot be written" for such an arch while retaining conformance to any existing C standard, and for such an arch to gain a conformant C compiler, a new C standard draft would have to be written that specifies an evaluation model for such architectures—as then the compiler could at least be conformant to that.)

Which is helpful to know: just compiling C for such an arch at all, is undefined behavior, no matter what you write ;)
I have put many hours into that fine game. There's also NAEV

https://github.com/naev/naev
I have never gotten deep into F# but have watched it from a distance for a while. I remember f# 1.0 and thinking this is cool but not fully baked. As f# has grown, I feel like because of or in spite of F#, C# has learned new tricks with each version. While I wish I had time to really ramp up and learn every intellectual curiosity I’ve had, I don’t feel like I have ever had enough friction with c# to “switch”. I’m working with very specific problem sets though so my case isn’t everyones. That said I’m still interested in F# and hope to get into it sometime...
>drinking water before purging

First of all, PSA that stomach acid is generally not more acidic than Coke.

Second, can anyone with some experience in chemistry and biology actually do the math as to how much drinking four glasses of water before purging actually helps? Assuming you double the volume of fluid in your stomach, I'd think that this would change the pH by less than 0.5. Is this significant?
this kind of thing is why pbx callout prefix is normally 7 these days, instead of 9.
Right, if the discussion isn't going your way you can always side track by making up faults and projecting agendas.

How is this helping us go anywhere worth going?

I was talking about std::shared_ptr, which is the closest thing to reference counting that STL offers.
What does Scinapse(academic search engine) data team’s do?
To be fair, your customers rarely care what the code your product is written in is like.

They just care it provides the value they're looking for.
2019 Hyundai Kona Electric – An Affordable EV That Has Serious EPA Range
Naughty Dog abandoned GOAL during the PS3 era, but still uses PLT scheme for scripting.

https://news.ycombinator.com/item?id=9813111
https://www.gamasutra.com/view/feature/134566/the_secrets_of...
If I understand correctly, a lattice or partial ordering means that A = B is possible for different A and B, but if A < B, then "B < A" is false.

But even if I'm wrong about a lattice, my claim is still true for programming languages. Perl > Haskell... for certain situations. Even assembly > Lisp... for certain situations. And yet assembly and Lisp are so far apart on the "power curve" that, if Lisp is not > assembly always, then... do we have any kind of ordering at all?

I view programming languages as being a tree, with branches spreading in all different directions. Some languages reach further in certain directions than other languages do. Your program is a vector. (Really, it's a bunch of different vectors, of different lengths, pointing in different directions, but one direction is the problem that makes it the hardest to write the program that you're trying to write.) Pick the language that reaches the farthest in the direction of whatever makes it hard to write the program that you're trying to write.

This means that your problem imposes an order on languages... for that problem. It's not a universal order, though. Others, with a different kind of problem, may view your order as completely wrong. And they are right - for their problem, your order is in fact wrong.
> Do people generally have a choice what ER they go to?

Yes, people often take themselves to an ER and have more than one within reasonable range.

> I’ve definitely seen people complain on the internet because they were passed out on the sidewalk and someone called an ambulance on them which stuck them with a large bill

The majority of ER visits are not people who had an ambulance summoned when they were unconscious, but, yes, in that case people generally don't have a choice about whether they go to an ER or which one.
Speaking as someone who has been doing C# for over 15 years, and still professionally, but who uses F# almost exclusively in my private projects, the biggest things are:

- discriminated unions. DU types don't exist in C# or lots of other languages, and change the way you program

- complex match expressions (fortunately coming in C# 8)

- value tuples (thankfully arrived in c# 7)

- the pipe operator and partial application (another thing that changes the way you program)

- super implicit typing (its to var what var was to explicit typing)

- and its use of option/result types, along with compiler enforcement of all conditions.

Before I picked up F# properly, I looked at it as fancy but overhyped. But then, its a bit of a plato's cave type of thing: you don't know why `type A = B of int | C of string * bool` is awesome until you have used it a bunch of times.
434 Points
124 Comments
123 Is
25 mes

And yet only one comment suggesting the direct approach...
You'd have an easier time finding Waldo.

Is this low-grade nerdery really any easier (or smarter) than just saying, "Yeah, yeah, NT is great, Unix sucks, now I've got work to do."
Thousands of books at my home too, some dating to the mid 19th century. The immersion of books still can't be bested by handheld devices. Also despite the Internet, the local library has remained quite popular, and ironically, among the young students. Taking notes from a big textbook on a table is still easier on the hands and eyes than scrolling and squinting through the same text on a 5-inch screen.
On a side note, I hovered the cursor over "Onion" and was surprised to find out it's classified as a fruit.

https://en.wikipedia.org/wiki/Onion
I'd argue that that's painting with too broad a brush. C# has picked up a lot of features to support functional programming, and has made great strides in reducing boilerplate and clutter, but there are still all sorts of things that F# has and C# either lacks, or requires a lot more verbosity to accomplish the same thing.

Pattern matching, for starters. It's not just chained if-statements on steroids; F#'s decision to make partial matching emit a compiler error is a real sea change in terms of the level of compiler support you get in guarding against unintended consequences in an evolving codebase.

Type providers. They let you interact with external data sources with about the level of ceremony you get in a dynamic language, but are still statically typed. The SQL type provider is particularly impressive. Not only does it generate your DTOs for you without ceremony, even when you `SELECT *`, even when the schema changes, but, if you make a mistake in an inline SQL query, you'll get red squigglies under exactly the spot in the string where the error is, just like if it had been a syntax error in the F# or C# code.

Computation expressions. F#'s equivalent of Haskell's do notation. C# accomplishes similar levels of purpose-specific expressivity in some specific areas - LINQ, async/await, etc - by adding syntactic sugar to the compiler, which means only the C# compiler team gets to do it. Computation expressions let you roll your own.

Currying and partial application. You can achieve the same result in C# with higher order programming, but it gets messy quickly. Also, there's an argument to be made that, similar to how objects are heavyweight closures, dependency injection is heavyweight currying.
Even reduced to its most basic form I find it moving. Drawing it out so long and so forcefully really drives a point of passion home. Thanks for sharing this!
To clarify, we found the range shrink if one trains for a fixed number of epochs and expand if one trains for a fixed number of steps. So tuning can be easier or harder depending on the budget.
Just to be clear, I was rather agreeing with "Forcing someone to do a job is slavery." And just pointing out that states do that a lot. But they couch it in language about "duty" and so on.

I mean, many millions of soldiers died in WWI and WWII. Many were volunteers, sure. But many were conscripts. And of course, having your country conquered may also not be such a great thing, unless your government are jerks.

Anyway, I distrust all governments above the village level. I do see the argument for ~state level government. Basically, to deal with groups of jerks. National defense is arguably the only justification for national government. And that's just because there are other national governments, controlled by jerks. So it's sort of like a multi-player protection racket.
Yes, we are reminded of that everytime someone with a slight sense of humor is squashed by a comment like yours.
I've found that FUSE/sshfs (at least on Mac) doesn't survive network reconnects. Switching WiFi networks, or even having the computer go to sleep, is enough to put it in a state where it can neither be used nor unmounted cleanly.
> It never compares two languages where people on both sides think they're on the more powerful side.

Which is precisely why adding Haskell into the mix is a useful extension of the discussion.
> I don't see any clear reason why they would not other than snobbery.

Snobbery is a pretty good reason for anything, I've found. In any case, it could be many things: expense (as my university regularly reminded us, each ILL cost like $20 on net), low demand from patrons (even if self-fulfilling, still a valid reason), lack of trust, not being plugged into the right ILL system/software... I don't recall any of the books I ILLed from my public library being indicated as being from universities, though there were several close to us.

I suppose I should try my public library when I have some spare time. I'm almost certain they'd be unable to get either books or theses or papers, but it'd be interesting to know the specific reason why not.

> There are many paid document delivery services. Here's my university's one:

Yes, actually, I know someone who used that one last month. (Scan quality could've been much better, IMO.) It is, unfortunately, rare to have a straightforward 'pay us $X and we'll give you a copy of any thesis' service linked or mentioned on the library website, and they are only for that library's holdings ("scans of book chapters and articles from the UT Libraries collection" ie not anyone else's). I would complain a lot less if most universities had it! I've sometimes wondered if more university libraries have it than I think they do, and they just hide it.

> As for embargoed theses, my impression is that usually the author wants to get a patent on something discussed in the thesis.

That would be reasonable, but in the subjects I usually research, that would make little sense. I think the last embargoed student thesis I ran into was a study on the stimulant effect of nicotine on cognitive performance; hard to see any patent on that being possible, much less profitable to apply to.
Exactly! If your prior is such that things with |utility| = X occur with probability less than 1/X, then Pascal's wager doesn't work.