skysight-inc/HackerNews huggingface dataset:
This is a pretty disturbing article, and I feel like Talese should have reported Foos to the local authorities. Foos is clearly a serial sexual offender, and should have been reported or at the very least put into treatment. Talese admits that Foos is an unreliable narrator and is pretty clearly a voyeur for sexual purposes, mentally shielding himself by saying, "oh, I'm just a researcher."

Journalism is one thing. This is enabling a predator, just as much as Foos' two wives.
When you need 31 galles of freshwater to make 1 gallon salt water drinkable, you have 32 gallons of drinkable water. Those 32 gallons are not wasted. When you make one jeans or a t-shirt, you may need many more gallons. You cannot drink that water afterwards, so that totally different.
If you call 311, TLC will slap a $300 fine on them, so taking out your phone and doing that will instantly fix the machine.
At around 5m/px, the imagery from planet labs doesn't currently have high enough resolution for it to be useful for tracing in OSM. It looks good only down to around z14ish.

But what they're doing is still really interesting. Their stated goal is to be able to image every part of the planet daily by the end of 2016. And it's possible in theory to process multiple passes of lower resolution imagery into a composite imagery layer with a higher effective resolution. So it wouldn't surprise me if they use their microsatellite approach to push into markets that are currently served only by hi-res imagery providers like Digital Globe (imagery from expensive satellites) and Pictometry (imagery from airplanes).
I'll add a few of my favourites:

