skysight-inc/HackerNews huggingface dataset:
Can you prove you actually tested the things?

And it doesn't work at all for me actually. E.g. I'm looking for cheap earbuds and happily find https://www.goodcheapandfast.com/articles/best-earbuds

- If looks are not the deciding factor, why are there two headbuds recommended that both are priced the same? Tell me which is best and maybe runner-up.

- The least I care about the the china-brand and the rest of the long SEO-titles don't do any good either. Only valuable piece of information here: has mic or not

- most important to me: (your) rating and price/value rating. This can only be gathered by reading your text, the latter doesn't get mentioned at all.

- most anything is a fashion-statement, I can't be buying pink or golden earphones, show me pictures!

- not sure how your reviews work, but the model you threw out won most of the hands-on reviews I found on the net

I also feel how amazon limits you. The best budget robot vacuums are both a bit above 250 and from what I read below that you still have to vacuum yourself in the end.
Meta-Review winners: https://www.gearbest.com/robot-vacuum/pp_009217978560.html?w...
and one of the roborocks https://www.gearbest.com/robot-vacuum/pp_009168125546.html?w...
"the app ecosystem on Android is like software on Windows circa 2000" amen. Maybe even worse, as it's harder to get people to pay for mobile apps than line of business / productivity software.
Yea but think how fast your Z80 interrupts can be with those shadow registers!
I’m sorry, but this one is BS.

Google interview is dehumanizing and arrogant. It sucks.
I'm pretty sure he's aware of Webpack's devserver. A common problem is multiple libraries (with different webpack configs) being built that are required inside a single app. I guess GP's approach is to run multiple devservers, all on a different port, and then put a reverse proxy in front of it.

Last I checked, webpack does support building multiple scripts (by turning the `entry` config setting into an array or object), but they'll all have the same settings (so that intermediate results used by multiple entry points only need to be built once). If webpack since added support for multiple entire configurations behind a single webpack dev server then that would be splendid of course, but last I checked they didn't.

We have a similar problem at my company that we build our frontend React code for the browser and for node, and the latter has subtly different build settings. Our solution is to run the webpack devserver for the browser, a webpack watch mode for the nodejs version, and then we run the nodejs version using nodemon so that it reloads whenever the webpack watch mode rebuilds. The nodejs version contains an expressjs reverse proxy to forward requests for things in the `assets` directory to the webpack devserver. It's messy, but it works. My biggest beef is that it's rather dissimilar from our production setup.

Of course if we'd done node+browser from the start we'd have written our code such that the node version could be run in node without a compilation step, but we were first frontend-only and then added server rendering, and by then the code already made use of a number of webpack-isms (such as weird require("raw!css!stylus!myfile.styl") type of stuff).
>This is not true. Revolution in Russia was performed by industrial workers, not by agrarians.

That's not an argument against what I said. The whole country was predominantly agrarian (and much more so than any western power).

That a small industrial minority in big cities was involved in the revolution doesn't change that.

>Also, Russia was third-fourth economy in the world just before war. Other countries in the world were much poorer and agrarian.

Yes, but we don't compare Russia to e.g. African countries or Latin American, but to the European and US western countries it had to compete with.
I don't work at Google, but I've been doing technical interviews for years and I almost always ask the same question. The reason is I've given hundreds of interviews with that question, so I'm prepared for almost all the ways people can solve it, and especially all of the ways people get stuck or approach it in ways that would probably be useful if you had more than 45 minutes but aren't going to work in an interview setting.

When I've worked with interview plans it was around having the right mix of different technical interview styles and not really technical interviews (like often someone should run through the resume and validate things claimed)
Despite widespread access to mobile phones, the digital divide remains
https://www.cnn.com/2015/05/07/politics/nsa-telephone-metada...

