skysight-inc/HackerNews huggingface dataset:
> people spend so much time debating what is and what isn't REST should be a red flag that maybe it isn't the answer to everything

Does not follow. People spend so much time debating what is and what isn't REST because there are a great number of people who do not understand the topic, have no actual interest in learning it properly, and then come to wrong conclusions and start making wildly inaccurate arguments.

Not all Web application problems can be cleanly modelled over REST, so indeed it is not the asnwer to everything, but most can. For those that can, using the REST architectural style is more advantageous than, let's say, remote-procedure calling.

> All the simple REST examples make it look like it is the perfect solution for CRUD tasks.

All the simple REST examples are written by those ignorants I mentioned above. The simple CRUD model falls apart when there is just a little more complication involved. REST does not mean just CRUD, as any decent REST book teaches.

> If the server returns 404 for a resource, what actually happened? Did the web server or my application return the 404.

⁇ If the server returned 404, the server returned 404. This means the client application/the user agent made a mistake, indicated by the leading digit 4.

> Conflating HTTP and application error codes leads to confusion.

When following REST, that conflating is actually a good practice. Not doing so means tunnelling a proprietary, possibly ad-hoc protocol over HTTP, resulting in non-interoperability. There is no need for any confusion, the response body can deliver a precise problem description applicable to the concrete error condition, perhaps even giving an indication how to fix the problem. There is a wealth of status codes <https://github.com/for-GET/know-your-http-well/blob/master/s... and many of them semantically map to typical application error states, and it's okay to fall back to generic codes like 422 or 400.

> HATEOAS is just superfluous. […] I just haven't found a practical use for it.

You need to bring a better argument to the table. Establishing relations between and traversing resources using links and other hypermedia controls is central to the REST architectural style. Every Web browser does this, for timbl's sake!

> REST encourages creating a CRUD interface for every single resource.

Not true. Nothing in REST encourages this. It's the software architect's fault if there are 100 (supposedly underutilised) resources, not the fault of the architectural style.
Shift1 system for 1-wire shift registers
Yes, I think it was inappropriate of Amazon, but I absolutely believe they consulted their lawyers before making this post.

It's the signal they're sending to future employees that matters here.
Amazon just did real harm to Mr Olsen's employability. To be so casual about this is typical Amazon. Also this is classic ad hominem attack. If the message is true attack the messenger.

Jay wouldn't need to attack Mr. Olson personally if the message was wrong.

Why does Jay lead with an attack on Mr. Olson? Could it be that that is the best he can do?
I'm basically an Amazon fanboy, but with the failure of the Fire phone, the continually over-wrought nature of AWS UI, and now this hamfisted response to the NYT, they are really losing their appeal.

Amazon: Your current employees had already written much better responses than this within 48 hours of the NYT article coming out. What is this drivel supposed to accomplish? Why is PR rant hosted on Medium? Why are you exposing old employee personnel records? Why are you putting political operatives like Carney in charge of your PR?

Get it together guys. The NYT article is ancient history now and didn't merit further response. It was an obvious hit piece but your reaction has been quite poor.
It wasn't. The Google "interview" involved being asked to regurgitate Linux header constants from memory.
Basho, Maker of Riak, Join Advanced Erlang Initiative to Promote Erlang Products
This is amazing and I hope it stays that way for another 100 years!
Maclisp ran quite fast on the PDP-10, even faster than DEC's FORTRAN (for a while, DEC was sufficiently embarrassed they put more effort into it).

High quality Lisps being proprietary during the chaotic '80s through the early-mid '90s was certainly an issue for Maxima, but for the licensed Macsyma (see my other comment on the history) I think that would have been an acceptable part of the cost of goods; too bad Symbolics demanded you by one of their Lisp Machines to run it for too long.

Self-promotion ... yeah, Mathematica wins hands down there ^_^.
> I think you're conception of what a Ph.D. signifies is very wrong, and it's leading you to improperly value what advanced academic training is worth.

