skysight-inc/HackerNews huggingface dataset:
I guess that you need to hire Portuguese or Brazilian programmers to write programs handling names. They have both accents and long names. https://en.m.wikipedia.org/wiki/Portuguese_name:

"It is not uncommon in Portugal that a married woman has two given names and six surnames, two from her mother's family, two from her father's family, and the last two coming from her husband. In addition, some of these names may be made of more than one word, so that a full feminine name can have more than 12 words.
[...]
For the sake of simplicity, most Portuguese people have two surnames"

Those Portuguese/Brazilian programmers will not forget to accept short names they may use a nickname. Examples from football are Edson Arantes do Nascimento (Pelé), and the various Ronaldo's and Ronaldinho's. http://www.telegraph.co.uk/sport/football/teams/brazil/78105...:

"Back when Ronaldo, he of the record for most goals scored in the World Cup, joined the Brazilian team, the squad already had a Ronaldo, a defender. So Ronaldo became Ronaldinho. Then another Ronaldinho came along, and they called him Ronaldinho Gaucho, for the area in Brazil where he was from.
When the first Ronaldo was done playing, Ronaldinho became Ronaldo again and Ronaldinho Gaucho lost the Gaucho. (For everyday use, that is. He's often listed as Ronaldinho Gaucho in squads, and his official website is www.ronaldinhogaucho.com.)"
I mentioned this elsewhere in the thread, but here goes:

https://zwischenzugs.wordpress.com/2016/01/24/ci-as-code-sta...
https://zwischenzugs.wordpress.com/2016/01/30/ci-as-code-par...
https://zwischenzugs.wordpress.com/2016/02/25/922/
I think it's harder to argue colonialism for Wikipedia specifically, given that they go out of their way to provide a plethora of sites for as many locales as they can, presented in a way best suited for their locale. Similarly, Wikipedia doesn't strike me as particularly interested in market capture and selling information behind the scenes. But, on the other hand, of the big names, WP seems to be the only site with this approach.
Chinese internet is as bad as the English one (plus a few funny expressions to avoid censorship—frequent use of certain puns for restricted subjects for example). My Chinese internet experience is largely relegated to the Chinese Dota community though, and Dota players in general tend to have a higher percentage of trolls. So my sample is probably biased.
>I call BS on this one, everybody knows radar cant go through cars/walls

Who says you need to go through them? People leave doors open a lot and most rooms have some kind of duct or opening at thresholds.
Yes, software is harder to manage (long-term) when the primary interface is a GUI.

However, the new Jenkins 2.0 fixes many of the issues you've described. Build pipelines are a major new feature, as well as the integration of a "Jenkinsfile" which allows configuration of jobs via a proprietary DSL.
Write you a Haskell: Building a modern functional compiler from first principles
"nah" is a perfect example of what i'm talking about. a tiny little passive aggressive textual slight that would go unnoticed by most, but allows you to exercise a smidgeon of that petty vindictiveness you are so incapable of dealing with (or delivering correctly, i suspect...) in person.
I thought it was particularly interesting when the author talked about differing reactions people had when taking psychiatric medication. It then seems that the effect of psychiatric medication has more to do with the person's frame of mind than any actual effect of the medication.

According to the author, if the patient rejects the doctor's authority, the patient can react even more violently when put on psychiatric medication. Even more interestingly, the author goes on to suggest that patients who do take the medication take it to placate authority, rather than for perceived effect. The author uses the example of someone in a highly stressful job taking Xanax instead of marijuana because while they might believe marijuana helps more, they don't take it due to employer drug tests.

It leads me to this question: when doctors think a medication is working, do they think so because of actual beneficial effects seen in the patient, or simply because the patient is complying with the treatment?
All you have to do to make tons of money is buy whatever stock that will rise by the most next week, and short sell stock that will tank the most next week.

How to find out which stock will rise or tank next week is left as an exercise for the reader.
Sex is how to hotfix mitochondria.
> Like, I've also had much worse experiences with some competitors where I'd file a report including a possible fix (something like 'change <= to <' in soure x line y), and 6 months later there even hasn't ben a reply let alone a fix.

cough Apple cough ...

A few years ago I reported an issue for iOS that _never_ got a response. When I made it to WWDC 6 months after reporting it, I went the support session and ended up running into the guy that wrote the bug. He was aware of the issue, it had been reported a few times, and he gave me a workaround until they released the fix. It was nice to finally get a resolution, but the whole process was seriously fucked up. After the fix was released in the next version of iOS they closed my bug report without a single comment.
It's cool that they're promoting the "pipeline" plugin to a built-in feature, but the devil is in the details.

Under the hood, it's implemented by taking a script written in a "DSL" (it's actually Groovy code), transforming it into continuation-passing style, and serializing its state. This is pretty cool from a theoretical CS perspective, but having played with it a little bit, the implementation seems very fragile. There are a number of long-standing unfixed bugs that cause the transformed code to misbehave in ways that you wouldn't predict just from looking at it, even if you're experienced with Groovy. I ran into a couple of them just during a brief period of experimentation. For instance:

