skysight-inc/HackerNews huggingface dataset:
Well, if the author kindof hasn't seen it, I guess I should ignore this stuff:

Boehm, Barry W., and Philip N. Papaccio. 1988. "Understanding and Controlling Software Costs." IEEE Transactions on Software Engineering SE-14, no. 10 (October): 1462-77.

Boehm, Barry, 1981. Software Engineering Economics, Boston, Mass.: Addison Wesley, 1981.

Boehm, Barry, et al, 2000. Software Cost Estimation with Cocomo II, Boston, Mass.: Addison Wesley, 2000.

Boehm, Barry W., T. E. Gray, and T. Seewaldt. 1984. "Prototyping Versus Specifying: A Multiproject Experiment." IEEE Transactions on Software Engineering SE-10, no. 3 (May): 290-303. Also in Jones 1986b.

Card, David N. 1987. "A Software Technology Evaluation Program." Information and Software Technology 29, no. 6 (July/August): 291-300.

Curtis, Bill. 1981. "Substantiating Programmer Variability." Proceedings of the IEEE 69, no. 7: 846.

Curtis, Bill, et al. 1986. "Software Psychology: The Need for an Interdisciplinary Program." Proceedings of the IEEE 74, no. 8: 1092-1106.

DeMarco, Tom, and Timothy Lister. 1985. "Programmer Performance and the Effects of the Workplace." Proceedings of the 8th International Conference on Software Engineering. Washington, D.C.: IEEE Computer Society Press, 268-72.

DeMarco, Tom and Timothy Lister, 1999. Peopleware: Productive Projects and Teams, 2d Ed. New York: Dorset House, 1999.

Mills, Harlan D. 1983. Software Productivity. Boston, Mass.: Little, Brown.

Sackman, H., W.J. Erikson, and E. E. Grant. 1968. "Exploratory Experimental Studies Comparing Online and Offline Programming Performance." Communications of the ACM 11, no. 1 (January): 3-11.

Sheil, B. A. 1981. “The Psychological Study of Programming,” Computing Surveys, Vol. 13. No. 1, March 1981.

Valett, J., and F. E. McGarry. 1989. "A Summary of Software Measurement Experiences in the Software Engineering Laboratory." Journal of Systems and Software 9, no. 2 (February): 137-48.

