skysight-inc/HackerNews huggingface dataset:
The author goes on a lot about metadata and bad search interfaces for it. Yes, classical music metadata doesn't fit with the "simple" pop music artist/album/song format. (Though the "featuring" and remixes in pop music also mess that up.)

Often people try too hard to fit data into a fixed schema or ontology. It made sense when data storage and retrieval was based around tabular and relational data, but in these days of search engines and document databases and JSON, it's just unnecessary. Instead of pre-determining the fields you search on, you should search with free text, then refine with whatever metadata happens to be available.

So instead of messing with Spotify's "artist" search, you could just go to Amazon (or Google) and type in "Beethoven's Ninth Bernstein New York Philharmonic" and you'll almost certainly get back the items you want near the top of the list.
Did you mean "a WTF service"?
I can appreciate Apple's strict screening policies, but it seems like there should be some avenue for appealing while making a genuine case for the value of an app. Quality is one thing because it's not particularly arbitrary, but when they are making value judgements on what kind of experience an app offers, that's a lot more up for debate. Elements like the Reddit's "Gray Button" show that massive user value can be had from one-and-done experiences.
Piece of wing found on La Réunion Island, allegedly come from missing MH370
We seem to be in violent agreement. "If you use your computer to commit a crime, you should be punished."
> Since [...] 2000, global recorded music revenues have fallen from $21 billion to $7 billion per year. [...] So where did the money go? Two places: into the pockets of Digital Monopolists and Digital Thieves.

The author here is making an absolutely incredible assumption here, which is that the decline in revenue for the entertainment industry is somehow fundamentally wrong and must be caused by bad people.

But it's far more likely that the revenue seen by the entertainment industry leading up to 2000 was an aberration, caused by a very brief window of time where technology enabled mass production and distribution by corporations without easy copying or sharing by individuals. But if you go further back than 2000[1], I'm sure you'll find that their revenue was much lower not all that long ago. I'd be very surprised if that $21 billion number didn't represent their all-time peak, meaning 2000 wasn't the start of the decline, it was actually just the end of a bubble.

[1] I'm having trouble finding that data myself, anyone know where to look?

Addendum: It turns out the worldwide music industry revenues actually haven't fallen since 2000. Which I guess explains why the article explicitly said "recorded music". According to http://www.businessinsider.com/music-industry-revenues-chart..., the worldwide music industry revenues in 2013 are about the same as in 2000 [2]. But what's actually happened is that most of that money is now coming from tours instead of recorded music [3].

This further reinforces my "bubble" argument. Before the advent of easily-produced recorded music, the music industry revenue must have been mostly live music. So the bubble here is just the short period of time when the music industry was able to make a killing on mass-produced recorded music sales. But that bubble is over, we're back to the industry needing to earn its money from live music and other secondary sources. But of course the music industry doesn't want to admit that this is a bubble. They want to pretend that the business model of selling recorded music is sacred and must be protected by law, regardless of the consequences.

[2]: It's 3% lower, but that's pretty meaningless.

[3]: It says 36% of the revenue is recorded music.
tablecloth math time: $2bn worth, assuming they're worth 10 times their revenue (let's be generous), that would require $200m in sales. they have 10m users, assuming 1% are paying, that means 100k users for $200m sales, meaning each user must spend 2000 dollars per year at Github. Sounds a little high considering the basic plan is $7/month, but with entreprise sales and growth rate, it sounds feasible.
> How did you get such a great domain name? From the awesome service at park.io

A little disingenuous since the domain was never listed on park.io and this site was made by the same company as park.io.

Makes me believe that they snatch up the best domains for themselves so people can't bid on them.

I've bought multiple domains from park.io before and had a good experience, but I was always worried about this.
As others have mentioned, the trade-offs can be pretty complicated. Perhaps the take-home is always better for you, I won't try to argue against your personal preferences, I'm simply going to list a few reasons why it turns out worse for a lot of people.

For one thing, as expected, the take-home questions are typically far larger than in-person interview questions. When you go into the office you're generally asked, in my experience, much simpler questions; you might get a simple FizzBuzz-like starter, and a few slightly more difficult ones. All in, it takes a few hours (Google and the like can be an exception to that, but I'll get to that after - I'm comparing smaller companies right now).

The take-home work I've seen has generally been suggested by the company to take 8 hours, but typically been a bit more; they've been along the lines of build a fairly simple crud (I've had one that was a calendar, another that's a stream, etc.) with a bootstrap-or-similar UI, back-end validations, and unit tests for the initial commit, implement these 3-5 features on top of it in separate commits (tested, also standard bootstrap-or-similar UI, proper validation, etc.) And then, simply provide access to the repo.

