skysight-inc/HackerNews huggingface dataset:
I think most people only live a couple of years after they're diagnosed. It's a pretty "effective" disease. There's no cure coming in the next week and he knows it.

Speaking of emotionally stunted programmers, I wish we could figure out how to cure that. HN seems to draw them all in, and they just add a lot of noise. You've only been here a week and you've got a -9 karma. Ever think that it might be you?

Wouldn't it be more interesting to take deeper dives into understanding these issues?
What would an alternative be for you?
You can't just freely reinterpret memory in C without following certain rules, or you get undefined behavior. Also, types have sizes, and alignment restrictions, and on some systems, trap representations.
I'll take the plan that is cheaper, and run a VPN to a VPS somewhere. Good luck intruding on my web browsing.
Even 2100 CAD ($1670 USD) is about half of San Francisco 1 bedroom rent. His post is still correct in terms of ratios.
http://sf.curbed.com/archives/2015/03/03/mapping_the_median_...
The confused terminology isn't related to function calls. In Java, objects are not values.

The confused terminology originates before you get to function calls -- you can't ask "are objects passed by value?" without first considering objects as values. Objects can't be stored in variables and objects cannot be the result of an expression. x = y does not copy an object y into an object x because objects are not values -- x and y are variables and they can only hold values, which objects are not.
It's not really fair to have this discussion on Shabbos/Sabbath when the people who really know are unplugged from the internet.
we had votes in every single neighborhood of the city. Our correlation was better with progressive parties (ARI) than conservative (PRO) ones even. Actually in Congress, The Workers Party (PO) brought more users to DemocracyOS than ANY other party.
As seanwilson has pointed out already, academic papers are written to be intelligible to experts in the field. They're not meant to be tutorials for practitioners. So you can easily get stuck if you're reading a paper in a field in which you're not an expert.

I also see a lot of useful tips here such as making notes, rewriting parts of the paper, and so forth. I think these ideas only work when you're already getting something out of the paper. These tips are optimizers, they can help you get more out of a paper if you're already somewhat conversant in the field.

In theory, if you're not an expert, you can keep following the citation trail, read all the papers there, become an expert and finally read the paper you actually want to read. I don't think this actually works. If you're not a expert, the paper itself will seem like gibberish. You won't know what citations are actually important and what citations were just pushed in to please a reviewer. And even if you somehow do, the citations themselves will be just as difficult to read.

So what are the solutions? First, seek out accessible papers. There are a lot of tutorials that get published in magazines like the CACM and IEEE Spectrum. These are written with an explicit goal of being accessible to a technical non-expert audience, so you will get something out of these articles. Maybe if you read one such article, you'll get the big ideas in the article and then you can read the technical paper(s) that the article was based on. Since you already know the big ideas, the technical paper won't seem so daunting. And maybe now, you can follow up on a few citations.

The general trick is to find alternate sources that simplify and explain the paper and then read the paper. Alternate sources can be tutorial articles, slides, blog posts, textbooks, talks and so on. This is actually how people learn to read papers in grad school. First, you go to few a masters level classes where the professors teach from papers rather than textbooks but don't necessarily expect students to read and understand all the details in the paper. Next you go to a few seminar-type classes where professors and students discuss the nuances of a number of important papers. There's a lot of non-obvious spoonfeeding that happens: the professors use their expertise to pick papers that important and accessible, they guide the discussion towards the important parts of the papers, they point out flaws and discuss methodologies, suggest projects for the students to implement and learn from, and so on. Over time, the students absorb these lessons by osmosis and become good at picking out and reading papers themselves.

If you're not going to grad school yourself, you'll have to recreate this process of slowly building expertise in a field by reading papers and comprehending them and trying to implement and recreate them. The key word is slowly because you're not going to become an expert in a day, or even a month. You'll have to keep going for a year or two and slowly you'll feel like a blind man who can see more and more of his surroundings everyday.
10% of total number of full interviews that needed to be conducted. At most publicly listed companies, firing can't be done without accumulation of enough evidence (what HR usually refers to as "paper trail"). This is true even when employment was "at will" mainly because of legal liability (for example, fired employee can claim that he was a victim of XYZ) and bad PR it can generate. I think Facebook is (or was) probably rare exception in aggressive firing and not sure how they managed it. Most companies also require annual review to be in place before firing occurs. Typically hiring manager would avoid firing within first year because that usually looks very bad on them. Most true negatives don't get fired until hiring manager changes or years pass by. At startups things are obviously different. Resources are scarce and true negative probably won't survive beyond 6 month or in worse case beyond a year. But still that's a significant period to cause enough of hemorrhaging for a true negative.
> i really need a word for when my friends do something stupid

