skysight-inc/HackerNews huggingface dataset:
Of course I do. The idea that a single individual directs (generally through a number of cabinet positions, notably Secretary of State) is how the US presidency worked under a number of administrations, most notably Bush Jr and Reagan. Jimmy Carter was a micromanager, by contrast. The physical process of running the US presidency does not come in an orientation, just a transition process (handoff of key information and items). POTUS function is a matter of philosophy and personal style in dealing with the bureaucracy. It's how the station really works, if you're interested in the reality.
Disclaimer: I am a former Amazon employee. I worked there for exactly a year. I assume I was doing well, I was offered increase bonus and base after my initial year.

This response from Amazon continues to amaze me - first a post from Bezos that quoted an employee's anecdotal experiences and makes the (totally absurd) claim that Bezos doesn't know what life is like working there.

Then they have a post (http://recode.net/2015/09/25/why-i-work-for-amazon-a-respons...) from a Senior VP who doesn't have the same experience as someone who isn't a Senior VP.

Now they are digging up dirt on employees to paint them with a bad brush. First, the person with the killer quote should have been removed, no question. Huge bias.

But the second and third people? Nothing in the piece is wrong - they could have been strafed with aggressive language and/or they could have been berated in their reviews. Look at the wording:

All three included positive feedback on strengths as well as thoughts on areas of improvement.
Far from a “strafing,” even the areas for improvement written by her colleagues contained
language like: “It has been a pleasure working with Elizabeth.”

This is the best you can do? "Contained language like"? This is truly terrible spin. At Amazon, they teach managers to give the classic "shit sandwich" - good/bad/good. I saw many examples (I was a manager and reviewed many pieces of feedback in OLRs - Organizational Leadership Review) written EXACTLY as ham-handedly as this: "Overall, it has been a pleasure working with Elizabeth. However, the fact that she did not know the margins for a specific warehouse group when presenting to our VP shows a complete lack of diving deep, and makes me question whether or not she really wants to work at this level."

The third example is similarly vague/wrong: "Chris Brucia, who recalls how he was berated in his performance review before being promoted, also was given a written review... Mr. Brucia was given exceptionally high ratings and then promoted to a senior position." That doesn't mean he wasn't berated - it could have been overly aggressive/wrong (and you cannot dispute ANY claims written in the feedback, all you can do is complain to your manager), just because it ended on a good note doesn't make it less hurtful.

But what this really shows is that Amazon is as ruthless as ever. They WILL go after you, they will dig up dirt on you, and they will terrify you into never speaking out. If you are a former employee (as I am), you know the stories are very very true, and NEVER speak out publicly.

When the story came out, we knew it misrepresented Amazon.

I'm sorry, Mr. Carney, the story was as accurate a representation of Amazon as I've ever seen in press.
I think there were some basic pointers in there, but yes I too would have liked some examples on how to do things better.

As much as I dislike people critiquing from a purist point, I also dislike my own ignorance on things that could keep my life simpler.
https://static.googleusercontent.com/media/www.google.com/en...

But I'm sure no true self-driving car is not limited to driving in fair conditions.
What do you use to sync Docker during local dev?
I have a team that works with w/m/lamp stacks and mean stacks. In order to streamline onboarding new devs, I'd like to move to Docker. We have Windows and Mac devs.

The catch I'm having is that you can't edit a file in Docker and see the changes in the docker environment. Synced/mounted folders are sketchy at best. Files stop getting monitored because they're destroyed by an editor like Vim, or something the sync'd folder is completely empty.

Tried: vboxsf -- Doesn't always mount folders
Tried: nfs -- Doesn't work in Windows

The best tool seems like rsync, but I haven't put the time into it, because I've lost so much time already just fighting with this one issue. Everything else is working. Docker builds the SQL (or Mongo) servers, provisions them, and even deploys them to the cloud.

Please help me with my local dev woes!
Seems to me like the article and Relay are broken.

1) Why the new declarative query language for fetching attributes (columns) from objects (tables)?

