skysight-inc/HackerNews huggingface dataset:
Yes, it's possible to have a conversation without data. Yes, sometimes it's all you can do, if the hard data doesn't exist, so "hard data or GTFO" is untenable. But you started slinging anecdotes, and that's a path to sloppy reasoning. Either stick to the abstract, or provide data that's useful. No reasonable person would be persuaded by your "I was getting lunch with a female coworker/friend" story. It was obviously selected with bias, by both your friend and yourself. It doesn't make you wrong... it makes your reasoning unconvincing.
Most annoying thing ever was doing IT work at a company where internet access was not granted to employees below a certain paygrade.

The amount of times I'd run into a problem and then instinctively fire up the browser just to get the "cannot connect to google.com" message.

They handed out ringbinders full of notes to staff insisting that everything we needed was in there.
Thanks for the feedback, it's a shame there isn't a good alternative—there are meetups but they're really a different beast and may not be running when people visit.

On karma, I feel guilty enough just enjoying reading HN but I realise I am missing out by not interacting at least a little.
People call it Google-Fu for a reason.

You could probably tell a lot about a candidate by how they Google for things. To effectively search, you have to effectively define the problem. Often that means having the understanding to redefine your specific problem into a more generic one that you can search for. Ineffective searchers will struggle to do that, or worse, simply throw words into the search bar and expect a magical answer.
Thanks:).
He has played with outsourcing work--all the SDL conversion was done by a third party. He hated the experience. Which goes back to the "he's a programmer, not an engineer" thing. I would personally love for this project to be tackled by a group of highly experienced engineers dedicated to the same vision, but that's complete fantasy dreaming, there.
Your suggestion that "there will always be socially restarted people" perpetuates the idea that things can't improve. Violent crime and overt prejudice to minorities and LGBT folks have gone down over time because it became a big deal. What we just said "there will always be bigots" and then stopped caring, that progress never would have happened.

Change is possible and we should strive to make it happen.
Interesting read, thanks. I was completely unaware of the whole customization/hobby/gear subculture around the AR-15.
> Well, let's get real. How many men think that? I've never seen that in ANY company I have ever worked for. Heck, I haven't even see this kind of thing in the university.

The big disadvantage about being a "hyper-minority" -- that is, a minority to the extent that you stick out almost like a celebrity would, is that you attract a lot of attention. A group of people might be largely composed of good people. However, someone who is a member of a "hyper-minority" is going to attract a far-disproportionate amount of attention from the most unsavory 0.5% of the group.

> It's like taking the example of a rapist (which this guy sort of is) and extrapolating it to some general trend about everyone.

I don't think that's a fair or constructive way to put the issue. Most men aren't rapists. However, a very small number are, and they can do a disproportionate amount of damage. This was even truer in days past, when society was more permissive about certain kinds of behaviors, and less scrupulous about avoiding unwanted approaches.

It's not a matter of spreading the guilt through the group. It is a matter of encouraging responsibility, however.
I pinged Dr. Belk about the dialog here and invited him to join this conversation.
It's not the art rendering it's the massive amount of calculations about dwarf feelings and cat mating the simulation is doing underneath that make it slow.
Can you name an industry(at least as broad as "tech" field) which has no sexual harassment lawsuits, or exceptionally few?

You can tell stories like the one in the blog about any field. Tech is not special. If there is going to be change, it will have to come from society at large, and not by fiddling with the dials of a specific field.
Here's what I've learned from talking to many startups:

1- First step would be a casual phone call to learn about each other. Make sure you also learn about them and ask them tough questions about their business. Both of you are interviewing each other: it's not just that they're interviewing you. You don't want to suck up to a startup which you don't believe in and end up signing an offer there.

2- If all goes well, most will schedule a Skype coding interview. You just have to be prepared for those and that comes from experience (which you should have from your open source experience). Don't pull an all-nighter learning algorithms as they will almost certainly ask you a question that you couldn't cover the night before. Hints: learn a dynamic interpreted and use it (Python, Ruby etc...). I made the mistake of doing those in C in the beginning and got stuck on the details / writing more code that they wanted in an hour long interview. Some were impressed by my C skills, but that's not exactly what they're testing here. Instead, most are looking at the bigger picture at this point. i.e: they're seeing if you can you write a quick draft solution, and optimize it later instead of seeing if you can properly allocate a struct in C and place different struct types in one list. (Writing such an array takes quite sometime --> they might be interested in how you'd design it instead of actually doing it at this point).

3- Then comes the onsite interview. This is where you get to meet the team, see the office, the location and experience a day at that startup. This is very important. Your initial gut feeling is more important than you think. If you don't feel comfortable, then do not sign an offer. You'll be at that office at least 40 hours a week with the same people. You MUST be very comfortable working with them.

