skysight-inc/HackerNews huggingface dataset:
This subject is covered in much more detail elsewhere on Hacker News:

* https://news.ycombinator.com/item?id=11390545

* https://news.ycombinator.com/item?id=11388418
I'd say those are features of agent-based systems as opposed to problems. But it depends on the application
You're not there for my benefit

Even as another lowly peon I absolutely disagree with this. My boss/manager is absolutely there for my benefit. As much as I'm there "to do some labor that (he) can't/won't do" he's there to do work that I can't/won't do, primarily to be my "human shield", but also doing all the legwork needed to make sure that interesting jobs (and thus money) keep flowing my way. If I didn't see any benefit in working for a manager, I'd be working for myself.
Linting Prose in Emacs with ProseLinter
"2. Having all the answers is not the goal. Motivating the team to find the answers is the goal."

That's one that I still sometimes struggle with as an engineer-turned-manager. The natural growth phase along this path is engineer to team lead, where you are probably still the most knowledgeable and where having the answers is workable and even desirable. The next step to leading a couple of related teams you can also usually get by by trying to have the answers. At some point right around there, it flips to where you know less than the people you lead and need to change your style as a result. I've seen a lot of people struggle with that (and I personally still occasionally struggle with it).
You don't have to imagine it; you could buy one 6 years ago (http://singularityhub.com/2009/05/12/smart-toilets-doctors-i...)

And that was version 2. http://edition.cnn.com/2005/TECH/06/28/spark.toilet/index.ht... Shows you could buy one in 2005. From that description, it seems there was some room for making the thing easier to use then, though.
Startup Life: What Aikido Can Teach Entrepreneurs on Failing
Why don't you rephrase that with the appropriate level of detail and not leaving out important facts: Is not wanting to pay for something that you were given and didn't explicitly request theft? And yes, I'm an anarcho-capitalist and jumping in here.

There are a slew of assumptions that are being made when arguing for a pro-state stance. Eventually, you'll stumble on this thing called the "social contract", and then magically all questions of validity are somehow answered. It's a convenient answer devoid of any first-principles, that many are content with using as a basis to defend the status-quo of the existence of a state.
Who’s afraid of the Easter Rising
This seems to be an improvement. You trust Google's network, and you get a HTTP/2 proxy. (Or if 443 is blocked, it falls back to HTTP/1.1.) Much better than browsing plain HTTP on a shared (corporate or not) wifi.
Insurance is state by state. And the $10K I had on my apartment before I dropped it wouldn't pay for a paper cut in the ER anyway. At least it was extremely cheap like $10/yr as some kind of package deal with my car insurance. That was for a masonry and steel and tile apartment building, likely a wood house would be much more expensive.
15 Proven Strategies to Increase Your Site Traffic Now – SEO Basics
We make extensive use of Akka FSMs [1]. I find their implementation to be a lot more intuitive and less verbose than the Erlang implementation. Of course, that is in large part due to Scala's succinctness and fantastic DSL support.

