skysight-inc/HackerNews huggingface dataset:
I take a Kurzwielian view. There is probably a significant transition in the physical bodies of an intelligent lifeform past a certain point of evolution. and a dramatic increase in cognitive ability.

Fermi's Paradox makes more sense when you theorize that ET transforms its biology into a computational substrate prior to gaining the ability to travel between stars, as will likely happen with us. When it does this it turns into something we won't even recognize, something likely a million times smaller than us due to miniaturization, and a trillion times smarter. Even if they are around they probably don't have the patience to interact with us, dumb as we are and with minds that travel 10^5 or so slower.
Three things your start up is probably already doing, plus some pictures and stories that make Richard Bronson seem like some kind of visionary.
This is so aggravating. It makes some people drink more, but it makes people like me leave sooner and come to the bar less or never. It's very frustrating when places where people come to drink socially are hostile to spoken communication.
This, by the way, is a sentiment directly addressed and validated in the video I linked.

Gnome 3 is, on the other hand, a very good alternative for those that hated Gnome 2, which is the crowd I fall in.
There were changes needed on Blink side (Oilpan project) and this sort of things take time.

Oilpan project: https://docs.google.com/presentation/d/1YtfurcyKFS0hxPOnC3U6...

You can track Darts's performance here: https://www.dartlang.org/performance/
Looks much better, and the wiki editor is great too to make quick changes on mobile.
Does “Stay in school, work hard” produce mediocrity? Can it produce greatness?
https://www.dartlang.org/community/who-uses-dart.html
I think Blossom [1] switched to it. They had some articles on their blog about the switch [2].

[1] https://www.blossom.io/
[2] http://www.ramen.io/post/46936028144/we-are-switching-to-dar...
Due to rough seas the rocket stage sank before they were able to recover it.

http://www.bbc.com/news/science-environment-27166780
In my original comment I mentioned a setup with a two person team. You know exactly who is reviewing or not reviewing your code in this setup: the other person. The two of you cannot possibly produce so many feature branches that you don't remember your own code that has not yet been reviewed.

If the PR method works for your team, that's great. In my experience, it leads to more friction and the reasons to implement it are usually "best practices" articles like TFA, not actual needs of the team.
I've been in this exact same situation. And I was offered positions. I guess that's my point - I didn't always find the perfect solution. I was pressed to continue to think about the problem until whatever allotted time was up. I wasn't [entirely] judged based on my final solution; I was judged on my ability to reason about the problem and demonstrate competency in my coding abilities.
Actually looks really good.

But... why are you leaking my information to facebook, twitter, yandex.ru and google analytics?
Agreed. Bower also doesn't have any notion of version pegging or shrinkwrapping like npm... which is a total production killer.
From the blog post, that seems like a rather perilous approach.. what are the chances they get all the builtin Ruby stuff to work the same way despite basing it on Java equivalents?
Do you still have to provide all of your email addresses to your PO every month? That sucked, especially on a hand-written form.
I think the comparisons with other frameworks like JQuery or Angular are a little out of place. I don't really see Ext as a competitor in that area. It's not really a traditional JS framework, it's more a GUI library that just happens to use the browser as the backend and JS as the programming language.

I mostly saw it used for intranet applications, where not being forced to deploy stuff for each change is a big bonus. In these cases, you're not coming from knockout, backbone or react -- you're fleeing from the wrath of Java Webstart and Swing. And compared to those beasts, ExtJS is a welcome change.

Yes, all the bad things said in the post and this thread are certainly true, but that still makes ExtJS better than some of the alternatives in this peculiar shithole. And no other framework/library seems to move in that direction. Components, sure, but no full-fledged widgets that end up in providing a desktop-like experience. Most widget libraries I've seen were enhancements/additions to mostly conventional web pages (Cappuccino as a possible exception).

Sure, you don't want to provide a 80%-ish emulation of native GUIs on the real internet. But for the corporate stuff like CRMs, it's darn useful. Even ravishing the DOM is better than Swing.

