skysight-inc/HackerNews huggingface dataset:
My approach to equity was to offer a range. We'd offer base equity and salary numbers, and then give them an ability to trade salary for equity. If I recall rightly, they got a modestly better deal than investors did.

In doing that, it became clear that not everybody even wants more equity. That was a little hard for us as founders to take, because we of course thought the equity was awesome, and wanted engineers to feel a real sense of ownership. But from the numbers, it was clear that some people would rather we sold more equity to investors and just gave them the cash.

I get that. If you've been around the industry for a while, you can accumulate quite a collection of expired startup lottery tickets. Landlords, mortgage-holders, and kids' orthodontists don't take options; they take cash.
cool helper functions, now that I want to use them, I'll need to update.
Another way I could say the same thing that sidesteps your argument is that the more generous you are with equity grants, the more ruthless you need to be about firing.
I was sarcastic about "a little bit" part. While it was expensive you got service and some attention. Still I agree that it is unreasonably expensive.
how did you animate some of the elements in your infographic?
Just noticed that you can't search on your website if you include '(' or ')'. 500 Internal Server Error.

i.e. https://sourcegraph.com/search?q=%28
We have this already - it's called the stock market and bond market. If you want to distribute the risk of investing in real estate, I suggest taking a look at REITs, real-estate investment trusts. They are companies investing in real estate required to pay out a certain % of profit in dividends.
https://en.wikipedia.org/wiki/Project_Thor#Project_Thor
I'm not feeling that particular frame; It makes everyone look like an angry nerd. That said, it's certainly better-looking than Google Glass. If the 6 hour battery life ends up being the final spec I don't see this going anywhere, but it represents an effort to fix perhaps the biggest marketability issue with Glass, which is of course that it makes you stick out like a sore thumb.

Edit: I have to add that it's cute that they named their startup LAFORGE...can't help but read that as a wink to Star Trek: TNG fans.
Skip the present business model, make a product out of your hiring model. To reach that predictability is worth a lot to most any company.
Because run-flat tires cost a lot more than removing a chip. Or buying a jammer, if they get clever about making the chip hard to remove.

You don't have any support for you claim that a, b, and c were unrealistic. Pot, kettle.
> That's different from what you'd expect at companies in virtually any other industry or category of tech.

What? That's fairly routine in many industries...

I feel bad about linking to about.com, but it emphasizes how common it is.

http://jobsearch.about.com/od/jobapplications/a/reapply-for-...
Your comment doesn't really make any sense. I'm not sure what pajamas and Target have to do with graphic design.
You've had critial success. You've made so much money you could retire, buy an island, and still have enough left over to turn it into a supervillain lair! I get it. You're only in it now for the love of creating, so why not leave the headaches of A titles behind? This is perfectly sensible. Handing off irrational to a protégé, taking your buddies and spinning off a smaller studio would be a great way to do this. Firing half the company that brought you success, however, is a bit of a dick move.
Though I don't have any experience with OpenBSD myself, I read somewhere that it was hard to virtualize.
> Venture as an asset class has underperformed the S&P over the last 10 years[1], so you probably aren't missing out on much.

And that's actually biasing the comparison in VC's favor.

The S&P 500 is a large-cap index. Venture capital is supposed to invest in early-stage companies with high growth prospects. A fairer comparison would be to a small-cap index, or to private equity, or to private equity that only takes on small-caps.

Also note that venture capital is risky and illiquid. It should earn a risk and liquidity premium vs. the public stock market. If it can't earn at least this premium, then it would be producing negative alpha.
It's hard to imagine that Facebook, Twitter, Dropbox, Google, Amazon, Apple, and all the rest of the companies that hire software developers, who have more or less the same type of interview, have gotten things wrong, yet have been so successful in hiring good people and building good products.

Perhaps the real problem is that those companies have taken all the people who perform well at whiteboard interviews, and what's left are people who struggle.

Still, I wouldn't say the system is flawed because it selects a certain type of people. Clearly those people do well.
I wonder if anyone in NY, SF, or any other 1st tier developer city can comment on the local unemployment rate for either software devs or IT in general. Here in Orlando/Tampa it's been around 2% for YEARS.
"I'm just hoping I can work my way to a comfortable retirement, and at least be able to sleep at night when I look back over my choices in life."

---

I feel the same way. I have ethics and morals. Humans are not merely pawns to be manipulated by me as I climb to the top. I try to live each day without regret. Anyone can get rich. The question is can they live with themselves afterward.
I have to completely agree... MongoDB does do okay in terms of small-mid scale needs, and is dead-simple to work with. It's a very natural fit with node.js, and does "good enough" for most.

I do think that over the next 2-3 years as PostgreSQL adapts and expands the V8 extensions (and JSON data type) that it will probably take over MongoDB, and that we may well see a "mongo" adapter for a postgresql based backend.

