skysight-inc/HackerNews huggingface dataset:
I agree with uptown. Specify the tasks!

In huge software projects there are 3 roles:
- UI-Designer: UI-Designer is responsible for the overall aesthetics of userinterface.
He defines the display concept of the dialogue system and the style guidelines.

- UI-Developer: The UI Developer is responsible for the implementation / coding of the userinterface in the target system to be developed.
He needed deep knowledge of programming (graphic) on the UI provided for software platform (and hardware system?).

- Usability Engineer: The Usability Engineer is responsible for setting up the execution and completion of the entire usability engineering process.

I think you need a Usability Engineer: UE is a Person, who is able to work out mental models based on scientific theory and heuristics and even realize them.
seriously.

and the world needs like, maybe 5 computers total.
do you really need schema for this?

look at web server logs, they have no schema, each line is not related with others, yet we are able to analyze logs
A fixed schema in the database means you only have one schema to deal with. But in schema-less DBMS you really have as many schemas as changes you've made. If you add a field to new records coming in, you now have 2 schemas. Every change you make is another schema.

Your ORM likely represents the last iteration of that schema and then you have code to handle all the past iterations.

So the point of having a schema in the database is avoiding that kind of hell.
What about the growth of virtual economies?
Jacob Appelbaum's Keynote on Surveillance
Nieman Journalism Lab Shows Racism In Look To Future
There is a general thread of sexism that permeates much of western life. It's endemic to all levels of American society. Addressing sexism in the hacker community seems fruitless to me when there is a much larger fountain of hate spewing forth over the general public. New souls will come into the hacker community and old souls will leave, and some of the new souls are going to be incorrigible sexists. Sexism must be fought at the society-level, where it originates, not in subcultures.

That, and more boys need to grow up with sisters. If you want to kill sexism, make sure boys and girls respect each other at an early age...
DRY is "Don't Repeat Yourself", not "Don't Repeat Ever". If your ORM fully correctly derives everything it needs from your database schema, that doesn't count as a repeat. If your ORM needs a couple of hints, but those hints are indeed extra information that your DB can't have ("this isn't just a string, it's an IP address") that doesn't count as a repeat. If you personally typed your schema into a database creation script and then you personally also typed the same schema into your ORM specification, only then are you violating DRY.

Code generation is a powerful DRY tool, not something it suggests avoiding!

I say that independent from the question of whether you should be using an ORM at all. If you are going to use it, either your ORM should come out of the DB or be responsible for creating the DB, either is fine, as long as you're not saying the same thing twice.
The real-time opinion platform for all your questions
if superpower is what you're after, you should get something stronger than a book
The problem of course is that diesel fuel goes thick and viscous at very low temperatures.
This article is exceptionally difficult to read because of the low contrast between text and background color and because Firefox won't allow me to highlight the text for some reason.
Even when you use OOP languages some tasks are really badly suited for OOP, so then just code it like it was imperative or functional. The relevant example here is reporting, where SQL is one of the most suited languages for this task. Use the right tool for the right job.
I guess you missed the part where demand for this hugely anticipated OS release is looking decidedly weak?[0][1][2]

(I love that after telling one person they don't know what they're talking about, while making obviously false claims yourself, you continue to lecture about 'reality'.)

BTW, I'm not posting in support of Lewisham's thesis, so I have no need for straws.

[0] TFA

[1] http://www.thefiscaltimes.com/Articles/2012/12/03/Why-Window...

[2] http://news.investors.com/technology/101612-629557-intel-bea...
finnegans wake
I don't know — I've never seen it. I don't see why you would; the full version is simple enough for anyone who can fry an egg.
"on-going experiences of misogyny, abuse, threats, put downs, belittlement, harassment, rape."

This seems a little strong, is there any evidence to suggest that women in a technical field have a heightened risk of rape vs any other field?

Especially something like lapdancing which seems to have no lack of female participants.
more efficient ordering / reduced turnover time / increased ticket size are good for almost all of the categories above.

while reduced turnover time might not seem to be what Ruth's Chris is looking for, if they're full to capacity, and people are ready to leave/pay sooner, don't you think the people will be happier and the restaurant can seat another customer?

again i'm astonished at how many people think increased efficiency = you have to rush.

nothing could be further from the truth -- it's because service is efficient that you DON'T have to rush.
For anyone else wondering what this API is about:

It generates a (random) UUID. According to Wikipedia "the intent of UUIDs is to enable distributed systems to uniquely identify information without significant central coordination. In this context the word unique should be taken to mean "practically unique" rather than "guaranteed unique". Since the identifiers have a finite size it is possible for two differing items to share the same identifier. The identifier size and generation process need to be selected so as to make this sufficiently improbable in practice. Anyone can create a UUID and use it to identify something with reasonable confidence that the same identifier will never be unintentionally created by anyone to identify something else. Information labeled with UUIDs can therefore be later combined into a single database without needing to resolve identifier (ID) conflicts.

