skysight-inc/HackerNews huggingface dataset:
They might, but as many HNers can no doubt testify, many of us use VPNs for remote work, and I know a fair number of government workers who do this, too. It isn't optional; it is a requirement.
What? In the original it was written in all caps as well.
Fancier than what we get in the Navy. :(
It seems so easy to pick up that I wonder whether it's wise to restrict hiring to those who are 'Go developers'.
I wonder how large percentage of tor exit nodes (and nodes in general) are operated by intelligence agencies? I remember reading that the various agencies across Europe were active in setting up and running mixmaster remailers -- and the (stated) purpose of TOR is to be a viable covert communication channel for spies.

Remember that a "node run by the CIA", can just mean that the ph.d. student that required some resources from the IT department has a handler. Said student might even think the thing isn't monitored -- although I suspect it would be easier to to involve the admin, then keep him/her in the dark.
I think, the best time to find hackers would be before killer applications[1] written in that specific programming language starts to appear. After that, time will pave way to The Go paradox[2].

The best places to find these people would be golang-nuts mailing list, /r/golang, #go-nuts irc etc.

[1] https://en.wikipedia.org/wiki/Killer_app

[2] http://www.paulgraham.com/pypar.html
You can look on the google groups, called go-nuts, and see how many devs are subscribed.

I wouldn't worry about an active market of Go devs to hire. If a language is any good, it'll attract developers. If you're a programmer, you should try out the language to not only do things you can do in other languages (to see how it fares), but more importantly, "What are the new things I can do with Go that use to be hard, but are now easy?"
> We've got it made.

That's one way to look at it. Another way is to ask yourself whether we could've been much farther ahead, as a civilization and a species, in terms of quality of life, human rights, technology and science, and so on, in 2013 given what we had accomplished already in say 1913, or even 13. I think the answer is a solid yes, we could've been 100 times ahead of where we are now. I wouldn't congratulate ourselves just because we have some professions where people don't suffer injuries at work, that's a pretty low bar we should've crossed ages ago. (I realize this is a tangent and I'm not really arguing against your main point...)
Another alternative is 'ts' which is part of joey hess's awesome collection of unix tools, moreutils.[1] I did not find out about ts until too late so I am still in the habit of using tai64n from djb's daemontools, which adds a tai64 timestamp to every file[2] and then tai64nlocal[3] in order to convert the timestamps to something useful to humans.

If you don't know about moreutils check out the collection. I don't know what I'd do without vipe or vidir:

Chronic: runs a command quietly unless it fails
combine: combine the lines in two files using boolean operations
ifdata: get network interface info without parsing ifconfi
ifne: run a program if the standard input is not empty
isutf8: check if a file or standard input is utf-8
lckdo: execute a program with a lock held
mispipe: pipe two commands, returning the exit status of
parallel: run multiple jobs at once
pee: tee standard input to pipes
sponge: soak up standard input and write to a file
ts: timestamp standard input
vidir: edit a directory in your text editor
vipe: insert a text editor into a pipe
zrun: automatically uncompress arguments to command

[1] http://joeyh.name/code/moreutils/

[2] http://cr.yp.to/daemontools/tai64n.html

[3] http://cr.yp.to/daemontools/tai64nlocal.html
According to the linked article, in order to understand Windows' behavior vis-a-vis drive letters and subdirectories, one must first:

> Set the wayback machine to DOS 1.0.

About the problems modern Windows versions create for us, no more revealing sentence was ever penned.
Ow, I didn't work with async.js ever. Does it work with nodejs as well?
That's also true. But having the ability to hire people who can hit the ground running with production code is an advantage.
I strongly disagree that reversibility is a small feature. Whenever Plugging the chargers to new iOS devices is effortless the same way as headphones jacks.