- iOS Dev Weekly (https://iosdevweekly.com/)

- Little Bites of Cocoa (https://littlebitesofcocoa.com/)

- objc (https://www.objc.io/)

- NSHipster (http://nshipster.com/)

- NSBlog / Friday Q&A from Mike Ash (https://www.mikeash.com/pyblog/)

- This Week in Swift (https://swiftnews.curated.co/)

- Erica Sadun (http://ericasadun.com/)

- Quality Coding (http://qualitycoding.org/)

- Use Your Loaf (http://useyourloaf.com/)

- Swift Monthly (http://swiftmonthly.com/)

- Cocoa, Objective-C and Swift programming News aggregator (https://twitter.com/cocoadevblogs)
Adding some corn facts, as it's how most American soda is sweetened.

90% of the land area used for growing corn is not irrigated (100% green water) and in this case it's no trade off. It's not irrigated because there is adequate rainfall.
Can someone explain the history of the US worldwide tax regime? Why is the US so out of step with the rest of the world on this?
You would think so. But the reason for rudeness rarely comes up. To those on the receiving end, the damage has been done and in the case of racism or sexism it is falling into a pattern that screams "You are not welcome here" to the person.

It's like the people who get arrested while walking home from work because they happened to enter a protest area. The reason for their being there is totally unrelated to the protest yet the effect of their being there is to increase the size of the crowd by one.

We can argue until we're blue in the face that this is unjust and the truth is that it is: it's unjust for everyone involved. It creates further entrenchment and higher barriers between people.
Am I missing something? What the article describes seems to be the most common way people use GitHub with a git flow branching style. Is the contention just over the "would _have_ to" part? I think it's likely the author knows that GitHub doesn't _require_ this. And even if not, it doesn't seem pertinent. Doing a PR from a branch of [a clone of] the main repo would require basically the same steps.
Water vapor is lost to the vacuum of space, though it's obviously not enough to make a perceptible difference, at least on a human scale.
>Yet even by the Treasury Department’s own admission, the latest rules will not be enough to completely halt the flow of companies seeking to renounce their American citizenship, just as the two previous rule changes did not. Such a move would be possible only with an overhaul of the tax rules by Congress, which few believe will happen soon.

I would have loved to have more info about that. What other loopholes didn't this fix? What are they proposing Congress do in this overhaul?
> I just tell myself it, over time, subconsciously changed my thinking to make me better at grasping software.

I make the same justifications :)
It'll make things more difficult, I think - doubly so if you've missed computers or internet 101 - but not impossible. I have a good colleague (android / web developer) who majored in electronics engineering. Others are self-taught, although that may imply they've been using computers for a long time already. I'd have to ask around for more of such examples.
JSR and MOVE.D are also features of m68k, but the mnemonics don't seem to match the opcodes. Maybe it's "Coldfire".
GitLab Pages
Good post Fred. I thought the examples were good and I didn't have trouble understanding the point of the article. It made me think about similar ways that I've been mistreated and ways that I've mistreated others, especially junior devs. Software development is truly an exercise in patience and as an industry we need to put more value on some of the softer skills. I can speak from experience that positive environments lead to better outcomes.
We've been using Gerrit since 2011, and it's worked really well this entire time. It does require communication if you have different features in different patches, but frankly, it's light years ahead of anything GitHub still has to offer in terms of pure code reviewing capability.
One issue, at least at my company, is that we just don't need as many experienced people. We have some uber-experienced developers who do architecture and coding for everything "hard", and then a mostly-interchangeable pool of young people who do the easy—but bulky and non-automatable (yet)—stuff.

Honestly, when you look at a lot of startups, nothing they do is even remotely difficult. And they're filled with young people that can build on the hard work done by (now older) people on cloud platforms, with frameworks, tooling, etc.

So on the one hand, yeah, we (seemingly) don't need as many older developers. OTOH, when we do need them, young people aren't even an option.
Fair enough - I can't disagree with anything you are saying here.

Honestly, one of the more astute things you mentioned was not getting into this situation in the first place, "Assuming my situational awareness was so poor I hadn't started avoiding letting them get so close in the first place," - I take full responsibility for getting mugged - it was after dark, on a deserted sidewalk - and my lack of situational awareness, directly led to the miscreants getting close enough to draw down on me and relieve me of my possessions.

I lived in a much rougher part of Oakland (17th and the lake, in 98-99) for 2 1/2 years, and never once came close to being on the receiving end of a crime, because I was always hyper aware of my environment. But, you get sloppy on the peninsula, and look what happens...
What do you think the likelyhood of an actual trial would be without public outcry about the situation?

Don't get me wrong, in general I would agree with you. It is completely unfair for folks in the US (Think casey antony) to be forced into protective custody after being found non-guilty because of the media coverage of her court case, and even as a teenager I found the whole thing surrounding OJ as ridiculous. But in extreme cases, this is often felt as the only recourse, especially to those in power whom may have some influence over whether or not they will ever be sued or arrested.
Well, you are a conceited jingoist if ever i saw one.
I've seen co-workers upgrade their production macbooks to beta/pre-release OSX versions, and then get upset when critical functionality breaks and its an ops "emergency" to get it fixed.

Their warning is appropriate.
The Logical CX: What's Your CX Personality
More worrying than this to me is that they're removing the fglrx driver. I'd love to use the open source drivers, but the radeon and amdgpu drivers do not seem to be getting equal amounts of love and amdgpu only applies to really new video cards.
There's another reason I've wondered about. It's not politically correct. All the Ubers I've used had white or sometimes Hispanic-American drivers. But taxis have all (except for Portland) been either African (esp ~ethiopian), Palestinian, some region of India I can't place, etc. They're dominated by recent immigrants.

So I wonder if average young white couple on their way to dinner or whatever, simply likes the white-driver experience.
honestly this is not correct from a communication perspective. Literally this is a team lead educating a junior developer who completely oversteps his bounds and does not even understand why this is an issue.

In dissecting your statement, "it's important that this server is configured correctly, so I think it would be better if I took care of it myself, if that's ok with you"

clause one is ok, but does not provide a 'why'. clause two leaves too much leeway as to whether the junior developer action is acceptable going forward. clause three is actively negative as it opens up debate for something that is not up for debate.

a proper communication would have been to take the junior somewhere away from anyone else, made sure that the tone of voice was unagressive but authorative, and stated something along the lines that, this is not a major issue but we need to have an important quick conversation, first explain that number 1 what the issue is, explain number two the underlying why, and explain what will happen go forward, make sure he understands this is not a debate, this is you giving him direction on what will occur going forward, i would give him an oppurtunity to meaningfully contribute in the future if it made sense, finally make sure he understands.

being to flimsy or wishy washy is NOT good communication
The Logical CX: What's Your CX Personality?
ssllabs says a+? https://www.ssllabs.com/ssltest/analyze.html?d=current.com

What was broken for you?
There's a big difference between mental illness and intellectual disability. I supposed you could argue that they're the same and should be treated the same, but, in practice, they're treated and generally thought about very differently in the US.
...and replenished from space through slushball comets!
To me, concerns oriented toward authorization and general security would offer a more objective and policy based framework for the discussion. The zeitgeist is servers are cattle not pets and that deploying chaos monkeys helps insure robust infrastructure.
You're missing the point. If the benefit was equal to the taxes paid, there's be no point in having taxes. Taxes should produce a net gain, so the benefit needs to be, on average, worth more than the taxes. We need to look at the amount the government spends on them.

And yes, this will automatically be around as much as the average company pays in taxes. If the total spent is equal to the total collected in taxes, then the average company has as much spent on it as it pays in taxes. The differentiation among companies/individuals is government picking winners and losers. Just like the fact that the wealthy pay more in taxes and the poor receive more means the government is picking certain individuals to have more spent on them. There's nothing wrong with that, of course, it's just what society decides.
From who's vantage point? The end user, or the corporate sysadmin managing a fleet of desktops and laptops?
As a mechanical engineer who has worked with software engineers on projects, I believe that the nature of the job can cause us to be more blunt than most. When the guys in the shop weld something poorly they don't get points for effort, they redo the work.
Likewise, when one of my designs has a flaw I WANT people to point it out bluntly and immediately to save me hours of work, the company money and reputation, an possibly even lives if the equipment fails at the wrong moment.
My dad is in the field as well and we both have to put effort into not being overly critical of others outside of work. I can certainly see how someone who seeks approval from others could be beaten down by this. Learning to separate your failures from your self esteem, as long as you learn from them, is a tough skill. I honestly think that "girl culture", at least what was at my high school, makes this much more difficult.
More Favorites:

- iOS Cookies (http://www.ioscookies.com/)

- iOS Goodies (http://ios-goodies.com/)

- NSHipster (http://nshipster.com/)

- Cocoa With Love (http://www.cocoawithlove.com/)
>Sorry, learning social skills, learning to manage your time so you can meet people, etc. is not the job of an employer or a profession as a whole.

Didn't learn job skills, wasted a free k to 12 education, made bad financial decisions? Here, let society help you. We'll tax people to help fund a social safety net because there should be a basic standard of living.

Didn't develop social skills? LOL, LOSER! Why don't you try to teach yourself some social skills. You deserve to be alone until you improve yourself.

Crass and perhaps too blunt, but people should be able to get the basic idea of this double standard.
Depends on the textbook tbf - a lot of textbooks are really, really bad. Same with basically all sources of information. They pretty much all make assumptions about knowledge level, mainly because they're written by people that (think they) know a lot about the subject. In a lot of cases (the PHP tutorials online are a poignant example), they don't or spread misinformation (yeah just use mysql_query ololooo)
Delusions of objectivity
> but that still doesn't make it a code editor in your book?

The GP isn't saying this isn't a code editor. The GP is making a distinction between a code editor and an integrated development environment. The GP's definition of IDE is integrating editing, building, testing, debugging, etc.
I was surprised to see the mention of Rollout which I hadn't heard of which claims to allow you to push hot fixes to native iOS apps. Although I've been out of the iOS game for a while, I recalled this being against Apple's ToS. Apparently this is is still true to some degree, but they have an interesting blog post about how they can work around these restrictions.

https://blog.rollout.io/2016/01/updating-apps-without-app-st...
If you don't understand, then clearly you should investigate why as you cannot form an opinion on something you don't understand.
But they most likely also want proper compensation.
A very simple thing that Make does is when you run `make` it will only run the recipe if something has changed. Using npm scripts eliminates this (as I'm guessing gulp does as well).
If a company looks like it would hire based on age, best to look elsewhere and put it down to "their loss."

There are, I believe, many companies that do hire responsibly.

Disclosure. [mid 40s; with children;]
Ideally you put together a team of young and old where you get something more than the sum of the parts.
If you snap at someone because you are having a bad day you should apologise to that person or at least clarify that it's not personal.

Having a bad day is not an excuse to be rude to someone, especially if they are not aware of that.
I find the language "production desktop" a little interesting, as opposed to "production server". Is a production desktop the same thing as my dev box, which I use to develop and maintain production software?
They should charge executives Irish income taxes if they pull that off.

(While Ireland's corporate taxes are low, their personal taxes are ~59% over ~100k, and that _includes_ capital gains, and a lot of things that are tax advantaged in the states)
There's also a number of them who probably skip over "women's issues" articles. Likely not enough though...
While these are almost certainly bad, they are not all specifically related to being a developer. Mainly just poor treatment of an employee.

The article had instances where a developer:

- lost essential computer access privileges

- was forced to re-invent technology

- was denied chances to advance his/her careers through academia

- felt group shaming

- was expected to spend most of the day picking up pieces

- was fired without review

The last one is more general but these at least have a technological slant to them, and they do seem to be related to some kind of passive, cultural bias. And each of the stories might have some weak points but the point is that some developers feel they are being treated poorly, which is a big deal. This crowd is very analytical but a dismissive response is not really the appropriate way to address these claims. (Not saying you're being dismissive, just the general attitude of comments.)

Your comment also hints on another pattern which is, every time there are small problems, there are going to be bigger problems underneath.
Association Rules and the APrioi Algorithm
I have investigated, why are you assuming I have not?
I had trouble making that make cense to.

This mini-thread might remind us that most of us make spelling, grammatical and usage errors, we usually understand anyway, and we should usually forgive and forget.

Said as an old person who makes more mistakes by the day, and cares less.
Yes, and is just as critical as a server. When the server is down, you're losing money. When a dev is down, your company (or you) are losing $X/hr, based on your billable rate or fully loaded costs.
Great read.
But wanting to do everything themselves, led this duo to create a great innovation.
What started off as a search for an easy to use ECG device, that required no help from a medical technician, led these two engineers to develop one themselves.

https://www.youtube.com/watch?v=qIXFQaKL_F0?=hn
> This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems.
I'm collecting everything that might help a Swift developer.

I try to tag urls to keep them organized. If you want to learn about Core Image or SpriteKit, for example:

http://www.h4labs.com/dev/ios/swift.html?age=10000&q=CoreIma...

http://www.h4labs.com/dev/ios/swift.html?q=SpriteKit&age=100...

I also provide a weekly view that ends on Saturdays:

http://www.h4labs.com/dev/ios/swift.html?week=0

All the raw data is on Github: https://github.com/melling/SwiftResources
Jenkins should always pass master. develop is for things that need to be done but necessarily mean Jenkins is at least temporarily very unlikely to succeed and thats "OK" or even "normal".

Or another way to put it is develop doesn't even have to compile. I mean, it would be nice if it does, but its OK if it doesn't.

master might not do what the end users think its supposed to do, but at least it compiles.

Or another way to put it is develop is for big revolutions and master is for small evolutions.

git flow releases are supposed to actually do what the end users think its supposed to do. Or it actually does what they've been told to expect.

It provides a natural flow of code, from a feature doesn't work but its worth a share, to it compiles but doesn't implement business required feature #1243 or feature #531, to we think it correctly meets the business needs at least as of one definition of need at one point. Or another way to put it is a separation of development process of develop to master from the business requirements of master to a release branch.

I suppose everyone uses it a little differently.
Blame the person who chose to translate "petition principii" so terribly.

No one in isolation would interpret the Modern English phrase "begs the question" as meaning "assumes the desired conclusion as a premise"; the natural, "naive" interpretation is that it's synonymous with "raises the question". So why blame the reader for the translator's mistake?

If you need a translation of "petitio princippi", maybe you can use "assumes the conclusion" or "takes $premise for granted" instead?
Robocar rides may have to come with a dose of Dramamine
I had the same impression reading the intro; I was done after reading about Agile and consultants. In every single instance I've seen these two combined, mediocrity followed. Even in the cases where they thought they had agility the results were still terrible and unproductive.

Most of the time its people not understanding the tech they're trying to use and instead of spending the time to learn it they look for something they already know how to use or they'll pay someone to do the thinking for them which usually overlooks most of the company's context. I know I'm grossly generalizing but that's the trend I've seen so far.

They'll bash on Git for not being enough like SVN, bash on GitHub/GitLab for not having the same workflow of the previous tool. But will happily pay $200 an hour for someone to tell them what to use/do even if they end up making terrible decisions.
I'd think that even if they can't use the leaked data in a prosecution, it'll give them some very good ideas on who needs to be thoroughly audited, and will provide some useful information for financial patterns that might indicate illegal activity in future.
Right! Here in Iowa we water the corn the way God intended, by waiting for it to fall from the sky for free. I can always tell when flying to CA when I get into Nebraska, those huge 'crop circles' formed by irrigation start to show up.
I know Vuka (the article's author) in real life. I'll send him a FB message and see if he would be willing to answer some of the burning questions asked here.

Will update if I hear back.
Vacuum powered fluidic ink “LEDs” and circuits
Ability to Watch a project but only for releases #410
I was under the impression that younger programmers are desired because they are perceived as being able to work a lot of hours and because they are less likely to have the family commitments that would prevent them from doing so.
It's not necessary to always treat someone as a child. Nor should it be necessary to deconstruct everything.

Quick to the point explanations. No need to dance and coddle.

The junior dev has the right attitude (wanting to help) but if he thinks tweaking a server some else has set up is a way to help without having gotten some okay shows how green they are and have not yet attained necessary decision making skills.

I like the enthusiasm but I don't like the lack of awareness.
From the GP:

> Atom itself is a text editor, not a code editor, which is why I'm asking if this set of functionality crosses that distinction line. If Atom is capable of being a true IDE (code editor) then that would be big news.

And like I said, I consider Atom a rust IDE for the mentioned reasons
WhatsApp Just Switched on Encryption for a Billion People
Because I've yet to find a git graphlog tool which made viewing pretty nonlinear git history (as precise a historical record as they are) anything but a pain in the ass, some of them barely even manage to display a dozen concurrent "branches".

This is combined with most of the "historical record" really being worthless garbage: does it matter that you had to implement 12 fixups at various points and rewrite the whole feature thrice after requirements changed? Probably not. Does it need to be enshrined in the project's commit history? Absolutely not.
On the rise of data science startups
> You do seem to believe that transparency is a fundamental right. Its not.

I wouldn't frame the issue in terms of rights, but management that hides relevant information is fundamentally dishonest and disrespectful. I wouldn't call it criminally fraudulent necessarily, but it's in the same spirit, though perhaps in a more grey area.
Really annoyed by the tooltips for some reason in most JS visualizations. It is fairly easy to tell what the exact numbers are already.

I think it would be a nice touch to make the standard error bars pop out or something else interactive. On printed plots, error bars is perhaps the only thing that you both want and don't want that would benefit from the dynamic nature of these.