Startups will often interview you for at least a few hours on different areas. Design, coding, algorithms etc... Just do your best and the single thing that they care about here is that you can actually write code that works and make good decisions. It does not have to be perfect, but it has to work. They're looking for someone who can build something roughly in a few hours, and then explain the shortcomings (so that it can later be optimized). Someone who can get things done, and perhaps become a leader later on. Since you've contributed to open source, you should have absolutely no problem here.

Good luck!
The second that App.net was announced and I saw the prices, I was out. You don't pay money to develop for a service that only developers are using.

The price was extremely high in comparison to what it offered: Sure, Apple charges to develop for iOS, but iOS has a few hundred million credit-card enabled customers buying software. App.net had a bunch of already-paid developers using the service.

I tried to figure out the point through a few emails with the creator but ultimately it felt like a service for developers flush with spending money to join a sort of app vanity press.

I'm glad that it's opening up now and I'm suddenly starting to get interested in the project!
Ikea Withdraws Meatballs After Horse Meat Is Found
Sony jumps on the Mozilla bandwagon, will launch Firefox OS device in 2014
Brian Boyer did the same when he was leading the news apps team at the Chicago Tribune (I believe he left for NPR this past summer). The team's motto was "Show your work."

https://github.com/newsapps
NBC.com hacked to serve up banking malware
http://llvm.org/devmtg/2012-11/Gregor-Modules.pdf
It's amazing you know the inner lives and decisions of all, or even a large group of women. Tell me where you get your diving powers.
I don't think he goes by Dave, any more than he drinks beer. :p
> As for motions, what kind of motions do you think are difficult to create?

It's mostly text objects. Text objects for scope, variable references, etc. I think there are motions I have not yet discovered that operate on syntax trees. These are nonlinear the way surround is nonlinear.

I was introduced to multiple selection and generalized cursors when one of the DabbleDB guys implemented a generalized cursor editor. I thought it was awesome and did a bunch of research:

http://static.usenix.org/events/usenix01/full_papers/miller/...

http://scholar.google.com/scholar?q=related:7040sK6UgeAJ:sch...

After reading a bunch, I got around to thinking what I'd have to do to implement an editor that could handle generalized cursors based on my experience with vim and hacking on it.

I came up with the idea for an edit core consisting of motions as compositions of partially applied functions. Takes a position returns a list of ranges, applying the list of ranges to an operator produces an edit. The jump from there to regions is pretty straightforward. The system also provides a clear path to how keyboard mapping would work (along with stealing the context ideas from ST).

I'm unaware of an editor that works this way but I find it difficult to believe I'm the first person to think of this. If I can successfully maneuver my job into building web development tools, I expect to gut Codemirror and replace the core operations with these primitives as a top priority but I haven't gotten there yet.

For context sensitive stuff: You can do clever stuff with it. As an example, if you're in a JSON file, after an identifier, and you type a : the editor can automatically put quotes around the key if it's not already quoted. My intro to the usefulness of context sensitive keys was that the ruby textmate bundle would insert Ruby interpolation (#{|} with | for cursor) when you hit # in a string.
There's a difference between talking and awkward, unwanted, sexist advances. If you can't tell the difference, then you're right, you probably shouldn't tell anyone off. But just because the victim doesn't say something doesn't mean they don't want something to be said.
> Are the above statements true?

Yes. Google not strictly being Google itself, but searching other resources. Doctors do research. Scientist read papers. Everyone references something else.

So don't think of it as merely Googling because you don't know. It's Googling because you know someone else has solved this, or something similar, and you want apply someone else's knowledge to what you are doing.
I sure would love to see examples of some of her more successful Bebe or Modcloth facebook / twitter / social ads. Or hear about how many iterations it took them to to get to a successful system.
Here you go: https://join.app.net/p/kvyxdfrbhj
When do we deem the App.net experiment a failure?
Actually, the statistics show an incredibly high attrition rate. No getting in heads required.
Would love an invite! :)

gaurav [at] dadhania [dot] in
If you're using a series of shell commands, each of which takes seconds to hours to run, you will be happy with make's ability to (1) run shell commands easily and (2) not run them again when they don't need to be run. You could write a dependency tracking thingy in any programming language, but at that point you might as well be using Rake or some other make replacement.
>>I with Obamacare this has dramatically ramped up and now there are boards to decide who gets what care based on cost measures, rather than medical need.

It would help if actually knew what you were talking about. There are no "boards." There is the IPAB which makes cuts to medicare if congress can't. I'm sure you are in favor of reducing this "socialized medicine" so your stated basis of opposition is nonsensical. Maybe you would prefer instead a "board" made up of people elected across the US that will make cuts to medicare instead. It's called Congress and maybe you should learn about it as I hear it has existed for a long time.

>>Command economies don't work, and the change in health care over the last century has been a centralization in control.
>>Whenever someone talks about the need for socialized medicine because "otherwise people would go bankrupt", remember it is the socialization of medicine that caused costs to rise to the point where people would go bankrupt.