The job requires being able to develop software. Candidate, who holds PhD, cannot develop software despite being a CS grad. This isn't charity; what would you prefer I do when I get such a candidate? I saw two PhD holders like this which, yeah, could be a HUGE minority but I'm being honest about how anecdotes can create bias and I also mentioned that I felt I did a great job not using my bias against them (we all have bias, remember).

Not knowing the language we use in house? Not a big deal. But if you can't demonstrate fundamental understanding of code structure in any language I'm sorry but I do not have the budget to educate you. I wish I did sometimes; someone who has awesome problem solving skills could be an amazing developer.

> What about documentation, quality control, or formal methods?

No offense but when shit hits the fan, none of those matter. At all. Unfortunately. Plus I think it's good when you make developers think about and do as much of the documentation of their own code as possible. Sometimes seeing it on paper can make you realize "hey, this is too complex to call; I think I can simplify!". At least in my experience anyway. QA / QC, yeah separate group is idea but rarely doable depending on your industry.

> Seems like you're ignoring the bigger picture.

Again, business is not a charity. Big businesses or academic arenas can afford more things but start-ups / small companies? Anything that isn't moving the product out the door gets slowly trimmed away as margins get leaner. It's far worst in the government contracting space where you're legally allowed to only have a certain amount of margin.
I imagine that new versions with the private API stuff removed will be allowed. I don't believe that this is some sort of lifetime ban on Youmi.
Show HN: Employee Vesting Calculator & Equity Guide
There would be operational gain. Modern signalling systems can reduce the time between trains to 30s or less, and computer-controlled acceleration and braking is more efficient and smoother for passengers. Also, at some point trains do wear out — i.e significant parts are worn out, like the chassis, that it makes sense to replace the whole train.

I'm just repeating the press statements of London Underground, who have been investing in new trains and signalling systems for the past 10-15 years. (It follows a long period of under-investment.)

New equipment does bring new bugs, which is why they introduce new trains on 'spare' track at night (without passengers), then with passengers on Sunday nights, then Sunday mornings, etc.
Didn't know this was happening, sad but not surprised though..
You can also drop files on the editor. Try it on the demo site.
Looks great! What if they added spatial navigation by video camera and voice control to cover people who have trouble controlling the chair with their body position.

At least for simple navigation I think the tech is mature enough to make it today. Just make sure to avoid obstacles and people and find your way from A to B.

Couple that with the Google car fitted with an automatic docking station and you have an almost complete system of transport.
I think the appeal to majority goes the other way in this case. The article insists that existing technologies which dominate usage today (ie. HTTP) are good enough, and that Facebook's innovations are misguided. The authors have previously made similar claims about the DOM (vs. React). And after all, HTTP comprises of a far greater majority of server architectures than Relay/GraphQL does at the moment.
Don't want to step on toes, but in short - you can't. Part of the problem is the age genius/criminal curve which shows you the productivity of a typical male, another part is that as you age there is only so much more bandwidth left for grinding shitty jobs and boilerplate code. The only solution is to own a dev shop by that age, otherwise you're f, excuse my bluntness.
I love how the start of this article reads like something out of Character Assassination 101.

Step 1: start by bringing up something negative about a person that has absolutely NOTHING to do with the issue at hand.

Okay, so the guy resigned because he did something bad. How does that make what he experienced while there not true? Oh, that's right, it doesn't. And the admission of fraud isn't a "crucial piece of context." You and I both know that. Unfortunately, you think the reader is dumb enough not to know it.

Step 2: Assert statements in the form of a question so that you can deny every making the assertion.

"Did Ms. Kantor’s editors at the Times ask her whether Mr. Olson might have an axe to grind?" Here, we don't actually assert that Mr. Olson has an axe to grind. We don't assert he's purposely lying to get revenge. We just highly insinuate it and make the reader believe it by putting it in question form.

This is an obvious attempt at character assassination and to cast doubt in the minds of the reader without actually saying he was lying.