The place where I have MongoDB in the wild, it's a great/natural fit for what it's being used for... searching (including geolocation) on about 30k active records for a vehicle classifieds site. It should work on up to 10x the current load on the single server instance it's on, and can be re-deployed to a larger cloud/vm instance. The SQL db is the source of record, and data is replicated to the mongo instance.

ElasticSearch was also considered, but didn't work as well when development was done (over a year and a half ago).
>"I'm honestly starting to believe that it isn't hard to hire, but that there's some psychological effect at play that leads companies to make it harder on themselves out of misplaced pride or sense of elitism."

I expect that a fair portion of "We can't find qualified people!" is actually "We can't find qualified people for what we're willing to pay."

Beyond that, I wouldn't say that it isn't hard to hire, but it certainly seems popular to make hiring as hard or perhaps more accurately - to make passing as easy as possible whether it's via veto, "culture fit" or something else.

I was hoping that the vote of confidence in "behavioral interviews" [0] from Google over the summer would help things a bit - I guess not.

0: http://www.nytimes.com/2013/06/20/business/in-head-hunting-b...
"Beef" in the second case is probably short for 'beef cow,' just like 'dairy' is going to be short for 'dairy cow,' not some weird anachronistic usage (unless the Normans once called cows 'dairies.')
You may have misunderstood. A file can have multiple, say 'deployment units'. You can have a 'migrate deployment unit' which depend on the 'model deployment unit' which forces the app server to deploy the migrate unit first. You can have code there that migrates the tables and fill with default values before your model entities become available for use. From your comment this seems to be the same as what Erlang does for your example, unless you are claiming that Erlang's implementation is superior which could be the true, since I have never written any non-trivial programs in it.
Agreed about it being positive. Event organizing can be tough and we want to make it easy. I think "joy" helps emphasize this.
By "projects" I mean code delivering actual software products (like for example the search, gmail etc.), not some auxiliary admin scripts.
So that he will tell them who is providing the source material...
I don't think the target audience of the blog post was experienced Scala developers (that would just be preaching to the choir!) so the use of unexplained jargon should be kept at minimum to actually reach the audience.
I'm not sure I understand this. Are the number helpers now escaping for a HTML context? Isn't it best practice to escape user input just before outputting it (so you know the context) rather than in every helper function?

Disclaimer: not a RoR developer.
Annnnnnd that's my thesis sorted. Part of it anyway.
Appreciate you're insight here, if anyone knows first hand, I'd imagine it'd be you with your experience on developerauction.
Looks like some rarely used view helpers. I doubt many of these are used in production apps.

Hopefully no Bitcoin apps use the currency helper. But I imagine in the context of an exchange the numbers come from the blockchain or a wallet, and aren't user controlled in the way that could be exploited.
I have had good enough luck that I won't dismiss a recruiter outright.

I treat recruiters like widening the funnel, and haven't found any correlation that suggests they produce better results.

I have found the best results is hitting people up through linkedin.
In my mind the bigger issue is that something like CSV parsing is so common, and so old that it just should be part of every higher level language's standard library these days, as common as split() is. That way people learning the language learn that you just do it with the library and get on with it.

(I agree with the rest, anybody can more or less learn their way around a library with a little time, but learning to actually code well is a much more valuable skill and much more rare).
Just realized I forgot to link the repo on the page. For now: https://github.com/aakilfernandes/sharebuttongenerator
http://en.wikipedia.org/wiki/Banknote#Early_Chinese_paper_mo...

7th century Chinese bank notes.
So accurate. I'm a grad student who studied security deeply during my time in school.

I want to keep my hands on a keyboard and I don't like airplanes (which rules out consulting) so I've applied at a lot of companies to be a ``security engineer''.

I can't tell you how many well-respected companies ask me to write min-heaps, depth-first searches, etc. I don't understand what they are asking me this for...It isn't even close to a realistic representation of what my day-to-day responsibilities would be. It is also an immediate turn-off....
Yes. We are all going to live an infinite number of years. So any difference ($30-60K a year) in salary is justifiable even if you are doing mind numbing tasks making other people insanely rich. Even if you die, you will be taking all that extra money into your next life! So slave away my friends :D

/s
There should be more properties by which system is valued. Free system can be inefficient, corrupt and slow like it is partially in my country. Still results surprisingly are quite similar to US looking at statistics.
In what ways do you consider them to be different from the point of view of an architect (other than the different clustering implementations)?

They're both document databases. They're both distributed. They're both supposed to scale.
You're right, this conversation is useless. Let's get back to pragmatically discussing how old whales are.
Cluster-Level Container Deployment with Fleet
>"Don't hire outside your network."