At first, this didn't seem wrong, in fact I figured "well, I guess it's a good way for them to see that you understand everything". But it came with several annoyances. For one thing, since each feature is a commit, unless you specifically try to prevent it they can see things like how long each part took; even if not consciously, this makes people try to get the work done quickly, without taking many breaks. It sort of reintroduces the "hard to 'refactor' your ideas during a 45m coding interview" problem. Another annoyance is that sometimes (and judging by other comments here, even often) they don't respond at all. The silence is unpleasant, to say the least. In-person, you can at least try to read tone and facial expressions.

The other problem is one company I applied with threw a 10+ hour take-home without any warning before the interview. So a bit over an hour in their office, and another 10+ later. This is difficult if you're working another job. It's very difficult if you have a couple such take-homes at the same time, and a full-time, in office job. Scheduling a few interviews around work, and other commitments, is pretty feasible, but throwing in dozens of hours of additional coding is more difficult.

With companies like Google, you know ahead of time approximately how long it will take. You can take time off accordingly. The process is known going in, and that's great.

Basically, I think that for many people, myself included, white-board interviews are very stressful and frightening, but not quite as much so as: scheduling lots of extra time around your life, budgeting X extra hours because they take longer than suggested, building out the (much larger) projects, still having the time-constraint/expectancy issues, and after all of that not always even getting a message/comment afterward.

Both interview processes suck.
For anyone that missed the #rubydrama in December when Brian "ended" Rubyspec, I summarized it here: https://gist.github.com/nateberkopec/11dbcf0ee7f2c08450ea

I think Brian "ending" Rubyspec might end up being the best thing he's done for it. Suddenly, as soon as he (and Rubinius) left, RubySpec is running and actively used on MRI for the first time in years, and JRuby and Opal have already swapped over to the new implementation. @eregon deserves HUGE credit for making this all happen.
Right, but still only twleve of us have been to the moon.

I think the parent commenter's point was that it's pretty naive to think that there will be no more human-driven vehicles at all. Change will happen quickly in some parts of the world, and other parts will take a long, long time to catch up.
Obama Wants the US to Build the World’s Fastest Supercomputer
But the web and the Internet are not things themselves, those are merely abstract words that describe a collection of privately owned computers doing things their owners deem in their self interest. Anyone who talks about what the Web should be doesn't understand what the Web is nor what decentralized means. No one gets to say what it is, it simply is what those who build it make it.
This looks great. It's clearly still in the early stages, but what's written so far seems to have a lot of really good advice about how to set up a Core Data stack. (Which, incidentally, is very different from where the default Xcode templates might lead you). I feel like I've already picked up some good ideas from these initial chapters.

Looking forward to the rest of the book! :)
I think he still provides a good warning to heed even with his "content creators" bias.
I didn't know Brian Kernighan was RaspberryPi fan:

http://swag.raspberrypi.org/products/babbage-bear

Great interview, the next video should be awesome as well.
It's very much alive in the java low latency space where even young GCs are a problem. Allocations of temps/short lived objects also wash your cpu caches, and generally there are other reasons to avoid any GC in this space.
question:

which is cheaper, stack object allocation/creation or object pooling, in languages like C/C++/Rust?
I have been working on a Django application with two periodic background tasks to synchronize some data with some hardware, I was using Celery+Redis to handle the schedulation. The solutions for running cron-like tasks on Python are not very mature, everybody seems to be using Celery.

Once deployed in production I spent countless evenings debugging why the tasks weren't running, why upon timeouts tasks weren't terminated, and why the task queue was getting bigger and bigger. 50% were configuration problems, due to the _bad_ and confusing documentation, 50% were due to introducing a sheer amount of complexity with Celery that I often spent my time reading through the source code to understand what was going on. And Python, with all its magic methods and abstractions, made that very hard.

One day I just rewrote everything with three Django management commands: two for the background tasks, one for the schedulation (with multiprocessing). I haven't heard from the client since.
Let's assume for a moment that email is true: how many businesses have policies that allow their staff to use language in that particular way?

And Github, like most other providers, have catch-all clauses in the ToS. This one, perhaps:

> We may, but have no obligation to, remove Content and Accounts containing Content that we determine in our sole discretion are unlawful, offensive, threatening, libelous, defamatory, pornographic, obscene or otherwise objectionable or violates any party's intellectual property or these Terms of Service.

