skysight-inc/HackerNews huggingface dataset:
Argentina is a great case. The coop movement there was the subject of a documentary called The Take (2004): http://www.thetake.org/index.cfm?page_name=synopsis
The only coke machine on the internet
The "Platinum Rule" is wrong because it is impossible to follow. Even if my ethicals only included "do unto others as they want done to themselves" how would I resolve two fighting men each asking for assistance in subduing the other?

The reason the golden rule works is because it places you in the position of the other. If I accidentally killed someone due to carelessness, I would want myself to be imprisoned for some time.
Thank you.

I bought Rubymotion in November and it took me a month or two testing out different gems etc.

I ended up using RMQ, CDQ, Restkit, formotion, bits of bubblewrap
Uh. In any complex application, you write services which are responsible for various business needs, and whose responsibilities only loosely overlap the way your webapp is accessed from the outside. You may even have services only used by other services.

And obviously, stuffing your business logic along with your web glue (whatever concrete representation you're sending to the outside, you're still stuffing parameters in a template, essentially) still violates SRP. Not to mention that it makes it utterly impossible to reuse outside of your web application, something which is sometimes desirable.
I am using one of these right now. Pretty fun.
I do think platforms like that are easier to use from a developer point of view. That, and you have a more standardized platform to run on - after all, HTML5 and all the technologies surrounding it aren't finalised or fully supported yet.
That is the part of the problem as per original article, isn't it?

With all seriousness... I would like to agree with your statement. But I can't shake that nasty feeling of the "to save this village we have to burn it" undertone from your statement.

Edit: JavaScript got created without major influence of Java (it had more impact on marketing of JS than the language itself). Also I firmly believe that there was a lot of criticism of the then newly baked Java language that turned out to be prescient and to the point e.g.:[1]. Thus I would argue that as much as existence of Java has boosted development of virtual machines and compiler technology it has impeded development of language syntax and semantics.

Erlang is waaay older than Java, so are Python and Ruby. Smalltalk was the real game changer, Java not so much.

[1]: http://www.jwz.org/doc/java.html
> It said “he messed up enough to need to leave, but it’s not a technical legal claim.” That’s.. ambiguous. It comes across as “something bad happened, but we’re going to pretend it didn’t to protect ourselves legally.”

I don't really see why people are confused about this. He probably exercised some poor judgement, as they said, but poor judgement and illegalities are often a long ways apart. The best thing for both parties was probably for him to leave. He was a distraction to GitHub, and this whole mess is a distraction for him. Part ways, both parties move on and continue. I don't think it comes across sketchy, personally. There was almost no way he was going to stay on long-term, given this history. It's a liability for the company, and honestly he's probably on eggshells around the company anyways.

Even as the author states, it's hard to PROVE that something was sexist. I imagine he said some inappropriate things, and maybe even did some inappropriate things, but proving that they were illegal is a WHOLE different bag.

>The entire situation reads: A male executive can do something that’s wrong/sexist. The company will want to cover itself legally, so it will discredit the claims.

Let's fix that. "An executive can do something that's wrong/sexist. The company will want to cover itself legally, so it will discredit the claims." Let's not make this about gender. A company has a duty to its shareholders to protect itself.
I think you are underestimating the value of a platform you can "sort of" trust. Not saying that this is the one, but seems like a step in that direction. Personally, I'm not interested at all in getting the newest from Samsung, Apple, etc. Having to use the phone as a completely untrusted device negates most of its features.
Of course when you have a web application running requests using some thread pool or even more lightweight worker, then what we call the "application" is likely the request and you most likely don't want to kill the app server because you have good reason to believe the other requests are unaffected by the failing requests.
The problem I have with customer development interviews is that people often suck at verbalizing what they really need.

I much prefer Amy Hoy's "safari" approach where you silently observe and record what people do and say in their natural environment (vs. the "zoo" that is a customer development interview).
The U.S. Navy has Installed First 3D Printer on the USS Essex
Great point! Freeboard is great for humanizing a single device, or multiple datasources at a time, but when you get into 100s of thousands of devices, freeboard can be used to visualize an analytics engine.

By the way, you can use dweet.io to fill that database or analytics enginge to your hearts desire. Then use freeboard to see what is happening in that database!
I think one should write testable code,past a certain "size" because somebody sometimes will have to maintain that stuff.

the question is should it be "unit testable" or is it ok just to write integration test.

I think the code you write should be unit testable,doesnt mean the units cant depend of apis you didnt write(while already tested).

should you expose everything for the sake of being able to mock stuffs up?

I'm dont know the answer. to that question.
>Then you find the middle ground that suits your context best.