If Mr. Olson is lying - sue him. You're within your rights to do that. But you're not suing him. Or the Times.

So, what's the point of this? Propaganda. And sleazy propaganda at that.
In contrast, I find the unrestrained positivity and uncritical acceptance of new 'products' on a site like ProductHunt quite bizarre.
I almost said "three weeks", but decided to back off on the hyperbole.

Yes, resistance to "flavor of the week" stack changes is definitely something that would turn poorly-managed companies off experienced devs. Companies still tend to be short-sighted on their experience requirements, though.
Orphan instances are forbidden in Rust. But you can still implement traits for types that weren't defined in your crate as long as your crate defined the trait, which is an extremely important feature that Rust code uses all the time (and is incompatible with structural typing).
Oh my :/ I don't know you, but this sounds grim.
Your refusal to accept basic facts of reality don't make for a very compelling argument, but I do admire your sticktuitiveness. You'd make an excellent Presidential candidate.
If you are interested in an approachable API for CSP, Go is good, along with Clojure's core.async. If you want to write asynchronous code, they are both great leaders in that area right now. If you don't need that API, I personally find the reasons harder to find in favor of Go.
Well, the best quote by Joel Moses, the father of Macsyma and therefore Maxima, is:

APL is like a beautiful diamond - flawless, beautifully symmetrical. But you can't add anything to it. If you try to glue on another diamond, you don't get a bigger diamond. Lisp is like a ball of mud. Add more and it's still a ball of mud - it still looks like Lisp.

So if your thesis is correct, that shouldn't be an big problem, unless there's something really wrong with the core.
Would Go provide a viable alternative to C++ for numeric and computer graphics 'kind of stuff'? I have no problem with C++ but the better-than-python proclamations got me intrigued.
"Here’s what the story didn’t tell you about Mr. Olson: his brief tenure at Amazon ended after an investigation revealed he had attempted to defraud vendors and conceal it by falsifying business records. When confronted with the evidence, he admitted it and resigned immediately."

It doesn't matter. If the devil tells the truth, it's still the truth.
I Analyzed 147 Cold Sales Emails and 93.9% of Them Sucked
If that's your example of a "fact", then maybe some criticism is expected? It's no surprise that some people are going to think that Tesla's Autopilot (driver must be present and alert) or actual autonomous cars driving on private property are examples that you didn't think of.

If you were hoping for a good discussion, being clear is extremely important.
> If you try to login with an email and a password, I will return a 404 with no further explanation if the auth request fails.

Auth is something different. You should return a 401 with no additional information indeed.

However, the point is that as an API client, you want to be able to distinguish between "this bookshelf does not contain book X" and "what are you talking about, there is no bookshelf here".
Working on Pet Projects
And when it comes to supporting corporations (biased or not), this is mostly a right wing media thing. Just because they do it from opposing sides doesn't make it ok.
It would be nice if all C libraries get rewritten in Go, but realistically, there are way too many for that to ever happen.
Mimic – [ab]using UTF to create tragedy
Nonsense. A URL is a resource endpoint. If a resource is a composition of other resources, it is perfectly acceptable to return all composed resources.

Let's try an example: A shopping application, with customers, products and orders. An order composes a customer and all products that were ordered. You'd have endpoints for retrieving a customer (/customer/<id>/), a product (/product/<id>/) and an order (/order/<id>/). When retrieving the order, nothing in REST prohibits you from returning full information about the user and about the products.

Now, advancing the discussion, the reverse complaint is that it is wasteful returning a full information complement when GETting an order. Easy peasy. Just use proper mime types and an Accepts header. Pass in "Accepts: application/json+order+deep" or "Accepts: application/json+order+plain" from the client side signaling the kind of response you want from the server.
Prohibition was primarily the work of one pressure group
Flag killed.

The unanimity of the commentary on the article (which was ranty, but had some reasonable points to make) is disturbing as well. No one is willing to take the other side of the argument?
What evidence?