(Did I mention that I don't like Swing?)
Q: What were your mistakes? A: Security.

I still can't wrap my head around how someone decides to do a startup around bitcoin and doesn't make security their first priority from the beginning.
You should flag a story if you think it's off-topic for HN, i.e. you think it shouldn't be here. Since useless PR stuff shouldn't be here, that's definitely a legit reason to flag a story.
We haven't raised anything. We're three broke college students who have been putting everything we have into keeping this thing going.

We're planning to expand to 150 campuses and bring on some people to man the phones/maintain our property listings, as well as hire campus reps/brand ambassadors at 20 key schools from that set of 150. Our 1y budget for all of this is <1M.

And yeah, we're based in LA, but we're all new to this and don't exactly have any connections with anyone in this industry, so we'll definitely start researching some groups and, I suppose, calling until someone wants to talk to us.

Thanks for the advice!
That's an interesting idea. Does it work well with non-js repositories?
Have a team meeting. Tell everyone what they did, how their efforts and contributions helped deliver the MVP, and give them a spot bonus. The spot bonus doesn't have to be large, I would say 100 to 500 dollars. The recognition and the bonus will boost their morale and make them happier employees.
I'll definitely reach out. It would be fun to jointly tackle a fun problem together.
Without reading and writing I think the whole 'Standing on the shoulders of giants' thing falls apart because you must be directly associated with the 'giant'. How do you transmit the ideas of an Einstein between generations of normals?
I would like to use it but Javascript Frameworks and libraries are being developed so rapidly that it gets difficult to choose Dart and plus it is yet to mature. I may be wrong.
>Editing code in production on a financial services platform? Wow.

Heh. This happens on good ol' USD platforms as well. You'd be surprised (horrified).
Elo ratings (such as those kept at eloratings.net) actually work quite well. Ultimately, they work like a weighted moving average.

The thing that I find hard to predict and build into my models is style of play. By style I mean: spatially-intensive, high-time-inpossession-the-ball-time (e.g. Spain with tiki-taka and Germany to some extent) versus time-intensive, opportunity-seeking/opportunity-creating (such as Brazil, Argentina, etc.)

Why? Because passing-intensive teams seem to display more of an own effect -- they fall or rise on the strength of their team, since it's an intricate, very technical and collaborative style. The results of opportunity-seeking teams are much more dependent on the strength of the adversary -- i.e. much more Elo-like.

Ideally, I'd be able to infer from the data a (exponentially biased to recent games) own-team/spatial play dependence factor as opposed to a strength-of-opponent/opportunity-seeking factor. In principle if all victories were explainable by a combination of those two variables the Elo residual/surprise would be a measure of this, but hey, teams get better/worse at opportunity-seeking too, even teams specialized in tiki-taka.
Homeaway/VRBO ranked higher than Airbnb for mobile experience
I disagree. The core write-your-code experience is full of jank, to the point where I have wondered in the past whether the XS folks develop it in XS. Its smart indentation isn't smart (randomly indenting another three levels, not being smart enough to stick to the indent level I pick when I backspace to where I want it--next line, back out there again!) and occasionally the text widget will "lose" a line of text and take a few seconds to remember that it actually exists.

The Xamarin toolchain has steadily improved and its PCL support makes a lot of things a lot easier, but I can't envision a use case where I would want to do my development in their IDE. I keep a Windows machine just to have VS so I can do the 90% case there and suffer through the 10% in XS.
You are offering three resolutions of the Fermi Paradox. All three of them are the form: some intelligent species will be unable/unwilling to communicate with us. This is incorrect. The resolution of the paradox have to be: ALL intelligent species are unable/unwilling to communicate with us.

You can try to take your probabilistic resolutions and multiply them all together to show a very low probability. But then you need an upper bound on the expected number of intelligent species. Which keeps increasing (number of Earth like planets).

(Mayans were not trying to communicate with anyone else. Those robots will be trying to. There is probably enough structure in physics and math to be the basis of communication with any alien species.)
So there are projects where I don't branch: ones where I am the only committer, and there are no features. For example, my puppet manifests for all the servers I manage. It either works, or I roll it back.

However, feature branches are just multi-stage commits. Sure you can invest hours of your life setting up CI, then writing code, not testing it locally before pushing it to master, getting an obscure error from the test/deploy process, fixing it again, pushing again, getting another error, etc. But you probably want to, you know, ship the product.

Having said that, if your workflow actually resulted in you writing better code faster and you ended up shipping earlier and making more money, I'd love to read about it.
And Churchill didn't even say the funniest line about it.
If you prefer Ruby that's cool, but I feel like I should mention that Xamarin is also statically compiled on Apple platforms: http://developer.xamarin.com/guides/ios/advanced_topics/limi...

In fact, every app in the Apple app store is statically compiled. App store guidelines prohibit dynamic code generation, preventing the use of a JIT compiler: http://stackoverflow.com/questions/21689993/xamarin-ahead-of...
There's a decent discussion here with a variety of perspectives:

http://english.stackexchange.com/questions/16/when-is-it-app...
8 1/2 ways the Internet of Things will change your life
Don't get me wrong, I like being in the office - I think there is more creativity and idea flow. Our team has 2 remote employees in DFW, but they are former employees and know the domain quite well.
I don't think that's meant as a justification for anything, just a statement of fact. Open source projects are heavily dependent on electronic communication (mailing lists, forums, etc.) for everything from feature planning to user feedback, but what all of those mediums have in common is that people are 100x more likely to post that they hate than that they like something. So, it really is true that no matter what you do or don't do, seemingly everyone on the Internet is going to hate it, when in fact that's just a very vocal minority.

Point being, even GNOME 3 (or Unity...) levels of vocal online user hate don't necessarily mean that a meaningful percentage of the user base actually dislikes the changes. Feedback should always be read and reflected on, just not followed slavishly. If you just try to avoid Internet hate from users, you'll never change anything, and even that philosophy will garner you a continuous stream of heated forum posts about how nothing ever changes.

It's kind of like reading Yelp reviews. In the aggregate, they help some places stand out from the crowd, but they're still not any sort of objective judgement on the place being reviewed. You always have to think about where the reviewer is coming from and take that into account. For example, dumbasses who go to some incredibly popular and trendy restaraunt at 7:30pm on Friday without reservations, and then post negative reviews because they had to wait too long for a table. Well, duh. In the software world, the equivalent would be complaints about a piece of software not being just like X (where X could be a previous version, or some competitor), when in fact your entire goal is to create something unlike X. If someone wants X and you're making Y, then have to take "Y sucks because it's not X!" complaints with a massive grain of salt. It still doesn't mean you ignore those complaints (maybe Y was a bad idea?), but you wouldn't be doing anyone any favors by doing the most common Open Source thing, which would be to either say, "oh well, I guess we'll stop making Y and just make another X instead", or (even worse, and sadly even more common), "I know, we'll make everyone happy by making something that's both an X and a Y! We can just put a checkbox in the settings!"
Remind me, which university did Bill Gates graduate from, again? ;-)
Being honest, there will be very little learning curve going from VS to Xamarin Studio. They tried to make that switch as painless as possible.

