One more reason to for tech workers to start organizing.
2,052 karma · joined December 11, 2008
[ my public key: https://keybase.io/albertsun; my proof: https://keybase.io/albertsun/sigs/N-C7CzpCwwG774s6_TUKXbTFeGrVXlDv8X7W0bxLzC8 ]
One more reason to for tech workers to start organizing.
Same car has grown by 5% over 15 years.
Any qualified human review would immediately be able to distinguish and vastly improve both the false negative and false positive rates.
But because these tech companies devalue that kind of work they aren't willing to invest in it.
It seems as though that case is still pending resolution.
For backend specifically, on the CMS team there's this job https://nytimes.wd5.myworkdayjobs.com/en-US/Tech/job/New-Yor... or a fun one with the cooking team https://nytimes.wd5.myworkdayjobs.com/en-US/Tech/job/New-Yor...
> In a not-so-distant future, if we're not there already, it may be that if you're going to put content on the Internet you'll need to use a company with a giant network like Cloudflare, Google, Microsoft, Facebook, Amazon, or Alibaba.
For context, Cloudflare currently handles around 10% of Internet requests.
Without a clear framework as a guide for content regulation, a small number of companies will largely determine what can and cannot be online.
On the second, thanks for the reference, haven't read that. Would be interested to hear how you think that change would lead to these effects.
And if you think some central mechanism has gone horribly awry, what central mechanisms changed around 1980?
Come work in the newsroom of The New York Times and write code to shape the future of journalism. The Interactive News Team is looking for full-stack developers (ones with ops experience would be particularly welcome at this point) who care about the news and want to help make it better.
We believe in work-life balance, shipping working products, and open source. Working in a newsroom isn't like working at a startup or a big company. Try it, you'll like it.
Full job description: http://www.nytco.com/careers/newsroom/interactive-news-devel...
Apply by emailing newsdev-jobs@nytimes.com
More about the NYT: https://news.ycombinator.com/item?id=9038615
And the journalism and code commnunity: https://source.opennews.org/en-US/organizations/new-york-tim...
Our open source code: https://github.com/newsdev/ https://github.com/nytimes/
Other NYT tech jobs: http://www.nytco.com/careers/technology/
The actual reason links to studies are often left off articles (particularly in cases like this with sharp deadline pressure to publish fast before the competition) is that the software powering the editing and publishing workflow really badly needs improvement. An incredible amount of work and knowledge goes into a story like this.
Versioning rich text through many different software tools designed for writing/editing and publishing across many platforms is hard. Sometimes people copy/paste by hand and in doing so a link can go missing. The news industry needs more technologists to work on these problems. We're hiring for people to do that, by the way: http://developers.nytimes.com/careers/
(Also, the link to the study is now in.)
The desire to translate all nutritional research into diet advice is what leads to fad diets and horrific misunderstanding of what science knows and doesn't know about nutrition and metabolic pathways.
The New York Times interactive news team is looking for a dev ops engineer to work on developing our infrastructure for creating breaking news applications, cutting edge data visualizations and immersive reader experiences. We don't develop the core web site or mobile apps (though those teams are hiring) we work on highly creative, very deadline driven applications that sometimes need to go from concept to production in hours. We work mostly in AWS and are transitioning from a chef based environment to Docker. We believe in work-life balance, shipping working products, and open source. Working in a newsroom isn't like working at a startup or a big company. Try it, you'll like it.
For more about this job and interactive news: http://jobs.nytco.com/job/New-York-Interactive-News-Develope... (the description isn't quite right, it describes a generalist but we're looking for devops)
More about the NYT: https://news.ycombinator.com/item?id=9038615
And the journalism and code commnunity: https://source.opennews.org/en-US/organizations/new-york-tim...
Our open source code: https://github.com/newsdev/ https://github.com/nytimes/
Other NYT tech jobs: http://developers.nytimes.com/careers/
(Source: I work at the Times)
https://developer.apple.com/researchkit/researchkit-technica...
It appears to mostly be an iOS UI toolkit of sorts for easing the creation of individual apps to collect research data. The hard work must still be done by each individual research project.
With repeated exposure to URLs more people will learn how URLs work. Hiding URLs means that people will never be able to learn.
And I would guess that those skills are all very valuable, but aren't enough on their own. Lots of the hardest and most important problems and needs to solve in our world are in fields that require deep domain knowledge.
It feels like because so many startup founders don't have the patience to go into a field and acquire that domain knowledge everyone is focused on problems that yuppies have that can be solved by looking at a screen.
And for more substantial tasks it'd be possible to write an agent in another language and then call it from ruby in some way.
Those are very different things and they mean very different things in people's lives.
Perhaps wifi devices should no longer provide constant MAC addresses....
The family history profiled here http://www.nytimes.com/2013/05/13/health/seeking-clues-to-a-... sounds extremely similar.