I suppose my point is that if you're a business you shouldn't rely on Github etc.
Licensing for Windows isn't as expensive as some people believe. Going in with their licensing plans, their cheapest server level with support comes to about $300/year. Redhat, for support, starts at $350. Yes, it can be $500+/server if you're buy it retail off the shelf, but any sort of internet related business, you're almost certainly not going to be going that way.
Eyüp Böcek İlaçlama,Böcek İlaçlama,Eyüp İlaçlama
4 iOS Design Guidelines Rules to Break
Many thanks for the clarification and discussion of the structure of your code base.
I wish they would say what they wanted the money for!
Seems a bit early to really tell...
No it reduces the cost to the employee, with no additional cost to the company. At least in $ or time terms. Sure ... a senior developer interviewer may need to fire up a few extra neurons.
Prior discussion: https://news.ycombinator.com/item?id=9970336
Although I havent worked with WCF for sometime (Web API is all the rage now), WCF wasnt too bad. Pretty good for making REST services, if you wanted absolute control. They streamlined a lot of the configuration needs in 3.5 and 4.
I never thought I'd see the day when HN's tide of hatred would turn from government surveillance towards the social justice boogeymen of Redditdom. You're arguing that feminism and "social justice warrior garbage" are the direct causes of Github censoring repos. It's not. If Github was pressured by people on Tumblr to use a regex to change the word, it would be a different story.

They have good intentions, but the way they chose to implement it is completely unacceptable. You cannot censor the internet. This furor wouldn't really have occurred if they'd just sent the sap an email politely asking them to replace the word with something more sensitive.
Not necessarily, they may well be profitable (I thought they are) but they may have wanted to sell some shares to get some value out.
It's been a while, but this was a common technique for agent based modeling in MASON back in the day.

Having tens of thousands of agents constantly being garbage invalidated was the use case.
I'm really glad to see this - RubySpec is a project that always seemed like a Really Good Idea, but the politics around it seemed to drag it down into not-productive territory. If it can remain a technically-focused project, it should be a large asset to the Ruby community.
Generally the stack, because the cache behavior is better and you can allocate an entire activation record at one time. The compiler is also often able to optimize the allocations better, for example by promoting stack objects to registers.
The issue tracker is absolutely a joke, but being a standard for company codebases is a huge moat. If it works well enough, what company wants to spend time moving a codebase/history.

I speak this as someone who managed developers at a company that was still using CVS. And yes, we discussed moving to git every so often, but it always was lower on my priorities than new features.
Bitbucket is free for private repos if there are <=5 contributors (unless you have a .edu email = unlimited free).
The author has some good insight on many things, but the insight is mixed up with ...something else, and that makes a conflated spaghetti. For example, why I and most of people I know opposed SOPA wasn't exactly because of piracy; I'd remind that opposition included also organizations like Wikipedia, EFF, ACLU, HRW and Reporters without Borders.

Most of the confusion seems to be there because being a content creator affects his viewpoint... which is understandable. But in a grand scheme of things, the future of professions based on copyright is quite minor issue compared to the other problems of technological revolution and politics intertwined with it.
For the most part stack allocs would be faster unless ctor does something ridiculously expensive. Also, one typically doesn't pool objects that are confined to the current thread's execution - it's mostly for heap references that outlive requests/transactions/etc.
https://twitter.com/jonostrower
Not sure if you're just joking or don't know what WCF is, but in case the latter is true:

https://msdn.microsoft.com/en-us/library/ms731082(v=vs.110)....
But when comparing the difference, and considering a code project for an interview has a tendency to be even more stressful, which would a person rather spend their time on? It certainly is not the code project - I have heard & experienced too many stories where companies vastly underallocate time, or not respect that job seekers have other things that keep them busy typically, including less bureaucracy/time wasting (especially if a candidate has significant open source contributions), or not looking at the project, or even rejecting candidates for non-code related reasons (happened to someone I know today).

I'd much rather freelance for that type of stress & when having to compare the economics time-wise, which a take home test simply does not match - that is the whole point.

If a company does not want to pay that much, maybe they should respect the prospective employee's time, especially since it is a job seeker's market.
They are probably valued at much more than 10x revenue as a fast growing company. And "users" is the wrong metric as big companies probably make up 90% of revenues, and most of that is not even visible in the public repos.
BitBucket is free for private repos with less than five people. Doesn't work for a lot of businesses, which is where most of the money is.
is this why github's been doing the censoring and making it a "safe" place? to appeal to a broader audience and please the investors? similar to what reddit recently went through

https://github.com/opal/opal/issues/941

http://readwrite.com/2014/01/24/github-meritocracy-rug
Funny, just read an article today proposing the same feature detection algorithm (the one you called 'grid merge'). Have you tried applying these techniques on scanned/photographed documents?
Cory Doctorow goes on to discuss that as well in the next paragraph after the one I initially posted, when talking about banning hands-free kits in cars:

"We understand that cars remain cars even if we remove features from them. Cars are special-purpose, at least in comparison to wheels, and all that the addition of a hands-free phone does is add one more feature to an already-specialized technology. There's a heuristic for this: special-purpose technologies are complex, and you can remove features from them without doing fundamental, disfiguring violence to their underlying utility."

Computers and software such as Google and MegaUpload are not special-purpose enough that you can make legislation about their design without "doing fundamental, disfiguring violence to their underlying utility".
Interesting concept! Just curious if you have any reports on how this affects the overall execution of a script, as well as the memory consumption and CPU usage? (Not in a place the moment to test it myself :P)
AWS CodeCommit finally available
I've had a few take home projects that weren't so bad.