But you're right about not prosecuting individuals.
I am very tempted by many of the messages in this, and as a 57 year old nearing the end of his career trajectory (it is unlikely to be upward from this point, although it may have to be onward..) I've been pointed at 'the barefoot investor' which sells a story of deciding to live on radically less than often promoted by the retirement industry.

But here's the thing: a model of low income sustained living removes you from economic engagement. If we all do this, we remove ourselves from the tax providing side of the equation which drives much of the social infrastructure needed to sustain a socially equitable lifestyle for all of us.

We can only all live frugal, if we agree to the consequences of reduced economic activity. Otherwise, its quite dis-equilibriating to hoard capital, and dribble it out to sustain a life. Thats not actually going to help.

Bit from box A, bit from box B.
Angular and Angular Material – Part 1
Other than men generally having more money than women, what gender difference do you attribute this situation to? What innate quality is there that trumps financial inequality for purposes of explaining who purchases sexual services and who sells them?
>In a nutshell, I'm saying your 5th scientific category of "make shit up" would be more accurate for a broader subset than your framing would tend to suggest.

I get you, I think I may have put my point across fairly badly in that case.
HOW POROUS ARE NATIONAL BORDERS TO DANGEROUS DISEASES
Eh, not a big deal. It's a topic full of landmines and communication challenges.
Consider the oldest knowledge workers - professors.

Some of the job titles for professors are: tenured professor, full professor, endowed professor, assistant professor, associate professor, adjust professor, teaching professor, and professor emeritus.

Going back to the essay, job titles also help prevent people from being punished for not doing things they don't want to do which are outside their job title domain - at least in places with decent worker protections.

Suppose someone hires me as a senior DBA, then three months later moves me over to iPhone app development, where I have no experience. I do poor work, so the employer decides to cut my pay.

FWIW, there are job titles which are not so limited, like "Fellow" at some companies. So I think it's a mistake to say that job titles only mean Taylorism-style factory jobs.
> Everything in this piece was completely foreseeable and does not reflect poorly on Amazon.

Most of what you say is true, except the part about expecting him to work in Seattle illegally. If true, that reflects terribly on Amazon.
They feel like part of a potlach economy. All that steel and concrete must have driven a steel-and-concrete economy quite well. That they had no good economic property once made, is less attractive but thats innate in potlach: you spend capital to destroy it, to force things to happen, not to build capital intensity in the things bought.

I bet more than a few of these were longterm pigsties. Not the ones on the beach maybe.

The bunkers which litter northern France are far sadder I think. These ones were sort-of self imposed stupidity, but the organization Todt carries a burden which is still being lived.
If only my kids would sleep to 7 am every day...
Our youngest (2y) is awake between 5-6am every day. Both go to bed between 7-8pm. Not much time before and after unfortunately.
Completely agree, especially as people that stop "doing" also often forget how to "think" about the actual problems properly.
China’s Shunwei Capital raises $1.21 Bn fund with focus on India
Introduction to AI and Machine Learning
One person recommended two of his stories. Dune and The Jesus Incident.
Not yet. "I am just an egg." :-)
It depends on how you define what a 'data record' is. State of a specific address can be changed and deleted if the contract is designed to allow it.
It's directly equivalent to a normal database that keeps logs of all historical commands entered.
These platforms own the food delivery and ride hailing platform too so it is much more difficult to compete as users have much fewer incentives to switch.
Even on programmable chips, not every part of the chip is programmable.

The goal is to make this so it cannot be overridden in software. By designing hard-coded logic in a chip that already exists, you can get the same level of security for essentially zero cost.
The headline is actually “Apple loses $1 trillion status after soft holiday forecast”
Maybe you really can't measure 'grit' unless you put the student through several orthogonal tests and see how he does for the worst.

