skysight-inc/HackerNews huggingface dataset:
Buying homes for subsequent resale is a capital-intensive, old-economy, bricks-and-mortar business.

Zillow will borrow money to buy the homes, which means that (a) the clock will start ticking the instant each new home is purchased, and (b) this endeavor can be profitable only if proceeds from resales/rentals are sufficiently high to cover cumulative debt service costs -- in addition to all property taxes and ongoing maintenance expenditures associated with home ownership.

Why would a heretofore capital-light SaaS business like Zillow want to do this?

The only sensible explanation I can think of is that Zillow's current business is no longer growing quickly, i.e., Zillow is now a boring, mature company.

The stock dropped 7% on the news last Friday.
The article introduces an interesting guy:

> Antonio García Martínez, ad-tech entrepreneur. Helped create Facebook’s ad machine.

He puts in some good points in the first couple of sections about how the internet was built on hippie good intentions, and how Wall St came in and made it about money, but the really interesting thing is how in the next section, about online ads and how they turned into a mass surveillance regime, he's totally silent.

Makes me think this is a bit of a puff piece for these people, who were all totally complacent at the time, speaking up now about how they went wrong, except they have nothing to say about what they personally did.

This doesn't look much like an apology.

Edit: wow, here's another beauty from Garcia:

> The algorithm, by default, placates you by shielding you from the things you don’t want to hear about. That, to me, is the scary part. The real problem isn’t Facebook — it’s humans.
As someone who doesnt use facebook at all, or ever... I'm getting tired of this. The internet is not facebook. Facebook doesn't control you, and the internet doesnt owe you an apology.

The internet is a fantastic invention, that has opened up opportunities all over the world; has lessened communications costs drastically, and enabled capabilities we have never had before.

If you are so outraged with facebook, stop going to it.
I was wondering the same thing. I suspect its value would decrease in those cases, due to the lower-level representation providing less semantic association, and therefore less information (per unit object) for modeling hit rate and lifetime. Also, the higher objects count would require more resources.

Edit: perhaps in a file system, the higher-level information could still be provided?
No offense and not to sound political here, but there isn't a such language as "Taiwanese". People in Taiwan write in Traditional Chinese characters and use Mandarine (official spoken language and the majority) and Southern Min (or Hokkien proper)[1] as their spoken language. Granted they might have invented a few characters here or there and had variations in some pronunciations in words, but if you ask a linguist expert in Sino-Tibetan languages, they will probably tell you the same thing.

[1] https://en.wikipedia.org/wiki/Southern_Min
> No, Chinese won't be the new English. You get to write and conversate in English in a short time frame (1 yr).

This merely means that you were (very likely) born in a society speaking English or some closely related west European language. You know, the "normal, easy" languages.
It depends on how you read it. Contemplative readers might get upset too for a bit, but then focus on the actual problem - how to fix it?
My understanding of the consensus in quantum mechanics, is that the wave function evolves deterministically, but the state of the universe falls out of the wave function non-deterministically. So the probabilities evolve deterministically, but the empirical state of all the 'particles' doesn't. Second-order determinism, not first-order.

https://en.wikipedia.org/wiki/Determinism#Other_matters_of_q...
>you're free to pick and choose what you find valuable

This is what they say, and sure, they cannot force you. But if you do this, they criticize and condescend, telling you you're like a child not eating all his food and that when you grow up you'll find everything they say is correct.

And Goenka is very clear that the goal of Vipassana is improving reincarnation.

There is one point where they say something, maybe literally "we do not teach dogma, only truth". Saying it does not make it so! They'd be much better off not trying to convince people they aren't pushing such beliefs than being misleading about it.

As far as sleep, I tried meditating. Both there and afterwards. I do not find it as resting as sleep, and found myself drifting off while meditating during the rest of the time. What happens in my case is that I'll be awake in bed until 3-4am then finally sleep. This is fine if I don't need to get up at 5-6. But I understand this is personal and I should have fixed my sleeping habits before arriving.

