skysight-inc/HackerNews huggingface dataset:
I'm sadly not particularly knowledgeable on US game development salaries. I can imagine it varies a lot by company and region.

I work in Vancouver, Canada, and a large portion of its industry is due to Canadians commanding lower wages. Combined with a weaker dollar, higher education availability, and single-payer healthcare, outsourcing to a Canadian studio can save a lot of money. FIFA, for example, is made in Vancouver and the franchise commands a large revenue stream. Provinces such as British Columbia and Quebec also provide tax incentives too, since it's high-skill work.
Governments today are isolated from the day to day struggle of their people. Their interests and values are not aligned with those they represent. Grassroots community movements do function similar to governments, but have the potential to be more transparent and less susceptible to corruption from special interests.

Ronald Reagan said it best:

"It has been said politics is the second oldest profession. I have learned that it bears a striking resemblance to the first."
This is how I'm precise where you're not: I'm literally quoting you and myself and you're just further adducing strange comparisons.

So again I challenge you directly quote my value judgments of the author. You can't though. Because none were made because my only point is that advice is facile for whom it is relevant and impractical for everyone else.

>Hey, I'm not saying anything bad about Jewish transsexuals...

I have no idea where you pulled this one from but let's run with it: if I saw comments and articles being written by Jewish Israelis about the impossibility for various reasons of the two state solution I would absolutely point that out without a shred of shame or cognitive dissonance.

>You (negatively) characterize people based on their race and gender and ascribe properties to them.

Show me where I ascribe a single negative property to the author? I explicitly said many many many times that the article is what I'm impugning. I said the writing is self-indulgent and the writing is self-aggrandizing. You can come to his defense all you want but he's not under attack - the facile categorical imperatives are.

Even if I weren't crystal clear in the initial comment every single one afterwards has underscored that I'm talking about the article. But you (and everyone that downvotes) willfully misconstrues in order to reaffirm their own allergy.

>very obvious and you deliver it with hostility and cynicism as if you were sharing verboten secrets.

I'll say it again: if that were obvious this post wouldn't have gotten traction.

Edit: you know what's beyond aggravating about having these meta-debates with people like you? The complete and utter lack of empathy on your part for anyone but this supposedly aggrieved/offended person.

