skysight-inc/HackerNews huggingface dataset:
You know, having worked for a union in my youth, I was gobsmacked by the... I guess you'd call it indifference to the quality of your work. Your production has nothing to do with your job.

Then sampling the cutthroat nature of capitalism on the 'management' side of things, I understood what the unions were fighting for. (Even if I think they fundamentally fucked things up along the way.)

And now, as a vaguely paternalistic employer, I try to enact the kinds of things which unions would try to do (reasonable work hours, good wages, respect for the people working for me and their efforts on our collective behalf), and eliminate the failings of the union system (mostly by ruthlessly culling dead weight-- verboten in a union).

And all in all, I find myself concluding that management is an art, not a science. It can't be process-ized, or bound up by rules. The tyranny of Wall Street excel spreadsheets in bleeding workers dry is wrong. The indifference of unions to the economic output of the companies that employ them is wrong. And the people who can square that circle are not interchangeable cogs that can be replaced at will.
>Telling me "Because I want it to fade in on mouseover" is a fireable offence.

How about, *because it creates incentive to try out the highlight effect and subsequently click, until the novelty wears of, at least.
>I recently had a family party where I went running around like a mad person trying to make sure everything was in order. Having wait staff take care of my guests would have been great

That's what caterers typically do. So, while you seem to think you would not be interested, you go on to explain a scenario where you would be interested.

I live in a small town (e.g ~20k), and we have 3 catering companies I can think of off the top of my head. We also have lots of restaurants (more per capita than San Fran).
Contemplating on whether should I use ASP.Net webforms for my ecommerce site or stick with a no/minimum-coding required solution such as wordpress/drupal
PLEASE LOG IN
Speaking of emeritus employees: When do salarymen retire? What happens after that? Does the salaryman finally get to see that beach in Hawaii that his wife has been visiting every year, or does the pension not always stretch that far? Do the perks keep going after retirement even for the non-CEOs?
The Different Kinds of Facebook Murderers
I think it depends a lot on what city you're talking about. Cabs in NYC are awesome. Cabs in SF are atrocious. There's lots of variance in between.
I don't think you should try to become a 'professional full time investor' and put everything in index funds until you reach the ratio of funds that would significantly beat your current salary, compared to the average returns of an index market portfolio.

Lets assume the average return is %5, so if you make $200k/yr annually in your engineering craft, then you would need $4 million minimum to match the market for your salary, and probably at least $6 million before you would consider switching your career to 'managing your own money'.
You misunderstand the nature of the implicit argument. The allegory doesn't have to address the intricacies of bone accounting or the fantasies of bone accountants because the story it describes has already played out countless times in countless economic sectors with one overwhelmingly favored result. The burden of proof lies squarely on the shoulders of the person who believes that this time the story will have a different ending.
Just out of curiosity - is there a problem with sharing data across goroutines when access to/mutation of said data is controlled by a mutex?

func (*Mutex) Lock

Lock locks m. If the lock is already in use,
the calling goroutine blocks until the mutex is
available.

http://golang.org/pkg/sync/

It seems to me this is a valid alternative to [rigidly] sticking to pure message passing.
Maybe both in succession?
I've literally never had that much trouble with Uber. I also live in a city without decent cab service.
Both this article, and the Washington Post article it links to strongly imply that the Arkansas woman's credit was wrecked as a result of incorrect information about a drug conviction, but none of the three main credit bureaus report criminal convictions on credit reports.[0]

The author argues for his second reason that data brokers should be regulated because "many of the lists have no business being in the hands of retailers, bosses or banks," yet he fails to make any logical connection between the reason he gives and the regulations he wants. Ignoring for a moment the complete absence of evidence or facts to support his claim, his argument fails the most basic scrutiny -- his reason has nothing to do with regulating data brokers.

The segue from personality tests -- an odd digression, to say the least -- into hand wringing over the possibility of employers secretly using lists based on health conditions is just absurd. Enacting regulations to address a problem we have literally never seen happen is the essence of bureaucratic incompetence.

It only becomes truly spectacular when you consider that regulating the company that sells the data does nothing to prevent employers from doing it anyway.

[0] https://www.privacyrights.org/how-private-my-credit-report
I know that in Colorado, a law was passed in 2012 (or earlier) allowing people to prepare food in home kitchens as long as it's sold directly to the customers (i.e. not wholesale). This has allowed many small-scale food providers to sell their goods at farmer's markets.

Also, this could be useful for established catering companies which have commercial kitchens.
I think like most attorneys he would stand behind the law and he would also stand behind his client. In this case it would mean forcing the prosecution to prove that his client actually did this illegal thing as well as making the judge and jury aware of all mitigating circumstances.