Non-symmetrical connectors are an affront to usability.
Go still hasn't found a niche to be useful to. Nobody's giving up 30 years of C for systems programming, nobody's going to use Go for web apps when higher level languages are clearly more practical, nobody will give up Haskell for scientific and massive parallel programming. All in all I think Go is an interesting experiment but it serves no purpose that I can use right now
I've spent the past couple of months working with Go, coming from a mostly C# and Python background. One of the attractions to the language for me is that it's straightforward to pick up. Because there aren't a lot of "fancy" features in the language like Linq or list comprehensions, it's easy to dive into a block of code and figure out what's going on without requiring a lot of background knowledge.

The language eschews some brevity in exchange for clarity, which gives me a lot of confidence that I can take a good developer from any background, give them a week and feel like they've got a decent chance of acquiring the knowledge they need to work with the language.

The newness of the language means that there isn't a huge ecosystem of libraries available, BUT the standard lib is pretty damn great, and there are more and more people coming to the language every day.

My favorite thing about go is it's overall sense of boringness - Go code seems very predictable. There's a culture of digging into the source throughout the community, and tools like go fmt & go vet ensure that most code looks similar.

It'd be worth spending a week with it to write something useful to get a sense of whether or not you truly like it, but my experience has been very positive so far.
Further reminds me that if you love something, even an everyday item, researching it's origin can be rewarding.
How to Create Data Products
https://profiles.google.com/114134834346472219368/buzz/YT9BZ...
I agree with this sentiment. Learning how to cook teaches you how to appreciate food, and helps you think differently about how food is prepared and even consumed.

Learning how to code, even if you don't become a professional programmer, will help you appreciate the software you use. It may also help you think differently about life, become better at problem solving (debugging IRL!), or at minimum, get frustrated at all the software you use on a day-to-day basis, because you know you would have designed it better. ;-)
Those cookies would be blocked for browsers with 3rd-party cookies disabled, and Firefox is making that option the default at some point in the near future.
Since when did Apple care about not having to replace your iPhone?
An Attempt at Making Reading Fun
C/C++ is the language of choice for scientific and massively parallel programming. as far as I know Haskell is not really competitive in that area.
Disclaimer: I'm not a type expert.

It's technically not written in all caps, the font that my blog theme uses for bolding renders as capital letters.

My personal jury is out on whether this is okay or not. Your comment leans me towards "no".
My problem with it is how frustrating it is to write when you're not very familiar with it, but I suspect that's more of a generic complaint about learning a new language rather than soecifically about Go. Every line I write, I go "argh, I wonder if this is the idiomatic way to do this" and I get frustrated a lot.

I love the features, though, especially the concurrency ones. It was conceptually trivial to write a multicasting TCP proxy in it.
I dig it the design and the story. But it reminds me of the new MySpace design.
I'm scared of a future where you witness a crime with video capable glasses on and be hunted for having the incident recorded.
Tap works well on iOS.
http://en.wikiquote.org/wiki/Cardinal_Richelieu
If you need performance why not go with scala. The play framework is super easy to use. Anyone who is familiar with mvc will pick it up very fast. There is also Martin Odersky's course which is a great intro.
Edict on Maximum Prices (301 A.D.)
Report: EU to Fine Microsoft over Browser Bungle
20 Ways Of Training The Mind On Positive Thinking
Lowest clearance for an analyst.
Self-awareness by numbers
Sure there are. But we could apply Dilbert's management theory to this and split governments to types on axis good/evil (G/E) and on axis competent/incompetent (C/E).
The worst thing you can have is an evil competent (EC) government.

Therefore I'd say it's more important to have an I government than a G government, because it is easier for a government to go from G to E than it is to go from I to C.
> You say "guess at some we dont". Well, we do know all about human failure.

You miss the point. We can continue to merely enumerate possible error scenarios until the heat death of the universe, and we will still miss some.

It is "human error" for an operations team to not put in place methods for ensuring their systems stay up within agreed parameters.