https://issues.jenkins-ci.org/browse/JENKINS-27893 (varargs are mishandled)

https://issues.jenkins-ci.org/browse/JENKINS-28277 (currying doesn't work)

https://issues.jenkins-ci.org/browse/JENKINS-26481 (calling a closure in a loop doesn't work right)

https://issues.jenkins-ci.org/browse/JENKINS-28183 (killing a pipeline job doesn't clean up its state properly)

And there are inherent limitations to the approach; for instance, you can't store any non-serializable values in local variables, which means simple things like foreach loops don't work (because you can't serialize an iterator).

I really like the idea behind the Pipelines feature, in principle. But I think building it around a general-purpose programming language, and then failing to support all of that language's features, is a recipe for headaches. If you never try to do anything more complicated than what's shown in the examples then you should be fine, but the borders between what works and what doesn't are very ill-defined.

EDIT: Oh yeah, and there's a surprising amount of functionality that isn't documented anywhere except for blog posts and JIRA tickets.
Yes, but so what? Are you saying they should pledge to support expression of the best and the worst of the humanity?
If you're putting lots of logic into ANY CI server you're doing it wrong!

Script your build so that you can run it with a single command on any build server or any developer machine. Then have the build server invoke said scripts (with arguments for any build-server specific paths etc).

Having spent a week fixing problems with inter-plugin dependencies I do agree with your point - Jenkins just isn't very good, like a lot of the free software from that generation (FitNess etc).
Are you a Windows user who wants to learn how to use the Mac?
There's an amusing short story from the 1960s called "Computers Don't Argue" which this reminds me of: http://atariarchives.org/bcc2/showpage.php?page=133
Yes, they would own the copyright on the elements of the video that they produce. They wouldn't automatically own the copyright on any statement you made. The papers you sign would probably contain language much like the language on a random forum's ToS, discussing an irrevocable, non-exclusive, limited, global license to use any statement you make and/or to license the clips containing your statements out to partners. I've never been on TV, so I don't know. While it is possible that they try to get you to transfer the copyright to any statement you make, the courts are generally pretty dubious of such attempts.

Also, giving a presentation to thousands of people, whether at a conference or over a broadcast, is at least perceived a lot differently than leaving a comment on a message board, especially if it's a small one or a niche community, so different things are shared.

Suppose one is foolish as an 18-yr-old and posts on a forum most browsed by his friends, "Ha! I just got Lifelock and since I know you can't do anything to me when I have that, my SSN is 999-99-999. Just try to steal my identity!" Suppose the IA saves this statement. The OP would have a copyright interest in it and would be within his rights to point out that the IA has no privileges that entitle it to rehost that content, so please take it down. That is totally fair.

There is no reason that copyright law should only be usable by media conglomerates that mostly use it to stop the spread of free culture and not by private individuals trying to clean up some of their past mistakes.
being able to config jenkins via code is huge! looking forward to trying it
I have been managing remote devs for 4 years and now running http://devteam.space. So, have a decent expertise at that. Maybe you can apply it too. Here are must have rules:

#1. You need to have a PM for remote devs, on their side. Or decide who is the PM out of these remote devs. This person will be your trustworthy manager. If something goes not right, you talk to him/her first. Ask him to provide all the honest and bold feedback from himself and all the other remote devs if something happens.

#2. Request daily short updates from every developer. Just 2-4 lines of text about what have been done during the day. Explain to them that you will not actually reply to these updates. It's just to keep everything transparent. So, they write - you only read. Rarely reply with some questions.

#3. Set the goals on projects you work on with them, request deadlines, you can set it in sprints. It's like mini OKRs (google it if you don't know what is it). It helps them to be accountant and spend their working hours wisely.

#4. Have at least one 30 min call per week with all the remote devs to chat about what you are doing and motivate them with some good news. So they would feel they actually get paid not just for the code, but they make a difference for your company and for your clients. Share with them what you personally have done during the week. All people want to work with even better people, so it should be clear for them that you are awesome. They will respect you more. Basically, treat them as your usual team members.

#5. Use some reporting tools. At DevTeamSpace we have this kind of dashboard - http://i.imgur.com/F6Q3COn.png . Maybe it would be helpful for you too.

In fact, so many companies struggle to manage remote dev teams. If you need any help - ping me at alexey(at)devteam.space.
Almost nothing that you say here is true. I should know. I am good friends with all three of the original authors of Mesos: Andy, Ben, and Matei together. We sat next to each other for years while working on our Ph.Ds at Berkeley -- first in the ParLab/RADLab, and then in the AMPLab.

As a quick disclaimer I should mention I am now an employee of Mesosphere. I joined Mesosphere because I believe in the technology they are building, and it is certainly not 1-2 years behind everyone else. In fact, I left my job at Google to come here.

To touch on the exact points that you make. Andy would agree that Mesos was not purely his own "brainchild". Ben, Matei and Andy all worked on it together as a class project in the Spring of 2009 (I was also in this class, so was able to witness it all first hand).

Moreover, many of the ideas in Mesos were largely an extension of some of Ben's previous work on Lithe: a multi-level scheduling framework for managing multiple parallel libraries in a single application. I even took some of Ben's Lithe work and extended it for part of my Ph.D work. If anything, Mesos was the brainchild of Ben more than Andy in this respect.

As time progressed, Andy and Matei decided to focus more on Spark than on Mesos itself. This has lead to the (very successful) Databricks startup they created. Ben, on the other hand, decided to focus more on Mesos itself, bringing it to Twitter and now to Mesosphere in order to commercialize it.

Andys internship at Google has almost nothing to do with how Mesos has progressed over time. The internship itself was significantly after the initial Mesos paper was published, and focused mostly on evaluating the performance of Omega over Borg. I know this because I saw him give a talk on his work on Omega shortly after completing the internship. To claim that Andy took the ideas from Borg/Omega and applied them directly to Mesos is simply false.

To claim that Mesos is somehow stuck in the past is also false. It's true that Google and the AMPLab collaborated closely in the early days with people like John Wilkes and others giving lots of feedback, but Mesos has grown quite a bit since then. They haven't been simply sitting around warming their asses either.
This is great.

Sometimes the problems of open defecation are more complex than just a lack of toilets.

Here's a short article that mentions some of these:
http://www.irinnews.org/report/102414/when-shit-happens
In which case you end up with an FPM command line with so many flags, there's not a lot of difference to other methods.
This seems like a less sophisticated variant* of the AlphaGo approach. In both cases, Monte Carlo Tree Search (MCTS) is constrained by model for likely future moves. Here, they use a genetic algorithm. In AlphaGo, this is called the "policy network".

* This is not to say that these authors copied AlphaGo -- my uninformed guess is that this general approach of constraining MCTS has been known for a very long time.
Scalable System Design Patterns (2010)
I wish Gould were still alive to defend his theories.
There's definitely more profit in the stores. My understanding is that some of the stations actually lose money on the gas just to get you there so they can sell you stuff at the store, which is far more profitable.
UK forms which ask for a city and a county present the same problem for residents of London. US forms which ask for a city and a state present a similar problem for residents of New York. You're part of a select club!
this is doppppe
> A Western, American system might not be designed to accept names with accents and vowels because who has those in the States?

Here in Brazil, names with accents on vowels are common. Yet some banking file formats still use positional (fixed-length fields) uppercase-only ASCII files.

The format I'm thinking of also has a field in the header to specify whether the tape is formatted as 1600 BPI or 6250 BPI, so I'm inclined to think the cause is more technological than cultural.
New items for the FQA :-)
OK, but the point is that we have items that could plausibly fall into either category, not that I plan to start a racist periodical.
Join the AppDynamics team
Sounds like they're using an internal tracker not publically accessible... making the public one more of a pony show than anything.