You've already presupposed that a middle ground would suit your context best.
The Gitignore.io Update
I upvoted this as I think it's one of the best comments on this subject. Technologists are phone averse because at their core they are socially uncomfortable. To categorize someone who uses a phone as a "sales buy" or "business guy" is simply a convenient excuse. Plenty of people, even programmers are productive AND use the telephone. Not everyone who wants to talk with you is some sort of unproductive salesman.

Email is not a perfect communication tool. I deal with clients and all too often receive or send an email that is misconstrued or taken completely the wrong way. Get on the phone and within minutes of speaking he issue is usually either completely debunked, or worked out.

I too avoid the phone, but find when I do pick it up and talk with my clients, or leads or other business people that it's incredibly productive and useful. It's also an advantage as many people will type one thing, but be unable to say that same thing when speaking on the telephone or meeting in person. I've have clients who were unhappy and started down the road of aggressive emails, who after a quick chat on the telephone completely backed down.

The telephone is also a great place to say things that you simply don't want on a written record. It's one thing to tell someone in person what you actually think of X, Y or Z, it's a completely other thing to write it an email where the person reading can't see your face/posture or hear the tone of your voice.
Yes, this is really what I mean by "over abundance". I'm suggesting that excessive application of unit test "fundamentalism" can lead to a variety of problems. A particular manifestation of what you describe as "doing something badly".
Even though I admire DHH's contribution to software he can be very extremist sometimes. Follow him on twitter and you see him taking extremes complaining about every other subject, including a lot of cursing.
My point was mostly a sarcastic insight into what it's like for these companies but you're right: there are valid uses and the fundamentals really are spot on. In fact I'm probably #1 fan of Martin Fowler who has spent many years researching, collating and understanding these patterns so they can be communicated to others effectively.

The problem is that it takes literally a decade to actually understand how to use these properly in one specific language (and possibly mostly effectively in another). Until you reach this point, your toolbox isn't filled with the sharpest tools as your team isn't going to be filled with 10 year+ senior staff across the board.

At that point, it goes to shit, every time. These patterns and techniques aren't just tools - they require experience right from the get go and a lot of people just aren't capable of nailing it even in a decade.
You would hate your life if you were surrounded by TDD fanatics?

Would you love your life if you had to change huge applications with 100k+ LOC without any kind of testing and if anything breaks at the client, it's your fault?

TDD didn't appear out of the void because some wankers want to deride everyone else, it's the ONLY WAY to have tests in the business world because if the features are developed first, the business guys will say "let's skip the tests to cut the costs".
Ruby and Ruby on Rails merged documentations
Veeder – Google Reader, News, Weather and Trends. Android KitKat Transparent UI
> Be glad you didn't. I don't think it would have sent a positive sign. Frankly, no one wants to hear about the things you didn't do, and things like acceptance letters and SAT scores don't matter going forward.

I know (it's why I don't usually go around talking about how I could have gone to Harvard). Though it does sadden me that the VC and tech ecosystem is almost as prestige-focused as Wall Street.

> You said elsewhere you go to NYU -- what's stopping you from maximizing your social and intellectual opportunities?

Mostly that I don't have much commonality with those around me. Everyone seems to be focused on getting the "right" internship and studying, while I'd like to have meaningful conversations about intellectually intriguing topics. Plus, my general lack of social skills and nerdiness at a school which is decidedly not nerdy.
I was thinking this is their first experiment into offering content outside their own platform. While the content isn't spectacular, it's at least a step in the right direction.
When was the last time ya'll went 'hell yeah' when you saw the team you joined was a) was not using a framework or b) built their own?

You're just begging to be swirlied, my dudes.
Maybe the intent of this posting was to poke fun at the thinking behind the quotes, but at least I think that web plugins are something that shouldn't be encouraged. Java and ActiveX applets as well as Flash and Silverlight content sucked with various levels of intensity, but they never ceased to suck. There was always at least some level of impedance mismatch between the plugin content and the surrounding web site.

With Unity web player, there's rarely any attempt to integrate it to web pages, it's just a convenient way to deliver applications through web browser. Still I don't feel good about it, as it doesn't work on this Linux laptop for example, nor it would on a range of tablets, chromebooks, etc. I'm disappointed every time when I see something that looks like a browser game, but requires some awful plugin to run.
The US government spends money in odd ways so you can say all sorts of odd things. Truth is education spending (1T) is more than direct military spending unless you include pensions and heathcare for military workers. It's also larger than social security.

Sure in theory state and local spending are seperate but in practice a lot of state and local spending is tied to the federal government.
Visualize your MailChimp campaigns and their relationships (Timeline)
Thank you for the feedback Rich.

You can build your own widgets in Freeboard, and once completed, users can share new widgets directly with each other through GitHub. We are looking to build a marketplace of sorts as well, populated by the community, and curated for convenience.
Let me know what you guys think. Reviews, feedbacks, suggestions and requests are always welcomed. Thanks for reading.
I think, as Peter Norvig once pointed out, that design patterns are a symptom of an anemic language design. They cost us time and complexity for their benefits. Java wouldn't need half the patterns typically employed to work around the limitation that there are no first-class functions.

