skysight-inc/HackerNews huggingface dataset:
Well, according to this answer (http://stackoverflow.com/a/7701264) V8 is about the same speed as accessing variables, however I would bet looking up properties higher up the prototype chain would take a performance hit.
I've actually brought it back on my downloaded copy; it's a color that never clashes with text colors I assign, and stands out pretty well.
If you want to compare, then imagine that you're in the middle of the interview and the interviewer suddenly tells you “get lost, here's the elevator”.

Saying “thanks but no, thanks” after the interview without telling the reason if perfectly fine for both a company and an interviewee.
The "Pianodoro": Take Your Productivity to Power-Level 9000
We use both of these features very heavily at Google, so I'm really happy to see them launch externally. The ability to restrict posts to within a company lets you create a corporate social network very easily (think Yammer, Chatter, etc.). One of the main complaints I hear about Google+ is that specific friends aren't on it, but that's much less of an issue if your company uses Google Apps. I spend a lot of time and get a lot of value out of within-our-company Google+ posts.

And since Google has widely distributed offices, I can't tell you how many video meetings I've attended, but it's a lot. Having the ability to join a video conference/hangout from a link in Calendar makes such meetings really easy to set up.
The only real reason I have for considering pirating something is that "it isn't available in my country for months after it's aired elsewhere", so this is great news.

Why on earth should I wait months before I can see it? I'm sure there's a reason advertisers do this but I don't see it.
Stripe CTF solutions
This actually speaks volumes of the true nature of the problem.

The problem is distribution and affordability.

You can buy Pepsi for ten rupees, and the fact that its everywhere talks a lot of Pepsi's distribution model.
I use it for my ecommerce platform. Great engine!
[T]hese cyborg tissues could be used to create very accurate organs-on-a-chip — lab-grown human organs that are encased within computer chips and then used to test drugs or substance toxicity, without harming a single bunny or bonobo.

That's the real story here - making a better OoaC. Organ on a Chip leads to faster testing.
Munich has 2,500 unexploded bombs buried around the city
Yes!

I would go so far as to say that almost all the most important revelations I had programming-wise where when I learned a new language and suddenly gained a new way of looking at everything I know. And the nice thing about this is, you will keep these insights whether you stick with the actual language or not.

That said, there have been a few languages that have failed to do so. Almost invariably, I loathe working with them.
It seems to me that most of these aren't controversial at all.

I disagree with one of the points supporting "Unit testing won’t help you write good code.", though, where he implies that writing the code reveals the edge cases. Surely the edge cases are something you should have carefully considered before starting to code? I've found that crystallising the edge cases as a test before writing the function can be really helpful.
Which e-commerce platform? I'm just curious.
In all this talk of locking were missing the real benefit to a heavy write environment, better yielding. this is going to be huge for those one off writes that in the past would have held the lock. Also I am looking forwards to playing with the new aggregation framework.
"Piracy is wrong" morally sure, but economically I don't know. It's a complicated question, and without actual numbers the arguments for or against are totally meaningless.
Progress Is When The Previously Unusual Becomes Routine
python on google app engine

https://developers.google.com/appengine/docs/python/overview

Easy to use, can support what you want to do, easy to maintain, easy to scale.
I think that VB6 was probably one of the most productive programming environments ever, until a project grows larger than a couple of business rules. You cant deny the immediacy of dragging a text box, a button and some other controls onto a form and having an "instant" application to automate things.

I've used a variety of "visual" tools for designing everything from ETL tools to synthesizers. They are great for POC designs, but I generally find them difficult to use for the complex stuff. Configuration and properties and logic are much more suited to code in my very biased opinion. :)
What are some tips to keep your emails from getting caught in over-zealous spam filters?
2 ‘Unity for Linux’ Games Made Available for Demo
Technically, this one was first. So there is that. :)
I love this project. It's everything that I'll never remember on my own and more.
> Because these people are starving? Is that not a good reason?

Probably not.

(1) Many of them aren't starving. (The system covers other people, who tend to crowd-out the actual starving.)

(2) The relevant question is "why are they starving". Feeding them typically solves the wrong problem and guarantees that you continue to have starving people.

(3) Such programs tend to reduce local food production, leading to more starving.

The law of unintended consequences doesn't care how good your intentions are.
.
Here is a better recording: http://vimeo.com/48399328
United Airlines Reservation System Goes Down; Blames “Network Issue”
Looks fine here, what's the issue?
Stylebot (chrome extension) lets you do that. That's actually what I use for HN, by example.