If nobody in your network has a track record of results, become a sycophant? What if all the hackers in your network are US as well? You got less than a 5% chance of a hope to do anything according to Altman.
There is a gold crunch as well - I can't find 999% gold at 1$ per kg.
That's funny... where I work now, most new development is being done in node.js, with a migration strategy to get most of our backend (for the apps I work with) onto node.js by the end of the year (from .Net) ...

I've been pushing for node.js (as a JS, and node fan) for the better part of the past 5 years now (since node started)... So, definitely not tied to MS, but do make my living on supporting their tech stack, for the time being.

I just wanted to point out that simply fronting IIS with nginx is a flawed idea, unless you have reason to do so, and/or already have the nginx infrastructure in place.
NameChanger is another great tool that helps with this family of tasks on OS X.
http://www.mrrsoftware.com/MRRSoftware/NameChanger.html
Wow. That looks outrageous. Unless it is some new antibiotics. Still in my case if I get sick I get some free services but I usually should pay myself for my medicine.
What to do With Your Recruitment Budget (aka The Great Lip Dub of 2014)
Perhaps coincidentally, companies say there is an engineer shortage while at least 80% of the Rails jobs on LinkedIn & Craigslist are posted by recruiters. Recruiters may simply be ruining the employment market, probably as a gold rush.
Making Angular.js real-time with Websockets
I know the company and I know about tptacek from HN, even a friend worked there a few years ago. I just wanted to understand if they were in some new specialized niche.
Yes, but I wrote:

What if you use the land price increase at the other end of a (quite) fast train to finance building the commute link?
At this stage in this new product category, the design of the actual glasses is so irrelevant. What matters is how big the required hardware is, the tech specs of said hardware, and the UI/UX within the user's vision. I'd say the UI/UX is the most important factor, since all the physical hardware will change as it advances.

These types of companies are wasting their time trying to design glasses around this tech. There are thousands of different styles of glasses, would probably be easiest if they just partner with Warby Parker or something to make lots of different styles, without all the work of designing them, since as they say in their video they need hardware/software engineering help. Those problems are more critical than glasses design.
The game business is like the movie business in that projects are "seasonal" rather than a constant thing. Unless you are working on a tight little indie game or a recurring blockbuster series (Call of Duty, Madden), the number of people that are required at any one time in development is incredibly variable. "Pre-production" headcounts need to be very small because the devs are still figuring out what the game is and so don't have anything for an army of artists or engineers to do.

Programming jobs in the games industry (and the entertainment industry in general) are not like "normal" programming jobs, despite the fact that they require an almost identical skill set. Put another way, they require the skills of a programmer but function on the employment schedule of a Hollywood lightning technician.