e.g. to determine whether the monkey or the fish has more
'grit', ask the monkey how deep it can dive into the ocean depths, and ask the fish how high a tree can it climb.
We are planning on adding support for DB/2 in Q1/Q2 2019. We are getting SAP HANA out first
Not a lot of comments here for the number of upvotes, but the trend of the comments strikes me as lopsidedly negative and I'd like to throw in something positive to the mix - Clojure needs more people publishing beginner friendly code even if it isn't using some specific function that does the same thing with less typing. So, y'know, I'm really glad we've got people out there who are documenting how they manage to get things to work under the new and generally unfamiliar paradigm of "practically functional". Especially since Clojure's Achilles heel is the combined double-whammy of its incoherent error messages and the learning curve for a beginner trying to pick up how to do common tasks in a world with 'no variables'.

We have a programmer with >15 years experience, who is learning a new language and in the process producing code that is neat, functional (in the sense of no bugs) and not unreasonably verbose. Clojure is a language that is dense with clever ideas, it takes a lot longer than a few months to get good at using them if they are new. The terse comments throwing out improvements or making corrections seem a little harsh, I'd hoped to see people talking more about concepts than naming functions.
Yes. And in particular:

> He talks about apps in general and how we have 100 installed but use max 30, so the rest 70 are useless, so apps are dying.

Mobile app usage is (likely) Pareto-distributed which makes it... just as alive as every other such phenomenon.
Node was designed to build networking applications just like this.
I’m going to write a blog post about it one day.

I believe it is inappropriate to ask engineer to prepare in advance for the interviews.

Last time I got contacted by their recruiter and sent links to coding websites - I replied “Great for someone just out of college”.

Google, you are boring company with insane interview process. When I worked there 8 years ago I met many people, who thought passing the interview made them better than other. I regret I didn’t tell them that they should check their heads.
Why the need for another new language? Why not just use Guile or Scheme instead?
There are jurisdictions were caselaw doesn't exist (which a lot of software engineers also conveniently forget a lot of the time) or law is written differently from the anglo-american legislations (which software engineers also conveniently forget a lot)
I would gladly hear more about this scenario. Why did the initial approach not work? How is the follow-up going to improve on that? And why was a rewrite the best way to fix things? Thanks for any insight you can share.
It is a little misleading in this context, even 25 years of experience doing IT often won't clearly mean you have the right skill set to be SDE2 (and vice versa).
He was renowned for sure, but he got a lot of hate for taking pictures of Erdoğan and generally not standing against him.

In today's political climate you cannot simply be an artist. You are apparently forced to pick allegiances or the public will announce yours for you.
aka the more women differ from men, the more they have equal opportunities.

But it's weird, where are all the correlation/causation and "soft science" comments? I guess it's still early.
"The vision was that, one day, every legal entity would have its own mobile app."

Yes, that was a classic bad idea. There were magazine apps which simply contained JPEG files of all the pages. In both orientations, even. That was both unnecessary [1] and annoying [2].

The successful apps are now all from the big players. We're past the "anyone can sell an app" era.

[1] https://xkcd.com/1367/
[2] https://xkcd.com/1174/
I work on a Windows 10 Enterprise Virtual Machine. I keep seeing ads in the start menu for Netflix, Forza Horizon etc.

I could at least somehow understand if this was a home edition, but imho totally unacceptable to have it on an Enterprise version.
I don't think this situation requires any level of intentional conspiracy. Intelligence agencies always want to know more secrets, law enforcement wants their job to be easier, and digital media were trivial to wiretap since early beginnings. Surveillance systems like NSA's seem like something that would naturally evolve - and accelerate post 9/11, as there was suddenly lots of money available to anyone uttering the words "fighting terrorism" and "national security".
> The problem is that there is almost no correlation between how candidates do in whiteboard interviews, and the ability to perform the job on a day to day basis.

What else would you use as metric? Talking about technical topics?

In my experience, there are people good at talking about those things, but miserably failing at the actual job. Introducing simple whiteboard programming tasks in addition has helped weeding those out and dramatically improved hiring success.
As a mobile dev, I of course jumped into the article, expecting some kind of insight that I had overlooked. Well, there was none. Those arguments have been around for some time and have not proven compelling.

