skysight-inc/HackerNews huggingface dataset:
Any U.S. freelancers having problems with freelancer.com?
I was awarded a programming job for $10,000 on freelancer.com back in March for a client with a good reputation. I began work on the project and a few weeks into the project the client created a milestone for $2500 and released the funds. My account was already -$1,000 as freelancer.com was charging 10% for their fee being I am on a free account. When the $2,500 was released, I requested a wire withdrawal and it went through the process on schedule, then it was supposedly sent on 4/22 but I still have not received it.

As the project progressed, the client created another milestone for $5,000 and released the funds immediately. I made a withdrawal request, freelancer.com locked the funds to send it, just like the first $1,500 wire. The next day I received an email telling me my account is now limited and they wanted me to submit a government issued ID and proof of residence, like a utility bill, before they would restore my account and send the wire. They said this would be resolved within 24-48 hours of submitting my documentation. I sent a scan of my New York state driver's license and my electric bill. They rejected both of them.

I then submitted a bank statement and my New York state driver's license. They accepted the bank statement as proof of residence, but rejected my driver's license again.

It clearly states on their identity verification form that a driver's license is an acceptable form of ID.

I am posting this because I am curious if anyone else has had this problem. I am currently getting the runaround, nothing but canned responses (if any) from their support and their facebook page.

At the very least, I want to warn NY residents that if they use freelancer.com, they can expect similar problems.
Yap, makes sense, I see your point.

Haven't heard of mandatory dialyzer type coverage yet. It would be kind of commit hook of sort, still external to the compiler though...
A restaurant recommendation web app:
http://imgur.com/iTKXwrC
A Student-Data Collector Drops Out
The usual solution is headphones. And if you're not the type of person who enjoys constantly listening to music, well--the headphones don't necessarily have to be plugged into anything (besides your pocket.)
That looks impressive, addictive, and fun. Congratulations!
There needs to be a transcript. I can't possibly go through the entire 1 hour 52 minutes.

Is there a transcript available?
I almost never chat with people on transit, but while commuting via bicycle I've often had conversations with fellow riders. I wonder what the difference is that encourages conversation. I guess maybe the likely shared interest in bicycles is a good conversation starter?
That's what I was after... confirmation that it's a Tragedy of the Commons.

There's political ammo now to make necessary changes in how things are done to make sure OpenSSL, TLS WG doesn't continue with business-as-usual.
Yes it often looks like casual labour, occasionally we see someone from the depot though. They made a few mistakes at first, delivering to wrong address and leaving parcels in inappropriate places. They seem pretty much fine now.

They don't have the fancy tracking that some of the larger couriers have now (30-minute delivery windows etc) but they seem better than some of the super-cheap couriers (e.g. HDNL).
You could also just pay, if you find yourself on nytimes often enough to hit the paywall. Crazy, I know.
I find that my eyes get tired rather more quickly when using LoDPI displays. (I have a non-retina MBP lying around that I use as a distraction-free writing desk, and using it is kind of a pain.) I'm not sure as to the exact mechanics of why, but I do notice it.
fluff piece.
Ugh. What's most needed is a erlang-platform like haskell-platform.... bring together vital tools (proper/dialyer/etc), have a great package index (like hackage/pypi/rubygems) + package manager and have a skeleton project generator (rails-ish) that sets up what was asked for.

Convention > configuration

The easier it is to get going and contribute, the more people will use it. (Haskell pushed hard on this later on and has really benefited. Node did it early.)
Just listen2dance?
Crashed on Firefox for me too, saw two - the diagrams looked pretty.
Govt or not, I know many people and companies that would have an initial bias against individuals w/ certain tattoos. The ones that come to mind are people I know responsible for some of the initial screening and first person to interview with. Right, wrong, that is the sample set I am thinking about.

Shoulders down, rarely an issue on tattoos. Many times easily concealed.

