skysight-inc/HackerNews huggingface dataset:
Honestly it depends on what the goals of the test are.

Ask 10,000 people in <x position> the same generic question. So ask 10,000 Sales Managers if they like dressing up for work , look for a correlation, compare the correlation to performance, get your answer.

Out of 10,000 sales managers, 3,000 said they enjoy dressing up for work. Of those three thousand managers 2,600 are top performers and get high marks from their coworkers. From this you can make a very slight up-tick towards someone answering true to them having the possibility of being a top performer. This would just be one question over hundreds of similar questions so it isn't going to be a deal-breaker.

Of course, ask 10,000 programmers and "false" might be the correct answer. That's what makes these questions powerful. There is no correct answer. There's only a relationship.
The Dude Abides on the Other Side of the Lens
India's SSI(Social Security ID) equivalent is private database
Cutting greens and tees and watering fairways.
This article completely misses the point of CodeSchool. CodeSchool's best selling point is exactly what the author is complaining about. I know how to program, I know how to design and analyse algorithms and I know my data structures inside out. I don't, however, know the best way to test Rails applications. CodeSchool provides a really accessible way for programmers to stay on top of the latest technologies, frameworks and idioms. It is not intended to replace a CS degree/education and I'm not entirely sure where the author even got that idea from.
Is the simplest answer then to have a T.o.S. that states no one under 13 is allowed to use your product until you can afford staff charged with handling security & privacy?

Then you can CFAA those little twerps.
About.com paid out $800, a few small companies paid $100, but Northrop Grumman took the prize for paying out $9300

Although not explicitly stated, I think there was a minimum requirement of $100 to get a payout from a given company. Checks were issued from each company individually, so you literally had to make $100 from a given company to get that payout.
Indeed there is no indigenous population and hasn't been since 1966 [1]. It's nothing but a strategically well-placed airbase with a few thousand personal and contractors.

.io is clearly a gccTLD. The TLD administration and commissioner in charge of 'the government' reside in the UK.

[1] http://en.wikipedia.org/wiki/British_Indian_Ocean_Territory#...
I think what started the startup scene in Berlin was largely low rents and an exciting city more than if it's entrepreneur friendly. On the other hand a lot of entrepreneur seem to complain just out of inexperience in business.
I switched to BitBucket a while ago and have been so happy. It has free private repositories, HG or Git, and most other important features that GitHub has.

Everything about GitHub is great except for the fact that you have to use Git.
1. I made money high school doing web sites and tech support for individuals and small businesses around my neighborhood. Most of this work either came through friends & family or people I'd met while working in a student job helping people use the computers at the local library branch.

2. I made more in college by making up a paid job with the student affairs department (one that did need to be done, not make-work), related to my role with the student government, and then doing it. Is that entrepreneurial?

3. After I dropped out of college I worked doing odd jobs / handyman work, and as a contractors apprentice, doing home renovations. Once I learned the ropes, I went out on my own and worked for myself doing that.

4. After I finished college I went back to doing freelance web development, again working for myself.

While I learned things at all of these, any of them could have been my first $10k if none of the previous had happened.

In between, I worked non-entrepreneurially at a series of non-profits / not-for-profits -- a summer camp, my university, a hiking club. I now work for a growth stage company, and it definitely has its advantages in stability and ability to focus on the parts of the job you like. No doubt I will work for myself, and for other non-profits, again in the future.
online poker, starting with $50 and slowly building up
Sure, "everything" might be a hack, but you should recognize that a hack is a workaround - and understand the limitations when you implement it (rather than acting surprised afterwards and asking for someone to change the rules).
Came here to say this, and drop this video[1] as well. It explains the differences between git and darcs/camp using an example editing session with both tools.

[1]: http://projects.haskell.org/camp/unique
I actually learned of Nyan Cat from all the silly Nyan Cat hacks that showed up on HN.
There are some great hacks (most are) like unix dot files, don't you think there are some dirty hacks? Like a NAT? And god forbid, i didn't want people to tell they should stop hacking. I just think worse is not always better.

IMO this means more hacking is necessary. The hierarchy with dots becomes unpleasant.
>If you're consistently writing buggy code and rebasing to fix it, then you're coding badly. Don't fix the symptom by rebasing endlessly, figure out your problem. And you do have a problem, because not only are you writing crap code, but you're committing it as well!

>Look closer at your diffs. Write more unit tests. Run them more often. Whatever, figure out what you need to do to avoid routinely making bad commits.

I disagree with this. Git is fast enough that you can commit early and often - more often than you can afford to run unit tests, even. I find it very useful to be able to commit each minor change of direction; half my commits don't even compile (I also believe in using strong type systems and the "compile error tells me what I need to change next" approach). If I need a "clean" history for review or similar (though honestly I don't see why you would - just review the differences between the branch head and branch base) I can always squash those commits thanks to git's nice history-rewriting features.
This is a genuine question - do you really believe the (to me, seemingly obvious and much greater and potentially more dangerous) costs of switching away from astronomical time for measuring something inherently astronomical like the length of a year are smaller than the costs of removing the occasional time-handling bug in software?