But the reality is that it is not even theoretically possible for us to engineer a system which can guarantee no downtime. Furthermore, no organization is willing to pay the bill to address even a relatively small fraction of the problems we can easily predict for the reason that many even relatively likely reasons are more expensive to protect against than is worth.

So to begin with, we can't prevent failure. And even if we could, what from the outside looks like human error is often internally a result of either intentional budgetary constraints, or unintended consequences of lack of resources.

It is not about lack of responsibility. It about dispelling the fantasy that there is someone who is guilty of not doing their job correctly behind every failure.

That is not to say that there might not have been unacceptable human errors in this specific case. But that is entirely besides the point.

> but not so in this case?

I thought it was pretty clear that my comment applied to the general statement that "human error is unacceptable", but perhaps not. I explicitly wrote "It's very well possible that Cloudflare messed up here" because I didn't want to speculate on whether the specific problems in this case before the causes were even known.

> Most of all, what I dont like is universal get outs.

They are not "universal get outs". Nobody is going to say it is acceptable if the error is caused by someone bringing coffee into the ops room and spilling it all over the single server, for example. But there is a vast range between someone who is grossly negligent and/or incompetent and who should bear the blame, and someone who is doing their job as best as is reasonable given the resources available to them, but who still makes mistakes or oversights or simply don't have the time or resources to address some reasonably unlikely issue that eventually happens to cause downtime.
That assumes working extra hard in your younger years makes you rich before 30, which in a vast majority of cases does not happen, no matter if you work for a startup, bigco or on your own.
My favorite quote from this talk is his comparison of the skate boarding community to the open source community (starts around 12:30)

"What is it to hack? It's knowing a technology so well that you can manipulate it and steer it to do things it was never intended to do.

And they're not all bad. You can be a Linux kernel hacker, make it more stable, more safe, more secure. You can be an iOS hacker, make your iPhone do stuff it wasn't supposed to. Not authorized, but no illegal.

Then you have some of these guys. What they do is very similar to our creative process. They connect disparate information and they bring it together in a way that a security analysis doesn't expect. It doesn't make them good people, but it's at the heart of engineering, the heart of a creative community, an innovative community.

The open source community, the basic ethos of it, is take what other people do, make it better, give it back so we all rise further. Very similar communities, very similar."
Google Chrome unsharp font rendering bug
Excel + Dropbox + synced Google Calendar.
As Ted already explained, I'm advising companies now. I enjoy this work greatly.

Programming is my hobby, now. It's fun and it informs how I work.
The issues I find with TOML:

https://gist.github.com/espadrine/5028426
but when you struck it out, the first impression is that it's actually not a problem, but in fact it's even a bigger problem. right?
Treat it like learning how to speak a foreign language (e.g., Spanish). There's obviously too much to learn, and it is easy to become overwhelmed. However, you can learn bits and pieces at a time. Just learn things as you go, and as you need them ("just-in-time learning"). If you learn a new skill or concept (e.g., OOP) make sure you practice it often so you remember it.

Over time, you will accumulate knowledge. Someday, you'll look back on today and realize how much you've learned, but you'll still know there is so much more to learn.
Good ticket system for startup?
I'm currently, as many of you, working on my first startup. Things are getting better and better, but now I think I should better have some kind of ticket system for communicating with customers, etc.

Now I could use some system like OTRS, Kayako, Request Tracker - or an hosted one like Zen Desktop.

What would HN recommend me?
The Success of the Social CEO
thanks for this post. i found it heartfelt and insightful, much more so than most of the dribble that crosses my screen daily.

the reality is that your dad knew he had to man-up, and being proud of himself and his family was his motivation.
So what does Lightning Digital AV Adapter do today that could not have been done using Micro USB->MHL? Looking at the reviews the Apple solution is a) pricey b) over engineered and c) performs worse than MHL. And you are talking about Apple haters creating a reality distortion field?

