skysight-inc/HackerNews huggingface dataset:
There is a lot to like about this style of hiring and it is similar to processes I have endorsed before. There is one unfortunate problem with it though. It rules out developers who have moonlighting clauses, which is a very large percentage of them (even if they don't know it).

At the end of the day the only system I've been able to think of that gets around many of these problems is a contract hire (3/6 months depending on prevailing employment conditions) that at the end of it has a lump sum payout of the equivalent time (so a 6 month contract would end with a lump sum payout of another 6 months) regardless of if the contracted employee continues with the company (either by their choice or the companies).

The advantage of this system is that it will not remove candidates from the pool who would normally not take on the risk of a contract position, yet allows for an honest assessment of the candidate/employer relationship.

This seems expensive up front but is often just accelerating bonus payments for employees that are kept, and is a small price to pay for removing bad employees quickly.
In addition to what fennecfoxen already stated, using their own visual sensor gives them control over the exact format of the data coming off the sensor, thus permitting them to use FPGA or ASIC based processing that would not be an option if they had to deal with image files coming off the iPhone's camera. It also allows them to collect extra data to help register the visual and IR images to each other.
I disagree. The whole point of abstraction is that you don't have to care about the underlying mechanisms (although most non-trivial abstractions are leaky as Joel Spolsky has written about).

For instance, someone who writes assembly should not have to know how a transistor works. A course in introductory programming similarly should not be about how a processor works.
Selectively Redirect Back
Doctors barely give you any time during an office visit, so I find it highly doubtful that they will want to waste more time searching online for someone.
CTEs in general are fine, just beware of using recursive CTEs to model graphs - and do graph operations - inside Postgres. My experience has been that the performance is pretty abysmal in that case, for even fairly small graphs. IMO, if you find yourself doing a lot of "graph stuff" just go ahead and store the graph in Neo4J or Titan or something.

Note that I don't mean to argue against the point of this post... CTEs are very handy. It's just that one of the more commonly cited uses for them is to do graph stuff, and my experience trying to that, specifically, has not been positive.
Which is more complicated and less expressive than haskell? That seems like a pretty bizarre choice.
This is horrible. mugshots.com is a fake website. It creates fake profiles based on queries it gets. So you enter in: First Name Last Name Drug. It will put a fake picture most likely based on last name. Meaning Ramirez isn't going to pull up a white dude. Gender is based on first name. drug or crime creates the context. It then creates several pages based on this. Then it relies on the person doing the search to apply bias. Throwing out information to make it fit your preconceived notion.

This is extremely dangerous and unbecoming of a doctor. What if the lady really had no idea. What if her son swapped out the sugar with cocaine in a panic and she OD on it.

Bottom line don't trust everything you read on the internet.
What?! I you might want to reread the article and then read the author's comments here and his other Go articles.

The author clearly knew about Go's lack of generics and was quite familiar with the language. After stepping away from the language for a while he decided to give it another try in a project where he thought the lack of generics could easily be worked around via Go idioms. He found out that the lack of generics _did_ hurt more than expected and wrote about that part in a way that projected his frustration.
>Personally, I see Haskell as the C++ of functional language

You should try it some day, it is absolutely nothing like your misconceptions.
The front page is working correctly for me in Firefox 26. When I hit page down or space the two lines that were at the very bottom of the screen move to just below the top bar.
So, poor performers can be identified if "they don't have enough roles" or "they're not a good fit for the company culture". What happens to them? I guess there are executives at a higher level that have the authority to fire these poor performers?

These "lead links" sound like managers with less authority to me.

If they are hoping for natural leaders to step forward then that seems how you become a manager in that company, you ask for it. Which, in some cases, is probably a better system than what many companies have in place that places people in roles they shouldn't be in.

The roles are still there, some of the requirements and responsibilities are shifted a bit, but they just removed the titles.
10 ghostery items and 23 Ads. Nice.
I'm a second year CS major. That's not a safe assumption. Some of them learn to swim, and some of them drown. A guy in my CS1 class last year (there was no placing out) failed to comprehend the concept of words controlling a computer.

Further evidence is the four class intro sequence steadily had fewer sections (of the same size) with each passing term
Obama is president, not his father. He grew up as a lawyer's son, not in a working-class household.
Reminds me of the saying: "Ideas only work if you do.."
You may be underestimating the stuff people post on facebook these days.
Exactly. They are just the differences. If you'd want a technical pro/con of Ubuntu/Debian vs Redhat/Fedora, that is an entirely different post equally as large (perhaps more-so). In summary, from an ease of sysadmin standpoint for large numbers of servers, redhat and the redhat ecosystem (cobbler, pulp, freeipa, sssd, abrtd, kickstart) just beats the living pants off of anything Ubuntu/Debian have. It is much easier to manage thousands of Redhat machines (without building everything custom like google) than it is thousands of Ubuntu/Debian machines. I know this because I've done both as part of my day job.
As much as I enjoy Dijkstra's wit in general (and I agree with the argument for learning functional languages early), I imagine taking a shot at "Texas's solid conservatism" didn't help his case all that much. For "enlightened" individuals, most left thinking and academic people are really no better at mitigating tribalism, prejudice, and ignorance of other points of view than the far fringes of the right. Perhaps it would have been more effective to appeal to the self interest of the council.
Luckily it doesn't change my response in any way other than in addition to all the "he" translating to "the author" all the "she" should refer to "the author's sister". I'm a "he" who provided software support to my sister, so you can see the likely source of that assumption. No negative implication of her ability to successfully portray her chosen gender role intended.

Also I think its lame to check out bylines to make sure I run stuff thru the right sexism filter; I clearly stated its a "good" article; not "good, for a girl" article, or "not up to the manly standards of excellence" article.
Are domain hacks devaluing .coms?
This may just be postering on the part of the UAE Government to get out of the deal, because they have been offered better terms from elsewhere. A relative in the US who was a very small military contractor delivered a radar system to the UAE Government last decade - on time, and on budget - only to be told that they didn't want it anymore and since they didn't want it, they were not going to pay for it. The company could not tolerate that loss and went bankrupt.
> Dijkstra assumes that students will already have been exposed to imperative languages before joining university

For those entering CS, this is probably true. But it's also probably true that that's because of the students' own initiative to investigate a topic that interests them.

I think high schools have gone the opposite direction. In the 80s, most high schools had some sort of computer class (often taught on TRS-80s or C-64s). These were introductions to programming taught in Basic.

Nowadays, most high schools still have a computer class. But now its Word, Powerpoint, Excel, and build a (static) web page. (There are, of course, some high schools with much better programs.)
Does anyone know if anything came out of this letter?
I miss Python's named parameters with default values. They are surprisingly hard to replicate in Go. Also list comprehensions.
You seem to have completely missed my point about crime not being evenly distributed. Yes, the US murder rate is unusually high for a first world country. That does not, however, imply that most of the US experiences extreme amounts of violent crime. Most of the US is reasonably safe, with certain parts being unreasonably dangerous. To merely look at the average is like saying that the Dundee neighborhood of Omaha, Nebraska is extremely wealthy since the average net worth of people in the neighborhood is over $9.8 million, when it's actually a bunch of middle class people plus Warren Buffett.

On the health care front, I have trouble finding anything that actually discusses the quality of care when you have access to the system, rather than discussing the quality of care for the country as a whole. This is the best I could find:

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

Relevant summary quote: "Overall, results for mortality favoured Canada with a 5% advantage, but the results were weak and varied. The only consistent pattern was that Canadian patients fared better in kidney failure."

Two major confounding factors are overall health of the population (essentially, how much of poor American health care outcomes are due to being fat) and unequal access. Statistics for the country as a whole ignore these, and therefore are not relevant when deciding how the American health care system will treat an individual who eats well and has decent insurance.

Again, the US health care system has deep problems that need some serious attention, but as best I can tell, they are financial, not actually problems with the quality of care that's delivered to those who are able to receive it.
Knowing the single fact that a language is ultimately a piece of software is different from having an intrinsic understanding that each high level construct has to be somehow translated to what the computer can do. Everyone learns the fact "compilers provide programming languages" pretty quickly, but beginning programmers don't get early enough into the habit of thinking how what they write in a high level language translates to what the actual computer does, and they end up with broken programs. Whether you are using Haskell or Java, if you don't understand the execution model it's trivially easy to run into problems with memory management, like reallocating memory over and over when growing collections, exploding the stack via inefficient recursions etc. etc.
thanks. (for future ref: link mentions selecting a secret chat avoids messages being stored on telegram servers and enables end-to-end encryption between devices)
I love using small CTE's to help with the hassle of the alternative - creating temp tables and then cleaning them up. They can be particularly useful for data modification, as you can't ordinarily do a recursive delete or insert all that easily.

PS: I always cringe when I see this sort of syntax though:
"FROM
users,
tasks,
project"

Much clearer using explicit JOINS imo, especially if your goal is readability.
I think its okay, isn't it the ultimate LITMUS TEST. If you instantly gave up after you googled that the idea has be done or "stolen". Then you were never passion enough to tackle it in the first place - in the first sign of 'competition'.

We are naturally go through this - and yes those people need to suck it up and should be actually EXCITED their idea was implemented - and if you are truly passionate about the idea, you should consider on joining the new team rather than scorn them.

They brag about their idea was "stolen" because they just desire the riches the successful implementation founders have received.
All SQL databases have this feature, it's nothing specific to PostgreSQL.

I don't like the "with" syntax though, I just do it all inline.

select * from
(
select * from blah 1
) a,
(
select * from blah 2
) b
where a.x = b.x;
When you know you're referring to a woman, sure. But when the gender is unclear, it shouldn't be a feminism issue. This entire argument has always seemed ridiculous to me, and I mean really, go look at the Spanish language...
By what method would you then ask for a reference? Probably begging, or asking with an expensive bottle of alcohol. This seems to needlessly burn bridges.
Which only demonstrates that occasionally someone manages to move between social classes, and has no bearing on the argument made above.
I spent my first few undergrad years as a CS major at UT before this change happened, and had no prior experience with programming (I started in '97).

The INTRO-intro CS class at the time actually used Pascal, and was endlessly confusing to me as a cold beginner.

My next course, however, was taught in Scheme, and immediately I felt more at home. And for the first time, I felt like I might have some actual aptitude for programming.

Without that peek into the elegant heart of computer science, I doubt I'd have stuck with it as long as I did.
Recursive CTEs can absolutely be more performance intensive, and even non recursive CTEs can be an optimization bottleneck. However from what I've seen with non recursive CTEs is that you're looking at a 1.5-2x difference in performance (in the bad cases) versus orders of magnitude. For making SQL more readable and shareable this seems a small price to pay, its much the same that people use higher level languages rather than dropping down to C for everything they need to do.
Yeah, graph storage is not a problem that is amenable to a SQL solution. ISTR that this very thing basically killed Friendster.
For every designer out there that really cares about typography in their designs that has high end monitors that are expertly calibrated, most of your audience probably doesn't.

Also check your work on a normal monitor.
Strangely I found myself struggling to pick up Standard ML despite having experience in C++ compared to my peers with no programming experience. It seems that they just treated it as math, while I had trouble changing my imperative programming mindset.

Also Larry Paulson is a legend.
"maintain a certain balance of powers" and "conquest" are not mutually exclusive.

"many" really just means "more than one", but okay: if 50 nations invaded and split up the US, would that be conquest?
Shell2web - turn status output scripts into apps
I agree on the explicit joins and called myself out on this in an older post - http://www.craigkerstiens.com/2013/05/06/my-sql-bad-habits/

Explicit joins are much better for readability, though I find myself well not using them enough...
Actually, you're not getting it.

While the use of 'them' and 'themselves' is increasingly acceptable informally, it still violates basic rules of plurality that most people agree upon, and is thus formally incorrect.
> Actually, if your students cannot understand what this line is after one full class of Java, then the problem is with the teacher, not the students.

I think you're dead wrong about that. Assuming somebody with no programming background at all, here is a (definitely not exhaustive!) list of things that must be learned in order to understand that line:

Method visibility, what is a "method", what is a "function", what is a "class", probably what is an "object" (because it is otherwise difficult to understand why a "class" is a useful construct), "static" methods, either need to hand-wave the use of the term "static" for methods associated with a class or know a reasonable amount of history and/or computer architecture, the idea of a "return type", oh, the idea of a "type" come to that, "void" itself, "main" and generally the idea of a program entry point, function arguments, the "String" type, what is a "character", how are characters made into a "String" (arrays and encodings with various amounts of hand-waving), the "[]" syntax, and arrays of arbitrary length.

A class period is, what, 2 hours? No, it doesn't matter how good you are as a teacher, you can barely cover all that material in a single period, let alone do so in such a way that the students have any idea what you're talking about. Teachers finding themselves a month (or three!) down the road telling their students "now you have enough background to go back and understand the very first line of code you wrote!" is absolutely an anti-pattern.

[edit: formatting and typos]
GHC, the most popular Haskell compiler, is also very mature and very good at doing high-level optimizations.
The advantage of CTEs is they have the explicit "WITH RECURSIVE" option. Whereas an aliased SELECT statement can't refer to itself as far as I know.
My intention was to compare and contrast two services for developers who have a handful of personal projects, small-to-medium-sized public projects, and/or development needs. AKA, people like me. I seriously doubt any business manager is reading the blog of a random college student for server advice.

I host a handful of things. My personal site, my blog, my Gitlab; Git Reports (http://gitreports.com/); a couple of medium-sized websites for organizations related to my university; and (currently) a couple of staging apps for some freelancing. I feel like my use cases are fairly common in that regard, although I suppose I could be wrong.

So I attempted to explain why I found DO to be much more useful for my use cases. I'm not exactly starving but I am a college student so price is important to me. The things I run aren't entirely inconsequential so specs and uptime are also important to me. Like I said in another comment, being able to easily spin up fresh environments is convenient especially for staging. I found the management features convenient and easy-to-use. I'm not sure why thinking that a better interface is a good thing is an invalid opinion.

If you're saying that I should have included more context about my use cases, I suppose that's fair. Other than that, though, I'm not exactly sure what your complaint is.
Yep all that extra CPU utilization on the the other cores is just garbage cleanup.

Go has a stop the world collector, hence the poor performance and single core usage.

Both versions would benefits greatly from reusing instances instead of generating huge amounts of garbage, however the Go version would benefit the most. With the Java version he is simply throwing hardware at the garbage.

Know thy garbage collector!
Worse, they imply that an idea is a tangible thing, owned by someone. Some type of property, that can be stolen and thus deprive you of something.
Read the third sentence of the article.
Deploying software at Pinterest
Possibly.I regulary use both static and dynamic languages and lack of generics was one of my biggest complaints. If it's a static language, I want generics. If the language is dynamic I don't really care (although some dyn. languages have generics).
Completely disagree. All the database developer "experts" I know of (including myself) hate the explicit join syntax.

I prefer to list out your tables and then do your joins in the "where" clause. For 3+ tables and mixing inner & outer joins it's especially better. I think maybe this only looks better once you become really really good at reading and writing SQL though. Maybe it's also because I come from the Oracle world where it is the standard.
'once respected media outlet as personal mouthpiece'

That should be given more focus IMO
Industry is far too low a bar to aim at. College should give them the fundamental understanding of programming that they can apply to a variety of situations. Employability flows out of that.
Addendum: High schools also used to teach typing (on typewriters). Now that keyboards are ubiquitous, typing classes have inexplicably been dropped. Go figure.
Not every business believes they really need a CRM. Plenty of old school businesses are skeptical of technology. 200 million companies includes every plumber/electrician/restaurant and a whole bunch of other mom and pop / small local business. The businesses that have bought CRM apps understand the ROI of a CRM. Not all businesses do though.
And you realize that machine code has to be translated to how electrons are routed right? Do you have a good understanding of how that works?

Embrace abstraction folks.
One of my favorite things about heaving to learn Scheme in my intro CS course was that it put most students on an even footing with regards to already (not) knowing the language. It's awesome to see Dijkstra alluding to that, "it drives home the message there is more to programming than they thought."

I'm having a ball learning Clojure now, and it would be much much harder if I'd never used Scheme. (I've done some functional programming in C++ and Ruby, but I wouldn't have done that if I hadn't done it in Scheme earlier.)
A doctor should be allowed to go by what you tell them. Full stop. I may not want to tell someone about the fact I eat tons of red meat, for example. I may not want my test results to be shared with the insurance company, who will then charge me more. Too much shared information is dangerous.
Amazon Route 53's ALIAS implementation takes a different approach. We only allow ALIASes to data that we know about authoritatively; so with Route 53 you can ALIAS to an S3 website Bucket (which also lets you do HTTP redirects), a CloudFront distribution (which can serve as a bridge to any arbitrary domain you may care), an ELB or to other records in your zone (which lets you combine routing policies in a compositional way).

The main benefits are;

No dependency on a third party DNS service, we stand behind our 100% SLA

DNS-based routing policies still work correctly

No delay in responding to health check failures

but there's another (future, for us) ancillary benefit too;

Compatibility with offline-signed DNSSEC

The big downside of course is that the record has to be in our system in order to ALIAS to it. For HTTP services, using CloudFront is a pretty good workaround, it can handle dynamic and static sites. If you merely want to redirect from your apex to your www. domain, then S3 with a redirect works great too.

We're also open to enabling ALIASing to other zones hosted in Route 53 on a case by case basis. If you have a multi-tenant service and you're managing (or willing to manage) a zone on Route 53 with something like [customer-or-resource-identifier].yourservicename.com we can enable ALIASing to those names. If you're interested, get in touch via the limit increase process; http://docs.aws.amazon.com/general/latest/gr/aws_service_lim... .

Obvious question: Why don't we enable ALIASing across zones by default? Firstly, zones which can be aliased to have to be replicated and available in all shards of our partitioned datastore (some day we may use some kind of cross-shard query protocol to resolve that, but even then we'd prefer to minimize the traffic) and secondly we want to ensure some stability for ALIAS targets and avoid situations where targets may be discontinued or deleted by their owners leaving our mutual customers stranded.
Indeed you are right. That's even more depressing. :)

I get that maybe more people are interested in the trackpad but I don't see why Lenovo improves the pad at the expense of the trackpoint. I disable the trackpad on my laptops so there's a net loss for me when they degrade the trackpoint buttons.

If they insist on degrading what distinguishes a Thinkpad then they'll be yet another generic laptop provider.
NVM install on Ubuntu 13.10 causes login loop