(References from http://www.construx.com/10x_Software_Development/Origins_of_...)
Yep. It's a high-risk project, but the pay-off could be huge (both for programming languages and browsers) if they pull it off.
A direct attack by a state actor (especially one like the US, which likes to be seen as following the rule of law) isn't too likely. China might attack bitcons, but why would they - they can just block them.

The people who do black ops don't generally do so to help the financial sector. They do so for national security. While the economy (and monetary system) is arguably a national security issue, I can't see them all being on the same page. The guys in treasury would probably rather talk to regulators than intelligence.

Simply banning them, and enforcing that ban would work though.
I think its important to note that if we didn't have ten fingers and created a decimal numbering system, we probably wouldn't be using the 10x factor
A Billion dollar stock is much more liquid then the BTC market, as a lot of bitcoins have been lost and many more are being horded.
While holding that unpopular view may be admirable, I agree with your parent that closing one's mind to the opposing view on any topic is not admirable. Perhaps he meant that he had already considered the debate and found all the arguments wanting.
A lot of the productivity difference is probably due to overall familiarity with the code base. In a year from now when you have to fix a bug or add a feature you will probably know where to go and have an idea of what needs to be done rather than having to go hunting for it or asking another developer. If a project is started from scratch I imagine a lot of difference in productivity is due to familiarity with the tools, frameworks, api's, etc. used.
Yep. https://github.com/primaryobjects/redant
Yeah, both sides seem to be having a "thank heavens we can get rid of all that crap we don't use" moment.
With the difference that Facebook's efforts help Android compete against iOS (at least for the moment) while Chrome is agnostic between Windows and OS X.
I emailed Tim Cook
A.O. Scott
My best memories of Roger Ebert were at the Conference on World Affairs at an event called Cinema Interruptus. The CWA lasted five days and was open to the public. Every single day of the conference, there was a Cinema Interruptus session. On the first session, attendees watched an film in its entirety. Over the next four sessions, the film was stopped - sometimes after a few minutes, sometimes after mere seconds - and Mr Ebert discussed the film with the attendees. Attendees were welcome to make their own comments, too; sometimes it was a hassle as there are people who just enjoy hearing themselves talk. But it was a great memory of mine that Mr. Ebert called one of my observations "astute." I was able to say hi and shake his hand after one of the sessions, and I was certainly impressed at how a person of such extraordinary merit would contribute his time every year to our beloved CWA in Boulder.

He will most definitely be missed.
Using an in-code secret key (as opposed to the not-secret-by-necessity salt) is commonly referred to as a pepper. It improves security in the cases when an attacker has access to your database but not to your code or filesystem.

Figuring out the hashing scheme used for a given hash is frequently trivial. All an attacker needs to do is hijack his own hashed password and salt and then run combinations of common hashes with salting patterns until he gets a hit. This is going to be hundreds of combinations to test on the high end, and will generally yield results very easily.
Neural Decoding of Visual Imagery During Sleep
Cryptograhpers are a strange and paranoid bunch. They have a few notions of security, including https://en.wikipedia.org/wiki/Information_theoretic_security or https://en.wikipedia.org/wiki/Semantic_security and a few others. You can follow the links from those two pages to find the other concepts.
"x10 developers" are, in fact, proficient developers, who are experienced with their stack and problem domain.

Well, I'd say this is only true for your typical corporate entity, where their products are basically just web applications that represent a state machine using some sort of database store for persistence (which is... basically everything). By the time the company has achieved some size, there's enough process and bureaucracy and projects mostly consist of what the OP described -- migrating from one framework to another, or some other incremental enhancement that's hardly pushing any sort of business of technology threshold. At previous employers that fit this description, I could have easily been 10x more productive if I didn't have to endure four hour sprint planning meetings or be required by an understaffed QA/DBA/sysadmin team to approve my code before release, all to do completely routine development changes that required no serious problem-solving.

This doesn't mean I'm a 10x developer. It probably means I'm a 1x developer, so a 'true' 10x developer would have been 100x more productive without the aforementioned bureaucratic crap. At these companies that would dogmatically follow Agile and had two week sprints, I might spend four hours, across two days, actually developing -- with the rest of the days filled with various meetings, interviews, waiting for QA/DBA/sysadmins, fucking around, etc. I could easily see how someone could spend only 15 minutes on what took me four hours, and his solutions would likely be more elegant. It doesn't matter -- the limiting factor isn't the development time, or even the development quality. In that environment, there is literally no difference in productive gains between a proficient developer and a 10x developer.

Given a "10x developer" is literally defined by his productivity/quality, if you think they're effectively overhyped/nonexistent, ask yourself this: are you in an environment where a 10x developer could actually demonstrate 10x productivity? At most companies, the answer is no, because a 10x engineer is doing in hours what takes people days, and nobody notices. But in the right environment, the 10x engineer will do in weeks what would take proficient engineers months, or do in months what would take years. They're the people that Steve Yegge calls "Done and Gets Things Smart"[0] or that Rands calls "Free Electrons"[1].

And if you work at a company that can't think in terms of months because it's always concerned about quarterly earnings, then they have no use for 10x developer, and chances are you couldn't even tell if one was even there.

[0] http://steve-yegge.blogspot.com/2008/06/done-and-gets-things...

[1] http://www.randsinrepose.com/archives/2005/03/20/free_electr...
In my experience there are both. There are certainly a fair number of 1/10ers that manage to progress through seemingly normal career paths as programmers despite not being very good. I've worked with some, and most of you who are also developers probably have as well. But there are also for-real 10xers on top of the baseline. John Carmack, Jeff Dean, Fabrice Bellard, et al. If you define hyper-productive programmers like those guys as your baseline then like 99.9999% of working programmers need to quit in shame.
>Currently, we generally use preprocessors such as LESS or Sass to compile from some more improved syntax into usable CSS2/CSS3 before serving (a la CoffeScript->JavaScript).

Unfortunately, even for static CSS, that's not going to be practical for element queries. You could do it in theory, but in practice, you'd end up generating tons and tons of CSS for even very simple sites.

>A shim is generally meant to be there just in case some feature (present in some modern browsers) isn't available in the current browser;

That's why I put "shim-first" in quotes.
FWIW, I thought of the exact same thing. I think Samsung/Oracle/BB etc. are going to end up maintaining their own WebKit or Blink forks. (Not sure why Google will agree to add stuff that doesn't benefit their cause. Just like how Apple is saying JSC or bust Google might down the line say V8 or bust.)
The Truth About Hair and Why Indians Would Keep Their Hair Long
Just write it down
Its a nice write up, but it gets many points wrong.

1) Bitcoin is not anonymous. Its pseudonymous since all transactions take place in public between pseudonyms (ECDSA keys). This is a big difference, one that hasn't been examined too well, and what has been written on it is not encouraging[0].

2) Bitcoin is not the first currency to prevent double spending without a third party. That minimally goes back to 2006 and a paper "Compact E-cash"[0] where double spending a coin reveled the user's identity and allowed for prosecution.