Eich himself admitted to avoiding adding classes to Javascript in his interview with Peter Siebel for Coders at Work:

SIEBEL: So you wanted to be like Java, but not too much.

EICH: Not too much. If I put classes in, I'd be in big trouble. Not that I really had time to, but that would've been a no-no.

It's a really good interview and I recommend the book. It seems like Javascript was supposed to be an Algol-syntax over a non-pure Scheme inspired core... but due to constraints was thrown together like most code is when there's a looming deadline.
Using Streaming Chunked HTML to Get Node.js to Deliver More Data
But the same limitation applies to the contenders, doesn't it? As they're not _that_ much more powerful to make a real difference in this case, or am I wrong?
I'm personally not a big fan of mocking; it introduces a lot of duplication into the system. On the other hand, I'm not a big fan of testing a fully integrated system unless you've TDD'd everything from scratch, because then people let systems get slow enough to make tests too slow to maintain a good pace.

If you're already in the "integrating with slow things" problem space, then one solution is to automatically generate the mocks from real responses. E.g., some testing setup code calls your Django layer to create and fetch a User object. You then persist that so that your tests run quickly.

And yeah, I'll definitely use end-to-end smoke tests to make sure that the whole thing joins up in the obvious spots. But those approaches are slow and flaky enough that I've never managed to do more than basic testing through them.
> Even the way you phrase it is dangerously wrong... validation of input and escaping of output are two entirely different things.

Yes, they are, but preventing injection attacks is the domain of the former more than the latter, and your suggestion that it is the other way is dangerously wrong. There are security risks addressed by the latter, but if you are relying on it to prevent injection attacks in the usual case [1], it means you are allowing untrusted unvalidated external data into your system and doing general processing on it and just trying to avoid a problem on output.

You prevent injection attacks by preventing malformed data from being injected into the system (at least, from such data making it past a validation component), not by allowing it freely into the system and trying to mitigate certain of its harms by escaping output.

Its true that proper escaping may help to limit injection attacks where imperfect validation has failed to prevent bad data from being accepted and processed, but even there more complicated APIs for string building don't make it more likely that people will do it right.

[1] the one place where it may be a proper mechanism for addressing injection attacks is when you are reporting the rejection of malformed input data, in which case you may have a legitimate need to use (some part of) the malformed data in the error report.
We appreciate the thought and will consider that. By the way, our examples are all live devices dweeting their data right now.
Isn't this the same as the rumor mill?
Deep Linking in iOS
> the intersection of code, config, and unique data circumstances

I'm sure I'm way over-simplifying here, but those sound like missed edge cases? I can imagine they'd be difficult to predict, regardless.
Let Me Mansplain to the Mans
Ask HN: What have you built with your raspberry pi?
I just got mine and need some inspiration. Low budget preferred.
Best Product Hunt AMA yet.
For me, as long as the IOPS as mentioned in my parent post aren't available, I can just as well connect the Disks through USB. shrugs
How FPGAs Work and Why You'll Buy One
Actually since Coke purchased a massive block (16 million) of MAC addresses [1]. I believe a lot of coke machines are on the internet today.

[1] http://www.wired.com/2014/01/coke-iot/
Or they're looking to partner and introduce you to some great opportunities.
Or they're shutting down their division and introduce you to all their customers.
Or they're desperate for your solution, but they're more comfortable on the phone.

I've had all of these circumstances in the last 1 year.

By ignoring requests to talk because your world view consists of a negative outcome from almost any kind of unsolicited contact, you're cutting yourself off from a lot of opportunities.
I'm not sure I understand what you're suggesting. To me this says that HBO is becoming more like most other content providers.
Simple currying would be simpler but the boss still might not understand it, and it's better culturally if the boss doesn't understand sixty lines of boiler plate than twelve lines of mathematical reasoning.

That's the whole problem, the notion that "the boss" needs to understand how the code works. OOP patterns are designed to "model" real-world business objects and processes so that they can be documented on a UML diagram that business analysts and managers can look at to grasp how the software works without having to understand how computers work. This is a big reason why the software gets unnecessarily complex--the real world is infinitely complex.

Most of the time, what you actually need the software to do is not nearly as complex, though, so it would be better to just write simpler code that does the thing that needs doing rather than models all the things. But in that case it's harder for the non-technical boss to understand the logic without a handy metaphor.

The layer of abstraction that seems to be most frequently violated in enterprise contexts, is the software developer's job itself.
It's nothing that's far fetched or unjust. Everything I've ever said about Uver is completely backed. I will look for the ticket number and post back, if you are curious though.
My desktop (really a netbook) has gigabit ethernet but it's not connected when the slower wireless works just fine. My ADSL is slower still so it just doesn't matter.

