skysight-inc/HackerNews huggingface dataset:
In my personal experience a solid work history is much better than a degree. Once you have it the value of a degree decreases significantly. Its almost entirely redundant. The only problem is you often need the degree to get the work history.

I've also noticed as I start working with people who have their Masters and some with PHDs that people take me seriously. It's like... I must know what I'm talking about. How else would I still be here?
Internet access?

At Google HQ?

Being an employee?

...no clue :(
What is CI and why do people want it? I looked up the acronym on wikipedia but couldn't figure it out.
What questions are you trying to answer about your web-app?

While I think reports like individual user streams are neat, I find they're not very good at diagnosing a product and driving growth.

One of the best charts for doing that is a simple cohort analysis / retention chart. If you've been storing historical data about your users in your database or in a log file, one thing you could try is importing historical data into Amplitude and then looking at your retention chart. I just finished doing this for a friend in Mixpanel earlier today. Here's the result:
http://aacook.co/retention.png

This chart only uses two user events (Sign Up and some usage event you define) but tells you so much. Week/week acquisition (number of new users signing up) is in the first column, new user activation in the 2nd column (number of new sign ups who reached a moment of value) and a basic form of retention (number of users coming back at week N).

In my friend's startup, they're doing a great job with new user acquisition but they have a clear onboarding/activation problem. Less than half of new sign ups reach the authentic usage state. In the following week, another 50% of those users drop off.
we use gitlab, it makes doing pre code review easy. when your code is ready, send a merge request, someone else has to review it to merge it.

most of the time it doesn't catch anything, but every now and then it does, so that's cool.

it also means we can revert features easily most of the time, should the need arise.

all in all, gitlab is really good and you should check it out
git hubs worst problem: FIXED WIDTH CODE READING

code is read way more often than written. and on github website all you can do is read it. why the viewports don't take up the entire screen width i will never understand.
www.facebook.com/thiet.bao.75
In the wings, yes, but this particular part is a control surface on the trailing edge of the wing. It definitely wouldn't be carrying fuel.
I really like this. It reminds me of Mr. Money Mustache's "50 Jobs over $50,000 - Without a Degree":

[Part 1] http://www.mrmoneymustache.com/2013/07/25/50-jobs-over-50000...

[Part 2] http://www.mrmoneymustache.com/2013/08/05/50-jobs-over-50000...

Quick question: How did you get pagination working? I haven't built anything big in Meteor, but I did go through the Discover Meteor book, and it said that Meteor doesn't lend itself well to pagination, so that you should use infinite scrolling. Does pagination break if the database is updated, or is it not reactive, or am I missing something?
Do you have a link for 'bing'? I found the yandex in the translations only (yet)
That's a pretty selfish attitude, no? You get a lot, or at least some, value out of the HN community, and yet you do not contribute to it in the way that really matters. Sure, commenting on articles is important, but it's also important to at least some times donate your time and sift through the garbage on the "new" page and up vote the jams. How else do you think quality articles end up on the front page for you to read? Magical pixies?

With the system outlined in my original post everyone could very easily contribute to HNs ranking system without spending too much time on it. Worst case, you have to look at 3 crappy article titles, that's not that bad.
I don't understand what the author is trying to prove here; the need to progress is never-ending. Holding it back is futile.
You could always use CloudFlare directly for that... I would presume that their underlying connection to Github is very close and reliable in terms of risk for MITM.
A lot of people at my company did this:

1) send out code review
2) commit the change and say "I will address the comments in the future."

A follow up never ever happens.
It could have been placed there close to a year ago, but it just took this long to find it. :P
There are plenty of places that do code reviews post-commit, but these places pretty much always just have their CI push to a staging server and not prod.
I honestly prefer to do both. Picking the right tool for the job implies that you've thought a great deal about your requirements.

Plus thinking is an enjoyable and rewarding experience.
That's exactly what the NSA would say to get us to use a new, backdoored hash function! /s
My understanding is that the pilot in the left chair didn't realize that the pilot in the right chair kept pulling his stick back. In boeing planes, the sticks move together, so that wouldn't be possible. And the pilot in the right chair clearly didn't understand that in the alternate law the fly by wire system was running in, his stick movements put the plane at risk.
> But my experience--and I've written plenty of Go, though I find it unpleasant to write and think about for all the usual reasons that Go partisans roll their eyes and so would rather deal with it as artifacts rather than actually writing it--has led to watching lots of developers make mudball codebases in the process (while blogging very heavily about how great it is three weeks in, and less a year-plus in).

I get what you're saying, and I agree with some of the criticism around the tooling, although I do think much of that owes to the age of the language. There are some specific things in the (sometimes rather cranky) replies to you that I think are incorrect but I'm not going to debate the merits of the language. Use it if you like, don't use it if you don't.