Points 1 & 2 were invariants from the start. On the contrary, excellent and fast on device search has enabled me to keep hundreds of apps, as long as I remember their names or keywords. I have always argued that pure information is better served as a single page website, and I have always told my clients so.

Point 3 is interesting, but at some point the OS vendors will take steps against that to maintain control. I also cannot see how shipping an app in WeChat is fundamentally different from shipping it on the App Store, bare technical details like programming language.

Point 4 is the one-sided observation of the centralize-decentralize circle that is happening in all ecosystems. Once FAANG have purchased all the startups and apps, people will crave for new ones. Governments will even incentivize that.

I think the only thing that can kill on-device apps in the next years is PWAs with WASM and friends (IF a central market place for PWAs develops). But Apple and Google will have it let that actively happen; and development paradigms might not even change that much, with Swift/Kotlin to WASM compilers in the works.
So you never updated and missed out on security updates? Or what do you mean by "exact same build"?
This is written by someone who lives in the "web eats everything" bubble. It also neglects the apple store.

The fact is, webapps are suboptimal, and unless something drastically changes, will remain so. Unless you have decent caching, they are slow, difficult to use, and generally annoying.

Why? firstly HTML/JS is a very slow presentation layer compared to native, which means less battery. You still can't multithread, so any heavy lifting is serverside, which means latency in anything other then decent bandwidth areas (so no travelling for you....)

Secondly, and possibly most importantly, the GUI language of the native OS doesn't exist, which means everyone re-designs every thing, making things much much harder for end users, old people and hard of sight.

Consolidation has a point, but I suspect its the OS that will provide these apps/function.

The data I have seen from the old company was this: people who installed our news reader app were 4-8 times more engaged than the people who used our uber mobile friendly and fast news site. Apps can be faster, handle offline/near offline far better.

Apps are here to stay, until mobile web changes from a inefficient presentation layer to something more like a windowing toolkit.
How to leverage UI/UX design on every step of the growth process
I don’t strictly disagree with anything you said, it all seems sensible, and yet it also seems quite narrow and I long for you to also allow small furry creatures from Alpha Centauri to be small furry creatures from Alpha Centauri...
I'm a UX Engineer at Google. The tasks we ask you to complete in an interview are very practical - sketching out the same kinds UIs that you might build in the real world.

The impractical part is that you'll probably be coding in a Google Doc rather than a text editor. It can be a bit disorienting.

I've also interviewed at Airbnb, where I was asked to code in Codepen for UI and in node for algorithms. I felt more comfortable in a more realistic coding environment, but one of their computers crashed mid-interview and the other's network access was broken. Coding in a doc and hand-waving when necessary is better than working in a more realistic environment if the hardware isn't reliable. (Realistic doesn't nec. mean unstable, but if you're expecting candidates to write working code in a fixed period of time, you need to make sure your communal interview machines are well-maintained.)
Sounds just like any other large organization that I've worked at: Too much bureaucracy, mindless procedures, politics, blame deflection, responsibility avoidance, siloed teams hiding behind a black hole support email address that don't communicate with other teams, etc.

Its the same everywhere, its not just Amazon. There are only a couple of realistic solutions:

- become a freelancer: this way you can switch jobs every year with no problem. You will get new challenges and you will be able to face this bureaucracy knowing that its only temporary

- work at a smaller company: they often pay the same or more and have a much more personal work environment, with much more opportunities for gaining extra responsibility and performing tasks that are actually relevant to the company.

- start your own small business and become your own boss. This way the only bullshit that you will have to put up with is your own.

Other than that, this is the definition of being an employee working for someone else: you are either doing something that someone else doesn't want to do, or that they don't know how to do.