One widespread use of this standard is in Microsoft's globally unique identifiers (GUIDs). Other significant uses include ext2/ext3/ext4 filesystem UUIDs, LUKS encrypted partitions, GNOME, KDE, and Mac OS X, all of which use implementations derived from the uuid library found in the e2fsprogs package."

Source: http://en.wikipedia.org/wiki/Universally_unique_identifier
I am a man, and the question of how to apply these experiences that female colleagues have has always troubled me.

Many of the events she lists seem commonplace in decentralized movements (groups are often mis-represented by zealous adherents without the leaders' knowledge or throw out their founders). Public faces of projects are often viewed as difficult to work with or technically lacking (partially or fully) due to their high profile.

So, part of me reads this and wants to say that she's experiencing the problems that I've read about (but not experienced) when dealing the "hacker community."

However, there are also instances of language that could ("level-headed", "don’t worry your head about it") or definitely are ("mommy-type") aimed at her gender. I don't defend people who dismissed people for their gender. I also think everyone needs to understand that it's her call if she felt discriminated against. We can't deny how she felt, even if all of the people who said what they said didn't mean it that way.

So the other part of me wants to do something that will help women feel welcomed into communities, but I'm at a loss as to what.

So much of the language quoted in the blog is subtle and insidious. If they had said "parental-type" instead of "mommy-type", it still could have been just as alienating, just not as quotable. The comments all seem to have two components: a neutral complaint (difficulty collaborating, concerns about technical skill, disagreement about direction) and sexist sentiment (don't worry about it, let us handle it, it's too much for you). I can see the second component, but I don't know how to call it out without getting the other party to buy into the undertones of their statements.

I feel like I understand where the author is coming from, but I also feel like these are also probably socially inept people who didn't like her. For some portion of those quotes, they probably did not consciously intend to be sexist, or reference her gender. It's a problem, and no one should be made to feel like they're rejected for their gender, but I don't know how to address it.
So that would have been a decent theory before the Windows 8 release. But if people were delaying purchases because of the upcoming Windows 8 release, there should have been a sales spike by now as all that pent-up demand gets satisfied. And the impression I'm getting from the news (including the original article) doesn't support such a spike...
I'm not really clear on how much hardware experience you need to extend this. For example, let's say I wanted to hook this up to my thermostat as you suggested, or to my espresso machine as you did. What would that actually require? Would I need those breakout boards? I can't even find any; how would I get one?
Hah, nice UK bass selection! Didn't know about Damu – awesome stuff.
this reminds me of an app I helped work on for the Denver area RTD https://itunes.apple.com/us/app/denver-rail/id523272854?mt=8
Well this is predictions for 2013. It seems reasonable to assume it will take over a year for the Rift to be released, affordable, well supported and a common trend.
Find a good one on body language. Can't recommend one now, but some 25 years ago read several and, done well, it amounts to basic mind reading.
Japan's equivalent of D&B is TEIKOKU DATABANK or TDB[0]. These guys will come by the office and run through a multiple of questions -- if you don't answer them, they will be reflected in their database.

Whenever you get a call from TDB it is both scary and exciting because you know that some major Japanese corporation wants data on your current standing.

Also, registering for a DUNS number here in Japan is very simple because most of the information that they are after is already filed with the government in an easy to access format.

[0] http://www.tdb.co.jp/
> The fact it comes from person X instead of person Y, and person X is not like person Y. When you see it enough times, you start hypothesizing about why it happens. Then you share notes with others in your situation and your hypothesis gets stronger.

>... then you post about it to HN and have a handful of comments insist that it's not happening at all.

The problem is that without this additional context you just posted it's hard for someone to make the connection because we see all of this happen regularly around us even without the gender or a race factor thrown in.
To be fair , a handful of blog posts (some with a feminist bent) could be as much a confirmation bias as anything else.

Technical people are more comfortable publishing online than those in other professions.
I'm going to piggy-back on your comment here solely because I've appreciated your comments in the past:

There clearly are talented women in tech (and other fields, I know a pretty amazing CEO), and clearly this is a problem that a lot of men aren't "getting", in the sense that either they don't see it as a problem or they don't know what to do about it.

Do you think there's an opportunity yet for some of the leading women in tech to start collaborating on projects together, just to see how that goes? i.e., conferences where both genders are invited, but the organizers are strictly (or at least mostly) women. I'm partly curious to see if there would still be some of the same personality conflicts, but mostly, I'm starting to think that excluding guys from awesome things might be the best way to change behavior.
I keep promising/threatening to make up business cards with the title "Angel Choreographer". I don't just know how many can dance on the head of a pin, I direct their steps on a regular basis.
There's no difference between this and designing the classes first.

Designing the classes first in an explicitly typed language actually works a lot better than designing a schema in a DB as you're not constrained by relational requirements and it's easier to change imo. Make a change to your classes and you can usually just right-click refactor, try and make a change to your SQL schema and it won't accept it at all until you unhook all the dependant tables.

Basically, I don't really get what point you're trying to make.

You never know your domain well enough to make a decent schema unless you've already written the program once before. Which is a pointless thought exercise where you get to point at flaws in someone else's nascent design. Like it sounds like you do in an interview, which is great for seeing their thought processes, but don't fool yourself that it's because of that design method.

In other words, the reason it worked so well is because you had already built it once, nothing at all to do with your choice of schema first.

In the end do what works for you, but schema first vs classes first is a trivial and pointless argument as both work fine.
Ask HN:  Anyone miss magazines like Business 2.0 and Industry Standard?
There were some great biz/internet magazines back in 1998-2000 that I loved reading, especially Business 2.0.

I guess the closest thing now is Inc.
Lots of good questions here, but I think the critical question is whether it's compatible with any of the other emerging standards like Z-Wave. Can someone from Ninja Blocks weigh in on this? There are a ton of Z-Wave components I'd love to mix in here.
It's inherent to the concept of "privilege"; the understanding is that the people with the most "privilege" in the western world are men who are white. If you are making a point that a group has "privilege", it makes sense to point out they are mostly white since it affects the amount of "privilege" they have.

That said, that particular remark seems to be imbued with some bitterness and desire to wound; which may be understandable coming from someone frustrated, but prevents me from endorsing it myself.

edit: quotes are not for sarcasm, but to denote less common usage/meaning
> Inequality doesn’t just spring up without a context.

There's the problem. People aren't equal, and they never will be. So yes, inequality is fundamental. The sooner you accept that, the better.
In one paragraph, the OP implies that some in the hacker community have "no will to fight harassment, discrimination and douchebaggery"

In the next, she describes "a bunch of privileged white boys" who seem to anger her.

Why, then, is she surprised to be called a "mommy-type" when others are angry at her?

My point being, people sometimes use mean words when they are angry. The best way to "fight harassment, discrimination and douchebaggery" is not to use that type of language when angry, or at all. The OP should consider her own message.
I live in NYC and have been following the city's technology initiatives closely. The silver lining here is that the city has come to terms with the fact that they are le suck at making awesomely designed consumer apps, and releasing the data to the public will be beneficial for all. My favorite part of this post is the "Commitment to Open Data".

Someone out there will make something amazing with this data, it's practically inevitable.

Speaking of, if you live in NYC you should come to this Reinvent Payphones Hackathon - same sentiment (full disclosure, my startup is helping to organize): http://reinventpayphones.prototypehackday.com/
It's an iPhone app too. I use it weekly.
Polldaal: a new polling interface
I think this piece would have been stronger if it were just 3 - 5 examples and then discussion. If the piece is going to be billed as a call for discussion about sexism, then the piece should be mostly about sexism rather than about things not related to sexism that went wrong with the project.

Also, for what it's worth most of the questionable behavior I see comes from the developers who are part of open source culture rather than from the ones who are part of startup culture. Not sure if others agree or disagree.
The highlight color is just a nuance darker than the background - almost not noticeable.
Not all of us use a language that has classes or where it's considered good taste to use classes to structure everything.
The mismatch is quite bad between OOP and MongoDB too. A document database like MongoDB does not represent well recursive data structures or having different objects of different classes where any of them can be the entry point.

MongoDB is good if your data is grouped into logical documents and is not an arbitrary object graph.
I'd say also read "Seeing What's Next", the third book in the disruption series. There he deals with a lot of stuff like structuring your business to take advantage of Asymmetric Motivation and Asymmetric Skills as shield and sword of your business, as well as building an orthogonal Value Network to the existing solutions to avoid co-option by incumbents (or not doing so accidentally, if you are aiming to be acquired).
This is indeed a much harder and deeper question than it seems.

I would ask Christopher Alexander's great question: What feels more alive?
I understand what you're saying, but you may be in the (annoying) position that to back up your argument you'll really have to enumerate all those interactions and show the pattern. Drawing one anecdote without the context is less convincing than: "trust me, I experience sexism in the workplace."
That's right -- bufferbloat introduces more problems than "solving" incast.

One of the main reasons for incast is the synchronised bursts+backoffs causing senders to timeout. As the CMU paper pointed out, the 200ms min-RTO is too conservative for senders to recover from timeouts. Reducing it can go a long way in mitigating the incast effect.

There's a project called "R2D2" at Stanford University that proposed adding a tiny shim layer that rapidly retransmits lost TCP segments. It was done in a transparent manner to hide packet losses from TCP thus preventing TCP from experiencing a timeout. You can read more about it here: http://sedcl.stanford.edu/files/r2d2.pdf. EDIT: The highlight (relevant to the blog post) is that it is a loadable kernel module requiring no changes to TCP stack!

Disclaimer: I work in the same group, and I am familiar with R2D2.
> Seriously, if you can't see a fundamental problem, I seriously doubt you're looking very hard.

If you missed the line where I said that "sexism is clearly an issue in the hacker community that needs to be tackled", then I seriously doubt you read my initial post very carefully.
It's not (see second to last paragraph - Q #3, and answer follows from the NinjaBlocks site). Z-Wave and Insteon are the defacto standard, if it doesn't support it - it's not going to fly. I'm guessing they didn't want to deal with licensing.

And, Z-Wave isn't emerging - it's been around for quite a while. It's not perfect (most low power mesh wireless networking standards have their flaws), but what NinjaBlocks has chosen to implement is not something you want in a system you depend on. Insteon has the advantage of wireless plus being able to operate over powerline (i.e. your home power distribution).
"Tribal Leadership" http://www.triballeadership.net/
The Best Astronomy Images of 2012
> why is a small but real bias against women in tech still not a huge problem?

Did you actually bother to read my post before hitting "reply"?

> sexism is clearly an issue in the hacker community that needs to be tackled
That's hilarious - "all computing devices" includes tablets, and even some smartphones. No wonder desktop Windows is "declining" in popularity against that whole market.
intradesting
That page appears to be a few months old and they hadn't actually built / shipped any "new" Ninja Blocks, so I'm hoping things have changed. :)
How can you be so certain that her interpretation, or your interpretation, of what is happening is actually in line with reality? One cannot simply observe something and immediately react emotionally and simultaneously imagine that they've just completely nailed the core of the issue with complete accuracy and no misunderstanding has taken place whatsoever.