I will say that we've been using Go for nearly all back end services for nearly 3 years now, and we all still think it's pretty great. Our code base has also remained pretty clean, and in fact we're investing more heavily in Go going forward.
This matches the 401k match that Google has had for some time now.

I would love to see this become a standard benefit in the tech industry. Given that many tech workers are young, and young tech workers usually have high salaries for their age (relative to other professions), 401k money is very, very valuable.
Well we could go into the whole 'swiss cheese' theory of accidents, and include a long list of causes. https://en.wikipedia.org/wiki/Swiss_cheese_model
Great interface! Very clean and I like the career path aspect to it.
I dunno, I slept in my office in grad school. It wasn't out of needing to feel like a hard worker or showing off or whatever, it was more that sometimes I just felt like working until I was about to fall asleep, and then I was too tired to head home.
7tps only with transactions that have a single input and a single output.

In practice transactions have multiple inputs and multiple outputs. Based on average size of recent transactions it comes out to ~2.3tps.
Also, as someone who has dealt with visa issues before, it's far, far easier to move around the world if you have a university education. Maybe right now you don't think you'll want to, but it's a tremendous opportunity to have.
It might be interesting to be able to follow other users (who you know will tend to like the kinds of stories you want to see) and you can share saved stories or something. Or have related content or per-account filters that change the frontpage.

If, as it seems, there's no objective standard for quality (since it can't be measured or defined) then maybe subjective filters are the way to go.
The article shortchanged Haxe a little by omitting mention of its vast, varied, and flexible runtime library.
The scroll lag is primarily caused by the top navigation bar's fade-on-scroll effect and the large background image. Remove both of those and the scroll lag disappears.
I don't know if the programming model of threads and channels that's used by haskell and golang strictly depends on the existence of M:N threading, but it sure is nicer to use than the model in java/rust.
The book is a fairly evenhanded account of where the controversies are, what positions are held, and what the major points of evidence are.
Continuous Integration. A good example of that service would be something like http://travis-ci.org or https://jenkins-ci.org. Basically it's a service that runs some predefined task (usually your test suites) at important points: when something is pushed to or merged into master, when a Pull Request is opened, etc...
How to link your domain email address to Gmail for FREE
Continuous Integration (testing)
Oh yeah, it annoys me to no end to be at a party, have people tell me "you have too much time on your hands" when they ask about and receive what I've been doing, then get scoffed at for not being a "true geek" for not having read this book or watched that movie. Or worse, having watched them recently, as an adult, rather than as a teenager when they did, so I don't appreciate it the same way they do through their nostalgia.
Yeah, I agree maybe for one night, but repeatedly?
The worst impacts of climate change are starting to happen faster than expected
Your closest partners
Which institutional investor should I specifically be concerned about?

Show me the institutional investor that owns 30% of American, 30% of Delta, 30% of Southwest, and 30% of United. [1] If this is the case, then yes we have a problem. The manager of this fund has a major incentive to have these 4 major firms collude and price gouge its customers, as competition among the firms would minimize profit for the index fund. It would major shares of the companies that own the entire market. I think it's safe to say that this institutional investor doesn't exist.

Which concentrated group of 3-4 (oligarchy) institutional investors own a combined 50% of American, 50% of Delta, 50% of Southwest, and 50% of United?

If this is the case, then yes, we have a problem. Collusion will occur between these funds, who will agree to use their voting/management rights to collude at the airline level, as they own the companies that own the market.

We're usually used to seeing collusion between the CEO's and boards of major companies in concentrated markets because we tend to think of these people as the people who profit the most from price gouging. Antitrust lawsuits against AT&T, Kodak, Standard Oil - these are all pretty concrete examples of collusion from brands that we (used to) interface with. [2]

Now we could be seeing collusion abstracted one layer - the owners/shareholders are institutional investors who don't have a well-known brand. Which institutional investors specifically should we be worried about? Unlike AT&T + Verizon, I don't interface directly with any of them, so I'm not sure which firms I should be concerned about.

Where's the data?

[1] 30% is an arbitrarily large number.

[2] http://www.hg.org/article.asp?id=6025
It's very nice looking.

Everyone criticizing the implementation, here, let me help you:

https://github.com/daveliepmann/tufte-css
For the "voting on issues" feature I'd really just love to see them clone Slack's recent "Emoji Reactions" feature.
How to programmatically auto-trigg Polaroid Cube
Yes, or with programs that I could use on the command line, like ImageMagick's convert.
From 2013:

"Already, the average size of a rooftop solar system around the country is 3kW – and many of the new systems are well above that. According to Johnston’s data, 5kW systems are now the most popular in the progressive “solar” states such as Queensland and South Australia – while 3kW remains the most popular in NSW and W.A. That is probably a reflection of the tariffs paid for exports to the grid.