So should I swap it for an RPi? For what use is all the processing power I have.
You can also use this to set up a bidirectional channel, allowing for bidirectional streaming. Really handy when your client isn't a browser.
This is basically a marketing move: HBO gets to keep their new programs so customers have to have HBO to see GOT and so forth (HBO gives up its back catalog but I doubt their old shows bring in new subscribers so that isn't a huge loss), Amazon justifies their Amazon Prime price increase and also gets people to buy Fire TV (Amazon Prime is probably not coming to any other device like Chromecast). I would say it's a huge win for Amazon and a so-so win for HBO, so likely Amazon is paying a hefty price to HBO for this ad campaign.
Thinking about an Android version?
"He probably exercised some poor judgement"

As you said, people seem to fail to understand the nuances of something like this. It's entirely possible that he meant entirely well, but acted in a manner that was -- as they mentioned to his wife -- terribly naive, at least for a company of the scale of Github.

Just to give an example of such a nuance, in a tiny startup there might be occasions where everyone might have a big drinking and cavorting pool party at the founder's pad. As the company gets bigger, however, such activities become legal liability cesspools, and it would be very poor judgment because everything becomes a perilous he said/she said type situation. That is an extreme example, but it's why senior management often become increasingly insular and detached as the company grows: Because they legally have to. It sounds like Tom failed to do this.

Which is exactly what it sounds like happened here.

I kind of despise this blog entry because while it berates the unfairness of the old boy's club and so on, it seems to argue that any woman who claims anything should be treated as unequivocal truth, punishment meted out to the harshest extent possible. That is scary, but it is sadly where many of these conversations seem to go.

Not all women are honest and truthful. Women are not above pettiness, power plays and self-interests.
I think the difference is that while the Golden Rule deals with actions (equatable to "hard skills"), the Platinum Rule deals with behaviors (equatable to "soft skills"). The latter does not say "render unto others the actions that they most desire", but rather "given that you are going to perform an action, perform that action in the way that best matches the way the other person is most comfortable with". It is not about the ethics of an action, but rather, how to behave in ways that are most receivable by other people.
Perhaps you missed the Java 8 release, which has lambdas. Though your statement certainly holds true for previous versions.
You are looking at a whole class of bugs as symptoms of a problem with the user interface rather than the user. Except here, the user is a programmer.
> Splitting front-end and back-end tests is desirable.

I don't feel confident without integration tests. An integration test should test as much of the system together as is practical. If I test the client and server sides separately, I can't know whether the client and server will work together properly.

For example, let's say I assert that the server returns a certain JSON object in response to a certain request. Then I assert that the JS does the correct thing upon receiving that JSON object.

But then, a month later, a coworker decides to change the structure of the JSON object. He updates the JS and the tests for the JS. But he forgets to update the server. (Or maybe it's a version control mistake, and he loses those changes.) Anyone running the tests will still see all test passing, yet the app is broken.

Scenarios like that worry me, which is why integration tests are my favorite kind of test.

> Automation-tests test functionality of your software not the look-n-feel or user-experience.

It's not about the difference between a drop shadow or no drop shadow. We're not talking cosmetic stuff. We're talking elements disappearing, being positioned so they cover other important elements, etc. Stuff that breaks the UI.

> The problem between JS and CSS shouldn't be that many either

Maybe it shouldn't be, but it is. I'm not saying I encounter twelve JS-CSS bugs a day. But they do happen. And when they make it into production, clients get upset. There are strong business reasons to

> If you have tons of this then perhaps what's broken is the tools we use? or perhaps how we use it?

Exactly. I think there's a tooling problem.
As a football fan, this looks like it can be fun. Especially as you're watching the game live, create a poll to see the opinion of people in real-time during a controversial play e.g. "Was Rooney tripped or did he dive?". Good stuff bg23.

One small nitpick: on your demo screen shots, you have "Which is the best player?". It should be "Who" not "Which".
this isn't practical. 15 minutes for one call isn't much, but this is the kind of thing that might become a regular occurrence.

running a software driven business does in fact require business staff handling sales and customer service. an engineer shouldn't be handling that by him/herself.
It seems like your response is based around "it's not easy to understand or comprehend, but can be with plenty of skullduggery". That's not what we need in the programming world. Things don't need to be made inaccessible for the sake of being inaccessible.
From Reddit

If you are on ubuntu just do this:
sudo add-apt-repository ppa:pipelight/stable && sudo apt-get update && sudo apt-get -y install pipelight-multi
Afterwards run sudo pipelight-plugin --enable unity3d.
Cheers :)

Credit to /u/rotundnut