That being said, it's quite common for attorneys to refuse cases they don't feel they can try to the best of their ability in good conscience.
>>(2) large yet maintainable systems

>>

>I have never seen anyone suggest Go for large systems or seen any open source code that even comes close to enterprise system size.

I might be moving the goal posts a bit here, but I think go's C heritage, and focus on message passing -- possibly coupled with something like protobuf or similar -- encourages breaking large systems into small services. So if you view a system as a "sum of functionality" -- I think one might still use go for "large, yet maintainable systems".

Now, it is of course possible to write micro services both in C++ and java -- but historically it appears at least in the java world, you end up throwing everything into a massive jboss container, exposing yourself to thousands upon thousands of lines of code.

With go, you deploy (relatively) small binaries, and a service can live as 20 binaries on one box, or as 20 binaries (along with some load balancers like haproxy or what not) across 300 machines. Or something in between.

I'd argue that some of the more sane java frameworks and projects also revolve around simplicity and separation of concerns -- typically leading to micro services. But a lot of people seem to end up working with large, poorly architectured beasts. That's probably more of a culture thing, than a language thing -- so I think people will make huge swats of unmaintainable go code as well...
> Why an engineer has to be paid, say, like three times than janitors?

Ask Mr. Supply and Mrs. Demand.
Reverse Engineering with Photoshop
It's sad that these sorts of responses are necessary. You'd think journalists would avoid such behavior, but you only start to notice it if you've been in the press.

Typically, resorting to misquoting and misconstruing only happens if a good counterargument to one's actual views can't be found. So I take it as an indicator of good (and possibly controversial) thinking if someone feels forced to respond in this manner.

Sam Harris has become quite experienced at handling this sort of attack, although he's had to spend significant time doing so.[1][2] Any victims of misconstruing might want to follow his style.

1. http://www.samharris.org/blog/item/on-the-mechanics-of-defam...

2. http://www.samharris.org/site/full_text/response-to-controve...

Note: I made a similar comment on the flagkilled version of this article, but I figured I'd respond here since it seems to be the canonical thread.
I think with "difficult" he didn't mean how physically taxing it is, but how hard it is to find people who can do it. Almost anybody can to the work in a sweat shop after a couple of days (weeks?) of training. Becoming a programmer is not something everybody can do and even for those who can it takes years of study before they are competitive on the job market.
Hey Kyle

Silver Fox Inspections is spelt wrong, thats just a minor edit.

Best of luck man, hope you make a success of it
PRs work. Pull requests serves to manage quality but also can find issues.
PCRE wrappers like the module you linked don't give other langs the nice regex integration available in Perl 5, they just give them support for "Perl Compatible Regular Expressions" (hence PCRE), a rough equivalent of P5's regex functionality:

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

But PCRE is 1990's parsing technology. Who cares if Nim copies parts of P5 regex via PCRE?

The page you linked says "Consider using the pegs module instead.". PEGs, invented in 2004, are more powerful than regex, PCRE ones or otherwise:

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

Perl 6 has Perl 6 rules, a unification of PEGs, regex, and lexical closures, built right in to the language. There's nothing like them in Nim, Java, or C++.

http://en.wikipedia.org/wiki/Perl_6_rules
Awesome. That's exactly what the big tech companies need to do if they want to break the media monopolies we have currently!
Does 767 LoC / 17KB really get to be considered tiny? I mean, sure, it's small and efficient.. but there are other contenders to consider, such as Fabrice Bellard's [0] tiny obfuscated self-hosting c-compiler in under 500 lines.

How can we unambiguously distinguish between what qualifies for the classification of a "tiny" c-compiler versus just a "small" one?

[0] http://www.bellard.org/otcc/otcc.c
If you consider C++'s standard toolkit to be Clang, Clang comes with clang-format.
OK, now demonstrate that this doesn't require fence instructions to prevent problems on superscalar CPUs (anything bigger than a low-end ARM today).
I have a friend who works at the American Cancer Society. They constantly have to refute the "[insert something here] causes cancer" myths. They do some pretty insanely large and in-depth studies on these things. They've even investigated the "your couch gives you cancer" myth.

In the end, they say that smoking is by far the biggest risk factor for cancer. After that, there's a "three-legged stool" of obesity + sedentary lifestyle + poor diet, meaning those things compound one another. Genes also have a measurable influence on your likelihood of getting cancer.

