skysight-inc/HackerNews huggingface dataset:
I won't even touch the political reflexive negativity surrounding Common Core.

However, the only non-political (I'm being nice ...) criticism I continue to see is in the mathematics. And it's always because of "word problems". Common Core likes "word problems" and reasoning a LOT.

I have taught math. With very few exceptions, everybody hates word problems. Most students just want "Give me the question and give me the procedure so I can regurgitate the procedure. Don't make me think." They don't want to reason.

You can see this even in senior year of high school in the US in science. Just try to get the students to explain why they are doing an experiment (In short: "state the hypothesis"). It's almost always a disaster. After a year, you might get a majority up to the point where they can actually state it coherently.

I have this problem even with some really senior engineers when debugging things. "We did X, Y, and Z. They didn't work." "Um, okay, why did you do X, Y, or Z?" "Huh?!?!?!" "Why should X, Y or Z have worked? Is there a relation between X, Y, or Z and the problem? What is it?" <puzzled stares>

So, I see the objections as positive evidence that the Common Core standards are doing their job. The fact that adults have trouble with some of these problems is no surprise. Most of them skated through reasoning and word problems themselves.
A lot goes into the infrastructure of the carriers, I think most companies cannot afford this.
This happens so often in this community that it's cringeworthy.

When I got to the first mention of Twitter I hit the back button.
As a follow up, here's one of my favorite articles on measuring journalism metrics. https://github.com/abelsonlive/_site_/blob/master/_posts/201...

It also serves as an entry into the rabbit hole of this slippery topic.
can't you remove this cost from taxes?
I do not understand much about low level languages or operating systems, but could someone explain why does this project need C in its codebase?
I live in Baltimore, and the only thing I can think of that the OP is referring to is the fact that it is extremely risky to get anything delivered to your place while away. If something is sitting on your front stoop, it is very likely to get stolen, even in the nicer neighborhoods. However, I don't see this being different than any other city.
First of all, congratulations. Can you tell us more about why you chose Chennai? Does it have a good startup ecosystem?
Every time I see Amazon make an announcement, I'm reminded of this quote by Conan O'Brien:

"Just remember kids, you can do anything you set your mind to, as long as Jay Leno doesn't also want to do it."

Substitute Amazon for Jay Leno in that!
> I think most people would be perfectly happy to walk to the street

Then it's a worse service and you might as well to the local post office if that's the case.
That's still a runtime check rather than a compile-time guarantee, and whatever the type does guarantee (i.e. constructed instances are OK) is identical to throwing an exception (or a checked exception if you want to guarantee handling) in an OO constructor.
A break the engineer chooses is chosen and is unlikely to interrupt flow. An interruption caused by the tooling is not chosen and is more likely to interrupt flow.

Tooling cruft also increases the startup cost of some tasks. Where the amount of pain you will experience trying to do it may inhibit your desire to dig in.

The author was generalizing he wasn't assuming perfect accuracy. But in an engineering organization the size of Twitter the productivity gains of a dedicated tooling team add up fast. Much faster than you might think.
I don't see any real difference in phrasing. They both involve multiplication, and you can always use repeated counting to multiply. Could you explain more where the difference is...?
The Era of Automatic Facial Recognition and Surveillance Is Here
Every time I use collect+ the shop always seems to complain about it (it's too big/I'm too busy/etc.). These have all been various different shops.
I don't know how it is in America, I live in the Netherlands, but I haven't interacted with a cashier in a supermarket for a very long time. Every supermarket has self-checkout, and still some cashiers for people who don't want it, of course. But a lot less cashiers than a few years ago.

You grab a scanner at the entrance, scan all your purchages and then you put the scanner away and pay at a terminal. The terminal prints out your receipt, which you can scan to open the exit. You will sometimes (this has never happened to me, but I've seen it to other people) be picked by the system for a random check to see if you're not stealing anything.

It is a really pleasant system.
Parent was referring to nuclear bombs, which use very highly enriched uranium.
> While the solution described is cool, it only applies to problems that can be solved with union types in F#.

I'm not even sure it achieves that. Without linear types (or "typestate"), if an operation (say, delete) actually modifies a database or a file -- as would normally be the case -- you can have outdated references of the wrong type (ActiveUser) pointing to the same DB record. They've just introduced a far worse runtime inconsistency (while staying perfectly type-safe)!
I've wanted to do this for a long time. Have you posted anything online about how you planned your trips, or have any favorite planning sites/books?
I've had terrible experiences with some couriers, but good experiences with DPD.

They provide a one-hour delivery window, a map with local van tracking, and the driver usually arrives in the earlier half of the time slot.

You can choose an alternative date or delivery to a neighbour right until the van rolls up.

Short of Star Trek teleportation or Magic Drone Technology[tm], it's probably as a good a service as it can be.
I don't pay for Prime.

Ether I or my wife buy something once a month 'next-day'. Amazon fail to deliver it, we complain to customer service, and demand a free month of Prime.

Rinse/repeat.
I heard that result from reading Peopleware, although this (apparently well researched) Stackexchange answer disagrees:

http://programmers.stackexchange.com/questions/179616/a-good...
OS development takes time and he clearly states this will change, criticizing such a young project with halfquotes is unfair and discouraging for the developers. shame on you.

I'm waiting for OS development to start up in rust as it is clearly the better choice then C/C++ for a kernel.
> I'm pretty sure it should be possible to implement something that detects which one the device is before downloading, so how did this situation occur?

If you only have 2 architectures, and .so files in tens of kilobytes, it's just more convenient than building and uploading multiple APKs. When you have 3+ architectures, and 7MB javascript runtimes for each, it indeed feels ridiculous. Looking at you Titanium, NativeScript and now React Native.

> Unless the images are truly very different (and I don't see why they would be), isn't it possible to just include the highest resolution images and resize if necessary?

Good icons can be quite different in different sizes: in smaller sizes you remove details, adjust line thickness etc.

Another, now historic reason is that early Android devices were underpowered and loading correct size graphic vs loading-and-resizing was important for performance.
There are lots of ways a package delivery can be "bad."

For example, delivery services routinely leave packages at my garage rather than my front door, because it saves them 15 seconds of walking. This is less convenient for me but more convenient for them.

But that's not all! Once they put a package low to the ground and not out of the way, so that when I went to drive somewhere, I backed over it.

I once saw a delivery guy deliver to a neighbor. He dropped the package at their garage door, knocked on the garage door, and left. I assume they are required to knock but it doesn't say where.

And of course because they never knock or ring my doorbell, the only way I know a package has been delivered is if I sign up for electronic notifications, or I discover it on my way out.

In other instances, I've had packages simply delivered to the wrong house, I guess because numbers are hard. Once I had a package delivered to the wrong city.

Usually it works well enough, but there's plenty of room for improvement for me.
And people who refuse to see it are usually blind...

The supermarkets I go to have greatly reduced their cashiers. In most cases by at least half, especially in small shops (3 cashiers has become 2-3 machines and one human).

As for bakers, they don't just make bread and cake.

Excellent video on the subject: CGPGrey - Humans Need Not Apply: https://www.youtube.com/watch?v=7Pq-S557XQU
I don't get it. It is perfectly valid to use immutability and the Type system to enforce those invariants
in c#.

abstract class User {
public string Name { get; }
abstract bool IsActive { get; }

public User(string name) {
this.Name = name;
}
}

class ActiveUser : User {
public ActiveUser(string name) : base(name) { }
private ICollection<Subscription> _subscriptions = new List<Subscription>()
public IEnumerable<Subscription> Subscriptions => _subscriptions;

IsActive => true;
public DeletedUser Delete() => new DeletedUser(Name, DateTime.Now);
public void AddSubscription(Subscription s) => Subscriptions.Add(subscription);

}

class DeletedUser : User {

public DeletedUser(string name) : base(name) { }
public DateTime DeletionDate {get;}
IsActive => false;

public DeletedUser(string name, DateTime deletionDate) : base(name) {
this.DeletionDate = deletionDate;
}

public ActiveUser Reactivate() => new ActiveUser(Name);
}
Granted the F# approach is somewhat nicer, but I don't think the C# approach with contracts is too bad (no recent experience with .Net - 6yrs ago contracts were painful to use), but you also could go the immutable route and via a method call easily return a new instance of User and enforce the invariant prior to creating a new instance etc.. It's a minor issue in the end, the bigger issue is that your client/stakeholder knows what they actually want and you actually capture those in-variants exhaustively and correctly (implementation is minor, F#/ocaml/haskell can't save you here)...
Expectations went up too. In proportion to the increase in efficiency. So people's perceptions of their own lives decrease in value. That's just how people work. You can say whatever you want about these absolutes. No one cares and you noted it yourself.
The things you mention are unrelated to the size of the planet. I actually talked to a number of bankers from the US Federal Reserve bank 10 years ago about using a virtual world to model money systems. The thing was, they wanted to take a world that I had create, and filled with people, and take over "total control" of the monetary system in that functioning world. My response was no thanks!
"Everybody has jobs"

Yes, even the delivery guys who have already been working all day and probably don't want to work past 5pm. There are several alternatives to get custom delivery schedules that work for you, like Amazon locker or Doorman.co.
The 3 Ways in Which I Overcome My Career Fears
Intro to JQuery Curriculum on Khan Academy
Yodel is owned by Shop Direct Group (Littlewoods, Very, etc). Amazon do have a minor stake though.
Seriously, traffic isn't that bad?

https://www.youtube.com/watch?t=1&v=Cds9uQMQAnA

and also the governor of the state wrote an oped about how bad Baltimore city is at being a city:

http://www.baltimoresun.com/news/opinion/bs-ed-hogan-baltimo...

I have lived in Baltimore for over 10 years. The roads are in terrible shape, there are only two streets to get across town and they are jammed 12 hours a day. 95 is under heavy construction and the entry points into the city from 95 no longer support the volume of traffic.
> that is where you should direct your hate

I beg your pardon?

> the will of the American voters

"A 2010 poll by Lake Research Partners found that a clear
majority of voters (61%) would choose a punishment other
than the death penalty for murder." (deathpenaltyinfo.org)

And between 1967 and 1977 not a single person was executed in the whole US, independently of the possible will of some states. The Eighth Amendment from 1791, the visible public disapproval and stuff.

And please tell where you've found any "emotional pleas"? Edit: or even "outrage"?
The comments on that article are crazy. How did so many nutters find it and comment on it so quickly?
> our jails are full

I find it good. So magistrates are constrained by capacity. Of course I'd prefer they don't fill up French prisons at 125%.

If we build more prisons, we'll fill them up. US is now famously known for having more people in jail than Stalin's gulags [1]. I quite appreciate France's leniency with penalties, because I'm not sure 3 months or 3 years is really different, apart from further distorting the social network of the inmate.

[1] https://en.wikipedia.org/wiki/Incarceration_in_the_United_St...
I wasn't referring to the Async/Task in C# / Futures or Promises in other languages. That model is too simplistic and can only be applied to a limited set of problems.

Much more interesting is to model actors / components that talk with multiple other actors / components concurrently and whose state and consequently the set of messages it can receive or emit is changing over time, depending on the state of the components it communicates with.

In Erlang's actor model it's not defeatist to say that the set of all possible messages an actor can receive can be as useful as Any or String in the face of an ever changing context, coupled with the fact that actors can expose different interfaces depending on to whom they talk to. Imagine a component that on one side receives signal readings determining if some physical asset is available or not and on the other side it accepts commands for that asset, but only if the asset is determined to be available. And the commands are numbers in a certain range that also varies over time depending on the signal readings.

And as a more recent example of where static typing fails are the transducers from Clojure. Same problem, as in ... modeling of state machines.

> And Haskell seems to be doing this just fine, by abstracting IO into its own aspect which can either succeed or fail

If you are talking about the I/O monad, I believe that the I/O monad sucks for doing actual I/O, though it's pretty cool for in-memory stuff. This is because it has baked-in the assumption that those operations are synchronous. Ironically it's the same big problem when you look at, say, the common Iterable pattern and compare it with monads. And I'm not up to date with latest developments, but Iteratees also suck.

BTW, I'm a big fan of static typing. I remember a time where I had a hard to reproduce bug that I couldn't understand and I fixed it by eliminating the possibility of it happening through the type system, which was sort of a revelation. But as with everything, there are limits in what you can express and I also believe in runtime constructs where it makes sense.
It takes one to know one. :-)
cashiers are getting extincted little by little, supermarkets all have self checkin, macdonalds rlies heavily on it, train systems in many countries have automated lines, bakers have long been replaced by industrial ovens and breads in EVERY supermarket and they are now low qualified workers helped by electronic ovens who unfreeze breads instead of workers. don't make any mistake as technology evolves it becomes cheaper to replace a low-skill worker by a robot and this trend will likely raise until it is much much much more cheaper to get a robot than a worker (this is probably already cheaper to have all selfcheckin than cashiers but companies are keeping them for social and ethical reason, my thinking being that those ethical bareers tends to get slimmer when cost difference increase)
Axel Springer Acquires Business Insider for $442m
Unless you know about "let a hundred flowers bloom", then it immediately acquires a meaning at best sinister. Ignorance should not be an excuse for callousness.
Q: Where can I deliver with Amazon Flex?
A: Amazon Flex is available now in Seattle. It will be available soon in New York, Baltimore, Miami, Dallas, Austin, Chicago, Indianapolis, Atlanta and Portland.

Smart move by Amazon to refrain from making any Bay-area city one of its test markets. It's like Amazon is saying "we don't need to prove this will work in the bubble; let's base our test data set on realistic markets."
How can I improve my Python coding style?
And yet I don't see any broad robot-making movement even remotely similar to early 00s FOSS explosion.

Neither an active startup scene (no doubt they are there, just not getting much attention).

Even 3D printing kind of lost coverage.

While we're at it, let's make a robot that collects plastic bottles and other recyclable garbage?
And also one that cuts Heracleum sosnowskyi and makes biodisel out of it?
You're not refuting an argument I made. Read it again. I was simply trying to highlight the point at which we might actually have some meaningful effect on the problem. Hint: punishment is irrelevant.
Fertilisers are made of the elements NPK, none of which are found in oil; natural gas is used to power the process and as an intermediate in ammonia production, but it's not intrinsic to the process.

(Running out of mineable phosphates is a separate "peak" issue)

http://www.forbes.com/sites/timworstall/2012/04/07/were-not-...
Because one guy is delivering a huge number of packages, and the service wants this to happen in the most efficient i.e. cheapest way possible. They do their best to come up with an optimal route for all the packages for the day. UPS famously goes so far as to avoid left turns whenever possible when planning their routes for the day, because it takes up significantly more time.

If you're picking a more specific delivery window then you're throwing off that planning and it likely requires the delivery driver to take a less efficient route than they otherwise would. That costs the company, and therefore it costs you.
To get efficiency, delivery companies have highly optimized routes to deliver as many packages in as little time and distance traveled. UPS even has algorithms to reduce the number of left turns. It's probably cheaper for delivery companies to make multiple delivery attempts than it is for them to allow recipients to specify their own delivery times.

Of course, there shouldn't be any logistical impediments preventing the delivery company from notifying you once a more precise delivery window is known.
> How idempotence has to do with anything? A regex match is supposed to return a result, not perform effects…

Correct, which is why I was asking why the GP wrote:

> I'm unable to see how the approach suggested in the paper could be made idempotent with Perl's regular expression engine while still maintaining linear performance.
"He admits to knowing that the boss was murdered and Glossip admits attempting to cover up the murder, his plan being to dissolve the body in acid. Glossip, as manager of the hotel the body was hidden in, reassigned cleaning staff specifically to prevent them from discovering the body."

A couple of weeks ago when Glossip was all the rage, the various sources arguing that he should be spared somehow neglected to mention any of this. They did mention though that the actual killer is the the one who fingered Glossip, which made me sympathize with the man's possible innocence. I must say, I'm far less sympathetic now.
Probably doesn't, but it does currently contain a copy of lua, which is written in C.
after the initial boost of productivity, the effect will
no longer be noticeable

But the purpose of the team isn't just to get the initial boost but also to prevent a continual loss of productivity as the tooling inevitably bitrots. When you hit a certain size that bitrot happens much faster than you might think. It makes sense to keep an EE team on just to do maintenance. And support future changes to workflow. New languages and frameworks. Large scale refactorings happen more and more frequently as you hit walls that weren't there a month ago.
I've been getting some landing pages and ad copy ready for when the Instagram ads go public, which I was told is tomorrow.

Also, I am working on adding a test suite to one of my previous applications that I made. I finished up the model/controller tests, so am on to the integration tests.
There's a fun sci-fi series by Richard K Morgan that uses this concept. It starts with "Altered Carbon."
There are some things worth doing the napkin math first before even bothering writing the code. That includes cache efficiency. Finding and fixing design mistakes long after you've written a few thousand lines of heavily depended on code is rather difficult to tear out when you realize the design was wrong to begin with.

Since it's mostly game engine programmers presently driving this design philosophy imagine a scene in a game. There are some number of entities in the scene. Is that number infinite? No. Do each of those entities exist in their own bubble? No. You want to process all of the entities that need updates all at once. One transformation. You also know that from frame to frame there may be 0 - N entities in the scene but you don't want to be constantly allocating, deallocating, and resizing data structures. So you sketch out a reasonable number of entities to support in a scene. You know the data each entity needs to track to participate in the scene and you figure the best way to pack all of that into a struct of arrays so that processing that update is fast and doesn't waste a byte of cache.
You haven't even written a line of code yet.

There is a give and take. You have to test out your assumptions and not be afraid to throw away bad code and start again. Once you start down a path you may find that the statistically significant number of accesses for entity data happens for the members related to the physics update. You might choose a different structure to pack that data into apart from the cold data that doesn't change much.

Much of data-oriented design is like this: save the modelling for documentation and diagrams and things that humans understand. Write the code for the machine since the machine is the platform. You lose mechanical sympathy when you start designing data structures based on intuition.

It doesn't cost you anything to think about these things. It's just engineering.
> WTH am I getting d/ved for?

No idea, so I upvoted you.

Now don't downvote me people just because I'm commenting about it. I didn't start it so it's not fair.
Fine edited to outrage. Your goal is to paint the US as similar to those countries but the fact is it is up to the states. Here are the states with no death penalty:

Alaska, Connecticut, Hawaii, Illinois, Iowa, Maine, Maryland, Massachusetts, Michigan, Minnesota, New Jersey, New York, New Mexico, North Dakota, Rhode Island, Vermont, West Virginia, Wisconsin, District of Columbia
3 Ways to Get Smarter with the Data You Have
im in the UK and any delivery tends to try my house first, then a neighbour and failing that the shop opposite me.

The only time I have any real issue is when it requires signing for e.g. speciali delivery, in which case I have to go collect it.

Saying that, I did have a delivery (ebay purchase delivered by courier) that was stolen. they must have watched the driver try to deliver and when there was no answer he went to the shop and dropped it off there. a few minutes later someone went in and asked for the parcel and the shop gave it out. not their fault and it should have been signed for so I was able to claim a refund.
You should have created some anonymous form that they could submit to. I know you said you wouldn't be offended, but most people would not be brutally honest if you know they are the ones saying it.
They'll probably get the idea if you start hitting them in the wallet. Any time the stuff you ordered smells of smoke, return it as having been damaged in transit (it's true!) and they should catch on pretty fast.