The problem Bitcoin actually does solve is you don't have to trust the bank to not devalue your currency.

3) Bitcoin does not solve the Byzantine generals problem. Bitcoin is assumed to be correct if 51% of the computation power is honest. If everyone is equal, this means that bitcoin only requires that the majority of the generals are honest. The Bzyantine generals problem has no solution if even 1/3 of the generals are malicious[2]: this is a rather famous result.

How is this possible? Bitcoin isn't dealing with a fixed n Bzyantine generals, its dealing with a peer to peer system where anyone can join and you need to prevent sock puppet accounts. It's a completely different problem.

[0]F. Reid and M. Harrigan, “An analysis of anonymity in the Bitcoin system,” in Privacy, security, risk and trust (PASSAT), 2011 IEEE Third Internatiojn Conference on Social Computing (SOCIALCOM).	IEEE, 2011, pp. 1318–1326.

[1]http://cs.brown.edu/~anna/papers/chl05-full.pdf

[2]http://research.microsoft.com/enus/um/people/lamport/pubs/by...
I work for Mozilla, but speak for myself. If you think it was about control, then you don't know how Mozilla works. We fight larger players with one arm tied behind our back because of our commitment to making things open and interoperable. We do it gladly, because we know that sometimes our reference implementation won't be the best implementation, and even if we fail, we want the tech to live on. Every day I have or overhear a discussion about making certain what we build doesn't privilege our own solutions over others. Are we perfect at this? No. Sometimes security of our users trumps a completely level playing field. But every time we have to slightly close a technology, know that it's done extremely begrudgingly.
Joseph Conrad on Writing and the Role of the Artist
This is one of those posts with a scandalous headline to draw you in, but without anything substantial to back it up. I am quite disappointed that this came from a stalwart of a tech blogger like Om Malik. I can understand this coming from an MG Siegler or an Arrington or from the joke of a blog, Gizmodo.

It hinges on the GPS location, which Apple does, quite publicly with theing like Find my iPhone. Google does that already, and so do every other GPS device on earth. I don't even need to know if you are stationary at one location every night. I can just connect the dots on your end points of your trips and figure it out.

Heck even an app like Yelp can figure my home address, based on my restaurant searches. Facebook already knows much more about us, with or without our permission; just by using the website.
The most notorious patent troll in America is Intellectual Ventures. It's just that because of their clout and their team, they don't get called out.
Are companies actively telling you that you don't have enough experience, just not responding, or are you getting discouraged by the job description? Having written many job descriptions, a lot of it is a negotiable wishlist and actual numbers of years is maybe one of the squishiest bullet points on the list and is more indicative of maturity and overall work experience vs exp in the role. Lots of PMs (not junior/associate/assistant PMs) get hired with just some "business" experience (finance, consulting, marketing, etc.). I don't think you should have a problem as long as you can demonstrate the qualities of a PM.