How about two words? I think the current in-phrase is "special needs".
Adobe Photoshop CS 11 Crack Keygen Plus Serial Number Download
Well... that's certainly one approach. Hire people because you like them. Though it probably isn't the best approach for getting results.
I applaud your effort to apply some styling to the manual, but this is, frankly, ridiculous.

To whit:

# Debian Jessie
$ du -hs /usr/share/doc/glibc-doc-reference/html/
9.0M /usr/share/doc/glibc-doc-reference/html/
$ cat /usr/share/doc/glibc-doc-reference/html/* > all.html
$ wget https://www.gnu.org/software/libc/manual/html_mono/libc.html
$ gzip -9 -k *.html
$ du -hs *
7.5M all.html # Local html
1.1M all.html.gz # -"- gzip'ed
4.9M libc.html # single-file version, from wget above
900K libc.html.gz # -"- gzip'ed

So, under a mb of data, for the whole thing -- and that's not even working with the various sections. It might have made sense on dial-up, but not really for mobile clients. The fact that you've completely broken the whole thing (eg: no mirroring with wget) doesn't make up for the savings. Also, if you'd kept the/a single html-file -- that file would've been cached, so doing some js-magic with hide/show should be instant, after the thing is downloaded. That's the old Dreamweaver way of pre-loading content (set sections/div/whatever as display:none, and toggle on mouseover link/clicks etc).

So this is not degrading css, this is just broken html for no good reason. If you want to load "partials", keep the traditional structure, and do your magic "upgrading" in js -- load the content asynchronously into a div or what-not -- and leave the links working for browsers without javascript/wget/etc.

All that said, the work you've done with the CSS is very nice. I'd probably add a media-query to collapse the sidebar -- it takes up quite a lot of space on mobile (especially in portrait mode). I'm also no fan of typekit -- if possible I'd prefer to use locally hosted (freely licensed, of course!) fonts.

As for search, maybe have a look at http://lunrjs.com/ .

And just as a reminder, on the off-chance that there might be some readers that are unaware: CSS Zen garden is still a good example of how html and css can go together in creative and gracefully degrading manner: http://www.mezzoblue.com/zengarden/

A final note on links/urls. With eg. vimperator, "gu" (go up) works for going from example.com/some/where to example.com/some/ -- so while most browsers have gotten rid of "forward" and "up" navigation arrows, they still do work.
This is a really tiresome issue for me. Lots of xenophobia and misinformation. As much as I hate an absentee owner tax maybe it would shut up the racists. I fear the issue isn't the high property prices.
Because nobody buys more than one phone ever. Those two numbers have no impact on each other.
A SafeJSONP Method by Egor Homakov
See also: w3m.
Those are very different skills. When I was a stock analyst, well before Reg FD, it was about getting information other people didn't. Same is true now that I'm a self-employed industry analyst. It's about relationships, and having the relationships be productive in specific ways.

Self-promotion generally takes some cleverness. It shares aspects with my previous example -- you use people who like you in ways that are productive, that don't harm them (or, much better, explicitly help them), and don't cause them to stop liking you. This requires understanding of other people's needs and motivations.

I did some clever negotiating things back in the day -- getting a game theory PhD in 1979 pretty much guaranteed that I was a negotiation "expert" in the 1980s, although subsequently general understanding of game theory and negotiation advanced and obviated such an advantage.

The first time a company threatened me with a scary libel suit I got their arch-competitor to, the same day, offer to pay my legal fees. That may have been my flashiest hack of all. :)
I'll second your first point about hard copies. It's one thing to skim a PDF on the screen to see if it might be worth my time, but if I really want to grok a paper I'm marking up a hardcopy.

This has also made me appreciative of authors who put in the effort to make sure that their graphs and diagrams reduce well to grayscale. Instead of referring to the red line versus the green line, they'll use labels, marks, different cross hatch types, etc. (Don't get me wrong, good color is still very nice to have too!) It's also led me to making it a point to print off drafts of my own submissions on a B&W laser printer and make sure that my figures and captions are still understandable. I expect that this makes it easier for any colorblind readers as well, whatever type of colorblindness they may have.
Im still waiting for proof on this claims. Regardless, the blockchain is still a protocol lacking good applications and products. But its fundamentals described in Satoshis papers + the traction it got, speak for themselves. It's a technology with growth. Show me another one like it, and I'll be glad to study it.
A classic source of Reformation-era putdowns!
That Calvin and Hobbes comic really hit me hard.
"It works just like Python"
That's where you get an impartial third party involved.

They can tell if you are indeed outside the standard deviation for the population, and help you identify if and how to get back up to par.
This is the most misinformed comments thread I've ever seen on Hacker News.
I still don't understand why they don't want the rent money on those properties.
The web is great in theory but is somewhat broken in practice. What I'd like to see:

* The web as a first class citizen on mobile. Apple have a lot to answer for here. For example Safari went years without having a position: fixed implementation and with an artificial 300ms delay on every tap event. That's crazy. They're either malicious or don't care. Neither is good for the web.

* Faster progress shipping new technology. We've had smartphones for a decade and we're only now seeing proposals for offline access and notifications.

* Access to lower level APIs. Browser vendors don't trust developers and as a result give us APIs that are crippled and late. See the sad state of workers and lack of text measurement APIs, or access to layout, or image decoding, or the cache.

Google are doing some good work here but then they go and release inflexible techonolgy like their transition API, service workers or web components that work brilliantly if you write web apps in the exact way they envision but are useless otherwise.

Real innovation is happening in third party libraries and frameworks. Browser vendors need to acknowledge that and support those projects instead of trying to replicate them natively.

* Publishers should stop shoveling crap on their sites. App upsell interstitials and overlay ads create a terrible experience that makes the web feel like shit. They wouldn't do that in their own native apps but standards are lower in the web.

* Developers need to stop kidding themselves about the web being as powerful as native. We try and tell ourselves the experience is just as good and point to toy apps and painfully optimized tech demos. It's not as good. And it's not going to get better until we raise our expectations about what our tools should be able to do.
GTOR to me seems to be about finding intents, looking at different signallings of thing or things happening across time. You state in the first paragraph that there's a clash with how GTOR views things, and you have three paragraphs prostelytizing for greenthreading assuming that I understood the initial clash you saw, but you've provided very little context to explain the "namely, [GTOR] confuse[s] intent (or abstraction with implementation"

Are you getting hung up on the fact that GTOR talks through some specific apis for reactivity? You seem very much opposed to letting someone mention callbacks, prormises or observability? But GTOR is itself about mentioning these things so we can get past them and think of reactivity more generally. Yet you seem mired in your hatred for these concepts, in a way that prevents you from seeing that the article is about building effectful processing- having code or data whose effect is the running of other code, in a general fashion. And your inability to see that generalness, your forcing some weird diatribe against non-greenthreaded systems as all missing the point, is there rooted itself in confusing an implementation with intent, for surely blocking or no, concurrent or non, code and data will create reactions amid others.

I suggest getting more into the categories about. Sometimes binding happens before event, sometimes event before looking. Sometimes event is singular, sometimes it's over a duration, sometimes it's ongoing- edge, level triggering and continuous. Sometimes event has concurrency sometimes it's over time.

None of these don't make sense in Erlang or any other runtime, even if you might not see them expressed as first class constructs with apis, even if the reactivity were more baked in, as Erlangs send is.

Most of all, I have a very hard time understanding what your clash really is. I feel very much I'm being sold something, but the first paragraph doesn't give me a clear idea of what it is I'm being asked to accept evidence for.
I know it's hard to say, but how fast is "the learning curve is pretty fast"? Would two months straight be enough to have a reasonable command (I get that it would be entry level at best)
I'm actually pitching a similar idea to a major corporation.

Here is a reading list if you are interested in the subject. There have been (at least) four conferences on the subject of online deliberation.

https://www.loomio.org/

http://wikis.evergreen.edu/civicintelligence/index.php/ELibe...

http://odbook.stanford.edu/static/filedocument/2009/11/15/Ch...

http://www.publicsphereproject.org/ncn/

http://online-deliberation.net/

http://en.wikipedia.org/wiki/Online_deliberation

http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=134286...

http://www.virtualagora.org/

http://parliament.sourceforge.net/ftf-paper.pdf Parliament: A Module for Parliamentary Procedure Software

http://www.cs.uu.nl/groups/IS/archive/henry/RobertReport.pdf Prakken, Henry. 1998. Formalizing robert’s rules of order: An experiment in automating mediation of group decision making. Tech. Rep. REP-FIT-1998-12, GMD.
It's not "direct democracy". It's just democracy. If you trace back the term used by the Greeks, they called both the technology and the concept agora. Etymologically, agora means "speaking in public", "thinking with others" and in many verses it's used as antonym of war.

Democracy is always a work in progress. Otherwise it would be a totalitarian concept.

So what we are trying to understand is simply democracy but for the digital age. Using computers and networks, and the power of software. Open source, collaborative free software.
Articles demonizing coding interviews always attack strawmen that are the worst kind of interview questions:
1) Trivia questions (i.e. "what is the name of the method to do X in Java")
2) Questions with precisely 1 solution (you either get the one solution or you don't).

These are indeed useless technical interview questions.

But that doesn't meant there aren't good technical coding interview questions. I tend to favor the kind that present a candidate with some example data and a set of constraints or patterns, and ask them to write code that analyses the data for those patterns or constraints and reports them. This sort of problem is ubiquitous in my domain. Importantly, I always choose problems for which there are multiple possible attack angles, not just one. And I don't give a hoot about syntax errors, or what language they use.

This sort of question gives you a good sense about the candidate's analytical capability (breaking down the "word problem"), and their ability to translate their problem-solving thought process into code. Because there are always multiple angles of attack, candidates have some leeway to exercise creativity.

In the end, it's not terribly important to me that they get the optimal solution. I do care whether they demonstrate strong analytical capability in the literal sense, meaning they can decompose the problem and the associated programming exercise into their logical parts and implement them. I also look for good communication skills in the questions they ask when reasoning through the problem - this is something that only an in-person technical interview can reveal, AFAICT.

There are probably many smart candidates that don't do well on these questions because they're just having an off day, or nervous, or don't perform well under pressure. I sympathize with them, because I've been there and felt all of the above.

But if the goal of a technical interview is to assess a candidate's analytical and coding abilities, and their ability to do both simultaneously, there is no shortcut I know of to just giving them a role-relevant problem to work on.

EDIT:wording.
The real benefit of React is not in virtual DOM, even though virtual DOM enable the real benefit to be feasible.

It's in enabling developer to think only in "recreating the whole DOM".

Subscribing to event and figure out what DOM to update is error prone. With React, you don't think about patching DOM to the right result, you only think about how the final result should looks.

Understanding to latest state of document overtime is also harder with manually patched DOM. You can't be sure how the current DOM looks like after lots of patching.
With React, you know exactly how the current document looks like, given value of props and state. Every programmer knows that referential transparent function is easier to reason about than state full function. React's render method makes rendering a referential transparent function, as opposed to manually patching part of the DOM.

React is not about performance, it's about making it easier to write Component that works. Virtual DOM helps making the idea of rendering the whole thing possible, which happens to also make it fast.
Not necessarily. If you ask 100 people if they have ever encountered these issues, all 100 will say yes. It's those whose lives are negatively impacted by these issues outside the norm who get the diagnosis and need outside help.
Microsoft's latest development isn't even a real office. It's just a temporary stopover for non-Canadians to get them enough time working at MS to apply for an L-1 to go to Redmond. The people working there will not have immigrant status in Canada and couldn't stay even if they wanted to. The contribution to the Vancouver economy will be only from custodial or clerical support jobs.

http://www.biv.com/article/2014/12/ottawa-gives-microsoft-tf...
Interestingly, the score for my comment has fluctuated back and forth between +6 to -2. Clearly something touched a chord, which is strange because a) WW2 is a valid counter-example to the claim that you need a huge standing army to fight and win wars, and b) the extent of my "tone" was a single word, "utterly".

May all the 'hyperbolic internet rants' limit themselves to a single word.
Funny, this was on /r/vancouver not too long ago.

There's so many things broken with Vancouver but nobody is willing to confront these out of fear of displeasing the wrong crowd that backs them into power.

In other major cities, there's very good protection against foreign ownership of properties to prevent the exact situation vancouver is in.

In other major cities, there's a strong and large economy to grow with the cities cost of living. Vancouver's wages have remained unchanged for a few decades, barely adjusting for inflation.

Having grown up in Vancouver, I feel sad, sad that I have to leave my hometown to find better opportunities. I find that most sane people have already left Vancouver, including my circles. Senior engineers are hard to find in Vancouver because nobody with a family are willing to stick around for a low salary and high cost of living. Employees know that the labor market is tight and that people are desperate for jobs, and frequently exploit them. Tech companies are strapped for cash, large tech companies come to Vancouver to hire foreigners (Microsoft being the most controversial to date), video game industry is unstable.

Vancouver is a sinking ship.
Personally I don't think it's so useful of a feature; it saves typing a few asterisks but obscures the fact that you're actually modifying some other variable

There are many real-world use cases where references are exactly the right feature, and the const-ness of that reference should make the intentions clear.

Performance-critical code is one place where not having the ability to pass large objects around by reference would be a performance killer. References allow us to avoid making unnecessary copies.

Yes, you can accomplish the same thing with a pointer, but raw pointers are much less common in modern C++. It's not just syntactic sugar; a reference conveys information. When writing a function you can eschew null pointer checks when using references, whereas a function taking a (raw) pointer should handle the null pointer case since technically you can call foo(nullptr) and it'll compile.

With a reference bar must exist for the foo(bar) expression to compile when calling void foo(const Bar& bar), so it's safer, simpler code.
FWIW, there are ARM instructions for virtualisation. Linux's KVM hypervisor supports them.
(Assuming Adobe isn't using lots of x86 assembly in its low level image/video code)
Very insightful, there's no doubt we have a lot of work to do.
Facebook / Microsoft is here too but they hire almost no Canadians, most are foreigners, until they can get the green light to work in the States.

Amazon is the only one hiring locally but I often find that they just advertise positions but never really end up hiring
Surprised there was no mention of Hong Kong as Vancouver is often dubbed Hongcouver and Hong Kong has to deal with the same kind of problems right now (that is, the younger generation can't afford to live there).