(It sounds like the company your friend worked at was also mismanaged on top of this cycle, which always makes things worse. Sometimes very much worse.)
Concatenating your large collection of controllers, services and directives. Running internationalization jobs, running unit tests, running JSLint, running LESS compilation. Creating a versioned file so you have a fallback. And more!
Guava is decent enough (though not complete enough for my tastes), and should be much much better when lambdas are available.
I could upvote this all day. I was rejected by a company that posts about their need for developers constantly, and it irritates me to no end. I provided a big batch of sample code privately, on Github, demonstrated the apps I've shipped, showed great enthusiasm in their product (I was a happy user long before I attempted to join the company). They see all of this before interviews and then they reject me because of how I named a variable in a 15 minute pair-programming exercise and said I should read Code Complete (I have mostly), promptly ignoring the thousands of lines of code they could inspect. I'm sure there was more to it, but still, left a bad taste in my mouth.
You make assumption that free health systems in Europe are accessible to poor as well. I can't speak about Western Europe but in Eastern Europe free has cost as well. While it is not as expensive as USA. Unless you get some rare illness that only USA doctors know how to treat.
Yeah, sounds like you could build a really cool civilization over that, I'm totally in. (Not sarcastic at all, I definitely enjoy the world and how it works.)
A 66% sale within 6 months for an AAA game is rare. (usually it's 33% max)

However, I got Battlefield 4 for $20 in less than a month after release, so it's possible that's the new norm.
I dual-booted Ubuntu for a time, but there was always some niggling issue that prevented me from ever fully switching over. I come back and give it another shot every few years and it's always the same situation.
Living in a high cost of living area is a FANTASTIC way to get your retirement plans going. Putting 10% of your SF income into your 401k is way better than putting 10% of your Austin, TX salary into your 401k. So while you're young and single you bank away lots of cash. Then you move and start a family elsewhere and retire comfortably. The problem is that I don't think enough people life-hack in this way.
Resubmitting Your Sitemap to Google
"one of our interviewers felt threatened by you because you're more knowledgeable so he veto'd you"

does this ever actually happen? it would never fly during any of the interview processes I've helped conduct.
Very correct on the indie thing. It's the only way to ensure some stability: keeping it small, keeping it simple.

The big game development studios have always been like this. Half the time, they do have concurrent dev cycles, multiple games in the works, concepts being fleshed out for the next game long before the current game ships.

Here's the problem: the publishers. They give your studio money at the beginning of a development process, and that entitles them to be utter ogres about schedules and ship dates. It's very common for a "next project" to be yanked out of your studio's hands and placed with another firm. It's also common for development studios to pull in outside firms to help them on projects, as when Gearbox pushed the Aliens Colonial Marines game to Timegate Studios.

The end result is that there is this humongous push to get whatever is next to ship out the door, and to hire and freelance help around that project. Once that project is done, shifting to something new would require repurposing everyone, which means a few months of unproductive work, or worse yet: a few months of no work... Check out some of the details in http://www.gameinformer.com/b/features/archive/2014/02/12/fa...

Going from the period of game development where you're experimenting, to the time where you're full-bore pushing on a final vision is not something you do overnight. it requires a lot of prep work from game designers, engine developers, and art directors. If they've just been doodling around and trying to "find the fun" as is the primary goal in most early game dev processes, then they're probably not ready to gear up for a huge push on something as soon as the previous game ships.

Thus, you get this scenario where AAA require millions of dollars to make, but developers don't have that kind of cash (save a very few), so they get it from a publisher, who then handcuffs them to ship dates. Anything you can do to get that ship date met will result in a return of vastly more money to your studio, due to how contracts tend to work, so you throw money at the problem through staffing up.

Then, when the game's done, you go around to publishers with the next idea and take on another million dollar contract. Why? Because the funds you receive from publishing that last game don't come into your account (if you actually get any money at all: many agreements are only for the up-front $) immediately. These are effectively royalties, so you will basically be waiting a full quarter to get your next check from the publisher. At this point, you can't afford to float 200 AAA developers and artists for a full quarter.

This is why online, in-game-transaction games are utterly decimating the publishers in terms of growth. Riot Games is immense. Valve makes oodles. Why? There are no publishers between them and the player. All the money comes back to them I don't think Riot's had a layoff yet. Valve's layoffs were entirely project-based, not funds-based.

Publishing yourself online is the future, in every way. It encourages agile development, and lets people go home at night to sleep (except the server admins, but they can't sleep in any industry).
Ask HN: Where can I find datasets of size greater than 1 GB?
I am looking for datasets of size greater than 1 GB for a graduate academic project.

Datasets which are publicly available (or available upon request) and contain location-data and/or vary over a period of time.
> You can't expect to slap a random distro on a random computer and expect 100% of everything to work without some tweaking.

Right, and I think most people agree with this. But we can't assent to that and then turn around and claim "Linux is just as user-friendly as Windows/OS X" or "Anybody can use Linux; it just works." It does nobody any good to pretend that Mint (or Ubuntu, or whatever) is yet at the level of Win 7 or OS X in terms of out-of-the-box usability. People who are unequivocally recommending Linux to the average layperson are doing everybody a disservice.
It's not at all hard to imagine that the best known company in the industry, the one that spends the most on direct outreach to clients, whose compensation system more or less sets the standard for the industry, a company that is essentially rolling in money, is able to make a conventional recruiting process viable for itself.

Having said that, if you talk to Google people who are close to hiring, especially about the process that connects "interviewers" to "recruiters", I don't think you're going to hear consistently good things about how the system works in practice.
Latches aren't async code control? Javascript has (async) best practices that survive more than a couple years?

Promises are great, I totally agree (as long as they're A+ compliant). But they're not on every platform, and it's not (usually) worth building your own if it's not there.
Google has a marketing division?
What for?? every person already uses their site everyday.

Why would they advertise at times square when everyone in the world is already eye balling their website everyday?

Also marketing is only needed for things people dont really need or want. A good product sells itself by word of mouth.
From the article:

Since that change, I haven't heard word one about our terrible, onerous, awful default body and title character limit policies. Not one. Single. Complaint.

So, they didn't do what the customers said they wanted, but they did work on the issue until people quit complaining.

“If I had asked people what they wanted, they would have said faster horses.”

― Henry Ford

Plus, IIRC, for the Edsel, they did ask customers what they wanted. And it has gone down in history as one of the worst cars ever.
We work a lot of with independent/non-professional organizers since they need tools that are a) affordable and b) are simple/do not have a large learning curve. Their events include everything from conferences to food and wine tastings.

Event app wise, we have all the features you'd expect (event info, social integration, attendee profiles, etc). We also have some unique capabilities given that we handle ticketing/registration as well. Not to mention, it's completely free compared to $1000s.
Crunchbase Enhancer – Useful Chrome Extension