You may also want to recraft your resume to be more pointed about your PM experience and less focused on your engineering aspects. Here are two great threads on Quora that can help you pitch yourself to the questions hiring mgrs might want to see.

http://www.quora.com/What-are-frequently-asked-questions-in-... http://www.quora.com/Recruiting/What-are-useful-interview-qu...
Drupal Create released on Github
Not the future. The Culture books happen rougly in the present day (although across a timespan of many centuries; CP is set 800 years before the other novels, The Hydrogen Sonata several centuries after Excession), and there is even a short story about The Culture encountering Earth.
I think the problem is that the author has normalized his development standard to proficient coders in the tech industry. I used to do enterprise software in the midwest and there are legions of 1/10th developers out there. Its easy move your baseline far away from the average when you are in the echo-chamber of high-tech startups. Compared to the true average developer there are definitely 10x developers.
That paper you link to uses a trusted third party. I highly doubt you could run a 51% attack for any significant amount of time on $20MM. Consider the coins being mined everyday are worth ~500,000USD.

That is not to say it is impossible, but there is almost no way anyone in the world could pull it off for $20MM except the people who already have ASIC designs.
Hm. Until now I thought dyno-presence is your issue, but now I realize you're talking about the actual "leastconn" part, i.e. the requests queueing up on the dynos itself?

If that's what you actually mean then I'd ask: Can't the dynos reject requests when they're busy ("back pressure")?

AFAIK that's the traditional solution to distributing the "leastconn" constraint.

In practice we've implemented this either with the iptables maxconn rule (reject if count >= worker_threads), or by having the server immediately close the connection.

What happens is that when a loadbalancer hits an overloaded dyno the connection is rejected and it immediately retries the request on a different backend.

Consequently the affected request incurs an additional roundtrip per overloaded dyno, but that is normally much less of an issue than queueing up requests on a busy backend (~20ms retry vs potentially a multi-second wait).

PS: Do you seriously consider Zookeeper "really slow"?! http://zookeeper.apache.org/doc/r3.1.2/zookeeperOver.html#Pe...
Like any investment it requires careful analysis, personally I prefer to pay attention only to the 200-day simple-moving average. Granted in the past 200 days it has changed a lot, however recent interest in it indicates that it may continue going up. Past performance isn't an indicator of future performance but it's a decent gauge of trends.

Most news articles call it speculative because the people using it can afford to lose the USD value of the coins and there simply isn't enough mass adoption behind it to maintain its value (which would be true), so trade cautiously and ignore news about it.

If you must then re-allocate your investment in or out on a monthly basis.
It occurs to me that this could actually be a very handy way to get help from more competent friends as I'm learning to code. I've had offers to review my code, but being able to do it live would be great. Great tool!
Governments could tax all bitcoin transactions that go through a centralized entity (such as Mt. Gox) a non-trivial amount, which would effectively kill it as a mainstream currency.
The fact that someone was recommended by a chain of people doesn't mean that good, or even competent. Perhaps the old CTOs weren't competent to judge or didn't have enough experience to have a proper baseline.

It's quite possible that I could judge someone at some task (say cutting & laying intricate tiles), and think they're quite good. They may seem fast to me because they're doing something that would take me forever. But if you brought in a real professional, they may laugh and say worker is going to slow.

The author said that the coder in question didn't show any improvement after 2 weeks of coaching. The developers at the previous firm he mentioned were slowly improving, that's why he kept them. From my reading I got the impression that if the PhD candidate had improved, he would still be there.
The types of layouts I was referring to are ones like:

http://layout.jquery-dev.net/demos/complex.html

http://developer.yahoo.com/yui/examples/layout/adv_layout_so...

https://gomockingbird.com/mockingbird/#

http://docs.sencha.com/ext-js/4-2/extjs-build/examples/build...

These layouts all use a combination of CSS for layout (floats, margin, padding etc) as well as absolutely positioned elements that are controlled using some variety of layout manager. Where this becomes especially useful is for collapsible, resizable, movable panels and windows.

A testament to the way in which CSS is lacking is evidenced through the hundreds of multi-thousand word blog posts that were devoted over the years to discussing how to achieve multi-column equal height flexible layouts [1]. This is something that should be trivial, instead hundreds of man years have been wasted trying to get boxes to line up nicely.