Neck and up? There is a definite bias to get by. Even myself, I'd be a bit more hardcore in questions.
He pled guilty to the two misdemeanor charges; the 43 felony charges he pled not guilty to. The document is embedded there in the link.
I know what you mean; it doesn't [thankfully] happen for complex interfaces, but I maintain that it's useful (OP possibly overstates) as a composition of smaller interfaces. It's completely possible to write a type which satisfies http.ResponseWriter, both technically and in spirit, unintentionally while still being useful.

I've used it around a Stats interface which required a single method: Statistics() map[string]string and have been able to hook up otherwise independent code into a common logger. Speaking of loggers, the fact that the built-in log package doesn't expose an interface has always been an annoyance to me specifically because I can't build my own code and know that it'll satisfy a log.Logger interface in other projects.
I don't understand the aversion to tattoos in many workplaces. I have tattoos myself, one on each leg and one on my arm. You cannot see them when I'm wearing my interview clothing, but during the summer when I wear shorts and a t-shirt at work you can easily see them. When people see them, they don't expect me to be the kind of person that has tattoos.

By associating tattoos with a certain type of person before you even get to know their abilities means that you lose out on a lot.

The same goes for people who have differently coloured or styled hair. The lead developer for one of our products at the company I work for has a green mohawk, yet he's an extremely talented and knowledgeable developer.

Appearances have nothing to do with knowledge or ability. The quicker people learn this, the better for all of us.
I don't often get talked to on transit. However, I do often get ranted at. The drunk and the mentally ill ride the subway too--and, unlike in other places, you can't get away from them there.

The etiquette against talking to people on mass transit is a bit like the prohibition most religions have on murder: something you don't need to tell most people, because it's covered by their internal compass--but which is instead intended to suggest an orthogonal reason for holding back to the people for which that compass is broken.
Because in the real world, where all our code must actually run, quicksort beats practically every other algorithm on the vast majority of inputs. Its cache behavior is better than heap sort, its memory usage is lower than merge sort, and even its O(log n) memory usage is efficiently allocated on the stack as opposed to hitting a slow system allocator.

"Engineering a Sort Function"[0] covers this quite well.

In some experiments of my own, I've found that even Smoothsort[1] (an algorithm specifically designed to have a smooth transition from linear to linearithmic behavior on nearly-sorted input) can't beat the C++ system's introsort (a quicksort variation with a fallback to heapsort) in already-sorted inputs.

[0] http://www.skidmore.edu/~meckmann/2009Spring/cs206/papers/sp...

[1] http://www.keithschwarz.com/smoothsort/
I wouldn't bother correcting it. It's that company's own fault for using such an unimaginative name.
Why I Don't Drink
Same thing I've been working on for most of the past few years: my graphic novel about a robot lady dragged outside of reality by her ex-boyfriend.

http://egypt.urnash.com/media/blogs.dir/1/files/2012/08/Scre... - the WIP page of the moment

http://egypt.urnash.com/media/blogs.dir/1/files/2014/04/phot... - I woke up with a crazy idea about the final printed volume this morning

http://egypt.urnash.com/rita/ - the comic itself

A lot of the past couple of weeks have been taken up with getting the second printed volume to bed. For the second time, as I managed to let a terrible show-stopping mistake get past me until I was sitting back reading the advance copy, with 399 more on a loading dock in China. My first $6k mistake! Which I have done my best to make sure will never happen again.
Be safe!
This is well put, but I can't offer the same concession about "this" ... what exactly is the problem? It provides access to the state of the object on which you are working, if utilizing OO paradigms within JavaScript. Sure "this" values when executing pure functions in some runtimes make little sense but if you understand what "this" means with respect to OO, you wouldn't be trying to access it in that situation in the first place.
Ah, thank you. Where i was going wrong was declaring `foo_test.go` to be a separate package from `foo.go`. When i write `package foo` at the head of both `foo.go` and `foo_test.go` this works fine.
Javascript is a tiny language, but it pack a serious amount of gotcha.

If you learn the javascript way, you just realise that the core language provide little to no tooling around it. Like if you really want to fully utilise the prototype based inheritance, or the functional aspect of the language, you will basically have to write a whole set of utilities and extension on your own.

