skysight-inc/HackerNews huggingface dataset:
Writing precisely and being regularly misinterpreted are incongruous and should produce cognitive dissonance which would let you realize that one of your assumptions is in error.

If I said that comments like yours are frequently written by Jewish transsexuals, you might object to that. You might, at the very least, think it's a weird thing I believe, to ascribe patterns of thinking and writing based on gender or ethnicity. You might also think, even if you couldn't exactly pin down how this belief of mine was problematic, that it represented a kind of belief that would be better off not shared.

"Hey, I'm not saying anything bad about Jewish transsexuals, just observing that they regularly write comments like this and get defensive when I point it out!" If I replied like that, you might think I was just gaslighting you rather than having a genuine discussion.

Regarding how I can blame you - I have already made this clear. You (negatively) characterize people based on their race and gender and ascribe properties to them. The central idea of your comment, that not everyone is in a position to choose what to work on, is very obvious and you deliver it with hostility and cynicism as if you were sharing verboten secrets.
I hadn't seen docopt before, but am curious why you think it's such a bad design.
I honestly think they expect you to fail the first time just getting used to the whole process
Do people still aspire to work at Google?

10 years ago I certainly would have while it was still run by Larry and Sergei. Today it very much seems like another Microsoft, IBM, Oracle - if you like working at large corporations great but you won't be doing anything meaningful.

Android, Maps, Search, Youtube, Drive are all mature products that can be labelled as done, their creators have long left so thats just maintenance work.

The closest thing to exciting would be their self driving division which seems to have made bad fundamental choices in LIDAR.

Anything else you can already see has a death timer on it.
Sand dunes repel each other as they move across a landscape
I’m also disappointed that Go isn’t approved, but the UI framework is implemented in Dart, so it seems like an understandable decision to permit Dart.
Sounds like an unnecessary personal attack.
> In most cases

In what cases is this not true?
Well, if by 'for years', you mean 25 years, you're right. ECMAScript is still hot garbage that clogs up computers and the internet, ballooning requirements on browsers and nearly forcing the monoculture we have in terms of browsers and rendering. If you want a website, you should write a website. If you want a program, you should write a program. Don't write programs to run in the same space as websites.
> The only reason I focused on the attractiveness stat first is that on apps like Hinge/Tinder it's a prereq to even getting to the economic piece.

Pictures of exotic vacations and the gear they’re wearing are plenty evidence of economic strength. You have time to go on far flung vacations and money to spend on them and the gear.
Perl came as a reaction to the Unix tooling that was awk regex and all that jazz. It was designed to replace those tools and it did a good job at that. Times have changed, however, and perl no longer fills a function. We have python now, which surpasses perl in functionality.
Java Applets over current connections, on current hardware, and written with Kotlin would be pretty nice. Especially if we still had plain old HTML and CSS too for non-applications.
Interesting. That would make him much worse in my book. Now should I remember him as an irresponsible fraud or a mistaken fool?

It is one thing to be so misinformed as to believe a flat earth has any plausibility. It is another to reinforce people in this mistaken belief to take advantage of them!
This obviously lends the question, given it's criticism back in the day, which PL is the next javascript?
Absolutely. Imagine if they were to learn how to do something else than webdev.
Lol, reminds me of examples like Kopi Luwak coffee beans - somebody, somewhere, followed a type of cat, civet cat, and, once the cat defecated, decided that _that_ cat shit looked most appealing, so why not go ahead and taste it? Or, pore through the shit, extract the beans found in the fecal matter, and make coffee out of those. Why not?

And, thanks to those people's sacrifices, we now get to enjoy good coffee.
"“Paper Software plans to use JavaScript as the glue which lets our development partners couple Java, plug-ins, and Paper’s multi-dimensional VRML user interfaces within a distributed, online application.”"

These quotes don't sound right. I was working for an ISP around 1995ish and telling people how to set up Trumpet WinSock and MacTCP and Internet Explorer. Java wasn't even public yet, was it? Someone wanted an interactive web page, so I used Perl and CGI.