CSS3 flexbox solves some of these issues, however there is still no way in which to arbitrarily constrain or anchor any container to any other container which ultimately limits its usefulness.

[1] http://alistapart.com/article/multicolumnlayouts
Democracy is also vulnerable to 51% attacks ;P
If you ask me to design a programming language, I'm a 0 and van Rossum and Kernighan and Ritchie are some finite number, so they are infinity-x me.

There are levels where people hit a wall. Some hit it at hello.c, some hit it at writing professional business logic with proper data structures, some hit it at assembly language or programming language design or operating systems.

Anyone in over their head at any level is a 1/10 or a 0.

The superstars of language design, if they had to dive into Java business logic, might be at 2x the productivity of a competent pro...or they might shoot themselves.

But if you create a Python or Linux...what's your productivity compared to that Java programmer? In terms of the market value of those ecosystems, increased efficiency by the developers and users in those ecosystems, it's not 10x, it's gigantic, millions of times the value-add.

The weird thing is, people don't get paid much more when they move from one level to another, unless they start the next Google or get shares/royalties...it's more on a log scale.
> But there are also for-real 10xers on top of the baseline. John Carmack, Jeff Dean, Fabrice Bellard, et al.

Those are the famous ones. Also, a fair portion of Members of Technical Staff (and higher) at Google are 10x.
Their tools truncated my changed password to 25 characters silently (first clue), their password reset tool emailed the plaintext password back to me (second clue), and their "api" endpoint errors out when I use special characters in my password (last clue).
I hurt my back rowing in 2009 in the L5-S1 area. Many physios diagnosed it as different things and many of them tried different treatments. None of them worked and it hurt for three years. I tried lots of different core exercises, some physios tried manual and manipulative therapy (which helped for a bit) but after a few months of sessions of dry needling my back hasn't bothered me with that injury in over a year.

I would much recommend dry needling, it's not the same thing as acupuncture.
Realpolitik. Some descriptions of the zero-day "black market" imply that the government itself is one of the bigger consumers, and various arms of the government routinely bids against itself to get exploits.
I don't know where you're getting your data from, but I know of at least one high frequency algorithmic trading firm that make ~$1B a year using mathematical models. The models aren't simple, but they're entirely automated and they behave exactly the opposite of how you describe them: you turn them on and they print unbelievable gobs of money.
You can't give 10x or 1/10 labels without context. If you ask a smart developer to code in a brand new language, he'll look like a 1/10 developer for a while; and an average developer can look like a 10x developer if he's working with technology that he's been using for the past 10 years.
10x at what? What is 1x?

Programming is a wide field. In some tasks, I'm faster. In others, very slow. Give opportunity to do only the things I'm good (and pay me!) and happy I will. But... I need to do a lot of stuff I'm not good, or is unrelated to programming per se (I'm a solo startup) and sometimes is like the time is stopped...
The Royal Canadian Mint developed MintChip[1] however there has been little interest.

There's a scathing Forbes blog post[2] too, if you're interested.

[1] http://en.wikipedia.org/wiki/MintChip

[2] http://www.forbes.com/sites/jonmatonis/2012/04/12/mintchip-m...
Yes but the fact that they are publicly visible makes them serve a secondary purpose.
Perhaps, but then our 6x or whatever factor would still mean essentially same thing.
Indeed. I settle for nothing less than the 0x10x programmers.
"As deep as anyone else in the field" implies formal writing, which I've never seen by Ebert. If it exists, does it compare with what gets published in a film studies journal, or has it been published in one? Do you have a link or article name?

https://en.wikipedia.org/wiki/Category:Film_studies_journals
So, Zipf rather than Bell .. ?
it's basically a bet,but you have more chance to win than in a casino, or at the lottery.
Google Glass Mirror API Emulator
If you just want to dip your toes in the water, you could always start mining. Doesn't take any initial investment or bank information or anything like that, just processing power.
scream it from the mountains:

"GET 'EM RACKSPACE!!!"