Do you understand how obnoxious it is to come to hn and be ambushed by this kind of humble-brag jibbering? We don't all live in this world and it is all kinds of disappointing to read this constantly. I choose to avoid it on every other media channel (I don't use fb or ig etc).I don't understand why this stuff gets posted here under the guise of "startup culture". It's personal brand building! It belongs in an issue of people magazine rather than a tech site (there's nary a technical issue raised in the entire 1000 words). I say ambushed because I confused this person with Jeremy Kuhn and figured the article was going to be about np approximations.
A Year of Surprising Science from NASA's InSight Mars Mission
I only have the help article to go on and the fact that their export functionality is for some reason hidden in the advance search drop down? as i've just found out...

Anywho, the help article does not state it it "takes days", so it does not have to "take days". Otherwise known as listening to the documentation not the observed behavior. Programming 101 here.
The sooner academic publishers die the better—not a very original thought, I'm aware.

There's still very much a distinction between (self-)publishing on the arXiv and publishing in a 'real' journal/conference within the academic community, and I think it comes down to two factors:

1. The arXiv moderation process has a much lower bar; you see some pretty rubbish papers (often from large tech companies) make their way onto the arXiv which would never be published in a 'real' journal; ultimately this isn't a shortcoming (the arXiv has had a monumental impact on academia), but rather that the arXiv isn't trying to be a peer-reviewed journal.

2. Visibility/'impact' is lower on the arXiv; there are ~14k submissions per month, so inevitably the signal to noise ratio is low.

I feel what we really need is for a few universities to put the many millions they spend on annual subscriptions into some kind of endowment to pay for proper editorial boards for a peer-reviewed arXiv instead, open access, perhaps with a token fee for submission (or a slightly higher academic affiliation bar). I think if two or three big universities from each of the US/UK/Europe suddenly made this change we would see the death of academic publishing in months.
All of them. Linux has one: C.

For clarity, this is talking mostly about what languages they will use when writing the OS itself (that’s what “approved” means in the article). They do also touch on what languages are supported (I.e. they’re building the infrastructure to allow it to happen) in userspace, but they’re not saying you can’t run other code on the OS.
Never clicked that because i have no reason to look for a dns export/import button in the advance search gui... hmm. good to know about, not sure why they put it there.
A pure Go library for loading, compiling, and debugging eBPF programs
You couldn’t today, as the homeowners along that line would tie up any effort to condemn their homes in court for at least a decade.
>I think the effects of memory bugs on security are often overstated.

How often?
I ran a ML based 3D reconstruction service for 7 years - given face photos of a person, reconstruct a realistic 3D likeness. I licensed a finished 3D reconstruction algorithm, purchased $50K worth of servers plus a federal reserve bank quality hardware firewall, and put it all in a Los Angeles downtown co-lo (the former Enron data center, actually.) I paid $600 a month to run that, as opposed to the equal compute capability being $96K per month if run at Amazon.

It kills me to see people being raped by the cloud, but everyone just lines up like good little boys...
not if you have a monopoly. Which is why customer support for most ISPs in the US is so abysmal.

And even if it is just a sufficiently large company, if the customer is not a large payer and the issue is non-trivial to solve, the the cost of losing that customer could very well be less than the cost of fixing the issue.
Perhaps. Simply having watched "Who killed the electric car" it was clear that it was already heading in that direction, even if it was snubbed at that time. Tesla was the agent in making electric cars cool though. It's true from a wider perspective that Tesla is a replaceable part of that timeline and perhaps inevitable, but the fact remains that it was Tesla who got the mindshare that has moved this forward.
> Tests should be easy and you should want to write them.

I must be using go wrong then because I've always felt they were easy and wanted to write them. The last big project I built with it had great test coverage.

> be opinionated about deployment, so that those rube goldberg tricks you have to do to put into prod are testable and reproducible.

Of all the languages I feel like go's deployment is probably the simplest, if it's hard for you you're probably doing something pretty wacky.
That seems like a tremendous waste of time and resources for everyone involved.
Its more like math is the underwriter that one is more than soft skills.
Why are developers continually attributing new meaning to old terms? This has nothing to do with Lambda Calculus, anonymous functions, or Lisp. Why call it Lambda Architecture?
Sure. Our numbers are smaller, as our org is much smaller but I think they hold up.

We have under 100 engineers at BuzzFeed, so for us we reduce time spent supporting applications by a single percentage is almost equivalent to having an extra engineer!

On a typical day we'll do 180+ deploys. That'll be roughly 60% stage, 40% production. To deploy outside of continuous deployments (e.g. to push a branch build to a stage environment), is as simple as browsing to our deploy UI, selecting the service you want to deploy, the version, and the cluster to deploy too. It takes an engineer about 40 seconds to do that (time measured from typing URL, to hitting the deploy button)

Continuous deployments means for production deploys for master, that step is automated. So that's a saving (in engineer time) of around 40 seconds per deploy. Over the last month over 1400 deploys were made via continuous deployment.

This means from a developer productivity perspective roughly 2 engineer days per month (1400 deploys * 40 secs per deploy / 3600 to get into hours / 8 hours per day) ) are being saved as a result of this change.

However this is really a side benefit. Our real motivation for making this change was to ensure that all master builds are deployed, and that each of our ~500 micro services is always on latest master.

This is to reduce developer anxiety of deploying over a branch build and thus minimize stress around making change.

The productivity side benefit is pretty nice though!
Find Rf Peoducts
> Both Kaggle and google colab offer free GPU.

I think this sentence invalidates your argument against:

“The number of places where machine learning can be used effectively from both a cost perspective and a return perspective are small.”

In a hobbyist world, free GPU time is an amazing thing, and you can do a lot of fun and rewarding projects using transfer learning and other techniques that avoid heavy engineering and data processing. In a business world, where your product must consistently and accurately perform well, problems that may be solved by ML need to be heavily scrutinized and researched, because for most problems there are cheaper, faster, more robust solutions. Free GPU time doesn't weigh in at this scale.
So when you read something like:

> Go is not approved, with the following exceptions:

>>>> netstack. Migrating netstack to another language would require a significant investment. In the fullness of time, we should migrate netstack to an approved language.

> All other uses of Go in Fuchsia for production software on the target device must be migrated to an approved language.

Does that not imply that okay sure use whatever language you want, but production software (that exists in repositories?) must adhere to approved languages?

I could be misreading
I'm on a mobile device, so here are my thoughts.

I didn't quite know what your site was supposed to be saying, to be honest. Is it a blog, a portfolio, a product-hunt like page? I really wasn't sure.

After reading a bit I figured it's a little bit of everything, which is kind of confusing because I feel not many people would stay long as long as I did to figure out.

The words "personal" on the page or in the header would help me a little bit to get where I think you are aiming at the site.

Your design was great, although I feel I'm missing some of it because the mobile site only has the "basic" version. That said, the splash page and the basic page are like two different sites, so that is very jarring for users, it was for me.

I was also confused about the buy me a coffee link, because most of the content appeared to be things you wanted to write about, and I get you may be looking for some extra side money (we all are), but seeing that link made me feel like you need to be a bit more focused on your target. My question was why would I tip you, I didn't know what quite you were providing in content on the site. My main driver for saying that was the loading bar on the home page, where it then took me to am about you page. Hard to understand in that flow what the site is about to me.