Amazon, like most employer, can fire at-will. And Amazon has the money and lawyers to fight long and hard ( unlike most ex-employees ).

This is a pure ad hominem attack that has nothing to do with the question at hand:

how good or bad is amazon as a place to work?

What would the response be if Jay had casually outted someone as transgender or gay?

"Back when Mr. O. was a woman before the sex change operation, ...."

or

"When Mr. O. came out as gay, ..."

Neither statement has anything to do with the issue of how Amazon is as a work place.

But Jay's decision to reveal unsubstantiated accusations in a public forum designed to sabotage an ex-employee's future earning potential says a lot.
Nothing about disavowing your own opinions makes them compelling to me.
RE: #2, agree that this absolutely happens just seems implausible in this situation. For argument's sake, let's assume this happens but it's not widespread at Amazon. I have not read any former employee accounts of it and the NYT would have ABSOLUTELY published something even if they had a whiff of it. Under that assumption, this guy happens to be one of the few people quoted by name in the article that happened to have undergone something shady at work? I don't know why he put his name out there if what Amazon claims is true and I definitely don't know why he would have put his name out there if your second hypothetical is remotely true. Just doesn't make sense.
Scents and sense ability: Diesel fumes alter half the flower smells bees need
fwiw, the NYT response points out that the quote from Dina does not contradict the reporting.

* NYT response: https://medium.com/@NYTimesComm/dean-baquet-responds-to-jay-...
Given that there's a GC and from what I understand(I'm no go expert) limited ways to specify memory layout I'd say no.
> the most valuable part of Office Hours was the back and forth discussion with a mentor

I completely agree and echo your sentiment from past experience.

I think your card deck concept is an excellent way to break away from product / engineering / screenshots and focus on the practical aspects of business execution as part of an interview scenario.

Many founders get caught up in product (low level details) and miss key concepts of business. It's easy to do, especially as a engineer (been there myself).

Your card product reminds me of this YC interview app: http://ipaulgraham.herokuapp.com/

Related: https://news.ycombinator.com/item?id=8334957

In hindsight, I wish I had your card deck when I applied to YC and was subsequently interviewed by PG. This would have forced me to shed my engineering mindset and put on my business cap.
I am an ex-Amazon employee and I had a totally fine experience while I was working there.

That said, my experience very much is totally an anecdote. It was a big company and different teams ran in very different manners.
How the NY Times used data to investigate an illegal sports betting ring
X-Ray Scans Expose an Ingenious Chip-And-Pin Card Hack
You could try London [1], the style is very similar.

The London Underground seems reasonably clean to me, but I used to live there. It's closed overnight, but it's also cleaned during the day — you will see a cleaner on many trips you make in the evening, and trains are often (usually?) cleaned quickly when they reach the end of the line.

Stockholm Metro also has some wonderful design, although it's modern.

[1] https://www.google.dk/search?q=leslie+london+underground+til...
The problem with a minor league for the NFL versus other sports is that an American football career is so short. You only have a few years of that level of physical abuse before you are done. By the time you spent a few years in the minor leagues, your career is almost over. This isn't like baseball, where a player peaks around 29 and you need more time for getting experience.
I never said what you're claiming I said, all I said was metadata isn't data insofar that it's not the 'data' you give to 1Password. I never said anything specific was or wasn't data.

And I'm not using an unusual definition of data, that begs the question. My point is just because it's about you, doesn't mean you own it.
Situations where you want a modern, strongly-typed language with easy C bindings.

IO-heavy operations, especially where it's primarily IO bound but there is a decent computational aspect (eg, working with an embedded database or doing lots of flatfile munging).

I've found the place where Go crashes and burns is if you're trying to implement / use lots of sophisticated custom data structures. It really really wants you to use the builtins, and the lack of generics is irksome.
So, SOAP and CORBA just with a 2015 flavor?
Wow that's brilliant. Why didn't I think of that!
Erlang is mentioned as a solution on page 6.