One way you could defend it is to promise features that can be programmed into the adapter firmware but if today it does 720p poorly I see no reason to believe something much more useful/better will come later. I am paying the $50 today, not in the future.
Not really related: But if someone is interested: I'm building an anycasted dns service.
I think we agree! I state rather explicitly that it took me 15 years of hard work and network building to find myself here.

However, I cannot rest on my laurels and for the record I'm just getting started.
Unfortunately, even Tor is not perfect. It obviously cannot prevent end-to-end correlation, and it also turns out to be very hard to do Tor right (e.g. not leaking information in the data streams).
If I read ts source right, it merely prepends the current time to every line it echoes from stdin to stdout.

now is different. It re-prints current time once a second while waiting for the input. You basically get the running clock at the last line of output.
I view it less as a cost factor and more as a convenience. Developing expertise with juniper and Cisco takes a lot longer. Each router vendor has its own quirks. Even just buolding software to monitor routers is basically a full time job since its a constantly moving target. New bugs are always coming up....
If you enjoy coding for other people as much as you enjoy coding your own projects, then we are wired very differently - and that's just fine.

However, I have found that many of the things I used to think everyone could do are in fact skills that I now get paid to use because they can't do them. Go figure.
Because you can live without all of those except for one.
This reminds a lot of Milton Friedman's pencil story (http://youtu.be/R5Gppi-O3a8?t=15s)
Marissa Mayer is no role model for female empowerment
Wonder probable reasons of major Amazon cloud outages?
Jason Russell: Kony2012 and the fight for truth
Funny they should mention this, when I first went to college I majored in Horticulture, the idea being that I would one day be an organic farmer.

Turns out that's a lousy way of learning the trade. They'll teach you a little bit of the hands-on stuff, but pretty soon it's all plant physiology. If you really wanted to learn, you had to go out and farm, not learn how the Krebs cycle works.

So, after having worked as a farmhand for a few other farmers, I dropped out, tried share-farming for a while. Worked well, other than the fact that the drought in Texas was breaking records, which wasn't good if you're growing vegetables, not to mention the high-temps and a lack of a greenhouse. In 6 months I was pretty much done for.

Still, I learned a lot, so much so that I figured I was probably smart enough to major in something more intellectually stimulating, so I went with engineering, found out I like programming a lot, and eventually settled in Computer Science.

Long story short, I think he's onto something, farming isn't just physically demanding, it requires thought, especially if you don't want to use nasty chemicals. I may not be the best coder in the bunch, but I've found I can figure it out a little faster than classmates who brag that they learned their first language when they were in grade school. I learned my first language, C, when I was 21.
I wish we had these type of programs in my Country...
I have a master's in Electrical Engineering and I'm a genius.
I think the solution to this problem probably doesn't involve trying to track down these bad nodes. Rather, more people should host Tor nodes, so as to reduce the chance of someone connecting to a bad one. As big as intelligence agencies are, they cannot operate too many nodes easily - the more nodes they operate, the bigger the chance that someone notices suspicious activity going on. On the other hand, there are a lot more civilians who can host Tor nodes without it being suspicious, thus dealing with the threat of intelligence agencies.

I'm curious about what the exact ratios would be, if there were a way to find this out (probably not).
I personally prefer osTicket. I have not tried OTRS but I have used Kayako which isn't too bad either.
I had the same problems when I first started learning the language, and while I'm certain I've got a lot more to learn I found that making a habit of reading lots of source code made a huge difference.

After a little while you start thinking about "can this code be clearer? Are the intentions obvious?" and that makes the code much easier to write.

Go is incredibly easy to refactor, so instead of worrying about being exactly right, you can focus on "is this easy to reason about?". My experience has been that this process will get you very close to idiomatic code on its own.
I agree with you. A small team of founders that are just developers who can design will outbeat ANYTHING that might have some VC money behind it.