Absolutely.

As http://queue.acm.org/detail.cfm?id=1967009 notes, fear of encountering leap second bugs ALREADY causes many factories to schedule downtime around leap seconds because of how serious the potential consequences of not doing so could be. It is just a question of time until someone who had such a bug doesn't realize it, doesn't schedule downtime, and suffers the consequences.

And what's the consequence of eliminating leap seconds? In the next few decades the Earth and our clocks will drift out of alignment by about 1% of the amount that they are already forced to be out of alignment for most of us by the fact that time zones are an hour wide. Which very few people will notice.

Even in your example, Linux machines didn't actually crash - some processes spinlocked. And it wasn't even all Linux machines, if you were running a mildly old kernel (say, the one that came with debian etch and derivatives) nothing happened whatsoever.

If the bug had been introduced during a longer period without leap seconds - not long ago there was one that lasted 7 years - then its impact would have been more widely felt. And it is true that it wasn't technically a crash, but many websites did suffer outages because internal services stopped responding. In common usage that was a crash.

Beyond that, there is no shortage of time standards that are both based on SI seconds and free of leap seconds - Terrestrial Time, International Atomic Time, GPS Time come to mind...

UTC is the standard for time in C, all languages derived from C (eg Java), and all languages written in C (eg Perl, Python, PHP, etc). It is also the standard in all Unix operating systems (including OS X), POSIX, Linux in all variations including Android, and has even been adopted by Microsoft. It is also the standard in widely used protocols written on top of that, like HTTP, and inside of any software built on top of them, such as web browsers.

Yes, there are other definitions of time that you can use. But UTC as published by NIST and distributed by the NTP utility is "the time" as far as the computer world cares. If you use anything else, people will ask - repeatedly - why you have the wrong time.
Wikipedia's Women Problem
Answered a tweet asking for help setting up an open source web service, ended up landing monthly $1K fee for "maintenance". Worked a total of four hours in one year for $12K, then the contract ended. I quit my real job soon after
Stock-market investment
Hm... I think this post is rather myopic and very specific for the author's workflow.

> "This bug started happening on Tuesday last week" [...] If you aren't aware of this and you start running your "git bisect" using your "good" base as the last commit made on Monday last week [...]

Well, or you could find the first commit on Tuesday last week and start with its parent. Or, better yet, have "releases" tagged or at least have a log of deploys (timestamps, commits); what if I developed something on Sunday and pushed it to production on Tuesday?

> You only get the plethora of merges if you're using git wrong.

I've seen it in real-world codebases. Some people just don't know how to use git very well (either can't understand it, or don't try to), and produce ugly history. I agree that for "noobs" it's better to merge than to rebase (less opportunities for failure), but good developers should know there's a place for both `rebase` and `merge`.

> And you do have a problem, because not only are you writing crap code, but you're committing it as well!

Well, one idea of git is to "commit early, commit often". It's much better to commit bugs and then commit fixes as well than to not commit and loose a bunch of code (due to a mistake or hardware failure).

I use rebase often. I should probably commit more often. Everyone has their own way, and we can all learn other ways and improve our work and life. But getting all angry and upset because someone uses rebase more often than you is an ineffective way to learn.
Paper route. I went through a couple rear axles on my bicycle because the papers were so heavy. At one point it just snapped right in the middle. I guess I'm dating myself now, you kids don't remember what an actual newspaper looks like.
The telescope was positioned at the L2 point about 1,500,000 km from Earth [1], which presumably precluded replenishing the liquid helium. Thats rather different to the Hubble telescope's 560km orbit which was (only just) reachable by the space shuttle.

Does anyone know why the Herschel was so far from earth? Easier stationkeeping at L2?

[1] http://en.wikipedia.org/wiki/Herschel_Space_Observatory#Laun...
I made a library application for Epic Games. Looking back, I think I severely undersold myself (closer to $1k than $10k). Then sold it to another studio. I'm thinking about converting it to a SaaS app, but I don't know how I'd gauge further interest (I made a barebones landing page but apparently google won't let you advertise those).

The one lesson that is extremely clear: networking is paramount. I only got the job initially because my name was thrown around by a friend and was only able to sell to the other studio because of a connection I made while doing the project.
Interesting story, thanks for sharing. Glad I'm reading about it and not living it.

I don't know much about this sort of thing, so I'll ask the obvious dumb question: why no batteries to start the diesel generator? Was it too big?