Of course, Australia still has some way to go to catch up with the US – where according to SunPower, which specializes in solar leasing products, the average size of rooftop solar systems has gone to 8.3kW.

That’s got something to do with the size of the roofs, and also the tariff measures. Most places in the US get a 1:1 tariff, so the incentive is there to put on a larger system."

http://cleantechnica.com/2013/05/28/graph-of-the-day-super-s...
Becoming Evergreen
Hi jsjigg - I'm not sure why that is. Please try again and we'll be sure to get back to you.
Why Blockchain is attracting some of the youngest and brightest
Of all the things I wish Github had, a mailing list service would be really amazing, and the kind of thing that wouldn't be done in the first few months. Sourceforge offers atrocious mailman-based email, larger foss projects on github suffer :(
Thanks! It was supposed to link to https://www.particle.io/

(how embarrassing)
This. The amount of time I have wasted looking in forks is staggering.
Do you really think that this type of a tutorial is needed here?
I'd also venture to guess that it isn't true.
I really wish there were some way to run code searches against branches/commits that aren't HEAD. If there is, it's not obvious.
Note that the plane was tracked on military radar flying west from the South China Sea, across the Malay Peninsula, and over the Andaman Sea before it flew out of range. Despite this fact, the Malaysians allowed search and rescue efforts to remain focused on entirely the wrong ocean for two days before they finally told anybody that they might be looking in the wrong spot, and it was four days before they actually revealed that they had a full hour of additional radar data that showed the plane had definitely not ended up anywhere near its intended flight path.

Of course, even then the search was subsequently done in the Andaman Sea area under the assumption that the plane crashed near the position of its last radar contact, as the Inmarsat data wasn't announced until several days later.
Really interesting to compare this with another (current) front page article, https://news.ycombinator.com/item?id=10012312

As someone who is employed by a company of <10 and had to take 1 of 2 weeks vacation for the my kid's birth, I wish I had this kind of benefit, but then if I did, I'd have to deal with all of the negative parts of working for a big company. It's a trade-off, and here in the hinterlands where there isn't VC funding to be had for every app idea or billions behind the company already, we end up with what we can. I'm happier in my small company 8-5 with almost no extra time than I would be working for a big company 7-7 with regular demands for time put in outside of the office.
Some people are interested in their work, especially at Google. I do things every night until I fall asleep, though not usually work.
That's actually where I want to take this, I'm thinking a wind speed sensor to recognize if it's on/off and a temperature sensor to turn it on/off automatically.
From experience testing Domo, RJ Metrics and Looker (which we ultimately went with), I know the ETL and modeling piece of integration can be extensive.

I'm curious to what degree you plan on assisting customers with that. While we have a team dedicated to working on this stuff now, initially one plus that RJ Metrics had going for them in my mind was that they had unlimited support that explicitly handled the modeling once we handled the ETL, and had dedicated analysts on our account.

Now, the obvious tradeoff there is that they don't know our data as well as we do, and all data has nuances. But for a fledgling company that can't dedicate manpower to analytics because they need to ship the product, that is a big game changer.

Ultimately we went with Looker for several other reasons, but that is an interesting factor to consider with your approach to sales/marketing.
> He joined Twitter in 2010 and held various roles during his five years with the company in business development, corporate strategy, platform operations, and corporate development. Prior to Twitter, he was at The Carlyle Group, where he focused on technology and education investments.

I never heard of Simon Lu before, but from the given description of his background, he seems like a typical corporate MBA, rather than someone who has experience founding a company and growing it, which, along various things YC has done in the couple of previous years, makes me think that YC is slowly moving towards becoming a typical VC.
Previous coverage: https://news.ycombinator.com/item?id=9622325
It doesn't strictly depend on it, but it is strongly supported by M:N threading since that threading model decouples the supportable degree of concurrency from the supportable degree of parallelism (unlike 1:1), without abandoning parallelism (unlike N:1).

You can do Erlang-style concurrency with 1:1 or N:1 threading models (and there are libraries for languages whose many implementations are N:1 or 1:1 rather than M:N that do that), but it makes most sense when you have M:N.
The problem is that most Americans are shocked by this. Almost all of Europe has 6-12 months? Canada has 12? So we act like it's crazy generous thing to have so much paternity leave. Good for MS & netflix. The sooner we have a wave of big tech following the trend the better.

I (working in the US) have a handful of friends that work in Germany and UK. The only "bad" thing about US employment is vacation and parental leave. As a male I don't see a need for 12 months but the fact that my wife get shit here (8 weeks of "sick leave" for having a child) is enough to constantly keep my ears open for opportunities in other countries.

We need to stop being surprised and should be saying "about time".
I am enjoying Ex Catmull's book "Creativity Inc" about his time founding and running Pixar and his struggles to build a creative company that keeps being creative.

The parallels to software engineering are many and obvious, and I encourgE you to read it (candour, search for quality etc).