After that, very few things significantly increase your risk of cancer. A lot of it is just random. Most of the studies you see linking cancer to something are bullshit. My friend says you should be skeptical of anything shorter than 10 years and with fewer than 100,000 participants, and even then there are many other factors that go into gold-standard research.
I have definitely heard from multiple people that for them Rust was a good stepping stone to Haskell. Hopefully it will be the same way with Swift.
This is probably a dumb question; but, does this mean they're going to facilitate some easy way to find where the comment stream will be for their articles? For example, will technology be written to find out if an article has been posted on Reddit and automatically have a link to the Reddit discussion around it?

I would find this useful, possibly.
I'm totally with you on personally sticking with indexed funds, but, out of a sense of charity, could it not be the case that the average cost of your friend's failures is lower than the average returns on his successes, so that he is still getting above average overall returns?

I guess I just feel bad for him :-|.
It honestly sounds like you have some anxiety issues that are interfering with your sleep. It may even be that you feel anxious about not sleeping (and therefore having a lethargic day), which keeps you up.

You should certainly look into "sleep hygiene". If you religiously practice it, you may have better luck. Some of the recommendations are: no caffeine, no alcohol, get out of bed if you can't sleep, don't work in your bedroom, wake up at the same time every day. I can't remember the rest.
Just use int and it works fine:
http://play.golang.org/p/nZcd3M5aL_

To me golang is readable while even small rust examples don't feel quite right right.
I did work in a company that set its work schedule entirely based on Lotus Notes calendar. Hour-long meetings anytime but "lunch hour". Phone calls asking why I didn't respond to accept the weekly status update meeting invite. White boards and laptops newer than 6 years old were seemingly banned.
It's inconvenient to use Telegram on many devices (e.g. desktop/mobile), because their "secret chats" are not synchronized between them (e.g. your friends have to keep two contacts "kristofferR – Mobile" and "kristofferR — Desktop", right?).

If you are not using "secret chats", their default chats are not end-to-end encrypted, so are not comparable to TextSecure.
You guys disagree with the Japanese programmer because of the difference in cultural contexts. You see how "valuable" programming is compared to janitorial in the context of our culture. Western society (business people, aunts, and teachers) assign monetary (and other) value to programming skills.

The Japanese programmer was talking about how noble the jobs are. You may think the programmer is underpaid. The Japanese programmer thinks the janitor is undervalued (not viewed highly enough for the noble work that he is doing). He has his own cultural context, with its own emphases. Their free market reflects their culture- programmers and janitors are "valued" more equally than in the West.

He's also saying that a more egalitarian valuation is better than ours which has greater variance.
That's not the complete truth either. Where I live there has been a nurse shortage for a long time, but they're not paid better anyway.

Before you say education, some specialist nurses have almost as much education as doctors. They don't receive close to the same pay.

Most of the answer is cultural expectations.
Yes, there is com.google.distance.delta, the "distance covered since the last reading" (in meters). The platform also has a built-in stream of consolidated and cleaned up distance data points (without jumps due to a poor GPS signal etc).
Beta tester from the start here. QKSMS looked the way it does from the start. Two months into QKSMS development Textra released that update. They're both following material design guidelines, but QKSMS definitely had it first.
I googled the Colorado law you mentioned [1]. It wouldn't apply for the use case mentioned by the OP. It seems to be restricted to food "products", like baked goods or pickles. It has a lot of other restrictions that would make it incompatible with the OP's service.

I agree about the catering thing, but it doesn't seem like that's the core of their idea.

[1] http://forrager.com/law/colorado/
Eh, Microsoft tried doing the "one thing at a time" approach in Windows 8. It didn't seem to work out for them. One can argue that it was partially due to trying to sandbox their entire software ecosystem at the same time, but in my experience, it was just too jarring when you did actually need to switch tasks or use reference material.
Try magento, shopify and Mozu
Software engineer here living in Japan for about the same time as the author, and with almost the same work experience.

This article totally nails it.

I have bookmarked this so that every time a non-Japanese comes to me looking for advice related to moving and working in Japan (which I should mention, does not happen as often as it used to) I can just send them straight to this article.
Thanks for listing them!
See my comments below.

> Nullability

What do you think of boost::optional?

> Polymorphism

unique_ptr is probably the wrong choice here. You should be using ptr_vector:
http://stackoverflow.com/questions/9469968

> Reassignment/swap

The indirection and heap (de)allocation also imposes a slowdown, though. Have you actually experienced this to be worth it in some cases, or is this just a guess?

> Release

I don't think this is a valid reason...? This is a pretty common idiom for releasing value types:

Type().swap(existing); // release 'existing'
I feel this is a symptom of people coming from dynamic, higher level languages, who may or may not have ever really learned concepts of CS, "switching" to Go for performance reasons. I don't intend to insult anyone or certainly the authors of the above.
Go is type safe but doesn't keep you from shooting yourself in the foot. You NEED to read the spec to understand when sharing memory is generally OK. I'm glad not to be penalized in performance or boilerplate to accomplish this. The downside, of course, are stories like the above.
I don't blame the language here, though. They give you the tools to be safe. Getting away from automobile analogies, let's try woodwork. I can give you a drill, a drillbit, a screwdriver, and a screw. Sometimes you should know when to make a pilot hole, and when it's ok to forego this. But folks looking for 'performance' or 'ease of use', or folks who come from languages that just give you a nailgun, will inevitably split the wood a few times.
This doesn't scroll vertically on the Blackberry browser. You have to sweep right to find the special scroll bar, click on that (hoping you don't miss), and then sweep back left to read the new text. A few iterations and I gave up. Maybe I'll read it later, maybe not, but the page is, for me, a usability disaster.

Designers - please consider using widely tested techniques and systems so you are at least aware of the people you exclude.
> per-object vtable

You mean per-object vtable pointer? Or per-type vtable?
The article and the thread miss the point. Echo is a consumer / market research device. It gets an always-on sensor into some small percentage of American households. This could be used to collect data on in-home behavior in unprecedented ways. The seven microphones could probably be used to echo-locate walls, movement, and furniture positioning. The rest is up to the "always learning, in the cloud" part.
The 6 inch phones are impractical.
Your comment is so generic it is hard to argue with it. Also it is a fact proven by the growth of the gdp per capita and average living quality that economics in general is not a zero sum game.

Currently the overall number of programmers/computer scientists/coders steadily increases and still there is a large shortage of workforce in these areas.

Please provide citations to support that 'countless economic sectors/countless times' claim.
Another data point for you (I'm not the grandparent poster):

I prefer to write exploratory code and spec out the design as I go along, and I also prefer map/filter (or list comprehensions) to for-loops.

I suspect it does have to do with coding style, but not in the way you suspect. I like to write very small functions - often one-liners, rarely more than a page - and have each function do one thing and one thing only. I also tend to code mostly bottom-up, figuring out what abstractions I need, writing them, and then writing the functions that use them. So I almost never use an inline lambda for a map, it's usually a function I've already defined.

All of the exploratory scenarios you list are handled by built-in functions in my language of choice (Python). Breaking out early = itertools.takewhile(). Using the index = enumerate(). Inserting the log lines, I'd just insert them in the mapper (although there's also trace).
This is quite interesting. I am currently working on a Java based state machine and it solves problems in a very unique way. It is quite a change from procedural code.
I feel a warning is appropriate for JPEGs. Removing EXIF data would definitely not be considered lossless by most photographers.

Same goes for comments in all file formats.

Neat idea but I'd be happier to use it if I knew it was an unqualified benefit rather than having to think about whether it might strip data I need.
You can try using a tiling window manager with in a more traditional desktop environment. I think Awesome has a wiki article on running Gnome with Awesome as the WM.
who needs a special website, just use google[1].

[1] http://www.mydigitallife.info/search-and-view-free-live-webc...
Nvidia Knocks Cover Off the Ball with Q3 Earnings Report
Personally I'd be more wary of startups that have few external dependencies, because it likely means their trying to do too much that is outside of their core competencies and/or not spending as much time as they could be on their unique value proposition.

Sure you can run your own centralized git hosting for your team. Do you really think you could do it better and more reliably than GitHub? Especially for less than $7/mo? And sure you can probably run your own instance of postgres, but how confident are you that your backups are going to be there when you need them? And that it'll be up as much as a dedicated instance of Heroku Postgres? I can probably count the number of people more experienced and qualified than that team (wrt running Postgres) on my fingers and none of them are going to run your database for $50/mo.
> is there a problem with sharing data across goroutines when access to/mutation of said data is controlled by a mutex?

Well aside from the deadlock or priority inversion of sorts that should work. Just like it would work in C/C++/Java etc.

The real problem is when the shared data is not controlled by a mutex, but should be.
The main point of the article - that most mutual funds underperform the index funds is so widely known by now that I'm surprised to see it reposted here in 2014.

"The high failure rate should come as no surprise, given how hedge funds operate. There’s no working model, so they vary widely, but the basic idea is that they rely on risky, untraditional investment strategies—ranging from arbitrage to taking over floundering companies, as Lampert did—to make big money fast. "

No, that's not the basic idea at all. And untraditional doesn't have to mean risky (a market-neutral strategy is an example).
I propose the tinyness of a compiler is directly proportional to the number of comments spontaneously arguing it isn't.