But the last one I did...

A junior just basically shat all over the project and claimed a lot of things.

[The submission was to write a few sample sort functions for a library... the recruiter asked for an app, the paper asked for a library.. I did both... what did I get shat upon for? The user interface/cli that wasn't required.. another thing.. Why did I have 66 commits?]
Studying sounds like a strong word here. Author's an administrator, not a researcher. And he's likely bought in to the Uber economy; current openings at Oglethorpe are administrative and adjunct:

http://www.oglethorpe.edu/apps/careers/
Are they still fast-growing? I would have thought that their growth curve would be flattening out at this point.

Most of the big tech companies already have a presence there, and they've been the go-to for VCS-using developers for a few years now.
Tesla Referral Program
Github currently may use the "social coding" part for marketing now, but it can build off it in the future. For example, StackOverflow built a whole careers site off Q&A, Github can choose to go further based on real code.
Nokia's problem was in large part "boardroom meddling", with a mix of "innovators dilemma" thrown in for good measure.

The company executives were worried about Maemo eating into their fairly steady Symbian earnings, and so where reluctant to commit fully. At the same time they feared going Android would turn them into just another "me to" company (Samsung has done some serious advertisement binging to get their current position).

And just as that seemed to clear up with buying Trolltech for their Qt library, aimed at using it for cross platform app development, the board ousted the CEO and brought in Elop.

But shit didn't really hit the fan with Nokia until Elop's "burning platform" memo. Pretty much overnight retailer dropped outstanding orders etc, and the Nokia brand basically crashed.
So it seems that the true test will whether a shop like HP would adopt Github Enterprise and pay $20/mo/programmer for 50,000 programmers and pay $1mm/mo to Github.
I think by 'ironic' you might mean 'smart' since the author is the president of the university. He has to run an organization in a market that is shifting towards utilizing labor following this model
I get that when it's just a personal project, but the Github workflow is also very nice to have. When I want a buddy to access my private repo, I just add his/her GitHub user name, I don't need to have them create a BitBucket account. I don't need to figure out how issues and PRs work with BitBucket, etc. It's the network effects and UI that I'm paying for - one UI private or public. Plus, it supports a service I value very much.

On a more important note, you're probably not GitHub's target market. It's more like agencies and in-house dev teams.
Defcon Password Cracking Contest
Checked with Stripe on the validity of this, their response:

"While we may have plans to expand this year, there is unfortunately no ETA at the moment, nor can we guarantee that if we expand to New Zealand that it would happen before 2015 comes to a close. We are hopeful, but cannot provide a more accurate timeframe at this time."
Re: IPO I didn't mean to say that the public markets would be wary. Quite the opposite - the short-term scrutiny from Q to Q that a company faces after going public is not for every type of company. Look at Twitter, Yelp etc. I'm not sure if Github is profitable yet, but unlike an Amazon (eCommerce), the market would expect most other companies to show rapid revenue/profit growth once public.
I learned about this before it became front page news here, and personally confirmed the repo was made unavailable for a while. That and its return is entirely consistent with the supposed email.
Ah. Nokia used to spend more on R&D than Microsoft and Apple combined, and this was in the iPhone days. I've seen terrific innovations from Nokia that were never monetized and were never implemented in a product, phones created just to experiment or show that you're the first that later went nowhere.

It was very sad to see Nokia fail.
Repository hosting seem to be a market where multiple companies can strive. Both GitHub and Bitbucket can capture more value.
Hi everyone... this is a side project we've started and keen to get feedback on.

The hypothesis we're testing is whether there is a bunch of freelancers, designers, engineers etc... around the world that have 1 or 2 overdue invoices that they're struggling to get paid, but getting them paid takes time they don't have and requires an awkward phone call they'd rather not make.

We've tried to make the experience much easier, friendlier and faster than hiring a traditional credit control person – so you can get that phone call off your To Do list faster.

Keen to hear your thoughts... would you trust us to make the call on your behalf? What are your questions / concerns?

Thanks in advance.

Matt
Co-founder
Do you have more examples like this? Sounds interesting.
I don't know why this was downvoted. This vulnerability in Jetty was the result of sharing a buffer between requests: http://blog.gdssecurity.com/labs/2015/2/25/jetleak-vulnerabi...
If its an option and they don't exhibit any bias towards candidates that prefer a traditional interview then thats fine, but they should make it clear in the article.
I support github banning all projects that use the word "pickle" or "umbrella" or "orange". Their servers, their rules.

I'm less touchy about mental illness words. I tend notto say anything when they're used. I sometimes say something if people (wrongly) link mental illness to violence. There has been more time for insane etc to change use.