Edit: Reading on, it seems like compressed air is the norm. Is it more space efficient than a battery big enough to start a large generator?
I've been working for around 11 months now as a marketing guy and I now touched my $10000 mark. In India $10000 is annual average salary of a fresh graduate. I'm into my 11 month of my first job and I touched it even though I started with below average salary. And the feeling is inexplicable.
How is this different from any other commercial vendor?
.io has a normalized meaning. Accept it, or simply don't use it :)
Kind of off topic, but I went to change my password for the IO NIC after reading this. Apparently they store it in plain text...
Typing in pages and pages of hex...hoping like hell you typed each character in correctly...
This is phenomenal news for France! After having married a French woman, lived in France and subsequently we moved back to the U.S., I realized how far behind France was in the entrepreneurial game when compared to the States. Yet, there are really brilliant people in France! These measures are definitely a step forward. I will be interested to see if they speak about it on Le Grand Journal this evening. Once we have children, we have thought about moving back to France because the education system is so good but, we have been very pessimistic about doing so because entrepreneurship is so looked down upon.

Unfortunately, I don’t think Hollande’s efforts are going to have too great an effect long-term. My experience has indicated that the French system is set up in such a way as to reward people who don’t take any risks. It is not simply the banking system or taxes that is to blame. There is a cultural stigma against taking risks that does not exist in the States. The education system is at least 100x better than the best schools in America, yet good test score count for very little when it comes to the hustle required in entrepreneurship, much less web based entrepreneurship where everyone is brilliant and hard working. There is simply not the same commitment to innovation. I often felt that I had made a faux pas when I lived in France and spoke about different business ideas at dinner or a party.

Unfortunately, politics is not the only problem holding the many brilliant people in France back from innovating and changing the world. In France, it is not culturally acceptable to want to be like Elon Musk.
Jawbone Agrees To Acquire BodyMedia For $100M, Opens UP Platform For Developers
> All of which is to say that the term "for-profit" doesn't necessarily mean the entity's sole purpose is to maximize profit, or indeed to make one at all; it's simply a classification for tax law purposes...

Except the minor detail that any for-profit is in fact legally OBLIGED to maximize profit for its shareholders.
My first thought when I read the title was "Please use mercurial", because git is just a complicated tool that most of the time provides a distraction from real work (admittedly, a tool that gives a wonderful false sense of superiority - "zomg I am 3l1t3 h4x0r because I could finally persuade git to do what I want").

As a hg user I really can't have any understanding when I get git messages like "![rejected] master -> master (non-fast forward) error: failed to push some refs to ...". What the hell am I supposed to do with that? And a few minutes later I find out that in git you can't pull all the branches at the same time. Seriously, just use hg and make the world a better place.
> Aren't we supposed to be a community of rational, thoughtful people that use facts and evidence to backup opinions?

HA! You must be new here.
Lost my job. Updated my resume. Got on the phone. And pinged all my contacts via LinkedIn.

And instead of taking the next F/T gig, I went to work for myself. 5 years and counting.
It's rather silly how SO closes relevant interesting questions if they don't fit their narrowly defined QA "format"
I wrote an ERP system for SMBs. (Enterprise Resource Planning, Small/Midsize Businesses). My first sale was to a 20 person automobile aftermarket wheel manufacturer for $20,000. I remember sleeping with the check that night.
20 year anniversary for WWW today
$10 for a gimmick program that will get used once?
There are remote-controlled RF switches for $20 for four. The Raspberry Pi can send RF signalss to these switches. Unfortunately, I don't have an oscilloscope to reverse-engineer the signal for mine, so the most I could manage to do is turn them off (but not on).

That's a very safe way of doing these things. If anyone else knows how I can reverse-engineer the signal, I'd appreciate it (I also want to make the Raspberry Pi open my garage door, same deal).
Solve interesting problems in Math, Physics and Computer Science
Day 146/147: Sketchy Website of Curiosity
Sockii: HTTP and WebSocket aggregator
Teardown: Samsung Galaxy S4
16KB! How luxurious, I had the standard 1KB. I saved my pocket money but by the time I could afford the expansion pack the industry (and I) had moved on.
5 Weight Loss Tips To Keep You Slim And Fit
Being overweight brings about lots obesity related health problems. In most cases, people who are obese suffer from type II diabetes and hypertension. If you are one of those people who have tipping the scale more than you should, start making a difference in your life today...http://bit.ly/ZPqaSr
"Why Linux Sucks" - 2013 [video]
I wouldn't worry to much. This is Norway, not the US, and our courts aren't quite as corruped-by-corporations, yet, as are yours. Do a little research on the DnB vs Røeggen case where the latter recently won a crushing victory in the Supreme Court, and ask yourself if there's any way that case could have been won in the US, against the largest US bank.
Moln.is - VPS hosting from the people behind the Pirate Bay
I made a porn site.
Feds want to expand wiretap law from ISPs to Google, Facebook
I was with the author until he/she got to the point of saying "bug started last tuesday". I don't know any serious development/testing teams that think like that, nor any developer that would search by day to find a bug.