Of course, javascript run in the browser, is small and super simple, so it packs a lot of fun. To me it oddly reminds me toying with assembly in the old DOS 16 bit days and I like it despite its flaws ( and well those flaws are being addressed in latest iterations ) But the flaws are real, and if you need to use it on a big project with a regular team, and not complete freedom of choosing the browser you support, javascript will make you cry more often than smile.
LoL you have it backwards. Publishers do not have magical pre-cognition of the success of a book. We have myriad examples of them shoveling money at authors for books which bombed and we also have them turning up their noses at manuscripts which went on to earn billions. Case in point, Harry Potter.
Yep. Cost guard, customs, secret service, federal computer incident response, FEMA, law enforcement training, INS, biological warfare defense, national communications system, and more.
Not only did he really fuck up and act like a douchebag, he then insults the entire list and tells everyone "Don't tell me how to do my job." Seriously, this guys career in recruiting is over. I wonder if he knows that yet.
I frequently strike up conversations with strangers, cashiers, clerks, etc. I offer to take group photos so the cameraperson can be in the shot, like, several times a month. Why? I've never really thought about it, but it's probably for the very reason revealed in the study. It's just a habit that makes me a happier person.
Why do they have to shut down?

Why not just switch the model from gathering students data to creating the apps anyways and just letting the school take care of sorting out which app works best for who.

Seems to me like there could have been a bunch of better ways to handle this other than shut it down
Renamed to https://github.com/steakknife/devops_toolchain
to avoid confusion.

A collection of individual tools that can be cherry-picked to solve nitty-gritty problems.
The trouble with implicit interfaces is maintainability: suppose Awesome gets a func PerformAwesomeness() added to it: what then happens to the code that thinks myType is Awesome?

Not too bad when it's all in one source file, but get a few megabytes of code spread through a few thousand source files, and you've got a formula for chaos and heartburn.
Android Homebrew (as in beer) recipe application: http://imgur.com/ESyqCeq

Currently in read only mode, it reads recipes from the phone and I'm halfway through adding in the ability to download recipes. Links in with the desktop version of Strangebrew (available in Java and QT for all platforms), which extends to a Brewery controller, to allow users to send mash temperatures and times to the system.
> Easiest thing to do would be to ask him to add a build target for raring.

Many PPA developers have a policy of only supporting Ubuntu releases that Canonical also supports.

Official support for raring expired 3 months ago. AFAIK it didn't even get the Heartbleed patch. The correct thing to do would be to update to trusty. It might even turn out to be the easiest thing as well, because you'll run more and more into these kinds of issues as everyone else leaves raring behind.
I like that, what kind of pickups are you going to put on it?
I think it comes down to two things.

* Acknowledging that it has many many warts. Weak types, modularity, every number is a double, etc. some of those warts are there. Explaining why they are there historically doesn't make them go away either. "Oh but it was only written in 1 month so.." -- "Yeah it is still broken".

Many things can be chucked to "not broken but different". But, some are just broken, no sane language released after 1990's should not be this broken unless it was on purpose (brainfuck).

* Realizing that in practice, currently, there are not too many alternatives and just learning to use it. Like you say just getting down to being pragmatic. One can talk about functional purity but that doesn't usually bring food to the table. A finished site does.

But you see how the two are different. Many confuse them. For example, saying the language is fine and great just because they learned it and are using it. Yeah, at some level we want to feel good about the tools we use, so it is harder psychologically to say "this stupid thing I have to use every day". It goes the other way, just because the language is broken and there is some pure language, re-writing the site into might be very risky.

I personally am looking at Dart with excitement but at the same time won't be urging anyone yet at work to switch to it yet. Kind of a chicken and egg problem, I understand, we just can't afford to take that risk yet. But with time who knows.
People write MLOC monstrosities in Java because they can. You get some boring financial topic and some sub-par programmers and they'll write as much garbage as the language can possibly sustain.

These things are a testament to how safe and simple Java is as a language.

Not having massive crappy code bases is a negative sign in terms of how reliable and easy to understand a language is.
It's hard to get off the streets and back to "normalcy" (or dignity) if people pretend you don't exist.