You will have limited responsibility, and be assigned a supervisor that will control your every move. That is not going to change, its the same everywhere.
how would npm install nginx be different from [yum|apt] install nginx?
I'm getting tired of the 'so many analysts were wrong about tesla'. It was completely obvious that tesla was going to be at least close to profitable, because they sold huge numbers of cars and the cars each sold for more than they cost. I predicated it, dozens of people did. there was nothing magic. gerr, this bugs me. carry on :-) (my predictions were postings here, not that it matters).
Then you'll enjoy this "guide" from /r/imaginarymaps: https://i.imgur.com/Vy0FS8F.png
There's still Consumer Reports, which actually buys products at retail and tests them. They're good for things like refrigerators, where price and value are not strongly correlated.
I would call it a leaky abstraction over a simple and reliable machine.

The ideal Prolog model is basically (timeless) predicate logic, eh? I think of Prolog as a useful but not foolproof mechanical calculator for predicate logic, and I'm happy that it works as well as it does with such a simple implementation (chronological backtracking with unification.)

The glass is half-full, rejoice! :-)
> people who installed our news reader app were 4-8 times more engaged

That's maybe because people that are engaged with something could be more willing to install the app. Also once the app is installed there is an icon on your phone constantly reminding you to use it.
If they're actually small, actually furry, and actually from Alpha Centauri...
I had a similar experience. I worked for a consulting company, noticed all my bosses worked 60+hrs/week and decided that it was best to jump ship because life's too short to spend your 30s and 40s working 60hrs a week juggling a bunch of death marches.
ahem

https://en.wikipedia.org/wiki/Lost_streams_of_Idaho
You can measure grit. The military routinely does. It takes an ordeal like BUD/S.
My father in law is such a "thinker". He has been since the 70s and worked on all kinds of projects from IBM Mainframes for up to Hadoop and Kafka for Insurance Companies and Telkos.

It's ridiculous to me how hard it is for him to find a new job at 60. He financially doesn't have to, but he wants to train younger guys on how to deal with all the weirdness one encounters in ETL Jobs.
Grit is not unknown in business and has similar problems with hiring. I helped a start up ran by some executives trying to pitch B average state school engineers as they reach senior status significantly faster than more competitive school graduates. HR depts in most tech companies pushed back as they like to hire top school candidates. Similarly as they pivoted to produce advanced hiring processes to recommend these students, HRs refused to lower their days and days of interviews that have low completion rates.

HR is almost always the failure in hiring and I am sure the recruiting/admissions will fight against whatever 'grit' factors and measurement is figured out as they still feel good personally about good grades and test scores.
We just wrote our own on top of Sql Server. Runs fine for thousands of accounts with many events per day. We currently host it on the smallest azure sql scale level. We have virtually unlimited scaling with azure, and should have no problem sharding it in future because we include extra metadata (event type, accountid, etc.) so we could choose to shard on any of those dimensions.
PNPM vs Yarn: monorepo node_modules
Population density of Taiwan: 650/square km. Canada: 4/square km.

Naturally there will be huge differences in what is cost-effective for these two very different countries.
This would be more useful for my team if it would also transpile into nginx configuration.
The Quick Brown Fox: The “hello world” of shortwave data networks
Tencent to Check All Gamers' IDs by 2019
That's sort of implied by the name. A non-recursive flatten wouldn't really flatten much, and would be called join, or concatenate.
We used to have wooden spaceships and iron small furry creatures from Alpha Centauri.

Now we have iron spaceships and wooden small furry creatures from Alpha Centauri.
Hi, author of the post here. I thought it'd be nice to post some information about the analysis.

I got some audio features (loudness, energy and valence) for Linkin Park's songs using the Spotify API. In the post, I do an album-wise analysis of these features, and how they vary across and within the albums using the Python Data Analysis Library, Pandas.

I try to articulate the general progression in style through the average change in these features, as well as the change in variation of these features.

If you're a Linkin Park fan, I would love to know how your experience of listening to LP matches with my analysis :)