2) Why build yet another transport mechanism on the top of HTTP, when there are so many to choose from already?

3) Oh, my god, boilerplate everywhere! What is this, Java?! /s

Seriously, though, the OP has some serious issues with Facebook, but to be fair Relay stinks badly of NIH. They had great success with React (a love letter to PHP), followed that with Flux (more of a design pattern than anything else), but this third attempt seems like it's trying too hard to create yet another data transport system.
I think some, perhaps most of this effect is related to the growth of the industry. Far fewer 25 year olds started a career in coding in 1990 than 2015. Fewer 25 year old coders in 1990, fewer 50 year olds in 2015.

That dynamic has existed for a while. When Gates' & Wozniak's generation started coding it was an unusual pursuit. Age gaps became part of the demographics. Like everything else, being common translates into being normal.

Other than that, I think there is a little more attrition in coding. Experience is important, but current knowledge is too. SV startups are riskier, so more appealing more to younger people. They use new technology, so less of a comparative advantage for old skills.

I'm not saying discrimination doesn't exist, I'm just saying that demographics play a big role explaining the average age. Some of the discrimination that does exist likely comes from simple human pattern matching. That's not what a coder looks like. All the coders I know are 25-40.

If I'm right, time will fix this.
Once again, you've clearly never experienced a recruiter trying to get you for a crappy job. Consider yourself lucky.

And since you haven't, you really need to stop telling other people what they can and cannot complain about. Seriously, at what salary level are people not allowed to complain about work conditions any more? What exactly are the conditions that an office has to have before one can no longer complain? Free soda? A snack machine?
Two biggest issues:
1. This just reeks of "No true Scotsman". My biggest issue with this REST purist rhetoric is that it seems no one can actually implement REST, but apparently if someone could it would solve most/all of our problems. But after many years of smart people unable to implement REST properly according to these critics, then maybe the problem is with REST.

2. "If you implement REST, you use content negotiation, and thereby eliminate versioning and typing issues"

The author is conflating the issue of identifying a client version and actually responding with appropriate client specific version data. It's one thing to identify which version via some mechanism (e.g. URL, query string, content type), but you still need the latest code to handle all of the versions you want to support. The author seems to believe that that using content type will solve both problems, whereas the real problem is actually having an implementation that responds with the right client specific data and not break between releases.
I’m pretty sure I know what the headline of this article didn’t tell me. What it was about.
He also lost me when he attacked React. React makes developing web UIs sane. It's a web UI framework written by grownups who took a CS class. UI is a pure function of state. Why is that so hard?

The fact of the matter is this: the web was never designed to be a rich application UI. Web UIs of any kind are a hack on top of the web. By definition they are embracing and extending because they were never there in the original HTTP/HTML spec to begin with. They're so popular because deploying actual apps to endpoint devices is so horribly painful by comparison.

This guy also doesn't understand what true embrace/extend tactics look like. Embrace/extend/extinguish is when you embrace something, extend it, and then drag the market into a state where the use of other things becomes impossible. Nothing Facebook is doing is doing that to the web as far as I can see. Web sites that don't use React, Relay, etc. work just fine.

If anyone is doing E/E/E against the web it is Google with Chrome and all the complicated nasty standards (e.g. the WebRTC mess) that it's dragging everyone into that only Chrome implements well. But even there I think it's a weak argument. I use Safari and Firefox and the web works fine in those 99.9999% of the time.
Federal regulators to require registration of recreational drones
Why does ASN.1 allow such large arc numbers? Is this a result of being designed before a reasonable (32 bit) word size was common enough to depend on? Ie that everyone would have to implement "bignum" so might as well set no limit?

It still seems questionable that they'd let any length be set, especially since you can just chain numbers together into a longer OID.