But the big one that struck me and I am looking for a way to try it is in "the brain trust". A group of 20 or so directors and producers gather every three months to watch the latest version of a film (I guess they all meet more than three months as they make more than one film at a time but whatever). The goal is to give feedback on what does and does not work as story arcs and emotional content and so forth. Not to fix it, but to raise the issues, and not to proscribe solutions but to point out blind spots.

Daily code reviews are great, but stepping back every few months with comfortable peers and just looking around a system is something that I would love - it seems to only happen after six or more months when things are starting to break.
Marketing by the looks of it. I have to say I like what Gitlab is doing these days much more than GitHub.
Reading Rainbow is Back
Let's go a step further: if we're worried about data persistence, should the table also be append-only? Soft deletes won't protect against a user manually wiping every field in their account.
It’s unsustainable growth, though.

Facebook is even today far overvalued. Their price has to crash at some point.

And even Google is stagnating.
Apple Music from a Radio Personality's Point of View
Yes, it was a completely incorrect reaction by a single pilot, combined with a catastrophically bad design for the controls, which caused that crash. It is completely insane to me that anyone would think that averaging inputs from two pilots and providing no feedback would be even remotely a good idea.
How to Think Creatively and Extract Hidden Value from the Data Around You
It stands for continuous integration.
Yeah, that's a puzzling one. I've been using a browser script for a long time now to make the code view full width.
Can I just say that I for one am incredibly glad you made this program, regardless of whether the GIMP plugin exists?

Thanks so much@
I am using Flow Router https://github.com/kadirahq/flow-router to route the app. And this is the package I'm using for pagination https://atmospherejs.com/miguelalarcos/flow-router-paginatio.... So far it hasn't let me down (there are a few bugs with the subscriptions on each individual page) but if you play around with the work style filter you'll see the collection reactivity and how it's reflected on the subscription and pagination. Thanks for your feedback!
Waiting for Meteor to support pagination natively.
I'm actually hoping they bring something into GH for business/enterprise that is better, or as good as TFS or JIRA... I like TFS, but non-VS projects are a pain... and JIRA is just well, not pleasant at all.

Once they have some sort of better issue tracking system, then migration tooling will become another big issue in that space.. getting from SVN+JIRA or TFS itself would be really useful to a lot of orgs, willing to pay. Something between TFS and Axosoft's OnTime would be pretty nice as an addition to GH.

Another area with a lot of potential would be a CI/CD toolset that uses your own cloud.. EX: you use api keys for Azure, GCE, AWS, DO etc, and then you can setup testing/limits and Github could just manage the provisioning of the test servers, and ease setup/deployment of test/stage/prod classes of servers for multiple languages.

GH wouldn't have to manage a huge infrastructure itself, just build/sell tooling that extends it's current product line.
You start by congratulating yourself for refusing to buy into the Java hype, then continue on with business as usual in C++ or some other non-garbage-collected language.
Start-ups are study in crisis management. If you watch too many motivational videos on youtube you are spending a ton of time that might be better used elsewhere. Success is a really good motivator and reflexively watching motivation videos / reading self help books / insert placebo here may work - for a while - but it can just as easily become a reason for failure by itself if done to excess. It's understandable but be careful with that.

Best of luck!
Inability to scale easily to clusters, unless the problem is embarrassingly parallel (ours isn't always), and no equivalent to the conceptual beauty and efficiency of distributed directed acyclic graphs that Storm amongst others uses. We could hack Python up to do this, but if the problem became TRULY huge, hundreds or thousands of nodes, we'd probably end up spending more time building a processing infrastructure, and repaying technical debt, than doing the actual algorithms, while Spark / Storm etc already have massive scaling ability built in. Still love Python and especially the Numpy ecosystem though and we stream thousands of ticks per second through it no problem, with a bit of help from multiprocessing, MKL libs and Numbapro. But as we get towards tens of thousands we're hitting the buffers, and most importanly, problem complexity is rising so the DAG approach is looking very attractive.
If you're interested in learning, ask more questions. This thread started off with some dubious statements, and when that was pointed out, you dug in deeper and deeper. That doesn't inspire much confidence that you will appreciate someone taking the time to educate you. Hence, the terseness.
"Small Reviews > Large Reviews"

This depends on what you are looking for. For style and "obvious" bugs? Agreed.

For finding bugs? Couldn't be more wrong. Functionality based reviews pick up far more defects, if done properly, than reviews of change sets. And it's because you pull back and think about the entire context of the feature.

Of course they also require a much more significant time investment and need to be run differently than a standard code review, but they are also much more valuable.
To be frank, it is pretty much ok for the +1 to be annoying: it's often what they are meant to. Thus, if a vote button were to be implemented, it would not be used all the time.
> We need to stop being surprised and should be saying "about time".

Hear hear.