You are right, there is a factor of learning that needs to be baked into your consideration but there comes a point where you put a little trust in people who came before you and tell you 'I have done this, I have been where you are - follow me and you will be fine'.

On the flip side, Nat Friedman is incredibly approachable. I am sure if you simply email him and tell him your concerns he will accommodate you with a longer trial period or some kind of money back guarantee, that just how he is.
Or this: http://imgur.com/JdfnF7a
Another related site that attempts to do a similar thing: http://kare.progger.io
If I were to summarize Django: it's a godsend for new comers (the whole package is fabulous & comprehensive with excellent documentation). It'll get you to your destination fast & in style. But very soon, as you start getting a hang of it, you'll realize that it's rigidity is wearing you out. I wish there's a django-light fork that takes all the good things in it and mashes it with jinja2 & SQLAlchemy.

Please make it a lot more modular. Maybe a kickstarter (like South did & Postgres improvement is doing)

P.S. I know there's flask, but it's still a while before it reaches that point for some of us.
With a sufficient basic income, zero is a living wage, and forcing a higher needlessly prevents some instances of cooperation. As far as I am concerned, it remains an open question whether the ideal level of basic income, all things factored in, is "sufficient" to that end (and, for that matter, what that ideal level of basic income is).
Or an alternative explanation - our space capabilities have risen constantly since 1957 and the Appolo missions were a Nixon administration PR hoax.
That sort of environment is depressingly common outside of the major tech hubs. My current employer just celebrated its millionth line of code on a glorified CRUD+reports application. I have been reprimanded for suggesting better development practices. Obviously, I am trying to find a better job that still pays reasonably well for a 40-hour work week.
This may very well be, but there's not much you can do about it at that point but continue to try to fix the problem. If you can't be amicable about it with the interviewer, then either they don't want to work you or you don't want to work with them (probably both). Might as well make the best of it.
The Latinate syntactical construction norms that moved over to English included, among many others, one around prepositions (from the Latin prae, meaning before) being placed before the object with which it is linked, never after.

It certainly isn't a rule, per se; and ending a sentence with a preposition is not wrong. But it is stylistically less desirable.

Dryden hated that Ben Jonson occasionally ended sentences with prepositions. He gave the norm added power and it has lasted, since his 1672 criticism, another 250 years. Dryden never said that ending a sentence with a preposition was wrong, only that it was ugly.