West is becoming more like semi-urban India as the vice-versa... flattening.
The advantage is that it allows interfaces to evolve without having to muck around with setting up shared dependencies. In a language like Java, if library A and library B want to share an interface, you have to create library C for the interface and modify A and B to depend on it, and if you want to add a method you have to modify all three at the same time. Furthermore, changing an interface isn't backward compatible so the correct way is to create a new interface every time you make a change.

In Go, they can both declare the same interface or even skip formally declaring it and just agree to implement the same methods. Furthermore, if one of them decides to implement a new method, the other can just copy the method signature and they stay compatible. This makes it a lot easier to coordinate API changes.
Agreed about C# multiple interface handling. I'd really like to see something like that added to Go at some point.

In fact it's probably not that far away from where Go is now. Go already has something very similar for implicit composition / mixins. Now, if you do something like this:

type Foo struct {
Bar
}

Then Foo automatically has the methods of Bar, e.g. Foo.bar() instead of Foo.Bar.bar() although the former is really just shorthand for the latter.

If you then have:

type Foo struct {
Bar
Baz
}

Then assuming that Baz also has the method bar() then you now need to be explicit about it and call Foo.Bar.bar() or Foo.Baz.bar() because the compiler doesn't know which one Foo.bar() means.

Of course, this is slightly different to interface disambiguation, but there's no reason why you couldn't have two function definitions with the same name and some added interface qualifier - the functions would then only be callable if the object is cast to an interface. In Go, casting to an interface is a bit like boxing, as it creates a separate vtable for that object's methods to match the interface ABI.

Hence, you could have say:

a := Foo(foo)
b := Bar(foo)

Now a has a vtable entry for Foo::foo() -> a.foo() and b has a vtable entry for Bar::foo() -> b.foo().

On the other hand, there would be no foo.foo() method unless one were declared separately without any interface qualifier.
Is it Too Late to Get Involved in Bitcoin?
Playing devil's advocate: Let's be honest here - just like gender, age, nationality, political view doesn't have anything with knowledge. Well.. It kinda does, but in a different way. Just like anything else. This is system - if you do not fit in particular one - it become expensive and risky to try to fit you in. Why HR should risk, what is the point? They will find another developer who have more in common with their management expectations. And then we start talking about not just knowledge, but blob of characteristics under "company culture"...
http://i.imgur.com/677PMkn.jpg

Today I tested https://github.com/rbanffy/testable_appengine on Windows and thought I should add a mention to the README.

This is completely unrelated to my day job, but we all have hobbies.

Also, about a week ago, I fixed https://github.com/rbanffy/3270font so now it works with https://github.com/milkbikis/powerline-shell
I just don't like the taste of alcoholic beverages, and therefore I don't drink them.
Why I don't do X? Seriously, you can do what you want and i am sure you have your reasons. Why must we feel compelled to announce our choices?
I built, and am continuing to refine, a site that features one link (and accompanying discussion thread) per day.

http://puu.sh/8p3D5.png

I got the idea from an Idea Sunday thread, built the first version in a few hours, and I've been working on it on and off all week.

http://threadaday.github.io
Java's `final` while useful for primitives, it is not really that useful for reference types, which constitute the majority of types. C++'s `const` is a much better solution. Better yet, both Rust and D have superior immutability constructs.
Well, that wasn't their goal, and I doubt it is easy to displace the systems these schools are using today. The board probably felt that it would be wiser to cut their losses.
Consider cases where A is defined in a library that B depends on.

You might have Name and Location where Location is (latitude longitude altitude). Now you want to map things, while existing objects Trucks with Name and Location are easy you want also map stuff with a name and address. You can get a latitude and longitude from an address, but not altitude and adding meaningless altitude is IMO a bug waiting to happen.
Not to mention that alcohol is a major carcinogen in the United States. From the National Cancer Institute: "Based on data from 2009, an estimated 3.5 percent of all cancer deaths in the United States were alcohol related." [0]