Milton Friedman also said that single payer system have many advantages over the system we have right now.[1] It isn't centralization of control its a broken system that has never had any reform whatsoever.

[1] http://www.hoover.org/publications/hoover-digest/article/729...
Anyone got an invite?

mcantelon at gm ail dot com
Head First HTML with CSS : http://www.headfirstlabs.com/books/hfhtml/

Once you are comfortable with HTML and CSS, you can learn new techniques / tricks introduced in HTML5 & CSS3 easily ( from any other source, say a tutorial ).
It varies by region. Your state health department probably publishes the data.

Remember that emergency rooms cannot turn people away, doctors can.

Poor people in general often don't have primary care providers -- even with Medicaid or private insurance. Reasons are varied and complex. Access is a big issue... for example, if you don't have a car, how do you get to the only doctor who is accepting new medicaid patients across town?
Yes, because the ones in the standard library are very cleverly optimized and they are usually a hybrid of related algorithms.(For example qsort in C isn't exactly quicksort) But if you have a novel problem of algorithmic nature, having already built an intuition should help.
Would love an invite :) john dot luxford at gmail
Warby Parker is so interesting, not because it's a story of an eyewear company, but because it's a story of a fascinating business model by design-savvy people.

I probably wouldn't wear their glasses, but they are beyond compare to their competition in this regard.

Kinda like a Zappos for glasses, with the difference that they make their own shoes.
No ;)

Obviously you are not alone in liking Twitter, but seriously, no reason whatsoever?

I don't doubt what you say. I just find it astonishing that Twitter behavior and service has been such an absolute match for you.
wow, you are clueless.

Approaching someone and engaging in conversation with them out of potential interest in who they are as a person is nowhere near the same thing as making offhanded remarks on their physical appearance without so much as an introduction.

get it together.
If it's an experiment it's neither a success nor failure. It's just a data point.
It is an interesting read, especially in terms of the surgeon's framing of the ethical question. I just wish medicine focused more on helping people keep their own organs functional. But that isn't heroic and headline-worthy. Sigh.
Our CTO routinely joins our meetings and basically says, "Great, we had 5,000 likes on our Facbeook page, how many more widgets does that sell?"

That is incredibly sophisticated thinking for a large co. In my experience, it goes more like this.

1. PR guys pay a blogger with no traffic to write a post.

2. Blogger writes article and gets paid handsomely (The PR guys don't know he has no traffic since they didn't want to offend him by asking).

3. PR guys flog interns to generate chatter via social media.

4. Interns tweet amongst themselves.

5. PR guys get some mathematically incorrect and dubious metrics for some ill defined thing like "social media reach" and declare that said blog post generated 190 million impressions, which is equivalent to (just because) $5 million dollars of media.

6. PR guys claim victory and celebrate. Their superiors wonder what the hell the PR guys actually do for a living and get back to their infighting over budgets and why the sales guys aren't getting more product out.

Total cost to big co? Hard to tell, but I'd guess somewhere around $20k when you add up all the salaries involved and the huge fees the agencies charge.

But the bottom line is that even the most wasteful social media is peanuts at BigCo. It simply does not matter.

[Note: this is not a made up story. The numbers are slightly off because I can't remember them, but that's about it]
I have the feeling that you misunderstood the article. It doesn't say that fat makes you fat, instead, it displays the lack of ethics and morality in the food industry when it comes to the obesity problem caused by overconsumption of processed food.
Due to additional sugars, salts, fats, clever advertising and more, they managed to make people eat more of their processed and unhealthy food then necessary, thus causing a diabetes and obesity epedemic (not necessarily because of the contents of the junk food, but because of the amount of it being eaten).

I never understood this article as a cricicism of fat - that word doesn't even appear to often. Instead, it diligently describes the amount of money invested into making people eat more of this stuff even though more of it is not healthy for them. Moralics and ethics aside:

“How can we drive more ounces into more bodies more often?”
Surely the programming languages, libraries, and platforms you were using had documentation. It's not the point whether you are using www.google.com, mycompanyintranet.com/wiki, or yelling across the room to ask a question.

By the way, the three attributes you just stated are what makes anyone good at almost anything.
This is hilarious! app.net was not designed to be freemium at all! I remember when they came out, the whole point of having no free accounts was so that you couldn't have people creating 50 accounts for spam (most people wouldn't pay the money to do this).

And also the idea was if people paid for the service, then you wouldn't need to sell ads or raise funding or come out with public APIs that you then took away when dev's used them in ways you didn't like.