I tried to be frank here, I hope this provides you feedback whether you take my words or not. God bless you and have a good day.
This list is about two different things: what languages are allowed in the project, and what languages are supported by end-developers.

I imagine that an end-developer could write their Fuchsia program in any language they want, but if it's not on this list, Google won't provide documentation or bindings for it.
*did

There was a forced password reset that enabled real password policies.
I hate the implication that only men are bad actors here though.
For my own company we built out at two regionally distinct colo facilities. That worked really well and operations was efficient and costs were moderate, clearly tied to CAPEX increments which were predictable.

Recent projects have been on AWS. For a project that is roughly on the scale of our colo in terms of instances, though with aggregate lower performance, we are buying one of our colos every year. It’s insane. Network costs are particularly egregious in AWS.

But there is absolutely no way we’d be permitted to build colo facilities for many reasons and there are many reasons why even if we could get permission to do so we would choose not to due the resulting death by a thousand cuts orchestrated by the team who happens to have inserted themselves as the owner for DC/colo like things.
Certain people have a printed copy of my keepass database password and know how to access it on onedrive (from one of my devices, no direct access) if they need to, so they can at least access bank accounts and health plan and all that.

They also know to log in to my PCs and null-write all the drives. ;)
Launch HN: Encoro – Get 360° feedback easily
For the non-enterprise user, isn't this the scenario established today, with no failed business?
2046 Lab
Change your understanding of “yes” to be “okay” . It will save you headaches a tons of money. Confirmation that they heard you doesn’t mean they understand or comprehend. You gotta jump right past the yes, to parrot it back to me or say it back differently to me.

#protips
> Does that not imply that okay sure use whatever language you want, but production software (that exists in repositories?) must adhere to approved languages?

> I could be misreading

To me, that reads: platform devs, i.e. people developing Fuchsia itself, must adhere to the approved language list. Which is not uncommon in projects of all sizes from small to large.

I think the wording is a bit weird because Google is expecting 3rd party device manufacturers to make modifications to the OS and expects them to adhere to the approved language list as well.
I doubt this was your intent, but my reading of your words kind of leaves me thinking that someone with no background knowledge would leave thinking there is(!) great known danger with at home LSD use, and also that achieving results reasonably equivalent to some of the outcomes described in clinical studies requires(!) the counselling that accompanied it.

As for now, the only evidence that can answer such questions is anecdotal user stories, of which we have lots, and from my reading in that realm, while there is undoubtedly very real risk involved the vast majority of feedback is positive.