You don't need business monkeys, or "UX experts" who can't code their JS/CSS. I hate it when iOS positions already have a lead designer who can't do Cocoa. It's such stupid notion.
It's like saying we're looking for a CSS developer, we already have a lead HTML developer.

iOS products are logic + design. And a developer who can design is far more useful, cheaper and faster than a developer + ux monkey.

http://news.ycombinator.com/item?id=5181963

"I like programming a lot. If I'm away from it for more than a couple weeks, I start to miss it.

The software industry deserves to choke on a dick and die, however. Fuck bad code, micromanagers, dopey "startups" that expect 14-hour days on the assumption that 0.0x equity slices represent real "ownership", closed allocation, and regimes in which programmers don't choose their tools. All of that can go to hell.

As software engineers, we're a defeated tribe. We work for businessmen, get little respect in comparison to the value we add, and often are pigeonholed into roles that are 3 levels below our creative and intellectual ability. We do most of our work for managers and investors who think we're losers because we don't have their jobs.
To me, quitting programming is just running away. Programming was never the problem. We need to take control of this game. We need to take it back and make it good-- and fast."

Let the downvotes commence.
The point wasn't to keep it from US citizens, it was to keep it from foreign governments.
Having worked with more ticketing systems than I can count, the only ones I've ever worked with that were effective were completely developed in house to meet the specific business' needs.

I hate to advise that, but that's just my experience with it. That said, your need is only in proportion to how much your tickets/communication with customers affects your revenue.
This is pretty simplistic view of labor and significantly ignores many of the reasons companies seek contract labor or outsource projects for development. The first thing you learn in microISV is that you need to determine as quickly as possible what is the actual, underlying cause a client (that is not a friend or foaf) is seeking your services. It has been my experience that it is rarely or never "we need some coders because we can't hire any."
I'm not sure I really see a point in this. How are you going to forget the server's time zone when it's listed in the timestamps? It doesn't really make sense.
The Scary Hidden Stressor
Is designing a building art? What about a website?

How about directing an advertisement or designing the title sequence for a television series?

Is researching information for a historical documentary an artistic or scientific vocation? Is such a harsh delineation even suitable?

Level design for a game? Texture design? Concept art?

Designing the circuitry for a synthesizer?

Many people are creating art for a living, though you may not see it as such. In fact, the authentic problem could be identified as society's very narrow definition of what "art" is. Artistic vocations are all over the place, and the prerequisites for entering such a career are just as, if not arguably more demanding than those for "technical" careers such as software engineering.

There's also frequently overlap between technical and artistic vocations and they exist side-by-side for many businesses so I disagree with the notion that people can't make money selling art (including the one belonging to the parent poster).
In Portugal we adopted the same system, 5 years ago or so, and i can say its not working as good as in Germany, for young adults who live in rural areas they don´t have the industry to get an apprenticeship like you did,not everybody gets a chance to work with smart minds like you did, and have the adult discern like you did to make yourself useful at such early years of life. That´s is a good story, i can tell you that. But it does not means that its reachable to everyone everywhere.
This just goes to show you have very little knowledge of how farming is done in the US. Here farming is very high tech, in fact they have some of the most advanced land navigation and machinery there is!

Also your argument is based on harvesting of a product, only one aspect of farming, that is manly produced in third world countries.
From what I recall, a non polar solvent such as kerosene is used in the crude extraction of cocaine. However, it's very very unlikely that "cocaine is then recovered by evaporation" since kerosene is obtained by the fractional distillation of crude oil starting at 150C. Even if it were possible to evaporate off the kerosene to obtain freebase cocaine it would be amazingly dangerous.

The actual cocaine refining process, I believe, is a fairly typical polar/non-polar acid/base extraction.
The niche I think go appeals to is Python/Ruby/NodeJS developers who are intimidated by systems programming (eg: C-style threads, manual garbage collection) but still want to work in a statically typed environment.

Goroutines and channels in particular are an interesting and useful abstraction away from threads and communication between those threads.