Base128 encoding seems fair though; the other varint formats are more exotic and only work with many ints at once.
Someone Built a Lego Safe with a Working Combination Lock
LOL, yes that is a very good point. And how does the web solve this, by reference :-) Which is of course how you always solve cyclical graph representations in my (for sure limited) experience.
Then just reword: "Doubled the expected lifespan with preventive maintenance and upgrades"
One-Step Hadoop/Spark Installer Update Progress
Add TV on it - http://www.chud.com/articles/content_images/117/WALLE3.JPG
The Web and HTTP were designed as support systems for a set of hyper-linked documents. Javascript came much later, and it's of little surprise to me that devs are having a hard time figuring out how to make them work together. The article is FUD, but some points are worth a read.
Asking a developer with a decade-plus of demonstrable experience to whiteboard is like asking an F1 mechanic to draw an engine and label the parts.
Yea, there was a reason why I mentioned DR-DOS when I was discussing the OS/2 2.0 fiasco.
> So we have to make endpoints around every possible subset?

No, you make endpoints for what clients actually need and use.

qyv has it right https://news.ycombinator.com/item?id=10413950 - responses are UI models and when you "model the problem domain of the UI layer" you're asking "which chunks of data do clients really need?"

If you really have clients that ask for "every possible subset" then this is a requirement that is completely unrelated to REST. i.e. you can try at solving it with REST, or without REST. The article actually says that: "If you're requesting some subset of a complicated object graph, and constantly re-negotiating which particular subset, then you have a problem which has nothing to do with REST."
Branding That Gets the Attention of an Influencer
Let's review a second so I can understand something, how does "I enjoy the same things my peers do, we play the same games, we watch the same things and read the same websites." equal a company's culture? The HP Way is a company culture, what you describe is a social club.
Well slow down for a second...

The web is a big public, interconnected network of documents and links between them.

Relay is encouraging single-page applications that use private data and privileged authentication schemes. That is, you have to login with Facebook or create your own private authentication services. The state that you're requesting with with Relay and GraphQL and using to build your HTML is dependent on personalized data and doesn't have much to do with linking to public URLs.

You can most definitely use React to build static HTML and work within the context of HTTP verbs [0] [1], but it pulls you away from the Flux pattern. You don't really benefit much from Relay/GraphQL if you're building web applications based on an interconnected network of documents and links between them... REST is a great pattern for those kinds of applications.

But yeah, I definitely see how a combination of React, Flux and Relay/GraphQL would inherently push an agenda that has very little to do with HTTP and the public web. Not that there's anything wrong with this, as there are many valid use cases for the web browser beyond the original intentions of the web, but it is a good thing to keep in mind.

[0] https://github.com/williamcotton/universal-react

[1] https://github.com/williamcotton/browser-express
If you worked for Amazon and you saw that Jay Carney was willing to reveal your personnel records if you talk to the media about unethical or illegal labor management practices, would it change your decision about speaking to reporters?

I think we should consider the possibility that this post will be more effective at intimidating current and former Amazon employees into silence, rather than persuading NYT readers.
Show HN: Flashcards for coders, now easier to get started
Unwanted Deposits and Bank Reshufflings
Anecdote warning, but I'm 38 and completely switched methods of nicotine ingestion over just a couple of days. I knew I liked the mild stimulant effects of nicotine. I knew they helped immensely with my ADHD symptoms. And I knew that stopping use would suck (both in terms of the temporary withdrawal and the longer term lack of something I knew existed that was desirable).

So when vaporizers improved to the point where I could use one dependably and reliably, I switched in the time it took to finish my last pack of smokes. I'm well aware that sucking nicotine mist with a bit of glycerine and and even tinier amount of food-grade flavoring is less healthy than breathing only fresh country air, results of every chemical analysis I've read (made with a good device, properly used, and with good quality liquid) show me that I'm getting the "active ingredient" with drastically less risky compounds than the inhaling of burning leaves. The less-healthy stuff that is in it is found in much lower levels than in cig smoke.