For students, they seem far more tolerant of medication, probably for liability.
>> ok, for the sake of compatibility, i would dig them from IAT table based on 16bit hash (folding fnv32) of API name + dll name

;)
The authors are no dummies, they've got a business model to support!
Very relevant to your point: https://en.wikipedia.org/wiki/Guns,_Germs,_and_Steel
Thank you for your answer. This is the kind of info I'm looking for.

Maybe you got my background wrong: I do not design ICs currently, I was wondering if I should. I do design boards (high speed digital and analog RF in the higher end) and do FPGA programming to make them work. CPU design is an area of interest, but way to niche for my current field of work to accommodate.

Which areas a PhD could leverage both computing and my hardware design experience? Also, any ideas of skills or tools set required for getting into one of the big 4s?
FAANG+Microsoft and they have a division focused on Hardware operating out of their MV office off of shoreline Blvd next to computer history museum. They hire for board level HW engineers to work on Hololens and their other HW initiatives. Check out their websites for the actual listings
Huffman coding

https://en.wikipedia.org/wiki/Huffman_coding
I used MathCAD in college engineering, but never the Word interface. My wife had to use it for all her engineering classes and was a whiz with it. Still, the overall system is pretty far behind in overall functionality I would say.
...and the article is not about Facebook.
Conversely, 食 also means "eat" in Chinese, but is now used almost exclusively in nouns like 食物 (food) or 食堂 (dining hall). The Chinese character inventory is simply too large to keep all possible uses, especially across different languages.
Interesting article. Not written in the same way but an interesting earlier HN post on similar topic: https://news.ycombinator.com/item?id=8877737

--
I think Indians(maybe Asians) get this detachment philosophy as a cultural gift. Practicing it is of course a different matter. But it is easier for me to understand (or at least not have too many doubts about) the Samkara/Sanskara/Karma thing. For example, when the linked article (100 Hours of Meditation in 10 Days — My Stay in Buddhist Prison) talks about the saliva-swallowing or a lady sobbing, it does not raise too many questions in my mind. Although Naipaul has written about its ill-effects (India A Wounded Civilization))

The term(detachment philosophy) is used loosely.
The internet was actually built on cold war ideas about how to survive and communicate after a nuclear attack. Maybe you could make the case that consumer computing was based on hippie ideals (Whole Earth Catalog...), but the internet didn't get big until well after those thoughts had turned very commercial.
The people who built it did not build the internet, they built the social platforms and ad systems that run on top of the internet. The internet existed long before these people built what they built.
Business Insider is always my first stop for science news.
It might be wonderful now, but I first used Go in 2009 and it was really hard to work with back then, so maybe the OP has a warped view of the current state?
EU GDPR Countdown Clock
I think the cost could well be close. Here, if you call 911 for a medical emergency you will get a police patrol car, an ambulance, and a fire truck dispatched in most cases. That's at least three vehicles and at least half a dozen people.

If this is happening once a week then it really seems there ought to be a better way to handle it.

Edit: if you also assume that an ambulance dispatch is usually followed by an ER trip, the cost balloons even more. Seems really hard to think that a 911 dispatch followed by an ER trip once a week is the best way to handle a chronically ill person at home.
Except mutex locking the rows is also vulnerable to read skew! For example, even if you lock the rows with SELECT ... FOR UPDATE:

> CREATE TABLE reward_members (id bigint, member_status text);
> INSERT INTO reward_members (values (0, 'silver'));

> BEGIN;
> SELECT * FROM reward_members WHERE member_status = 'gold' FOR UPDATE;
> SELECT * FROM reward_members WHERE member_status = 'bronze' FOR UPDATE;
> SELECT * FROM reward_members WHERE member_status = 'platinum' FOR UPDATE;

-- In concurrent transaction: > UPDATE reward_members SET member_status = 'platinum' WHERE id = 0 AND member_status = 'silver';

> SELECT * FROM reward_members WHERE member_status = 'silver' FOR UPDATE;

