I am a developer at The Washington Post and I help build newsroom facing tools. I also am the Chair of the DC chapter of ACM and produce a podcast called DC Tech Stories.
So I am in the odd position of being an internal facing developer so I don't know much about the front facing part of WaPo. My team builds tools for the newsroom. Each team usually has ownership over their own particular section - we have a whole big native team, a team that works on WaPo.com, a team focused on analytics, a paywall team, and if something like Instant Articles becomes popular, either a new team will form, or existing teams will lend out devs (short or long term, it varies). There is a hierarchy structure of upwards reporting from these teams into upper engineering management that drives strategy. Does that kind of answer your question?
I am a developer at The Washington Post and I help build newsroom facing tools. I also am the Chair of the DC chapter of ACM and produce a podcast called DC Tech Stories.
Reporters want to make their articles more content more engaging so they use our tools to do things like add user polls or context notes - here is an example: washingtonpost.com/pr/wp/2017/09/1...
My team was part of the collaboration to make a tools for journalists to make context notes attached into their articles - we had to make it look good and work on wapo.com AND make the internal editor easy for journalists to use ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
How does The Washington Post think about web vs native, AMP, Instant Articles, etc? What direction is the organization going with these platforms?
So I am in the odd position of being an internal facing developer so I don't know much about the front facing part of WaPo. My team builds tools for the newsroom. Each team usually has ownership over their own particular section - we have a whole big native team, a team that works on WaPo.com, a team focused on analytics, a paywall team, and if something like Instant Articles becomes popular, either a new team will form, or existing teams will lend out devs (short or long term, it varies). There is a hierarchy structure of upwards reporting from these teams into upper engineering management that drives strategy. Does that kind of answer your question?
Yeah that makes sense. What are some of the problems you're typically working to solve as an internal-facing dev?
Reporters want to make their articles more content more engaging so they use our tools to do things like add user polls or context notes - here is an example: washingtonpost.com/pr/wp/2017/09/1...
My team was part of the collaboration to make a tools for journalists to make context notes attached into their articles - we had to make it look good and work on wapo.com AND make the internal editor easy for journalists to use ;)