I think they are changing their tune now b/c they can only get devs to pay for an account.
Sent you one
Nope not FogCreek, it's possible the origins of our made-up language was done for similar reasons
Agreed. Nowadays in technical interviews, I make it a point to say that I would google the problem. Not googling just because it's an interview is exactly the kind of thinking that gets people stuck on real problems -- i.e. inside the box, instead of outside the box thinking. If you were given a real problem, would you limit your problem solving approaches to those implied by the context? That's exactly the kind of person I don't want to hire.
It seems like you still don't believe me that people keep patches to themselves because the open source community is so unpleasant to deal with. We had several huge threads about this the last time some alpha jock devs got called out for being assholes. Here are some examples:

https://news.ycombinator.com/item?id=5112713
https://news.ycombinator.com/item?id=5112665
https://news.ycombinator.com/item?id=5112513
https://news.ycombinator.com/item?id=5112763
There are a few problems with that in my experience: you cant use all open source projects in a proprietary context and open source projects all have different dependencies. The former flat out stops you from using the code (and you shouldnt even read it to avoid any accidental lawsuits). The latter is a big problem because you dont want to use eight different frameworks in one projects.
I'd love an invite as well (yeri@tiete.be).

Cheers.
Please stop. Stop this. Stop being dismissive. Stop being condescending. Stop trying to intimidate a woman in tech who is trying to speak up about the pervasive sexism that demonstrably deters women from entering the field and then pushes women out when they do try to enter. Stop the bullying. Stop the patronizing. Just stop.
I feel the same way about my bash history.
those went fast! all out people
Jekyll is easier to get started with.

If you know ruby, middleman can be very powerful if not it can be a pain.
Someone. Anyone. Write a LiveScript version. Please?
Could you please state the reasons for this change: 'cannot return a value from a constructor'. Besides breaking working code, this feels more like an added restriction than an added feature. I'd love to know why this is in 1.5. Thanks!
Ok, this is what I think we will see a lot of. No talking, no vision, no touching, just some simple gestures.

Dave Rosenthal (former MIT/Sun/nVidia not archivist guy) and I talked a bit about gesture control when the first MEMS accelerometers came out. They allowed for a wide range of controls but they drifted horribly so it wasn't possible to do a sort of "hold for fast forward" kind of motion. You had to have a move to start and a move to end.

To some extent this is the same problem as the Leap which can know where your fingers are but you can't hold a gesture and move your hand (afaict, I've not seen the LEAP SDK in action yet)
If I recall correctly, EB1 and EB2 visas are skill-based immigration visas. IMO H1-B serves the purpose of allowing skilled workers temporarily in the US
I'll be interested to see how they respond to you uploading that.
So, yeah, right now, email might be a good medium ... but there is a saturation point.

Long term it'll continue to be too, just as with anything else. There are only so many magazines, newspapers, TV channels, Web sites, foods, restaurants, drinks, etc, that we can cope with/consume each day too, but new ones come along and knock others out of business without breaking the tolerance for the medium (luckily!) :-)
Even if you are working on the cutting edge, you are still building on top of previously learned knowledge. Google is more than just quick fixes or simple solutions. If your expecting a problem to be solved by a recipe, it's not cutting edge.

However, reading papers and studies that relate to what you are working on will provide you with a better foundation to solve the problem.
This is an amazing reply.
Ah, type hinting. Reminds me of Groovy, when people who use dynamic languages realize that 95% of their method calls can be statically verified at compile time anyway. And, huh, turns out Intellisense is nice. :-)

Running with my own tangent, IMO Groovy went about this backwards, where each IDE grafted their own type inference on top of stock Groovy in their own unique way, instead of just specing it as part of the language.

Granted, that was what they had to do, because it seems at the time Groovy's committers were too proud to realize that their users actually did want static typing. That seems to be changing with Groovy 2.0.

Anyway, sorry for the grumpy comment on your post. Auto completion is wonderful and amazing, it's awesome to see people building IDE-ish features like this in lightweight editors. I'm always psyched to see that.
This is something that bugs me about whiteboard-style interviews - they test almost none of the typical day-to-day aspects of programming. Without Google, without docs, without a REPL, without the code-run-debug cycle, how is it that you think you're assessing how effective I am in real life?

EDIT: not to mention that you're also not testing me for one of the most important abilities of a coder in a software shop: how well I learn new things.
Korean Words and Phrases for TOPIK Beginner 01
You've worked at a startup? Documentation is usually the last thing people do unfortunately, at least in any kind of useful way. Sometimes there was documentation, but when only 10 people in the world are using a language there ends up being undocumented behavior or things that you can only discover when it happens to you or you ask the guy around the corner who created it...

edit Also wanted to say there is a huge difference between being able to Google and "Copy-Paste" a solution vs Googling the source documentation and figuring out the problem. We definitely could not have copy-paste programmers.
This sounds like a terrible, shoot yourself in the foot idea for the vast majority of weight trainees. Why on earth would you want to make something hellishly hard(weight lifting) even harder with shitty nutrition?