>[Go is] way to easy to program than Erlang
Total Uninstall Pro 6 Crack and Serial Key Free Download
Public mudslinging between big names ... does that make Medium the new Twitter?
You'd be amazed how many of these guys make it past even very good resume screens. A resume is easy to lie about.

You're right, phone screens usually get them, but not always. A fair number can still make it through.
With private set; you still have to invoke the setter in the constructor. For some cases, it's more readable to have the value of the property calculated in the same place that the property is declared.

Also, when reading code, private set; doesn't guarantee that the property is reassigned elsewhere in the class. You have to read the whole class to verify that.
This is what we do. For frontend positions, we give a laptop and a jsfiddle page to code up the answer to a technical problem that should take about 45 minutes. Then we leave the room and come back in 45 minutes and discuss how they did.

I know I tend to freeze up when writing whiteboard code in front of a interviewer, so I do not want to subject somebody to that when I am interviewing. When you are looking over someone's shoulder, you are not getting a true picture of their ability.

The other thing is that writing code on a whiteboard has nothing to do with coding in the real world. You write some code, test by running in a browser, command line or IDE, refactor, test again etc. Expecting someone to write perfect code without running said code is ridiculous.

Whiteboards should be used for sketching out ideas, i.e. architecting different ways to solve a high level problem, like how should I organize these objects in the application? What should the interface look like?
>So I'm being downvoted for pointing out that a liberal newspaper calls itself liberal? Next thing I know I'll be getting downvoted for calling Trump a right-wing presidential candidate.

I can't downvote, but I assume you're being downvoted for calling a relatively centrist paper left-wing. Perhaps if you'd said 'liberal'/'left-leaning', the downvotes would have been lesser? Who, in your opinion, is a centrist-ish paper in the US?
Go with a LLC. The paperwork requirements are minimal in most US states. It will also provide protection of personal assets in most cases, in the event there is a lawsuit, etc. I would also make sure that you get a general liability insurance policy.
> I hope you will give everyone a fair chance.

I certainly do / did (haven't done hiring in about a year now). I'd like to think I'm very analytical and put the person above any bias I have I just wanted to share how I thought it was rude to be bias against older folks and then I was doing it myself going into an interview with someone who held a PhD.

In the end I didn't let my bias get the better of me but that type of instinct, regardless of how inaccurate it may be, is tough for anyone to get over and everyone has them about something.
Grabs popcorn.

Olson is clinging to a lie, trying to defend his reputation.

Notice how he tries to blame Amazon for his departure, the "revolving series of bosses" and "overwhelmed" with work. "He and others couldn't keep up". Deflection.

He's doing his best to construct a version of events where he is one of the innocents, caught up in the nasty Amazon shit-storm.

I bet he got a shock to see Amazon reveal his fraudulent activity in a medium post! You think Amazon would make such a claim if it weren't true?

Nobody wants to see personal information released like this, but Amazon were slapped in the face with that NYT piece. Let 'em have their medium return fire.

Fraudsters and liars stick to their guns till the bitter end and beyond. It's best to weed them out, and have karma deliver what is deserved.
Isn't it painfully obvious? They're discussing joint events, like dinner. Whoever owes money in the relationship pays.
Most talented people can write 200 "productive" lines of code per day (not copy/paste java boilerplate).

So, 100x would mean you are now writing 20,000 lines of code per day.
"Other constructions in Go show the influence of non-ancestral genes here and there"
Here's a mechanism by which initial HN sentiment can be negatively correlated with eventual success:

- Great founders describe the MVP accurately, even self-deprecatingly: "Sleep under my kitchen table." They mention the flaws, because they want the most useful feedback.

- Less-confident founders describe the gold-plated, fully-featured potential future version of the product and don't mention the flaws.

At least on a superficial read, the great founder's description seems less promising, but they usually end up with a better product.

I certainly see this dynamic at work in pitches I've been given.