"JavaScript is a great way to get cross-platform scriptable access to databases and move the resulting data into Macromedia Shockwave, where it can be rendered, animated and made into live interactive multimedia for the Internet."

Live interactive multimedia? At 3.6KB/s? I remember a T1 (24 simultaneous calls) being a big deal, now my phone seems to have about 40 times the bandwidth.

A lot of familiar stuff came out around that general time, but it didn't spring forth fully formed. Someone was creating what would become eBay at the time too, but that doesn't mean it was a thing yet.

Maybe these are all genuine quotes, but they feel like they are from someone who thinks of 1995, 1998, 2002, etc. as all being "a long time ago".
Try https://devdocs.io/ instead. browser based and offline*

I refresh it before every long haul flight.

* Uses localstorage and sometimes can be cleared.
This doesn't seem any more ridiculous than companies setting a higher price and then always having the item on sale. I think JCPenny famously tried simply lowering their prices and sales went down. I guarantee if you ask the average person "would you rather companies cut the BS and just lower their prices rather than have items on sale in perpetuity" they would of course say lower the prices. But as the anecdote would demonstrate, that isn't how things actually play out.

The point is, when it comes to consumer behavior, I don't think anyone has a clue what to expect. It would not surprise one bit if vacuum companies make louder vacuums because the consumer thinks it works better.
I'm currently at a company where our iOS product has millions of paying customers. FWIW:

We run a flavor of the coordinator pattern + MVVM. We use delegation to handle messaging between view models and view controllers. Services are currently handled by a super ugly singleton, but that's a by-product of legacy architecture. New features usually inject the service directly into the view model.. and there has been some talk in potentially moving the service to the coordinator to mimic a unidirectional data flow.

The issues you mention, i.e. globals, lack of unit testing, fat view controllers and lengthy functions... none of that stuff, if included in a pull request, would pass our code review. So generally we self police each other to avoid code smell.
> I find it fun how the cost of the cloud is forcing people to consider what absolutely must run in the cloud

Honestly why ever go to the cloud? It seems like a Larry Ellison boondoggle with the absurdly high costs and lock-in. (Ever look at moving your data?)

Running your own metal is cheaper if you actually fund it.
I think it's amazing how frequently people involved in various CS and IT things are directly participating in threads about their work here on HN.
That doesn't seem like a non-serious criticism to me. They're trying to build something huge that's of immense strategic importance looking forward potentially decades. It seems appropriate to adopt the utmost caution about incorporating a language that's promising but for which widespread traction might not materialize as expected. Though to be fair, the same (and more) might be said of Dart...
compared to the serious criticisms of the others

Adoption and community are one of our top factors. It's a pretty serious one, IMHO.

EDIT: our as in our company. Not in any way affiliated to Fuchsia.
Whether you're right or not depends on whether one believes that algebraic datatypes could only have come out of a fascination with the "mathematical properties of the type system". Because ADTs are a serious win in terms of robustness and efficiency of development. They are now found in Rust (for example) but were invented in the 70s in the functional language community.

An innovation like that, which was not stumbled on by mainstream imperative language designers, arguably comes from a focus on abstract mathematical structure. You might be right if you believe that profunctor optics are going nowhere, or that dependent types and type–level programming are just too complicated, but as a research project, strongly typed functional programming has many strengths, and I don't just mean strengths that are not essentially related to the type system like purity or laziness.

'“The ability of the [strong] type system to catch [mundane] errors allows us to spend more time thinking about other, deeper issues in our code and drives down our error rate, making it possible to move faster while still maintaining safe and reliable systems,” says Yaron Minsky, co-head of the technology group at liquidity provider Jane Street. The firm, as it puts it, writes “everything that we can in OCaml”, a functional language, and employs 300 OCaml developers.'
Thank you for this suggestion, that sounds like something good to keep in mind! It makes sense that companies are beginning to think about this as well.
Do you have an ownership stake in the company?
I started to write a comment about the poor job Haven is doing defining "old phone". There wasn't anything on their website, git pages, or online slide presentation. Then I realized _they_ aren't using "old phone" anywhere...