FSMs make it so easy to read and debug code. It helps that Akka uses an actor system (based on Erlang's actor system), which simplifies dealing with concurrency.

> However, if the dog is sitting and you pet it, we have no idea what might happen. In the Erlang world, the dog could crash (and eventually be restarted by its supervisor).

Akka FSMs have a whenUnhandled state which can handle any event that your FSMs don't explicitly handle. Also, not handling an event doesn't cause the actor to crash. The event ends up being dead lettered.

[1] http://doc.akka.io/docs/akka/snapshot/scala/fsm.html
Mussels are grown along the West Coast as well as the East. They can be farmed in tidal rivers. Molluscs such as mussels, oysters, and clams thrive in intertidal zones and it's areas such as these where you would harvest them in their natural state.
When you speed read you pick up phrases and even whole sentences at once.

In a language that doesn't use capital letters so much, they stand out and whilst speed reading you do need to slow down a bit and figure out what's weird with the sentence being read. You can no longer just directly pick it up, you have to read it one notch slower and build it. This can be quite noticeable when speed reading. It happens with large words too. As you get used to certain capitalized words (names in a book, common large words, things like Internet) this speed bump decreases, but it's still there for people.
Self-ownership... Then you could theoretically "cede" that ownership of your own body to someone else like a family-member / spouse (perhaps a will, or have it done prior-to-death). And thus, in that frame of reference murder becomes an extreme form of theft.
Seeing fat32 nowadays is a red flag by itself.
If your window is broken and I replace your window but take your TV as payment, did I steal your TV?

Maybe you had a different window you wanted, or maybe you did not want to replace it at all.

"Paying for services" implies some kind of voluntary exchange. Government is not voluntary, government is violence, and any "service" provided by government is done so at gun point under the threat of violence and paid for in the same manner.
While that may be true, how is that observation relevant?
He does talk in the interview about why he doesn't do that, and the reasons aren't completely unreasonable (basically he wants to avoid professionalising the dev process)
The centre left is in sharp decline across Europe
Apple – Autism Acceptance
Features, yes, provided one has time to actually think of the protocol and express it in terms of some formalism (CSP, TLA+) to at least informally sketch a proof of major global properties. Or do some extensive testing (https://aphyr.com/posts/291-jepsen-zookeeper https://aphyr.com/posts/316-jepsen-etcd-and-consul ).
I appreciate more attention being given to software estimates, but it seems like there's a lack of looking at the research in this area of software engineering. Most people have a single hocus-pocus equation that generates numbers they find convincing. Furthermore, it's often the case that these numbers are never changed over the life of the project.

That would be like predicting the weather with a single model, once, for the next three months. Of course that isn't going to work.

There are a few key points I think are often overlooked:

* Estimating is less about understanding time, and more about sizing a project and effort -- a study in software economics.

* Bottom-up estimates need to be based on historical performance. They should always be ranges and should include a notion of confidence. They should be democratically created if you're estimating for a team. You can do something simple (like Estimatr) or use a tool with a lot of data behind it (like Personal Software Process) - I do both.

* Top-down estimates should also be used. I often use COCOMO and COSYSMO, with monte carlo risk calculations (http://csse.usc.edu/tools/COCOMOII.php).

* The two approaches will give you two answers (both in ranges), with confidence intervals, which provides you a better sense of the size of the effort.

* Generating and publishing an estimate has a psychological effect on the team - consider that wisely (read Peopleware).

* Estimates are good for about two weeks, after that, they've become stale.

* You're not done with a project until you've recorded your performance data (for future bottom-up estimates).

* If a project is going to last three months or less, the research shows that nothing matters at all -- estimates, process, etc. -- do whatever keeps you/the team motivated.
> I find it amazing people are still producing new things for the C64,

With his USER and EXPANSION ports, the Commodore 64 was designed from the ground up to be expandable, and to be used as a controller, either in industrial applications (controlling traffic lights, for example), or as a complete house systems controller.
One lesser-known fact about laptop hard drive encryption (the kind that's built in to the SATA firmware) is that the passphrase used to encrypt the disk is often not the passphrase that you type in to the BIOS. On Lenovo laptops, for example, the passphrase is generated by a complex calculation that was only known to Lenovo until someone reverse-engineered it: https://jbeekman.nl/blog/2015/03/lenovo-thinkpad-hdd-passwor...

If you remove the disk from the laptop (perhaps because the laptop breaks) you are unable to decrypt it (or remove the encryption key to reuse it as a blank disk, for that matter) unless you can reproduce not just the passphrase that you type in, but also the algorithm that the BIOS used to set the password on the disk. If you no longer have the laptop that you originally used to encrypt the disk then it's going to be difficult to decrypt the disk even if you do know the password.

Imagine the conversation:

"What's the encryption password for this disk?"

"'changeme'"

"Hmm. That doesn't seem to work with hdparm..."

"Well, that's what I typed into the laptop to unlock the disk, but it may not be what the laptop sends to the disk. I have no knowledge of the algorithm that <laptop supplier> uses, and no longer have the original laptop."

"Ok. Wait there while we talk to the laptop supplier."
> why do so many people want to live in the US?

The same reason why a million refugees came to Germany:

False expectations.

What people expect from the US is a country with no taxes, great economy, and the ability to become a millionaire within of months.

That’s why.
Yes, my friends (who are not really runners) both expected to compete and probably finishing around 3:30 - 4:00 but aborted about 3/4 into the race

I have competed in 4-6 hour races in other sports. Trust me I will never show up unprepared again ;) longest most painful days of my life

Best of luck with your future marathons - maybe I'll give it a go one year
Hello everyone; the defining feature of Stu is that it allows to parametrize rules and to execute a rule over a set of values for each parameter. This can be achieved more or less easily with other Make-like tools, but Stu makes it the central concept and therefore has a clean syntax for it. Stu is mainly used in data mining projects where we often iterate over many datasets, many variants of algorithms, etc.
Sidenote — I find it odd that Baremetrics make customer details public — eg if you view the images at https://convertkit.baremetrics.com/stats/reactivations, you can see everyone's Twitter handle, despite the "anonymous" customer names
Build sports car, use money to build affordable car
> My biggest gripe with Windows has been the lack of a decent pseudoconsome system that would allow an ecosystem of terminal emulators to developer, as one has for POSIX-ish systems.

This has been up since the turn of the century:

* http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/ca...

The demonstrators in the Microsoft video do warn that they will be avoiding some of the holes of the system in their demonstration. One is very briefly visible at 08'13", before the demonstrator rapidly clears the screen (again), when they run apt-get to install git:

E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)

The new Windows NT Linux subsystem apparently doesn't have pseudo-terminals.

The old Windows NT POSIX subsystem (the Interix-derived SFU/SFUA one) has pseudo-terminals with both BSD and System 5 access semantics, in comparison.

* https://technet.microsoft.com/en-gb/library/bb497016.aspx

* https://technet.microsoft.com/en-gb/library/bb463219.aspx

Moreover, a Windows console window that is the controlling TTY of a POSIX program in that subsystem has the POSIX cooked input mode with local echo, and generates escape sequences for extended keys.
While the meat of the article may be (somewhat) good, I take umbrage with the very first sentence: "A finite-state machine (FSM) is not really a machine, but it does have a finite number of states."

A finite state machine is a machine in the same sense we can claim this of a wheelchair ramp: both can be thought of as a "simple machine" (level, pulley, wheel, incline, etc) from which we build "real machines" [in the ordinary, conversational sense] like engines and dishwashers.
Can you remember a 256bit AES key, though ?
>How do TPP and other trade deals which allow Chinese people to compete economically with Americans destroy jobs?

By moving factories which previously employed Americans to countries where they don't, leaving those Americans unemployed.

All of that cheap stuff you buy at Walmart that was made by Americans pre-1990 isn't now all made by robots.

>Out of curiosity, did ending Jim Crow (allowing blacks to compete economically with whites) also destroy jobs?

No. No jobs were moved overseas via Jim Crow laws to take advantage of lax labor and environmental laws.

Out of curiosity have you ever looked into the details of any of these trade deals? Because many of them implicitly support slavery.

Does that matter to you?
Estimates are, by their nature, uncertain. The problem is less about uncertainty and more about having punishment or reward tied to them, implicitly or explicitly.

Too often the first estimate turns into the plan. That's what makes us all so gunshy of estimation.

That's not a problem with estimation, though.
Asking from an attendee point of view.
> Robots are going to pay the social security tax.

Those robots are owned by business owners like half of the people commenting in this thread, and, like the comments already show, they’ll push for 0 taxes on their robots.

They’d rather have people die than to increase the costs of their products by a few dollar.
I've seen this too. I'm lucky to work at a place where engineering estimates are taken seriously.

Most of the objections I see to estimating are objections to their abuse.
Good thing is that taste is acquired. Taste is the least important thing for an individual. For a silly population it's probably the best marketing tool. So yes, it will take time to adjust to the taste of the ocean.

Better that than killing ~3 trillion ocean animals yearly and destroying the oceanic ecosystems.
Working all day to solve other peoples problems is exactly what work in general is though. People aren't paying you to solve your own problems.
> I have no idea why you imagined it would involve beating and robbing anyone.

Reading history books gives you strange ideas.
(Tedious disclaimer: my opinion only, not speaking for anybody else. I'm an SRE at Google, and I'm oncall for this service.)

The reasons why this happens are complex and difficult to debug. Please contact your ISP and ask them to pass the details of the problem on to us.
Wow, reading the comments is fascinating. It is amazing how strong people's opinions can be on something that is ultimately inconsequential. Well, here's my two cents:

I've never thought internet should be capitalized. I was always under the impression that was the majority view of tech people though from reading the comments here, I may be mistaken. It seems even that what is or is not a proper noun is not self evident. I do not consider internet or moon or sun (other common examples in these comments) to be proper nouns. Those are not their names. Just because we generally consider them singular and unique does not make them proper nouns anymore than "the car" is when I talk to my wife. We only have one car. It is singular and unique, but "Car" is not it's name.

However, follow whatever rule you want. Most people are terrible at following the rules anyway, even when they know them. We just have to accept a certain amount of variability in these things. Just know that it will always look strange to me to see internet, sun, or moon capitalized.
StubHub Will Use Virtual Reality to Let You Preview Your Seat
For me the most interesting part was the idea that the center-left has lost the momentum that their forward-struggle gave them. Now that a lot of the things that they tried to reach have been reached there is not much left they can aim for and rally people around. I wonder though: are there any parties in the developed world that do have a real forward-looking vision?
Then you lack the history of your code, storing only the latest version. Though for personal projects, this might not matter, it's all a part of discipline in my eyes.

If you see SCM as too time consuming, then I think you need more practise, and as such, should be using as much as you can.
Sounds like TA is asking for some Fun!
I don't know if this is true for J&J, but the paint industry is quite large and banked on racism allowing them to get away with harmful lead additives. This kind of cold calculus is hardly out of bounds for US corporations:

The lead industry even sought to place the blame for lead poisoning epidemic on parents and children, claiming that the problem was not with the lead paint but with the "uneducable Negro and Puerto Rican" parents who "failed" to stop children from placing their fingers and toys in their mouths. Children poisoned by lead, the industry claimed, had a disease that led them to suck on "unnatural objects" and thereby get poisoned.

http://www.theatlantic.com/health/archive/2013/04/why-it-too...
"The realization from that is that the thing I've spent a large part of my life doing, which is building computer languages, is not such a bad idea. In a computer language, you do get to represent more sophisticated concepts in a clean way, which can be progressively built up in a way that isn't possible in natural language.

One of the things that I'm interested in is how we communicate goals to AIs. How do we talk to the AIs? My basic conclusion is that it's a mixture. Human natural language is good up to a point, and has evolved to describe what we typically encounter in the world. Things that exist from nature, things that we've chosen to build in the world—these are things which human natural language has evolved to describe. But there's a lot that exists out there in the world for which human natural language doesn't have descriptions yet. Even though our AI systems might effectively find those descriptions, we don't have ways to say those ourselves."

I really try to understand Wolfram's point of view but always end up completely disagreeing with him. He is so blatantly biased to wanting everyone to use his baby Mathematica that his reasoning doesn't make any sense. My arguments:

1. For starters, ZERO programming languages can represent a concept in a more sophisticated way than natural language, simply because we don't encode understanding in code: where a computer sees a loop condition, followed by an if and a return statement, we see the real meaning 'check if this item is in the list'. The meaning is so much more useful because it tells us the WHAT not the HOW. By know the what, we can understand what is trying to be accomplished, and so be able to predict behaviour, see logic errors the compiler can't see, make modifications to add other features, change the entire algorithm if the data structures change (use hashtable perhaps) and so on. The fact that Wolfram doesn't grasp this point, makes me seriously consider he doesn't have a clue what he's talking about.

2. The next most important thing about natural language is it is not sequential, like code. There is no structure for one precise all-important reason; you do not know what you are talking about! How many times have you had a conversation with someone, for them to then tell you that you are wrong, or perhaps add modifications to what you just said? Natural language facilitates a way for multiple nodes (humans) on a network (social groups) to share information that is not fully correct, and is expressed in such a way that another node on the network can pick it up, and express modifications, resulting in a final timeline that the group can agree on. Algorithms written in code on the other hand are BRITTLE, and expected to be correct every step of the way. The fact that no programming language can agree on a single way to handle exceptions/errors in production systems is simply a byproduct of them being unable to adapt like natural languages can. It really shows off the incredible power of our natural languages, and I hope I'm alive to see the day we crack natural language understanding!
Thanks for your feedback. Idea of the service is to easily save links for later use. There is some hidden tags automatically created when saving a link. ;)

You cannot comment a link but you can edit the title or add tags. I use "note" tag for links that I need to check later. It reminds todos 'cos after I've checked the link I remove it.

The date saved is shown when editing a link. The architecture is quite flat and everyone needs to find what works for them. I hope you could register and test the service yourself. :)
Pretty sure those are random too.
Are Conferences the Future of Work?
You can't access localstorage or anything for persistence? Can't create a popup with copy-pastable text? Any means of input or output from the game short of screenshots and manual typing at all?