Regardless, not trying to be one of "those guys" and I typically don't go out of my way to even talk about this stuff because nobody has any reason to care about my personal conclusions about addictive stimulants.

At the same time, of every adult I know who uses a vaporizer, none of them smokes more than a cig/cigar or two per year anymore and the vast majority lose their taste for smoking after the first few days getting used to the less immediate dose from nicotine vapor versus combusted tobacco.

(also teenagers can't legally buy nicotine solution either. Never stopped them with cigs but I don't know any teenagers currently so I can't speak to their nicotine use or preferred delivery methods).
I agree with pretty much all of this.

We developed an API because we had desktop/mobile/website. They all use the same API. I call it REST-ish.

I can't see how people think returning 404 for a "this product doesn't exist" is defensible. You now have two different things intertwined: this product doesn't exist (generally not a huge deal - what if an end user manually edits the url on your storefront?), and this url makes no sense (a huge deal - something is broken).

If you had code that threw the same exception when a product didn't exist vs when the table in your database doesn't even exist you would be ostracized. I don't see how it's somehow OK because it's REST.
Fractal Compression also stalled because Iterated Systems have many patents in the technology and licensed it under too-high-for-hobbyists terms. They should have released a low-end version as freeware/open-source and concentrated on the commercial licenses / support (similar to SQLite).
That's why it's called risk. An able-bodied person can injure themselves by taking risks just the same. Why should disabled persons be subject to limitations decided by someone else that are designed for the lowest common denominator? That's the only question being brought up here.
From Dusk Till Dawn: Dimming the Lights for a Better Reading Experience
Pushing:+3+Reasons+To+And+Not+To
s/he meant "relatively left-wing (from my perspective)", implying his position is to the right of wherever NYT may be.
Does anyone know of really good REST APIs?

I feel like a lot of people talk about REST being better or worse than other technologies, but I haven't seen a single 'perfect example' of a REST API. If that's because it's impossible to make one, then that clearly tells us something, but I can't see any reason why we couldn't make one, it just seems that no one does.

By "really good", I mean something that includes HATEOAS, versioning, uses content types correctly, utilises caching properly (probably HTTP 2 only with server-push, but still), etc etc.
Complete strawman. Facebook is quite clear that GraphQL is designed to address weaknesses in REST as it is typically implemented, not weaknesses in the actual concept of REST.

> We are interested in the typical attributes of systems that self-identify as REST, rather than systems which are formally REST.
But then why do we have such a strong culture around hiring the "10x" engineer?
What I want is a human-sized quad copter :)

Maybe they'll exist by the time I need one.
An infected ad killed my computer several years back. I block all ads everywhere for everyone I know.
First Python Conference on the Caribbean Call for Proposals Is Open
A few data points to consider:

1) I happen to work in a dev tools company and we definitely see momentum towards git in our customer base. Broadly speaking 2/3rds of our customers (SMEs, F50s, etc. across a broad array of industries) are using it wholly or migrating to it.

2) Several of the larger proprietary SCMs are debuting git compatibility (e.g. p4), implying a belief that expending engineering resources along those lines is perceived as worthwhile.

3) The stackoverflow dev survey that came out recently had git with ~69% of the market: http://stackoverflow.com/research/developer-survey-2015#tech...

4) GitHub (just part of the git market) has over 10M repos now: https://github.com/blog/1724-10-million-repositories

You can always hope for more data, up to the limit of every programmer on earth answering your question(s), but the trend in the available data is clear: git is extremely popular and becoming ever moreso.
Sometimes an API can do something, but doesn't it make it easy. An alternative that makes it easy isn't just a little valuable, it's a lot a valuable.

This also applies to correctness. An API that can do something may be a bit of smashing a square peg through a round hole. An alternative that is round peg through a round hole is much better.