I could have sworn that when talk of the app first surfaced, they actually used terms like: "repurpose your old phone". That seems to have vanished ...or... the initial articles (along with the title of this post) are editorializing.

Still... it would be nice to get a sense of system requirements somewhere on Haven's pages. They have not included reqs anywhere. I have a ~5 year old phone (Android 4.3, 2gb ram, 16gb storage, 720p) that, I guess, I'll pull out and experiment with.
Out of curiosity, can anyone point to a similar resource aimed at languages not written with the Latin alphabet? Chinese, Japanese, Arabic, etc.. I'm curious which "knobs" are available to other languages, and how preferences differ.
It maybe different from Facebook and Google, but is hiring for positions on teams that unique? That's how my employer does it. A lot of our public facing job ads are for specific teams. We have a few general public-facing job ads but I think team/group matching is done early in the process for those also.
what's the point of this post?

i suggest to simply read the original AH blog post and skip this rehash
The default has been to leap before lurking for many years now. I don't expect it to change back ever again.
Thanks, I'm with you on the big data buzzwords and trying to avoid overengineering things (one of my favorite HN posts ever is https://news.ycombinator.com/item?id=8908462).

Right now the data scanning is just a fork of https://github.com/BurntSushi/xsv/ running in a container with plenty of ram, and we've handled files in the ~20GB range with no problem. I think we could actually scale up to ~100GB files with xsv, which seems to cover 99%+ of data providers we're running in to. Providers might be processing massive amounts of data but the eventual deliverable they share with their customers is rarely too big for one machine.

That said, we will probably move away from our super simple stack towards running a Spark cluster in the medium term. Not for "big data" (actually I expect Spark to have higher latency and possibly to be slower for a moderate sized dataset than the rust solution) but because we want to be able to run multiple parallel scans over the datasets for upcoming future features. Some of that will involve a DAG of dependencies (e.g., do type detection first to figure out fields that are categorical, then generate visualizations where the plots are grouped by whatever the values are of the categorical field). There are also a bunch of nice libraries in the spark world for more comprehensive stats.
I got this treatment and I was living on the east coast when I was interviewed. Very fast, no nonsense process.
The reasoning does sound serious: "The properties of the language are not yet well-understood, having selected an unusual language design point (e.g., borrow checker) and having existed only for a relatively short period of time". It isn't just "it isn't popular thus it is not good" but "it does something weird that no other language does and because few people use it, we haven't yet figured out what potential issues that weird part may have".
Interesting 2-tier pricing model. Either:

- Free (all features, 3 months of history)

- Premium (all features, $9/user/month, for unlimited history)

I don't think I've seen a free tier with literally "All Features" except history. Seems kind of like a perpetual 3 month trial, I like it!
To me a "complex algorithm" is something that's grinding through the data doing some kind of interesting transform.

Dealing with the tons and tons of crap people will put down in a field no matter how explicit you make your directions is not a fancy algorithm. It's down and dirty drudgework that is of little interest to the more math oriented algorithm side of the house.
"... you find only an external skin which is at the same time a structural component and the tank wall ... Engineering has two phases, structuring and integration: we ought not to forget either one..."

That could be interpreted in non-horrifying ways. Sure, the cost of a function call (especially with a modern compiler that can intelligently inline) is negligible in most cases compared with the engineering benefits it offers.

But what about cases where it's less clear? In databases, there are constantly cycles between:

Cycle phase 0: Abstract Storage: separate storage from computation to make the database system easier to test, replace, and reconfigure.

Cycle phase 1: Push computation down to storage: wow, look how much better performance we can get if we intermingle storage and computation!