The "all operations offset" sounds tricky but interesting. It'd be problematic in a typical usage scenario, but probably work well with my horrible "every line of code runs in a 1-cycle loop on its own thread" style :P
I have to agree. With SCM, I feel more in control, and worry less about my code and files getting lost, and feel like I am free to do anything.

I tell my developers when they're worried about testing something on code, just create a branch and try it, and if it fails, just move on. You shouldn't ever be worried about losing code, or changing things. This is one of the greatest advantages of SCM -- how many variations of a codebase you can have, and how easy that can be.
The infuriating part is that Taylorist management dogma has made the average (likely mediocre) manager better compensated than the average engineer despite most being demonstrably lower skilled at management than an individual contributor of similar years of experience.

This pushes even middle management roles into a more sales-like personality set of people that are money-motivated to a larger degree than is perhaps healthy for the needs of the role. Upper management does need a sales angle to a degree but your usual engineering manager is not being focused appropriately if they have to "sell" the needs of their department - the prioritization for different departments are better done in committee fashion transparent across managers rather than one-on-one back room dealings that a lot of situations turn into when we talk about "managers should be enabling and removing barriers." Political in-fighting among managers is negative value to any compan - it's a civil war in effect. Some companies resemble the economic output of war-torn nations almost as a result.

In the job I just left, management couldn't remove the most important barriers at all - the biggest cost savings that every competent company could do easily would always be the last thing possible. Meanwhile, most management directives boiled down to "do more with less than is healthy... and don't burn people out!"

When you have managerial dilemmas, something will be dropped. Work just plain won't get done, deals won't be made, costs will overrun, or people will burn out and leave. Your company culture is what will determine what to sacrifice.
Linus Torvalds's Double Pointer Problem [video]
This puts the punishment of suspension in context. It's to punish the parent, not the student (i.e. forbidding use of the daycare).