If someone who could benefit from these substances is in a position where they are unable to obtain professional services (most people I'd think at this stage), it would be unfortunate if they didn't bother looking into it because of reading overly protective risk assessments.
One of my colleagues literally apologized when he had to call out (with pneumonia) after coming in progressively more sick for a week. We have fully paid and (IMO) stigma-free sick leave, but nobody ever apologizes similarly for coming in sick and increasing the viral load of the office.
LPrint
Operations teams deal with both. You design your system with enough spare capacity that you can live somewhat degraded for a time - you must if only due to the lead time. Software failures are far far far more common than hardware failures so once you combine these, the occasional midnight trip to the colo is both rare and oddly satisfying for hero types.
I've found that often "lacking motivation" is a misinterpretation of "lacking understanding of a fundamental idea." Do you really lack motivation to implement clock recovery in your toy software modem? Or do you not know how digital PLLs work.

IMO knitting is closer to CRUD dev: it's a little challenging but it's mostly just reading/following patterns and counting (although this is coming from someone who crochets and doesn't knit.)
> This document describes which programming languages the Fuchsia project uses and supports for production software on the target device, both within the Fuchsia Platform Source Tree and for end-developers building for Fuchsia outside the Fuchsia Source Platform Tree. The policy does not apply to (a) developer tooling, either on target or host devices, or (b) software on the target device that is not executed in normal, end-user operation of the device.

As far as I can tell, this is supposed to be “the” languages that can execute on a Fuschia-powered device.
Australia spy chief warns of “unprecedented” foreign espionage threat
All of the current mobile OS. I also prefer seeing it formalized than hidden.
> In actual fact, most people try to avoid JS whenever possible

Eh... if this was actually true, the web would look very different. I just can't square "web programmers hate Javascript" with "web programmers are obsessed with SPAs/CSS-in-JS/NodeJS backends/etc..."

> Writing in other languages still means transpiling to JS in the end

I'm assuming you already know about WASM, but if you don't, the future is starting to look relatively optimistic for other languages on the web. Still some problems to solve, but C++/Rust already have pretty promising toolchains working today.
Hey ZhL,

that's not just you.

It's me and everyone else I know.

That's why these are called whiteboard firing squads.

The only way I know to improve on whiteboard interview performance is to do more whiteboard interviews unfortunately.

I know it does not make sense. I know it does not teach your or help you further any actual skill you will actually use day to day, but that's the problem we programmers have painted ourselves into.

The "remote" equivalent to whiteboard interviews are "live coding" sessions where you type code into a site like codebunk.io

Some random person who works at your potential employer will send you a link to a site you can type code into and ask you to solve a "5 minute problem". It's not fizzbuzz, it's not a for loop - it's going to be something slightly tricky like finding the sum of 3 numbers that add up to a specific number.

One thing I can recommend at a whiteboard firing squad is to see whether the firing squad has people in it that want you to win.

If you think out loud, show them you know what you're talking about, they might come out, feel your issue and work with you.

Isn't that the kind of people you want to work with regularly anyways?

I am happy to work out some trial whiteboard interviews with you if you feel that would help.
"Complex javascript apps just weren't a thing"

I don't know what you were doing in 1995 and 1996, but I was building Javascript apps. They were "a thing" for me at least.
The Mullvad VPN app is written in Rust.
How so? It took far less time than other interview process I’ve been involved with.
You completely missed to grep anything valuable out of a fairly obvious response. Is there judge there under duress?
Those are models now??

I'll trade my laptop for an abacus before I trade it for a pixel.
which textbooks are interactive like that?
A lot of people only have a number of exes that they could measure on one hand. It's not like credit reporting or playing fortnight where you can prove 'your references' multiple times a month.
A couple of things..
- The tablet is ~5 years old. Even if it was 8 years old, I think you should still be able to order a pizza online.
- TLSv1 is far from plaintext. But in any case, the TLS version doesn't matter in this case. The site was loading properly.
- Even if the TLS version was outdated, are we now banning people from using the internet for using an older device?
- Submitting the form didn't work, the navigation was partially broken. It was probably a JS issue, but I don't know.
- The moral of the story, to me, is that, as a web developer, you should also care about those $few% that don't have all the green boxes on caniuse.com. Depending on how many users your site has, this may just be a few people or it might be millions - among them, possibly, your Mom.
The Wikipedia article is also kept reasonably up to date with the URLs: https://en.wikipedia.org/wiki/Sci-Hub

They used to have a .onion address, which I assumed would continue to be the most reliable way in, but it's been down for a long time. I'm surprised, it seems like Tor would be the best way to remain up and accessible.
> First, I don't have the exact numbers. Second, yes, out of 100 people that apply, less than 1 get an offer, on average.

Hiring 1/100 applicants is not unusual for any company. Put up an ad on any job site and you'll get hundreds of resumes from across the planet. Given the low effort of putting in the initial application, the odds are not a big issue there. The interesting question is the number you seem to be guessing at, namely the odds of getting an offer after investing so much time and effort in the grueling interview process. If that's very low, then they are quite evil.
Travel tip: get AXA trip protection for your next trip
What colo company did you use?
A knit is not a knot.
A more positive take than many of the comments here: this seems like an thoughtful and balanced synthesis of the various tradeoffs between languages for systems development, at least from the perspective of a large project with many developers.
Xtree blew my mind when I first found it and it was then THE first thing I installed on every new DOS computer I built/got.
Oh no! I'm seeing it down.

https://downforeveryoneorjustme.com/whereisscihub.now.sh

Sending HugOps to everyone at Zeit trying to keep 99.99% uptime for now.sh at a time like this
Yeah, if "doesn't need the job" is in the top five things you'd say about them as a team member... you really want people who will tolerate or even attack with some zeal the grind that it is to get a business going.
For the distribution of languages inside fuchsia, this is the output of "tokei -s lines" in the git checkout of fuchsia: https://gist.githubusercontent.com/est31/5c13979043e760a597a...

According to this, Rust is the language with the most lines in fuchsia. It's important to point out however that of those 2.2 million lines, 1.4 million come from the third_party directory, which includes vendored libraries, mostly Rust ones, and sometimes also multiple versions of a library. The src directory contributes 0.7 million lines of Rust. If you add up the two numbers, you get 2.1 million, so most Rust code resides in those two directories.

This is the tokei output of the src directory: https://gist.githubusercontent.com/est31/5c13979043e760a597a...

To compare those 0.7 million with other big Rust codebases: Servo has 0.39 million lines, the Rust compiler 1.4, and parity-ethereum has 0.18 (using tokei and only looking at the git repos here, without excluding and tests or including dependencies outside of the recursively checked out repo).
Complexity control by gradient descent in deep networks
Thanks man! Lifelong masshole here.

Your post was much better than mine, but I appreciate the comment.