I don't know enough to say what this situation looks like.
The problem is that traversing a HATEOAS graph (like the www) requires a request at each edge. (The query is only the entry point to the graph, it doesn't help you traverse the graph. Relational joins make it so you don't need to traverse the graph, but this requires a lot of custom endpoints that bake in up-front knowledge about which nodes of the graph will need to be pre-fetched)

edit: Either you edited or I misread, but "You can describe traversals of the graph or tree in a query embedded in an HTTP endpoint" - this is basically what GraphQL/Relay is: an easy way to do arbitrarily nested or recursive queries, like those you find in real complex applications.

(Plug: I am a React consultant, hire me!)
The tone of that article doesn't make me want to join their team...
Ask HN: Should I incorporate as a freelancer?
I've been freelancing for a few weeks and I am wondering if it's worth it for me to become an Inc, LLC, Sole Proprietor, etc. The only business expenses I've had this year so far are moving and office space. I will be working out of Philadelphia and currently have clients in Boston and Vancouver, but that will likely change as I get more clients. Additionally, I foresee growth as I have been doing similar jobs for my clients and will likely continue to do these types of jobs.

Thank you!
Agile Testing in Mobile Context
How Your Smartphone Can Detect Bipolar Disorder
in 6 years here this is the first post i felt compelled to comment on without even reading the article. the comments here reinforce my decision...

if you have read the GraphQL docs, and built a sufficiently complex REST API, there is literally, technically speaking, no way to support this claim.

still i skimmed the article... it must be satire.
I'd guess you haven't interviewed that many people then. IME, lots of people look like they'd be good fit for a higher position like architect, but then when asked to code up a somewhat simple problem they perform far worse than average.

Insanity would be you assuming they are good at problem solving and coding without even checking.
I think there were extra instructions for Lisp, it certainly ran the Gabriel Benchmarks faster than you would expect for the advertised clock speed. I only spent a day talking to John Fitch about the implementation and most of that was looking at his bindings to the GUI from Lisp.

Cambridge Lisp was written in BCPL which was one of the languages provided with the machine so you probably wouldn't want to completely replace the instruction set.
That's a good question. Let me see the original article:

> Bo Olson was one of them. He lasted less than two years in a book marketing role and said that his enduring image was watching people weep in the office, a sight other workers described as well.

If other workers described the same sight, I don't think his input's important enough to require personal credibility, so I'm not too concerned. But the use of "lasted less than two years" would be more honest written as "spent less than two years" or something, because there's an implication that he chose to leave voluntarily.
Clowns to the Left of Me, Jokers to the Right: Twitter's Big Problem
I want to see benchmark comparsion with the Rust version.
AWS S3 doesn't expose a flush()-like call in their API, hence what is the point of exposing something that the underlying service doesn't support?
People running hurt themselves when they hit people, a wheelchair (itself) won't normally be 'injured' by hitting a person. Moreover there's a natural limit to the momentum in an impact as heavy people usually can't run as fast as lighter people. Motorised wheelchairs usually have relatively heavy batteries and some relatively hard, sharp, edges.

Joystick controlled chairs I've seen have had the joysticks as dead-man's handles too.

I suspect that would lead to some reluctance to embrace the idea completely.

From the perspective of disabilities the demonstrator is certainly using their legs a lot, it seems the usefulness would be for lower limb amputees primarily?
One thing I'm working towards on a Mac is to have a NFS server VM, and storing the working files in the exported NFS share. This sidesteps the vboxsf rubbishness, and changes the problem from the host needing a server to only needing a client. I think nekodrive should work for this on Windows, but I've not tried it. Mac works fine.
Every company I have worked for, since 2001, has used Perforce. My latest employer was starting to think about maybe possibly using something else, but I doubt it will happen.

I suspect this is a generational thing. The companies I have worked for were generally formed in the nineties or 00s, when the free source control systems didn't exist or weren't yet popular. The companies being formed now use Git almost universally.