From my subjective perspective for example the OP you're responding to used the phrase "big bad men" to sum up the article case that the problem is sexism / men / external rather than her lack of understanding / expectations of unearned respect / internal. It's up for argument which one of these positions is valid, but I just don't grasp how people can immediately jump for the second one as if it were indisputable truth?
That's a great article, and thanks for it, but what I meant was that none of the criminals in The Wire were FISA-eligible targets; even "The Greek" (who was not Greek) was a lawful US resident.
I think it's possible, just a bit too hard to make it a quick "piss off the RIAA" project. Instead of merely parsing out the URLs it would require linking the infringing titles at the top to the URLs below.

I would do a first pass that tries to compare the URL string to the infringing content. The second pass would cURL all of the yet to be identified URLs and then parse it for content that would link it back to the infringing content titles. I'd actually expect the page titles to contain the infringing content title most of the time (also there's probably a small number of sites that account for 90% of the takedown notices).

This all leads me to another thought : what's to stop someone from parsing all the DMCA takedown URLs for the content they contain and then generating a search engine for them. Legality for US citizens would be minimal here at best but not all of us are from the US.
IPhone5 was a misstep for the "back" button
iPhone5 is taller because they copied Samsung. This intent to please users will only annoy their UX because iPhone not only stepped out of the leadership role but just made it more difficult for the users to tap the "back" button with the same hand they hold the device. Android phones have the back-button integrated on the bottom of the screen, that's why they can afford to have long screens. Therefore it's not possible to browse an iPhone5 app with just one hand.
Now wait a second.

I am in a highly organized secret Facebook group mah-self. The thing is that this highly organized quality means that they could jump anywhere if they really wanted to. Perhaps you "semi-organized".

Basically, I think lock-in to any social networking pretty much has to come through a group disorganization, through the fact that a given setup works for some members of the group but these members are not so committed that they'd actually jump from one group to another.

But there are other factors, I think G+ only has traction with early adopters. By starting at Harvard, Facebook itself spread from high-social-prestige people to the rest of us. G+, for whatever reason, may be spreading the same way but that kind of effect only works with the tenuous connections you want to have with people who aren't wholly committed. The cohesive connection you with people in a set group don't require any given medium to happen.

Anyway, personally I'm not going to G+ due it's even-more-draconian-than-Facebook anonymity policy (Facebook's policy is pretty much that they only say they care).
It's not desktop Windows. It's Windows.

See my posts re declining PC sales for why this would matter (hint: people are getting work done on devices).

Then we can fall back to the argument that consumer PCs aren't really important anyway.
On a related note I saw a link posted about a year ago to a "guide to life-type pdf that was written by the CEO of an investment fund. The book had some good points in it, if anyone could share the link again I'd appreciate it.