GOTO cycle phase 0.
CareRev (YC S16) Is Hiring a Senior Back End Engineer in Los Angeles
CareRev (YC S16) | Senior Back End Engineer | Los Angeles, CA (Marina/Culver City) | Full-Time | Onsite

Us:
We build software to help the health care industry fully staff RNs, CNAs, MAs, Therapists, and Technologists efficiently. We are experiencing strong growth selling to both Surgery Centers and Hospitals.

Role:
Senior Back End Engineer with 7+ years experience. We're looking for someone that tends to think data and data structures first and loves RDBMS.

Our Back End Tech Stack:
* Postgresql
* Redis
* Ruby
* Rails
* Linux

Compensation Package:
* 140-160k/y salary
* Stock Options
* Health/Dental Insurance
* 401k
* 2.5k/y continuing education (conferences, books, online courses, etc)

Email us at derrek at carerev.com
In fact, it is you asking people here to believe in your odd and unfortunate worldview.

You are obviously enormously invested in completely ignoring social conditions women and people of color overcame to do what they did.

Of all things, in a thread on the occasion of her death - for a few, what we get is anger and indignation in reading about this woman's accomplishments. Think about that.
Very early in my career I worked for a dev shop that would literally hire 2-3 Indian teams to do the same project in the hopes one would turn out ok and it was still way cheaper than domestic labor. I was often brought in to fix bugs and performance problems. It was during this period I saw the worst code of my life: Pulling every record from a sql database table with a 'select * from table' then a strcmp on each numerical (and indexed) `id` field to find the record. It had worked in testing but blew up in production. It was truly unreal to see that.

The other interesting thing I got to see was a shakedown of our company after we poached talent from a connected local company. We had the option (which we took) to pay several years worth of the average per capita income to local government henchmen to be allowed to stay in business.
> Writing the code out-of-order is the whole point.

Yes!

MyDef, https://github.com/hzhou/MyDef, is such a system.
If not even one of your exes would be willing to give a positive testimony, that in itself is a fairly powerful signal.
I loved Grouper. Met a lot of cool people and had a lot of fun. My guess is it was an operational nightmare to scale. There was a lot of manual effort on Grouper's end in selecting the venues, matching the groups, making the reservation, and paying for the first round of drinks (the model was you pay $20 per head to Grouper but it covers your first round).
The Fuchsia project has the opportunity to influence the evolution of the language.

I think this is a big one, even though they listed this for Go I'm curious if they actually believe it. I certainly don't.

For Dart they're potentially a significant stakeholder, for Go though I can't imagine them getting any significant changes through that don't benefit server side programming at Google.
All apps already have "self-disclosure."

That's the algorithmic match and the human match. I am X looking for Y, etc.
10gbe will depend on the workload. In general, I'd assume it's fine because it takes a parallel raid setup to saturate. Upgrading to 100gbe is pretty unreasonable cost wise unless you buy network gear from a back alley van dealer.

Although once you reach 4 2080ti, you ought to consider switching to a titanium grade psu and rewiring if you're in a 100-120v country. If you're feeling cheap, just steal the phases from two different circuits. Last I looked, most psu operate around 5% lower efficiency on 115 vs 230.
Good to know! I'll look for an OS written in Rust elsewhere then. Fuchsia is interesting, but could be much more so.
I think this statement is a reference to a wide body of fake material circulating on social media platforms, including, for instance, a drawing of an airplane dotted with x-y damage locations, which is neither an aircraft that was in use in that theater, nor a type of figure produced by Wald or anyone related.

I did read through one of Wald's papers after reading that article, and I agree with the thesis that there's little in them about survivorship bias or a strong need to correct it. Maybe "debunk" is the wrong term; it's more of a clarification and re-emphasis of his actual work.
Why constraint 1 - given USA Labour laws
Not "stupid" but "inexperienced".

Rather obviously, people who implement OSes are usually the opposite.
NYT_diff Twitter bot tracks NYT headline, slant changes
I'd say absolutely yes, it is.

I wrote up my experiences learning TypeScript here:

https://blog.isquaredsoftware.com/2019/11/blogged-answers-le...
Yeah, but when something is built in-house like Dart is, I imagine there's some level of support the Fuchsia team will get.
Yes, as is done routinely by mutual acquaintances today.
> I think it was called Livescript back then)?

As Encyclopedia Brittanica (!! who'd have thought) puts it,

JavaScript was developed in 1995 at Netscape Communications Corp. and was conceived of as a companion to Java. It was originally called Mocha and then LiveScript before Netscape received a marketing license from Sun.[0]

And then it became 'a dialect of ECMAScript'...

[0] https://www.britannica.com/technology/JavaScript
I'm not going to "citation needed" for stuff that was published as mainstream news. I wasn't espousing any particular party leaning (but if you need to know, I'm a progressive/lefty).

This question is in bad faith.
> Usually conducting interviews is part of your performance and you are expected to do them

Whoa! Really?!?!?!

That's a huge difference from any of the places I have worked. If you didn't want to be on the interview loop, nobody in their right mind thought it would be a good idea to command you to do so.

Normally people wanted to be on the interview loop simply so they had input on the people who might become their colleagues. But there were people who wanted nothing to do with the loop and that was okay, too. Maybe you simply had too many deadlines or just were an introverted personality.

But forcing people to do the interview loop? That's seems like a recipe for disaster.
The way I've started to think about testing is like this: you should test your interfaces, because the interface is what matters. If your code is a web app, then you should be testing the user interfaces and workflows that users interact with throughout the app. If your code is a library, then you should be testing the classes and functions that users will be interacting with when they use your library. In my opinion, everything else is an implementation detail.

But, I think this distinction gets blurrier the larger your organization. While you may have intended some class in your web app as an implementation detail, the larger your organization is, the more likely it is that somebody will start using that class for some other purpose. And thus and implementation detail becomes an interface that other people depend on.
What is the legality of a site like this?
In libgen, you can search for stuff and find books/docs that match the query, but unfortunately that appears to not be possible on sci-hub, which is inconvenient.

That said, both are incredible resources for academics, researchers, students or even folks just wanting to read up on a subject in more depth than Wikipedia has.
I mean, just because y'all didn't doesn't mean others don't or you shouldn't.
It's hard to understand criticism when it is not put into words.

From my perspective, a developer from the company the article is about arrives in the comment section. I ask an honest question about the communication process internal to the company. I am told this developer is the CTO and is supervised by the CEO. Then I state the fact that I would appreciate if we also knew what the CEO thinks about this situation.

I don't literally expect answers from the people I addressed and that's OK, they are probably too busy working on the subject matter. If they take time and write one, that is really admirable and I'd be thankful.

What I don't understand is why it is considered inappropriate to be curious about these topics, as judged by the amount of downvotes I received.

Maybe the tone I intended for my post got lost in translation, since I'm not a native English speaker.
I actually did reference a user created page on the OSM wiki about the format which matched what the official docs said. But was told that wikis are not a referencable source for wikipedia.
Favorite sentence: "After a tough interview with Google and several interviews with small start-ups and companies, I have concluded that employment is not for me."

Me neither brother, me neither!
Haskell quicksort isn't quicksort, it's an illustration of quicksort.
It's not an in-place constant-memory implementation.

See also the Haskell Sieve of Eratosthenes, which isn't a Sieve of Eratosthenes, and is in fact even slower than naive trial division:
https://www.cs.hmc.edu/~oneill/papers/Sieve-JFP.pdf
I also really don't get it. Obviously things like company compensation are really important in a job offer. But what matters for my day-to-day work satisfaction is the work I'm doing, my team-mates and my team's culture. I don't think I could get really excited about a new opportunity before I knew what I would be doing daily.
We never went cloud, except for ancillary things like build machines, nagios etc that run on tiny VMs. Whenever I looked at the economics I could buy a server of the class we needed for roughly 2x the monthly rent for the equivalent from Amazon.