It's a really good extension. Click it, click directly on your page to select a DOM element, enter any valid CSS, and it's saved for your next visit.
Could not agree more, I attend a fortnightly hackathon for just this purpose, one day when my dream job comes along (but don't tell my employer...) I want to be ripe and ready to be drilled by whatever they have to offer.
Other discussion: http://news.ycombinator.com/item?id=4448409
Django-- it's popular (easy to get support questions answered) and a lot of fun to learn. Although Flask and Bottle look interesting too.
Why isn't Bill Buxton suing Apple for a billion dollars?
Interesting discussion on SA on this. I don't think it is rude but I do think the OP could have executed it better. There is always someone who is 'co-ordinating' the interview and they are ready to step in if it is going poorly. That person would be the person to talk to about cutting it short.

That said, you should talk with folks about your discomfort as well (you are interviewing them as well). So asking them if you could use your business skills would be appropriate too.
If you're interested in a digital approach to this, take a look at Labradoc (http://www.labradoc.com/) a site I created to make it easier to keep project logs.

I primarily created it for myself (http://www.labradoc.com/i/follower) because getting into the habit of creating project logs had a huge positive impact for me.

Here's an example of a small project I worked on earlier this year: http://www.labradoc.com/i/follower/p/project-sms-text-scroll...

I consider it a form of a "commit log for your day"...
Video games are actually one of the leading suspects for the drop in violent crimes.
lsof -i always gets left out of these lists. It's really handy for quickly seeing what daemons are running (under which user) and on what interfaces they're bound to.
This is an extreme case but in the realm of "fresh out of school kid interviews in mega-corp IT department." Just know that when you have no work experience and are interviewing basically to be a person at a desk you will be subjected to some level of impersonal group weeding.
Personally (and in my circles) the term coder refers to someone who writes code, whereas the term programmer refers to someone who actually designs and executes their application development as a structurally trained computer programmer.

I write code at work. But it's one-off or personal use programs, mainly scripts to automate some repetitive or mathematical task I don't want to do by hand constantly. Contrast this with our development staff, who write code used by their customers (internally and externally), follow a program design model, conduct meetings to discuss the program, do code review, and attend application development council meetings to make sure all the disparate programmers at the company follow the same design/development principles. They program for a living, and it's serious business. My code merely makes my job easier, but I could work without it.

I can bang out five lines or five hundred lines in any language I want, any design I want, any amount of bugs I am willing to accept, and without approval or review by anyone. I think it's important to differentiate between those who actually program and those who merely write code.
Well, if they are controversial opinions that only a subset of all programmers are going to agree upon, of what value are the votes?
I've gotten feedback when I interviewed on why they did not extend an offer. Its emotionally difficult when interviewing to put yourself out there, but getting feedback does help you understand how the interview went down better.
Startup entrepreneurs working together to create a common legal fund could be a great way to offer protection against lawsuits by those companies who might want to throw their weight around...
> He could feel sudden hostility from everybody in the room at the time.

Sounds like he made a good call here. With a professional interviewer, the worst you might get is "perhaps you could help us by explaining why you feel that way?" Who would seriously want to bully someone into staying to be interviewed for a job they didn't feel they could do? Personally I would thank him for his honesty.
That's true, however asking someone on the spot to write a function that requires domain specific knowledge isn't a good solution. What are you in fact testing, do they know how to code or do they know how to calculate the area of a circle. I can code but I'd fail horribly on the area of the circle thing simply because I haven't done anything like that since grade school math class probably 30 years ago.

So his comment is valid in that coders should code but his example of how to tell if someone can code I think is flawed.
Do you worry about lock-in with regards to persistence? How hard would it be to get the data out and switch over to controlling the back end yourself?
Comment felt a bit like this to me : "I don't like Google+, so I'm going to post a list of things that suck."
That's interesting. And might be considered as a paradox. If he isn't smart enough, how can he write a simpler code?

Or maybe he's just humble that he's not smart enough.
One of the reasons DB-level locking is actually quite important is that the replication oplog is on the 'local' database and your data is on other databases -- so your application is no longer fighting with replication for the write lock.
Well there was a push for retail stores a while back.

That push ended at the same time those stores got stoned and looted by the various small traders men who were protesting.

2007 link (wow 5 years ago?) http://www.rediff.com/money/2007/may/12ril.htm

Our lack infra wise, is in Logistics and cold chain storage, last I checked.
Can Judges Deny Surveillance Orders Based on Fourth Amendment Concerns?
When I read articles like this, I dream of Wetware:

http://manybooks.net/titles/ruckerrother10rucker_ware_tetral...

http://www.amazon.com/Wetware-Computer-Every-Living-Cell/dp/...

Why do so much work if you don't have a dream?
I find the "nobody could possibly dislike our culture" groupthink the actual brilliant bit of information in this, it happens way more than it should.
MySQL vs. MongoDB: The Complete Edition
MySQL vs. MongoDB: The showdown. One of our MVBs is on a quest to make this test work in his favor! He's documenting his every step through a series of articles and you can find them all here!
I agree and perhaps handing a coder some code and asking the coder what's going is maybe a better test of their skills then asking them to code on the spot.
Topic 4: So comments are a problem because people do not update them? I believe the blame is misdirected there. I agree that one should make code very readable but comments can be very useful. Just because someone uses the tool incorrectly doesn't make it a useless tool.

Topic 18: His questions are not about writing code, they are about writing algorithms. The kind of code I write on a day-to-day basis does not require working with math equations of this type. I could eventually do it but I would probably have to research and test before I would be happy with it. Most definitely not something I could do on the spot during an interview, but I guess that means I can't write code.

I don't think I have much of a problem with the rest of them and agree with most of them.
Ah yes the Google's real customers meme again.

It hasn't ever had any validity. You are Google's customer as they need you to click on relevant advertisements.

The advertising companies are also their customer. The intention is to hook two customers up together.

Google are matchmakers. How you can twist that into what you posted I don't know.
Assuming the accounting is correct, I think the guy was OK to end the interview politely (without throwing a fit or making grand statements) and leave.

It was also not surprising they were shocked and upset, but that in itself doesn't mean he should have refrained from ending the interview, or that he was unprofessional.

I have thought of walking out myself, I think most have.

For example one interview the manager presented a long monologue about how stupid he felt people from a certain well known outsourcing country were. It wasn't even so much that he was racist, it was that that his stories showed he was closed minded, judgmental and reactionary. I doubt these personality factors were limited to his opinions about national origin. I continued the interview and declined the subsequent offer, citing another better offer. The other offer was for less money but was a project I wanted to work on more, the diatribe wasn't really relevant and only would have been if the offers were similar or his was for more interesting work. I chose not to give him feedback about his rants because I wanted him to keep doing it so other candidates would have the same warning. Him not saying what he really thinks certainly isn't going to change his actual personality.

In other cases I see the interview to the end out of curiosity and to have a good story to tell, but also because you never really know what is going to happen without seeing it all the way through. I may find out more about their business, I may make some contacts talking to people there. Or maybe it is a wash out, but having flown across the country I am going to make it to the end of the day's interviews.
None, almost certainly -- if you have enough RAM to fit your working data set, then MongoDB's writes are just changing memory. If it does need to read data from disk before changing it, the new yielding architecture that others have mentioned will help prevent lock contention.
Sony's live IFA event
I refuse to peg every remaining second of my existence to the highest hourly rate someone else will pay me for it. I won't say "My time is valued at $XX per hour, so it makes sense to pay $XX for someone else to do this." Valuing all time at an hourly rate is logical if a human is trying to maximize the amount of money made across their life - since you could theoretically pay for this task to be done while working, you would have more money than if you did the task yourself. Maybe you work every waking second.

But I don't. I don't want to.

I want to maximize life enjoyment across my life, not the money earned. Instead, I compare what I'm doing now to what I could be, including consequences, and decide which I'd rather do. Then I do that.

---

Not to mention that money has limited utility - you can only trade it for things which currently exist, and which other people are willing to trade. No amount of money will buy you a Star Trek Transporter, nor will it revive dead people or let you live forever. It won't buy you food from the ground; you have to trade it for something else and put that in the ground, and wait a season. Most of what money will buy is boring.
You occasionally do need a way to cut interviews short.

I was once chastised by a manager because I didn't boot a candidate after I was done, aborting the schedule. (He came to me while I was writing a negative review of said candidate.)

It turns out that the candidate offered to fight a later interviewer. I thought that the candidate was a jerk but that was a bit surprising. (The interviewer in question was a rather mild person.)
The OP is keeping a journal, so he has developed a real practice that works for him. I agree that a few sentences describing what he puts in there would have made this article stronger.

The second image of the journal page seems to show a list of possible approaches to a problem. The fourth image looks as if it has performance data and evaluation of a working system, so that is a couple of ideas. I think it is quite a brave thing to post the actual images. Perhaps fortunate the OP does not record team dynamics in his journal.

I work as a teacher, and I use a cheap page a day diary to record a few key points from each lesson. The 'readymade' aspect of the page a day diary seems to reduce the 'threshold' for making notes.
Here is the original FB post from the first thread (thanks to reustle for copying it and posting it in the comments of the first thread):

---

Hey everyone, we're going to be deleting our Facebook page in the next couple of weeks, but we wanted to explain why before we do. A couple months ago, when we were preparing to launch the new Limited Run, we started to experiment with Facebook ads. Unfortunately, while testing their ad system, we noticed some very strange things. Facebook was charging us for clicks, yet we could only verify about 20% of them actually showing up on our site. At first, we thought it was our analytics service. We tried signing up for a handful of other big name companies, and still, we couldn't verify more than 15-20% of clicks. So we did what any good developers would do. We built our own analytic software. Here's what we found: on about 80% of the clicks Facebook was charging us for, JavaScript wasn't on. And if the person clicking the ad doesn't have JavaScript, it's very difficult for an analytics service to verify the click. What's important here is that in all of our years of experience, only about 1-2% of people coming to us have JavaScript disabled, not 80% like these clicks coming from Facebook. So we did what any good developers would do. We built a page logger. Any time a page was loaded, we'd keep track of it. You know what we found? The 80% of clicks we were paying for were from bots. That's correct. Bots were loading pages and driving up our advertising costs. So we tried contacting Facebook about this. Unfortunately, they wouldn't reply. Do we know who the bots belong too? No. Are we accusing Facebook of using bots to drive up advertising revenue. No. Is it strange? Yes. But let's move on, because who the bots belong to isn't provable.
While we were testing Facebook ads, we were also trying to get Facebook to let us change our name, because we're not Limited Pressing anymore. We contacted them on many occasions about this. Finally, we got a call from someone at Facebook. They said they would allow us to change our name. NICE! But only if we agreed to spend $2000 or more in advertising a month. That's correct. Facebook was holding our name hostage. So we did what any good hardcore kids would do. We cursed that piece of shit out! Damn we were so pissed. We still are. This is why we need to delete this page and move away from Facebook. They're scumbags and we just don't have the patience for scumbags.
Thanks to everyone who has supported this page and liked our posts. We really appreciate it. If you'd like to follow us on Twitter, where we don't get shaken down, you can do so here: http://twitter.com/limitedrun
I see how you're doing the math, but I think you're presenting it misleadingly to say your monthly cost is $1400+$1000. First of all you left off the $600 principal; you may recoup that in a sale but you still gotta pony it up every month. Second, your $2000 a month mortgage payment seems low on a $500k home. Talking to realtors and friends that have bought, the rule I've been told to go by is plan $700-$800 per $100k for mortgage and property taxes (not including any HOA). So that means a cost of $3500-4000 PLUS HOA dues every month. Even if you are offsetting $1000 of that with tax benefits, renting for $3k still looks attractive, especially if you factor in the cost of maintenance of a period of 10 years or more. Between two homes I've rented I've not had my rent increased once by a landlord in the past 6 years.
So far as I'm aware I haven't attacked you personally - my post is entirely focused on your argument and statements.

> "Besides you can give every reason under the sun why working hard may not yield to results. Or you can try working hard and see for the results yourself."

Again, an empty statement unless accompanied by specifics. It's easy to ask "why don't these people just try hard work?", but the specifics get, naturally, much more complicated.

- What is the realism behind expecting hard, industrious work from a demographic of people who can't even reach caloric break-even each day? How realistic is it to expect severely malnourished and starving people to bootstrap themselves? This strikes me like finding a person who's been stuck at the bottom of a well for days, tossing a rope ladder down, and wondering why they're not climbing. The answer is simple: they have passed the threshold where they can help themselves, but they are not yet past the threshold where they cannot be helped by an outside force.

> "There will be failures, misfires and hits off target."

The consequences of which is quite severe. When we try something and fail, our feelings get hurt, we might lose some money, and maybe we get to pull our belts in a bit tighter for a while.

When the already starving fail, they die. I don't think it's extreme to say that we shouldn't experiment with social policy on the potential deaths of tens of millions.

And this is actually a salient point - subsidy and direct-aid programs like this are never meant as a permanent solution to anything. Nobody is dumb enough to believe this. These programs buy time to find a systemic solution - because it's better to keep these people hobbling along while we try to fix the larger systemic issues that perpetuate their poverty, than to simply let them all die while we tinker with the knobs and switches.

> "But with a little trying eventually a person will make it."

Reality does not support your argument, even in first-world nations. Despite the stereotypes, the USA is full of industrious, hard-working people who have not made it. The entire world is full of industrious, hard-working people who have not made it.

And this is why I think your argument is typical. In order to reconcile your world view (that enough hard work means success) with reality (the vast, vast majority of the world is unsuccessful), one must make the assumption that those who haven't made it have not worked hard enough.

This is a sadly typical view that's as vindictive as it is false.
Is it usual to have a team of people interview someone, rather than a lot of one-on-one or two-on-one sessions? This reduces the number of developer-hours used in interviewing. I don't think that adding a 3rd or more interviewer will add anything, and it can be intimidating for candidates, adding noise to your search for a suitable one.