> UPDATE reward_members SET member_status = 'gold_group' WHERE member_status = 'gold';
> UPDATE reward_members SET member_status = 'bronze_group' WHERE member_status = 'bronze';

-- In concurrent transaction: > UPDATE reward_members SET member_status = 'gold' WHERE id = 0 AND member_status = 'platinum';

> UPDATE reward_members SET member_status = 'platinum_group' WHERE member_status = 'platinum';
> UPDATE reward_members SET member_status = 'silver_group' WHERE member_status = 'silver';
> COMMIT;

> SELECT * FROM reward_members;

id | member_status
----+---------------
0 | gold

What you would need instead are "predicate locks". Unfortunately Postgres does not expose predicate locks to the user. Predicate locks lock all rows that match some predicate and prevent any row where the predicate is false from being modified so the predicate is now true. If Postgres did have predicate locks, you could grab a predicate lock on "membership_status = 'gold'", before running the gold UPDATE. That would prevent any row from concurrently having it's membership_status to gold while the transaction is executing.

Stricter isolation levels are an option. I would only use them if data correctness is an absolute must. I try to avoid them because they abort any queries that would otherwise have a race condition. You then have to work around queries spontaneously failing.
Compare with this new Russian patrol vessel:

http://www.thedrive.com/the-war-zone/19796/russias-new-littl...

...packed into a vessel displacing roughly 1,700 tons. In comparison, the Freedom class of Littoral Combat Ships, although faster, don't pack anywhere near this must punch and they have over double the displacement. They likely cost far more per hull too—basically half a billion dollars each.
FPGAs are certainly extremely useful but most hft is moving away from purely speed focused stuff. Only one place that I know of does asics like that and it was a complete boondoggle. The difficulty of changing, printing and verifying an asic just doesn't make sense especially once your latencies are a tiny fraction of exchange jitter, and the smarter player saw the trade you wanted to make way ahead of time anyways.
Yep. I can't rationally explain why I feel this way, but I feel like that might be changing a little. The #MeToo things seems like a fore-shock of sorts. Some very large names, and possibly institutions, appear to be about to tumble under their corruption.
I agree that the optimization isn't possible but this is for correctness reasons. The performance penalty of the extra branch is almost negligible due to branch prediction.
That argument can extend to any complicated system developed over hundreds and thousands of years. Off the top of my head, English Common Law is an example as well as English spelling and grammar. English is a horrible language with massive numbers of grammatical exceptions. I thank the many gods that I was born in an English speaking country.

Speaking of not knowing how to pronounce a Chinese character, that is not entirely true. Many of the characters you see in Chinese have a radical in the construct that indicates a sound. Unfortunately tone is not indicated.

Chinese won't be the new English, I agree. But emoji, which function exactly the same way Chinese characters do (image representing a meaning) are already an English augment.

Sort of an additional aside, there is a way to type a Chinese character by radical assemblage. So even if you don't know how to pronounce it by pinyin, you can still retype it into an e-dictionary. Similar method is used to look it up in a traditional dictionary. I never bothered to learn as it requires a touch typist skill to be fast enough to abandon the pinyin entry.
100 out of 250k people doesn’t surprise me. Despite all the media, “ordinary people” aren’t doing crypto currency trading much. Many also probably are on a hold pattern, and don’t have anything to report yet.
That really isn't face blindness.

That's self important people thinking they can demand attention by simply existing.

There's no either/or in the kind of situation. It isn't EITHER "you did recognize me and avoided me on purpose because you hate me, and we're enemies now" OR "you have a debilitating disorder and are blameless" because that puts the recognizer on trial for a crime, in a world where failing to kiss the ring breaks the law.

Truly, it's not a crime to blow past people while you're in a hurry, and the enemies your friend made are simply demanding assholes.

I've had the inverse happen, where I see someone's evil twin doppelganger, stare hard at them, walk over, and then... Oh! It wasn't them, it's just a total stranger.