[0] http://www.cancer.gov/cancertopics/factsheet/Risk/alcohol
The x in my name is more than just a delimiter!
This feels like a very "American" article [1], in the way it frames the discussion. The intro suggests the author has a policy of not drinking at all (or only every few months), but most of the bullet points only apply to why you shouldn't binge-drink. I did not find anything in this article that applied to normal drinking. If you drink a glass of wine with lunch, and one or two with dinner, as a typical southern European, you should not have a hangover or other such issues, unless you have a relatively rare (for those of European descent, at least) sensitivity to alcohol.

I'm slightly tempted to write a follow-up article with, "why I don't participate in bro culture", based on this article's pervasive reference to clubs, "certain intoxicants", and other such questionable things the author appears to indulge in, but which seem stupid and harmful to me.

[1] To be fair, the U.S. may have gotten its drunkards-vs-teetotallers attitude in part from Europe. Sweden in particular, and the UK some centuries earlier, used to have a very similar divide.
It's proper grammar. Blockchain is not a word according to any dictionaries that I know of.
http://www.lulu.com/shop/brian-evans/arduino-programming-not...

http://playground.arduino.cc/Main/ManualsAndCurriculum

http://www.neuroproductions.be/logic-lab/

http://shop.evilmadscientist.com/directory

http://www.seeedstudio.com/depot/

http://forefront.io/a/beginners-guide-to-arduino

http://www.learnerstv.com/Free-Engineering-video-lecture-cou...

http://www.electronics-tutorials.ws/

http://www.ibiblio.org/kuphaldt/socratic/

https://upverter.com/

http://www.afrotechmods.com/tutorials/

http://www.eevblog.com/wiki/index.php?title=Main_Page

https://www.circuitlab.com/

http://jacquesricher.com/NEETS/

get yourself a nice soldering iron and read read read
This makes me wish for a downvote button.
The word tattoo appears 3 times in this article, two of them in headlines. Nothing substantive in the article actually says tattoos sharply impact hiring. Can anyone cite an actual source?
> Almost everyone will at some point ask me why I don't drink, which is fair considering it's engrained into human society.

There should be no need to explain why you don't drink. Period. There's nothing wrong with not drinking and there's nothing weird about not drinking. If people are asking with any sort of condescension, you are probably spending time with the wrong people.
Everyone's got their vice. Some people have many. Alcohol just isn't yours. I personally love beer. I really enjoy it... but i have nothing against anyone for making the decision not to drink it.
I was about to post the same thing. A glass of wine with dinner, for example, can enormously enhance the experience without any of the downsides that he mentions. Not that I care if people don't drink, but several of the arguments were pretty spurious.
The author's not telling you not to drink, he's just explaining why he doesn't. It's OK for some of those reasons to be against specific kinds of drinking he doesn't want to engage in.
Agreed!

Also, Go-QML and gotk3 are probably the only two golang non-web, traditional "widget" type UI projects worth exploring if you want something to just build apps and not spend a ton of time hacking the library itself to do what you want.

There may be some decent ones I'm not aware of but all the ones I've looked at other than Go-QML and gotk3 are some combination of abandoned, not yet ready for prime-time and/or horribly flawed at some basic level of their design.
Fast Antialiasing (1992)
asking why someone doesn't drink doesn't imply condescension
Dear God, is it that bad? Sounds awful.

Does Bezos seriously forward any complaints received at jeff@amazon.com to the right person? I'll bet that is panic-inducing.
None of his points explain even from a personal perspective why he doesn't drink, though. Which of his bullet points explain the pros and cons of wine with dinner vs. not having wine with dinner?
>I go to clubs. I enjoy certain intoxicants.

Sounds like he gets high, but doesn't drink.
Wow, that's quite a list! Thank you very much!
Some companies, failing to differentiate themselves from fraternities, hold "drink-ups" instead of meet-ups. Sometimes not drinking ostracises you from a culture. (I have this problem in an even-more-conspicuous way: I don't like hot drinks, or the taste of coffee. This makes "let's get coffee and chat" a bit awkward.)