(Incidentally, Winston Churchill never said that this was a grammar rule "up with which I will not put." See: http://itre.cis.upenn.edu/~myl/languagelog/archives/001715.h...)
Has this version been submitted to ECMA?
Unless your environment demands it, it doesn't matter. In fact, it can be a bit of a pain in the ass to implement on your own, if you are not using Heroku or some such. The main point there is to not put secrets into your git repo. How you accomplish that for the most part doesn't matter.
Sorry, but your line of thinking takes for granted that criminality doesn't pay. On the contrary. Having a hidden fortune is more valuable than having a pubilc fortune, objectively in that you pay less taxes and forego frivilous lawsuits and subjectively in that you can walk around less paranoid of kidnappings. Second of all, there's no way to stop Karpeles from mixing his coins. People who don't have much experience using Bitcoin are often operating in the PayPal model, where it takes a trusted third party to spend your money and even if not, the other person is known. In the Bitcoin space, there is no trusted third party, and if your coins are mixed and you and the other person are behind Tor, there's effectively no identifiable information involved in the transaction.

Embezzling Bitcoins is the perfect crime. As has been mentioned already, Karpeles has a history of computer fraud, so embezzling digital money would be right up his alley. He had the means, motive and opportunity to do so. When you consider the rampant embezzlement in a historical context ... it's pretty much case closed. Your argument boils down to "this time it's different". Also, laughing stock digital billionaire? Sorry but there's no such thing as a laughing stock billionaire. I'd take a billion knowing it would make me the "laughing stock" of the world, and so would anyone with a brain.

If the community hadn't called Karpeles out on using transaction malleability as a fictional excuse for losing 850,000 BTC, and we had all believed Karpeles, he would in all likelihood be looking at Japanese bankruptcy court followed by a lifetime of traveling the world with a hidden fortune rivaling Satoshi's.
Why do you want it to be supported in Chrome? Any performance improvements seen by your users won't apply to those using any other browser.
We made a donation to watsi today too, as part of our in-house flossing contest. A dry-erase marker and a bathroom mirror keeps the tally, and about once a month, someone wins. When the tally gets reset, the total number of flosses is donated, in dollar form, to a charity.

You win, because $1/floss is worth it in aggregate to prevent future dental bills. Someone else wins, because they get the treatment they need to live a better life.
Sure, I stretched that too far. But hopefully the point is made. Then should we expect no students (or anyone) to be able to build a compiler (or os kernel) in any amount of time given the internet and whatnot? While I may be articulating this poorly, I think my fundamental issue with his point is solid.
an ex of mine had a prescription for that stuff. Super intense.
It's a federal felony. There's only one way to expunge that, a Presidential pardon. It's a long process and kind of a long shot. I haven't even applied for mine.

He should definitely apply for his rights restoration when eligible. I got mine done. Florida isn't currently restoring firearm ownership rights but that's good to get done if they ever start doing it again.
I wonder how much empathy was involved in writing the AARD code. (http://en.wikipedia.org/wiki/AARD_code)
I agree re: it not being the agent's fault if the buyer insists. But I've seen all too many cases where it's the agent doing the 'gentle push' to higher prices. "Well don't forget this will give you a tax break over renting, and that will add up to a couple hundred a month..." Etc, etc.

I'm shopping for a house again now, and even now I've had to tell my agent that the top end of what I provided as a limit is actually a limit, and I want to see properties under it as well.
"If I stay out late with a girl, it's almost automatic that I will escort her home regardless of the inconvenience to me."

That works for those holding on to even the lowermost rungs of the middle class. Below that the condition of women, oppressed by caste and class(not direct but still a strong co-relation), their plight is hellish to even think of.
> Interesting is fairly subjective

Interesting is a social construction. As such, I would define interesting as worthy of publication in a first or second-tier conference at some point in the history of the field.

> If you cannot demonstrate ability to solve a simple, well trodden problem how will you be able to solve a new one?

0. I've seen many well-respected researchers who have solved truly interesting, new-to-humanity problems stumble on well-known problems others consider easy and/or fundamental. In fact, this is probably true for every single researcher. And doubly so for practitioners. One person's fundamental technique is another's blind spot.

1. Simple != easy to come up with. Often exactly the opposite! Take the TH algorithm as an example. It's a very simple algorithm. Small. Simple. Optimal. Awesome. Not trivial to discover, however.

2. Well-trodden -> unless the algorithm is absolutely fundamental and taught everywhere (e.g. sorting), you've given up on testing problem solving skills. You're just testing whether the person's intro/DS/algo professor covered this particular algorithm (and maybe their memory). Or, more likely, rather their random interview studying happened to hit your pet problem. Since curriculum is not anywhere close to uniform in CS -- even among top schools -- this is just silly.

3. Simple problems don't always have (simple) solutions. Create a fair voting scheme.
Why do you want to raise money (i.e. sell part of the company)? It sounds like you can grow organically, maybe raising your prices is in order?
I was able to spend 5 minutes on this site and get more valuable information than I would have gotten if I'd spent an hour watching the news or two hours searching and curating information for myself.
Ok, that was poorly worded. What I mean is that a linked list can be thought of as a restrictive graph. I'm just saying I'd prefer to think of it as a graph. I could still be wrong. Is that kosher?
What do you plan to do to "take this thing to the next level", and how much money do you need to make it work? The scale will determine what route you go; needing $10k is very different from needing $10M.
"runner up: Not using Tor, an overseas VPN, or an SSH tunnel when I knew how" wasn't a particularly great thing to say here.
Contact me, I can help - http://about.me/dmitry
The documentation is like a book. Start with the tutorial: https://docs.djangoproject.com/en/1.6/