Its much more likely to hear "the bug was in build 'x.y.z'" to which the next question is which build was green, and then bisect from there.

Searching for commits on tuesday because a tester happens to notice a bug on tuesday is a recipe for disaster... Or at least a completely wasted work day.
Colleges Adapt Online Courses to Ease Burden
New phone service for startups and small businesses
By selling imported dreamcasts...
FOSS developers like to forget that GCC is also full of language extensions and nonconformance issues.

This is pretty standard type of issues for any ANSI/ISO language regardless of the vendor.

Oh boy the joys of doing C and C++ development across multiple OS in the late 90's with commercial compilers.
Can't agree more. I never use rebase; the author's contention that using rebase is a sign that you've f@cked something up is spot on.
Saturn Cyclone Seen Up Close By Spacecraft [video]
Great point here. I do agree that having clearly conflicting information flowing is a bad thing. I may go back to the drawing board and see if we can draw up alternative templates with different language so we're providing for people in different cultures.

Thanks for that feedback. I do sincerely appreciate it.
High School student here. Made my first 10k the summer after my Junior year as a software development intern at a startup that had recently been acquired by a larger tech company.
Enthuse.me Creates Simple, Professional Landing Pages
Stealthy No More, Skillz Brings Cash Tournaments to Mobile Games
I very strongly disagree with this post. But I should be clear that I also strongly disagree with the statement 'always use rebase!'.

Merge and rebase are two similar but distinct ways to update a branch in git. They are both appropriate at different times. A very good guide to sensible merge/rebase policy can be found here

http://lwn.net/Articles/328436/

(see also http://lwn.net/Articles/328438/)

I use rebase regularly. I always work on branches other than master, i.e. task and feature branches. I never rebase branches that are shared with other developers - development to these shared public branches is always just adding new commits to a stable history. Merging is important but rebasing is a wonderful tool.

With respect to the issue of timestamps, I did not know this and am very glad to learn it, you do have a problem here. My position would be that I would rather throw out the timestamp chronology than abandon rebase. Typically in my experience bugs can, and usually are, tracked against a particular commit, which solves this problem. However, I appreciate that this won't always be the case, but throwing out rebase for this is a high price for a moderate reward IMHO. :)
Just curious what you mean by market research? Interviews with actual potential customers?
People do this? Like put unfinished clumps of code out in the wild? GitHub is not your personal backup drive!

Along the same lines, what is the point of the "it builds" widgets that I'm seeing lately? Unless you have some kind of stable release available, it had better build.
Temp agencies taking immigrants for a ride in Chicago
Freelance PHP dev work while I was in college.
Brand Bigger: Is your business defined by what it sells?
If they were suing Google or anything like that, you'd be right. But they're not. They're just saying "Google, your index would be more accurate if you made this change".

They have figured out a limitation, think it's unnecessary, and are suggesting a way of making the system better. They're using the blog post to encourage others to support the suggestion.
My son does a paper round on his bike. :) The tradition is very much alive.

The weight of his papers is quite staggering. I sometimes think it weighs more than he does. :)
I noticed on your blog you referenced a recruiter that screwed you (or someone over). Do you think that experience and others has fundamentally altered the way you view recruiters and HR-types?
Every complaint I've read about rebase is this same one, over and over, and I think it's based on a false premise.

> Rebasing destroys your history, and therefore destroys the point of using a VCS.

The answer, of course, is don't do that. Don't rebase public branches, and that includes master and whatever else you're deploying from.

In any case, you can't rebase master unless you're willing to force push, and if that hasn't tipped you off to the fact that you've gone off piste, what will?

> If you've got an entire history that's been heavily-rebased and your problem is "This bug started happening on Tuesday last week", you have a big problem: You can't just track back through your simple, linear branch until you get to last Tuesday's commits.

This hypothetical scenario of last Tuesday's bug therefore makes no sense. You can do exactly that, because you don't rebase history: you rebase work in progress onto the canonical record.

In summary, rewriting history would be bad, but that's not what rebase is used for.
First $1,000 Admob Ads.
I work on it, but overnight cures do not exist for this kind of thing.
Obviously, there's a level of understanding that requires source access, but problems for which that level of access is necessary as few and far between. This problem, for instance, is not one of them. I highly doubt that most people who are using an OS for which they have source access are either interested in or capable of doing analysis at that level.
The example given in the "story" is useful.
A customer read about what we were doing in the newspaper after the governor threatened to shut us down, and then wrote us a very large check without even asking the price.

It was never that easy again.
This is a huge challenge, especially when we know it's the case. Most companies simply don't respond. It's personal preference, but I always err on the side of turning the other cheek and doing what I can to build new relationships.