Recognition and social grace don't have hard rules. Same goes for being late to work. If you have some dick boss who fires people for failing to have their ass in the chair by 9:01 AM, better to break that rule hard and often up front, and find out that the boss is tyrranical overlord, and get fired in a week, than live on for years with the spectre of doom hanging over your head.
Where is the demo?
I recommend familiarizing yourself with the languages that these Chinese characters encode to better answer that question. Homophony is extremely common in Mandarin; eliminating characters would make reading very very difficult.

Chinese is not the only language that uses these characters. Japanese and Korean do too. For these groups, the learning curve is much less; that something does not come easy to English speakers is not evidence of its inherent deficiency.
Lobbying / lobbyist are nothing more than a polite euphemism for influence and corruption.

I think it's worth adding that non pre-filled (i.e., the status quo) is also in the IRS's best interest. A person's mistake(s) allow for fines, interest, etc. The policing + enforcement also increases the IRS's head count. Layoffs by the fed gov never play well politically; to say nothing of lawyer and/or accountant fees incurred by the accused.

Bottom line: Everyone wins, except for the average American citizen. He / she is screwed. Again.
100% would recommend doing code reviews.

The most effective way I've found to do code reviews is to create a pull request for the code you would like to have reviewed. Send it out to someone or a few people that you would like to take a look, get them to approve or reject it, and then take a look at their comments and see what you can do to address them.

Some guidelines for code reviews:

1. Build each other up. The purpose of a code review is to make sure the code is good, but also to help the team grow together. If growing isn't the focus, then code reviews can quickly become harmful.

2. Get code reviewed early, often, and in small chunks. No one wants to review a 1,000 line change spanning several sub-systems, and this is the quickest way to get people to just blindly approve or to discourage them from taking the time to review. Smaller changes make it easier to justify taking 10 minutes to look over the code and make some good, constructive suggestions. It also makes it easier for the person writing the code to implement the suggestions.

3. Don't take it personally. It can be easy to let our ego get in the way when reading someone's comment about our code - after all, we might be proud of it after having spent 45 minutes on the 10 lines that someone just said "could be cleaned up"! Keep in mind that code reviews are about growing and learning, building better systems, etc.

4. The review is about the code, not the coder.

5. Honesty is key. Don't be a jerk, but don't avoid making suggestions just because you're worried it might offend someone. That just makes the review pointless!

6. Be willing spend time with the reviewer if you wrote the code, and vice-versa if you reviewed the code, to go over the suggestions made. Sometimes a comment isn't enough to adequately explain something.

I could probably write more suggestions, but I think these cover the basics.

As for tools, I just use PRs. Create one, either add certain people as reviewers or put a link to the PR somewhere that you can ask for reviewers, and then await their approval/rejection/comments. Once you have approval from the reviewers, merge it. From there you can start to build out different processes/rules around it as you see fit, but it doesn't have to be complicated and doesn't require anything fancy.

I would recommend doing them more async as opposed to scheduling "code review meetings" however. These tend to be more wasteful and can introduce a lot more stress.
That's reasonable. I usually avoid the higher isolation levels because they can cause queries to spontaneously fail. You need to be able to put in the extra work for handling the cases where they fail.

If data correctness is an absolute must, you should go with serializable.
C++ Web framework – a MVC web framework
Land mine, has taken my sight …
That’s just the anthropic principle restated.
I bet this was in before the SPF also went in. You should feel free to take this up with IANA, of course :)
Carl Sassenrath (Amiga and Rebol inventor) tried to do this with Rebol. He had what he called iOS (internet operating system) that would let you share the tiny Rebol source files. A 1/2 page of Rebol can run a fully functional GUI with graphics...etc as there is a DSL for most things and high level primitives. The interpreter is < 5MB, so you can transfer everything over the web, but still avoid JavaScript...etc. A cool vision that didn't pan out. The Red project is continuing what is cool about Rebol, but with native compilation as well and a cross-platform compiler for Mac, Linux, Windows, Android, BSD, and several others. They have a whitepaper out on Dapps (decentralized apps) and how to use it with ethereum and blockchain. Worth a look.
Payroll taxes are based on wages, so they would also need to removed if you want to hide pay from the government.
Cache replacement algorithms are fascinating and have always been one of my favorite research and development hobbies. I really like the LHD concept but the comparison to other algorithms makes it less informative for practical use cases than it could be. Specifically:

- It primarily compares against relatively weak, naive algorithms like LRU because (inexplicably) that is what many open source systems use. All of the high-performance closed source systems I've seen use better algorithms that are not represented here. Maybe an availability bias? Also, some great algorithms don't even have names AFAIK, just implementations, which doesn't lend them to easy reference.

- CPU cache efficiency of algorithm implementations is often highly relevant to real-world performance of cache replacement algorithms. This is frequently overlooked in the academic literature, which focuses on hit rate under various workloads. Many algorithms that produce good hit rates have poor throughput in practice due to CPU cache behavior; quite a bit of R&D at database companies focuses on minimizing CPU cache thrashing from these algorithms. A slight reduction in hit rate that substantially reduces CPU cache thrashing can be a big win. Cache throughput often comes from surprising places.

- Schedule-based replacement mechanics are ignored. Given some large number of concurrent in-flight operations against the cache, you can adaptively reschedule the order of operations to approximate Bélády's optimal algorithm. For many workloads you can get a step function improvement in cache throughput from this, and it applies to the aforementioned CPU cache efficiency as well. Design of schedule-optimized cache replacement algorithms is not trivial; the obvious way is NP-Hard, so the challenge is in finding efficient approximations.

Generally though, I like the formulation of LHD. It would be interesting to see how it sits in the broader scope of real-world cache replacement algorithm implementations. This is one of those areas in database computer science where the closed source design theory is richer than what makes it into the academic literature, so it is more difficult to figure out what the state-of-the-art even looks like.
Maxima, the gpl'ed version of Macsyma (which I used in grad school days for stat mech calculations on spin systems with Potts, Ising, and other models) is available for most systems. There is a Jupyter kernel for it[1].

I am personally more a fan of Julia than Python, and Julia + Jupyter is an awesome combination.

[1] https://github.com/robert-dodier/maxima-jupyter
> See: inciting riot.

The concept of "Inciting a Riot" is one of the more obvious overreaches to control distasteful groups that leads us down the path of thought control (vis a vis postmodernism or original economic stratification). If someone is so ignorant or intent that they take an unlawful action due to spoken or written word, they had problems before. The edge cases are something more akin to accomplice. Those "rioter" problems were historically in education/comprehension (ironically something the internet has helped with in many cases) or mental defect or justified outrage. Because capitalistic and social opponents could not affect the changes they wanted or changes fast enough, the idea of a riot was born as a club. Even in america, the right to assemble is curtailed by the judicious application of this opposing legal construct.
Yes, we all know that. But how many users did the early Internet have, and how many now? And who helped it grow? People like those who contemplate in the interview.
UChicago to Commercialize Hoffmann’s Generalized Software Optimization Framework
Fun with lists (in R)
I never said that we shouldn't give the military the benefits they get. All of the benefits except for pensions are benefits accounted for now and part of the current budget - they are not based on bad math.

I said you should pay government emmployees more now and let them save for their own retirements. You should want that instead of being forced to stay in for 20 years to get any retirement benefits.

And being in the military is statistically not the most dangerous job.

https://www.fool.com/investing/general/2014/03/15/dying-for-...
Rigorous Benchmarking in Reasonable Time (2013) [pdf]
> [...]but what the intrinsic differences are that make certain things intrinsically hard or impossible in one of the two systems.

Not a complete answer, but I like to think about it this way:

git was made by a file-system expert and is file-system based and Fossil was made by a database expert and is SQLite based. So a lot of the limits can probably derived from the limits of and differences between old school file systems and traditional relational databases.

I wrote old school and traditional because when is comes to modern file-systems and modern databases the lines get blurry.