jeremyjbowers

Hi! Jeremy from The Post here. We’re still evaluating what it would mean for us to run an instance. But we’re definitely adding rel=me to our author profile pages ASAP.

I did! We had a brainstorming. It was initially (during development) called "Shazongress" but we couldn't get that one out of committee.

Hi! I'm Jeremy, one of the developers.

We'll probably work on something like this for the next version. One reason it's harder than you think: We would have to buy / own rights to the photographs before we could use them to train -- most of those photos are owned by Getty or the AP. And our own photographs are perfectly lit and square, which made them awful for training face recognition.

The other hangup (which I didn't get to in the article) is having to add / remove people. New members are constantly being added and that's a maintenance burden for us. Amazon usually has the new member within a day or two. (Our team is very small and we have a lot of other responsibilities!)

But good points, definitely.

The House allows iPads on the floor, and reporters are allowed to bring laptops into the gallery. It's how we get our live votes transcribed! https://www.nytimes.com/2017/05/08/insider/how-we-beat-the-h...

Even worse (weirder), the Senate bans electronic devices on the floor. If a Senator wants info, they have to sprint out one of the doors to the lobby where they have an aide waiting with an iPad (usually).

Oh, that is interesting. Also, hi Jon!

Yup! That's what we do! (Hi, I'm Jeremy, the developer who worked on this software)

The New York Times | Developer, mobile web | NYC | Full-time | Onsite | https://www.nytimes.com/

We're looking for a seasoned front-end developer to make our web-based interactive projects performant and more reflective of native mobile device behavior.

Interactive News is the special digital projects team embedded within The Times' newsroom. We draw on technical expertise to imagine new editorial forms and collaborate with reporters, editors, photographers, videographers and graphics editors to tell stories in interesting ways.

You don't need previous journalism experience but you should be a critical thinker who can help us bring thoughtful experiences to our readers.

Apply here: https://nytimes.wd5.myworkdayjobs.com/en-US/Tech/job/New-Yor...

The New York Times | Developer, backend + infrastructure | NYC | Full-time | Onsite | https://www.nytimes.com/

The New York Times' Interactive News team is hiring a developer to work on our backend services, infrastructure and tooling.

Interactive News a special digital projects team embedded within The Times' newsroom. We work with editors, reporters, photographers, designers and other developers to create newsroom-facing tools and reader-facing projects that expand the horizons of our digital news report.

Our stack is Node / Rails / Go / Django and MongoDB / MySQL / Postgres / ElasticSearch on Docker via Kubernetes and Google Cloud services. And we need your help keeping all the moving parts moving.

Apply here: https://nytimes.wd5.myworkdayjobs.com/en-US/Tech/job/New-Yor...

This is absolutely correct.

Thank you. We worked hard on our last two or three job advertisements. This represents the culmination of probably 8 months of conversation and experimentation.

We open-source an awful lot of our code, including our entire 2016 general election codebase. https://github.com/newsdev/

I'm Jeremy Bowers, and I'm hiring for this job. If you have questions, I'll be monitoring this thread or you can email me: jeremy.bowers@nytimes.com.

You know the saw about software development; if the features are fixed, flex the deadline. We're the opposite: We can't move a general election or we might have to respond to breaking news. We value your ability to make decisions about how to get a piece of software working quickly but without making it impossible to maintain. It requires creativity, and we think of it more of an art than a science.

Hi! We're a mix of Python, Ruby, Node and the occasional bit of Go. We decided not to add that to the job description because we don't make our hiring decisions based on command of a particular language. If you have concerns, send me an email: jeremy.bowers@nytimes.com.

I work with Albert at the Times. If you're interested about how our team came to be, you might like this article: http://nymag.com/news/features/all-new/53344/

There hasn't been an acknowledged S3 outage since April 2009 that we can find. Also, we use two different buckets in different geographic availability zones to allow us to stay up if one AZ goes out. Finally, our biggest projects are cached in CloudFront, which would serve a stale cached item if the backend were unavailable.

I can attest that it's unintentional. We roll pretty informally. And, frankly, we're pleased that anyone outside of the small (and insular) news apps community is reading about our setup.

For elections 2012, we actually used S3 buckets in two different availability zones and CloudFront to abstract away the backend.

In the event that we lost a geographic region, we planned to switch to a different S3 bucket.

We're trying to do as much in the open as we can! The way we figure it: If public media can't share code, who can?

We do use EC2 for cron, but could easily use a laptop instead if there were an outage.

Some of our more dynamic projects do require a server; the inauguration project that uploaded photos to Tumblr did, for example. https://github.com/nprapps/inauguration/

When we run servers, it's usually Flask and Nginx/uWSGI.

Most of our sites run entirely on S3. While we do have a cron server running, we could just as easily ship the updated JSON files from one of our laptops.

In fact, for the 2012 election, our fallback in case EC2 was unresponsive was to decamp to a coffee shop with a laptop and s3cmd.

Actually, I've decided that ProPublica's approach is pretty weak by comparison. There are other shops doing it much better.

Danno12, there's a fairly sizable Django community in media because the software was developed by a newspaper's tech staff (the Lawrence Journal-World). There's some good Rails development happening too, with the NY Time, ProPublica and others.

Good work like this getting done in small- and medium-sized newsrooms all around the country thanks to frameworks like Django and the work-at-all-hours ethos that reporters and developers tend to share. Kudos for taking the time to do the writeup.