Sadly, this is common for a lot of places (they're afraid internal discussions would get negative attention if made public in some tracker).
This reminds me of the (endlessly hilarious) tax protester argument that you don't have to respond to a court summons where your name is in all caps:
https://en.wikipedia.org/wiki/Tax_protester_conspiracy_argum...
No single person, has full purview and that is by design.

Even the President likely doesn't know every program comprehensively, not for lack of access but because it's so large that it would be hard to get all of it in such detail.
Great article, thanks!

Do you know if the Dataflow API is actually used internally as well? That's another thing that's a little confusing.
Is WebAssembly going to solve anything though? Most of what I've read about it is that it will be an accessory to JavaScript. Things like databases, video encoding, 3D rendering, etc.. Will we really be interfacing with the DOM APIs in C?

Even if that is how it plays out, we'll still have a dozen frameworks to decided between, at least one for every language that targets WebAssembly.
The Journey of Hello World Through the Haxe Compiler
Satellite / drone camouflage.

I'm certainly not a military expert, but it seems fairly obvious that China's military would benefit from being able to hide from high altitude surveillance. They're not doing a whole lot with these vehicles in combat at the moment, but masking their position and numbers seems like a pretty important objective for someone trying to build up an arsenal without escalating tension.
This is sick, and not the good slang version of sick.
The amount of genetic material passed on does not remain the same. Each offspring is an independent event, and which half of the genes gets passed along is selected randomly. So if an asexual organism has genes "A B C", then both it's two offspring will get "A B C". If a sexual organism has genes "Aa Bb Cc", and its first offspring inherits "A b C" from that parent, the second offspring could inherit "a b c" in which case the "B" allele is lost.
Sounds like NMI actually is TMI. Perhaps you meant NMN?
Sexual preferences that psychiatry considers mental disorders, like BDSM, fetishism and transvestism, or previously homosexuality and masturbation, usually have nothing to do with forcing anybody. Seems like much of psychiatry basically boils down to "we don't like this, so we consider it a mental disorder". As for the sexual stuff, I guess it comes from the old Christian idea that sex that is not for procreation is wrong, which is probably a result of agriculture. In an agricultural society, you want the maximum amount of children, I guess.

I find it fascinating that so many people are holding on to these obsolete beliefs (I mean, there are probably already too many people on this planet from an environmental point of view), although these beliefs do seem to gradually crumble as we speak.
Just my opinion, but AI should be controllable and should probably start by, as the "Bayesian brain" theorists say, developing a robust and reliable model of its environment. The Bayesian brain aspect of this is the belief that what AI needs to do is to minimize its own prediction errors.

I take that to mean that an AI should learn to be safe and predictable on human terms before it is allowed to start to diverge from human expectations. Even that sounds a bit scary.
As long as it only affects people who didn't vote for the governor, it's not the government's problem.
Here is some more information on the problem: https://news.ycombinator.com/item?id=11361398

Apparently some of the questionable responses are partly identical to months old tweets, so it seems in addition to some parroting 'vulnerability' (which was exploited by 4chan) they also had a poorly sanitized training set to begin with. It seems odd that this was not mentioned in this public statement.
Ask HN: How is kernel code tested?
Dimensional modeling, though often associated with a traditional waterfall methodology, is not tied to this delivery methodology.

It remains the most understandable model to the largest population of end users. Analytics is a very broad term, as I mentioned in my original post, and the audience is huge. If "analytics" to you implies an audience of primarily data savvy end users, then dimensional modeling may not hold as much value.

I tend to find that the data scientists at our clients still do a lot more data wrangling than data science when they don't have clean models to work with as a baseline.

Additionally, there's a big difference between exploratory analysis of new data sources where access and low latency are key, and well-known domains that have fairly predictable needs. The former have a habit of transforming into the latter. Dimensional models remain one of the most efficient physical structures of data for a read-dominant workload.

Long story short, I think it's worthwhile to both of us to look outside our bubbles. I work for a BI and data science consultancy. My focus specifically is in core BI workloads, and so I'm definitely overexposed to more traditional modeling techniques. I can guarantee you, though, that the cycle time for a usable pilot that includes a fully realized dimensional model is more on the order of a handful of weeks than months in a typical delivery.

What's your bubble?
Hipchat Downtime – An update on this week
> One thing I think many people are missing about the most 'inflammatory' tweets is that they are all pretty much the result of people giving it a command like, hey tay, repeat this [insert inflammatory remark.] This is indicated with the inflammatory tweets starting with an @ reply.

Hang on. You had to tweet the bot to make it say anything, and it would reply to you. So the presence of an @ reply means nothing - you can't tell from that if the bot was given a command or not.

Some of the threads were pretty clearly not the bot repeating stuff when commanded.
It is clear that build stages should be first class citizens. We based GitLab CI on the awesome work that GoCD and Concourse did in this respect. Our DSL allows you to assign jobs to stages https://gitlab.com/gitlab-org/gitlab-ce/blob/43e49f52e30199c... and jenkins seems to have picked a similar syntax.

What is interesting is that Jenkins has a DSL but that this is not part of the repository. This means that it is hard to extend when you introduce new functionality and when you push an old branch it might not work anymore. I think that the model that Travis CI pioneered clearly wins.

I'm torn on the plugins. One one hand it is great to be able to plug so much in. But the plugins have access deep into the Jenkins internals, preventing a rewrite of core functionality. Our idea is: "Because GitLab is open source the enhancements can become part of the codebase instead of being external. This ensures the automated tests for all functionality are continually run, ensuring that plugins always work. It also ensures GitLab can continue to evolve with it’s plugins instead of being bound to a plugin API that is hard to change and that resists refactoring. This ensures we have many years of quality code and great monthly releases ahead of us." https://about.gitlab.com/direction/#vision
Were you aware of the problems or potential confusion when changing it?
Thanks ^^
It's all about improving developer experience
>US merchants don't do this. Most of the ones who take a deposit (hotels, car rental) have signs at the counter warning that they may put a substantial hold on your cash if you use a debit card, which won't be released for quite a while.

My company used to send us on work related trips which were paid for in advance, but relied on us to provide our own cards at the hotels for incidentals. After a few (presumably less financially stable) employees used debit cards with low balances to check into hotels (effectively leaving them with no money during their stay), this policy changed so now the company credit card is used for hotel check-ins.

I personally hate the new policy because I have good credit and like getting room service, and for some reason I find it kind of emasculating that I'm not allowed to use my own card.
What makes you entitled to receiving somebodies money, though? If they feel they want to know about your home life, and you don't want to tell, why should they be obliged to give you money? It's fine if you want to keep it private, but other people have the right to spend their money as they wish, too.