At the 2012 Computer-Assisted Reporting Conference in St. Louis, the Reporters' Lab team presented a demonstration of their current tools for investigative and public affairs reporters.
Design thinking: Building a developer experience from scratchBecky Todd
Becky Todd discusses redesigning Atlassian's developer documentation from scratch. User testing revealed that developers struggled to navigate outdated content and often failed to complete onboarding tasks. Todd then led a redesign process that improved search, navigation, and content updates through design thinking. This included community contribution, early adopters, and building a content authoring toolkit. Follow-up user testing showed developers could now complete onboarding tasks in under 30 minutes and deploy usable code.
Adopting Continuous Integration in an Ops Groupcolleenfry
The document discusses adopting continuous integration (CI) practices in an operations (Ops) group at Turner Broadcasting Systems. It describes setting up a CI server to run automated tests on code commits, creating standardized build processes, and developing tools like DIB (Daniel In Box) to catch issues earlier. This encouraged more teams to adopt source code management and testing. Lessons learned include how in-process testing is important, providing upstream tests to downstream teams, and culture being a key factor in CI adoption.
Towards an Agile Authoring methodology: Learning from Lean (AgileTheDocs Conf...Ellis Pratt
This document discusses applying Lean principles to technical writing in an Agile environment. It defines key Lean concepts like waste and value and identifies common types of waste in content production, such as unnecessary formatting, long review cycles, and content that is not useful to users. The document advocates treating documentation as code by using the same tools as developers and publishing content incrementally. Overall, it argues that Lean can help technical communicators optimize their processes and content in Agile by identifying and eliminating waste.
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
JAX London 2014 "Moving to DevOps Mode: easy, hard or just plain terrifying?"Daniel Bryant
DevOps - is it for you? Heard about the wonderful ways it could benefit your organisation, but put off by the scary stories? Can you really make the transition to DevOps, and is it worth it? Listen and learn from two DevOps practitioners about their hands-on experiences in making the change. Covering a range of real life examples, this talk will explain the real business benefits to be had from using DevOps techniques, as well as the technical and personal aspects involved.
Whether it’s a small team within a startup or one of hundreds within a large organisation, this talk has practical advice on how to approach the challenge, what critical changes need to be considered, and what tools and processes are best suited for the situation. The adoption of DevOps is a game changing event for the industry. Learn why and learn how you can benefit from it too.
This talk was presented with Steve Poole (@spoole167) at JAX London, October 2014
Moving to a DevOps mode - easy, hard or just plain terrifying? - Daniel Bryan...JAXLondon2014
The document discusses moving to a DevOps model and describes it as both easy and terrifying. It advocates breaking down silos between development and operations teams by emphasizing common goals, shared responsibility, and standard technology. The benefits of DevOps include faster reaction times for businesses and extending agility across IT organizations.
This document provides an overview of getting started with DevOps. It includes an agenda covering topics like DevOps frameworks, practices, and tooling. The DevOps framework section outlines the people, process, and technology aspects, including mindset, practices like pipelines and automation, and DevOps toolchains. It also discusses how to build a DevOps team and adoption plan. The overall document serves as an introduction to DevOps concepts, best practices, and provides guidance on implementing DevOps.
Slides from my talk at DevOps East 2015 #BetterSoftwareCon. The talk was on how continuous delivery/deployment is not required for DevOps. But DevOps without successful CI is crippled and hard to grow and sustain
Design thinking: Building a developer experience from scratchBecky Todd
Becky Todd discusses redesigning Atlassian's developer documentation from scratch. User testing revealed that developers struggled to navigate outdated content and often failed to complete onboarding tasks. Todd then led a redesign process that improved search, navigation, and content updates through design thinking. This included community contribution, early adopters, and building a content authoring toolkit. Follow-up user testing showed developers could now complete onboarding tasks in under 30 minutes and deploy usable code.
Adopting Continuous Integration in an Ops Groupcolleenfry
The document discusses adopting continuous integration (CI) practices in an operations (Ops) group at Turner Broadcasting Systems. It describes setting up a CI server to run automated tests on code commits, creating standardized build processes, and developing tools like DIB (Daniel In Box) to catch issues earlier. This encouraged more teams to adopt source code management and testing. Lessons learned include how in-process testing is important, providing upstream tests to downstream teams, and culture being a key factor in CI adoption.
Towards an Agile Authoring methodology: Learning from Lean (AgileTheDocs Conf...Ellis Pratt
This document discusses applying Lean principles to technical writing in an Agile environment. It defines key Lean concepts like waste and value and identifies common types of waste in content production, such as unnecessary formatting, long review cycles, and content that is not useful to users. The document advocates treating documentation as code by using the same tools as developers and publishing content incrementally. Overall, it argues that Lean can help technical communicators optimize their processes and content in Agile by identifying and eliminating waste.
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
JAX London 2014 "Moving to DevOps Mode: easy, hard or just plain terrifying?"Daniel Bryant
DevOps - is it for you? Heard about the wonderful ways it could benefit your organisation, but put off by the scary stories? Can you really make the transition to DevOps, and is it worth it? Listen and learn from two DevOps practitioners about their hands-on experiences in making the change. Covering a range of real life examples, this talk will explain the real business benefits to be had from using DevOps techniques, as well as the technical and personal aspects involved.
Whether it’s a small team within a startup or one of hundreds within a large organisation, this talk has practical advice on how to approach the challenge, what critical changes need to be considered, and what tools and processes are best suited for the situation. The adoption of DevOps is a game changing event for the industry. Learn why and learn how you can benefit from it too.
This talk was presented with Steve Poole (@spoole167) at JAX London, October 2014
Moving to a DevOps mode - easy, hard or just plain terrifying? - Daniel Bryan...JAXLondon2014
The document discusses moving to a DevOps model and describes it as both easy and terrifying. It advocates breaking down silos between development and operations teams by emphasizing common goals, shared responsibility, and standard technology. The benefits of DevOps include faster reaction times for businesses and extending agility across IT organizations.
This document provides an overview of getting started with DevOps. It includes an agenda covering topics like DevOps frameworks, practices, and tooling. The DevOps framework section outlines the people, process, and technology aspects, including mindset, practices like pipelines and automation, and DevOps toolchains. It also discusses how to build a DevOps team and adoption plan. The overall document serves as an introduction to DevOps concepts, best practices, and provides guidance on implementing DevOps.
Slides from my talk at DevOps East 2015 #BetterSoftwareCon. The talk was on how continuous delivery/deployment is not required for DevOps. But DevOps without successful CI is crippled and hard to grow and sustain
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
But We're Already Open Source! Why Would I Want To Bring My Code To Apache?gagravarr
So, your business has already opened sourced some of it's code? Great! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
OneDrive and SharePoint are the main ways to store files in Microsoft 365. OneDrive is for individual file storage and is private by default, while SharePoint allows for team collaboration on multiple document libraries. Both offer up to 1000GB of storage space.
Microsoft 365 includes productivity tools like dictation across Office apps, communication features in Teams like chat, calls, meetings, and file sharing, as well as access to third party apps.
OneNote is a digital notebook that automatically saves and syncs notes in various formats. Features like highlighting and tags aid in organization and navigation. It is free to use and can be accessed via various devices and browsers.
This document provides information about accessibility features in Microsoft 365. It discusses OneDrive and SharePoint for cloud storage, productivity tools like dictation in Office apps, communication features in Teams, and accessibility settings in PowerPoint. It also covers the Immersive Reader tool for reading documents, live captions and transcripts in meetings, and other accessibility apps like screen readers and magnifiers.
Live Conversation: Connecting with customers in real timeUserTesting
Live Conversation customers, Devin Harold from Verizon and Nayaab Lokhandwala from Alaska Airlines, have used human insights to build better products and improve user experiences.
Live Conversation helps you to easily get insights from UserTesting’s diverse panel or your own customers through in-depth interviews. Speak to your target audience by conveniently connecting in real time through interactive, live video conversations.
Easily draw insights, observe non-verbal cues, and ask open-ended questions to understand the ‘why’ behind the what. Get connected with your exact buyer in less than 24 hours and dig into areas of interest using seamless video technology that enables you to share screens and receive live feedback.
Learn how to:
Get user reactions to prototypes, messaging and designs in just hours
Quickly explore user sentiment and attitudes
Understand and perfect the customer journey
But we're already open source! Why would I want to bring my code to Apache?gagravarr
From ApacheCon Europe 2015 in Budapest
So, your business has already opened sourced some of its code? Great! Or you're thinking about it? That's fine! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
Michael Larsen discusses lessons learned from his involvement with Weekend Testing, a volunteer organization that holds short testing sessions online to help testers learn and practice their skills. Some key lessons include: considering participants' varying access to applications and internet speeds based on geography; the value of focused session-based testing to thoroughly test applications; using a "divide and conquer" approach to split testing tasks among groups; ensuring testing goals and missions are clearly communicated; and being aware of potential cultural differences that could impact requirements or date conventions. Overall, Weekend Testing is an effective way for passionate testers globally to collaborate, train others, and have fun advancing their testing skills.
User Research for the Web and ApplicationsDani Nordin
In this workshop given for Skillshare, I discuss basic techniques and deliverables to help teams understand their site's users, organize content and visualize task flows.
This document summarizes experiences from developing an ontology about software in an agile manner through workshops. It describes holding workshops with various stakeholders to gather requirements, prioritize features, and begin populating ontology modules in an iterative process. The goals were to avoid lengthy conceptualization, get early results, and allow priorities to change based on examples discussed. This approach allowed for collaborative authoring without everyone needing ontology expertise and separating knowledge gathering from formalizing axioms.
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
Digital technology was essential for all aspects of evaluating the group's opening sequence project. They used Blogger to host evaluations in various formats like text, images, presentations, and videos, allowing easy access and feedback. Photoshop enabled visual analysis of footage. PowerPoint and filmed presentations helped structure evaluations. The public nature of Blogger provided valuable unbiased feedback to improve their work.
This document discusses tips for improving accessibility at small companies without dedicated accessibility teams. It recommends (1) focusing on changes that individual employees can control, like design and testing, (2) learning required accessibility standards, (3) conducting accessibility testing using free tools to identify issues, (4) organizing issues by type to identify patterns, (5) prioritizing fixes for major roadblocks, (6) scheduling fixes in releases, and (7) educating other employees about accessibility best practices. The overall message is that small teams can make progress on accessibility by leveraging individual efforts and taking a systematic approach to testing, organizing, and fixing accessibility issues over time.
Testistanbul 2016 - Keynote: "The Story of Appium" by Dan CuellarTurkish Testing Board
When I demo’ed what is now called Appium at the Selenium Conference in 2012 I had no idea what I was doing starting an open source project. I knew little about how open source operated and worked behind the scenes. Thanks to the help of a great community and the advice of some seasoned open source contributors, Appium has quickly become the most popular open source mobile automation framework. Along the way, mistakes were made, lessons were learned, and occasionally we got things right. I’ve put together a collection of stories and lessons that I’d like to share with others to help everyone manage, contribute to, and consume open source software projects more effectively.
Agile Success Story -Tester & Developer Working Together for Higher Quality M...XBOSoft
The document summarizes a presentation given by JeanAnn Harrison and Jonathan Spurgin on best practices for testers and developers working together in an agile environment. Some of the key points discussed include setting clear goals and expectations, using respectful terminology, ensuring good communication and collaboration between teams, having testers learn the full architecture to better understand bugs, and reviewing log files together to help isolate issues.
A super enjoyable and entertaining walk through API memory lane, then a primer on how to test API's from a unit, integration, and monitoring standpoint. Then a demo on a CI/CD implementation I created at Snagajob.
Daniel used several new technologies in constructing, researching, planning and evaluating his project. He used websites like Blogger, YouTube, Prezi and Slideshare to present his evaluation electronically. Videos were recorded using QuickTime player and posted to YouTube, with links between Blogger and YouTube. Screenshots were also embedded in blogs using grab screen capturing software. Throughout the process, picture-in-picture was used to show audience reactions alongside self-narration of the project's technology use.
1) The document discusses using multimedia like video and audio to enhance teaching. It provides reasons for using multimedia, such as positive student feedback about supplemental materials.
2) Options for creating multimedia at RAU are reviewed, including available hardware, Panopto for uploading and sharing videos, and tips for storyboarding and producing content.
3) Various types of multimedia that could be used are suggested, such as lecture recordings, how-to guides, interviews, and virtual open days. Accessibility and interactive options are also covered.
TERMINALFOUR t44u 2012 - Support and Extranet developmentsTerminalfour
Our Extranet has long been the central resource for clients and partners for all things Site Manager. This year it’s received a significant overhaul making it more interactive, more engaging and putting more information at your finger tips. Learn about your ‘T4 Knowledge Base’. Laura Murphy
Meetup TestingUY 2016: Adopting testing in a cross-functional teamClaudia Badell
Meetup TestingUy | Uruguay, Montevideo | 13th December 2016
Abstract
In this talk Claudia will tell us some of the actions that have been applied to incorporate testing as a team strategy, in the context of a cross-functional team fully dedicated to developing a product. Claudia will also share some lessons learned during this process.
Duration: 45 minutes
Bienestar Financiero al servicio de su jubilación anticipada
Pago de su 🏡
Estudio de sus hijos
Directamente a tu cuenta bancaria
Con Tesorería Auditoria Jurídica comercial
Administración de carteras
Apalancamiento Financiero
Desarrollo de tu marca personal
Acceso a Desarrollo de varias industrias
Cuentas bancarias
Estructuras Físicas en USA y en América Central
Avalado por Bolcomer
Puesto de Bolsa Comercial
Turismo
Y mucho más
Link de registro
https://business.myinfinity.global/maurod8/
https://therusnetwork.com/
Contacto:
https://goo.su/pzm1fja
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
But We're Already Open Source! Why Would I Want To Bring My Code To Apache?gagravarr
So, your business has already opened sourced some of it's code? Great! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
OneDrive and SharePoint are the main ways to store files in Microsoft 365. OneDrive is for individual file storage and is private by default, while SharePoint allows for team collaboration on multiple document libraries. Both offer up to 1000GB of storage space.
Microsoft 365 includes productivity tools like dictation across Office apps, communication features in Teams like chat, calls, meetings, and file sharing, as well as access to third party apps.
OneNote is a digital notebook that automatically saves and syncs notes in various formats. Features like highlighting and tags aid in organization and navigation. It is free to use and can be accessed via various devices and browsers.
This document provides information about accessibility features in Microsoft 365. It discusses OneDrive and SharePoint for cloud storage, productivity tools like dictation in Office apps, communication features in Teams, and accessibility settings in PowerPoint. It also covers the Immersive Reader tool for reading documents, live captions and transcripts in meetings, and other accessibility apps like screen readers and magnifiers.
Live Conversation: Connecting with customers in real timeUserTesting
Live Conversation customers, Devin Harold from Verizon and Nayaab Lokhandwala from Alaska Airlines, have used human insights to build better products and improve user experiences.
Live Conversation helps you to easily get insights from UserTesting’s diverse panel or your own customers through in-depth interviews. Speak to your target audience by conveniently connecting in real time through interactive, live video conversations.
Easily draw insights, observe non-verbal cues, and ask open-ended questions to understand the ‘why’ behind the what. Get connected with your exact buyer in less than 24 hours and dig into areas of interest using seamless video technology that enables you to share screens and receive live feedback.
Learn how to:
Get user reactions to prototypes, messaging and designs in just hours
Quickly explore user sentiment and attitudes
Understand and perfect the customer journey
But we're already open source! Why would I want to bring my code to Apache?gagravarr
From ApacheCon Europe 2015 in Budapest
So, your business has already opened sourced some of its code? Great! Or you're thinking about it? That's fine! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
Michael Larsen discusses lessons learned from his involvement with Weekend Testing, a volunteer organization that holds short testing sessions online to help testers learn and practice their skills. Some key lessons include: considering participants' varying access to applications and internet speeds based on geography; the value of focused session-based testing to thoroughly test applications; using a "divide and conquer" approach to split testing tasks among groups; ensuring testing goals and missions are clearly communicated; and being aware of potential cultural differences that could impact requirements or date conventions. Overall, Weekend Testing is an effective way for passionate testers globally to collaborate, train others, and have fun advancing their testing skills.
User Research for the Web and ApplicationsDani Nordin
In this workshop given for Skillshare, I discuss basic techniques and deliverables to help teams understand their site's users, organize content and visualize task flows.
This document summarizes experiences from developing an ontology about software in an agile manner through workshops. It describes holding workshops with various stakeholders to gather requirements, prioritize features, and begin populating ontology modules in an iterative process. The goals were to avoid lengthy conceptualization, get early results, and allow priorities to change based on examples discussed. This approach allowed for collaborative authoring without everyone needing ontology expertise and separating knowledge gathering from formalizing axioms.
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
Digital technology was essential for all aspects of evaluating the group's opening sequence project. They used Blogger to host evaluations in various formats like text, images, presentations, and videos, allowing easy access and feedback. Photoshop enabled visual analysis of footage. PowerPoint and filmed presentations helped structure evaluations. The public nature of Blogger provided valuable unbiased feedback to improve their work.
This document discusses tips for improving accessibility at small companies without dedicated accessibility teams. It recommends (1) focusing on changes that individual employees can control, like design and testing, (2) learning required accessibility standards, (3) conducting accessibility testing using free tools to identify issues, (4) organizing issues by type to identify patterns, (5) prioritizing fixes for major roadblocks, (6) scheduling fixes in releases, and (7) educating other employees about accessibility best practices. The overall message is that small teams can make progress on accessibility by leveraging individual efforts and taking a systematic approach to testing, organizing, and fixing accessibility issues over time.
Testistanbul 2016 - Keynote: "The Story of Appium" by Dan CuellarTurkish Testing Board
When I demo’ed what is now called Appium at the Selenium Conference in 2012 I had no idea what I was doing starting an open source project. I knew little about how open source operated and worked behind the scenes. Thanks to the help of a great community and the advice of some seasoned open source contributors, Appium has quickly become the most popular open source mobile automation framework. Along the way, mistakes were made, lessons were learned, and occasionally we got things right. I’ve put together a collection of stories and lessons that I’d like to share with others to help everyone manage, contribute to, and consume open source software projects more effectively.
Agile Success Story -Tester & Developer Working Together for Higher Quality M...XBOSoft
The document summarizes a presentation given by JeanAnn Harrison and Jonathan Spurgin on best practices for testers and developers working together in an agile environment. Some of the key points discussed include setting clear goals and expectations, using respectful terminology, ensuring good communication and collaboration between teams, having testers learn the full architecture to better understand bugs, and reviewing log files together to help isolate issues.
A super enjoyable and entertaining walk through API memory lane, then a primer on how to test API's from a unit, integration, and monitoring standpoint. Then a demo on a CI/CD implementation I created at Snagajob.
Daniel used several new technologies in constructing, researching, planning and evaluating his project. He used websites like Blogger, YouTube, Prezi and Slideshare to present his evaluation electronically. Videos were recorded using QuickTime player and posted to YouTube, with links between Blogger and YouTube. Screenshots were also embedded in blogs using grab screen capturing software. Throughout the process, picture-in-picture was used to show audience reactions alongside self-narration of the project's technology use.
1) The document discusses using multimedia like video and audio to enhance teaching. It provides reasons for using multimedia, such as positive student feedback about supplemental materials.
2) Options for creating multimedia at RAU are reviewed, including available hardware, Panopto for uploading and sharing videos, and tips for storyboarding and producing content.
3) Various types of multimedia that could be used are suggested, such as lecture recordings, how-to guides, interviews, and virtual open days. Accessibility and interactive options are also covered.
TERMINALFOUR t44u 2012 - Support and Extranet developmentsTerminalfour
Our Extranet has long been the central resource for clients and partners for all things Site Manager. This year it’s received a significant overhaul making it more interactive, more engaging and putting more information at your finger tips. Learn about your ‘T4 Knowledge Base’. Laura Murphy
Meetup TestingUY 2016: Adopting testing in a cross-functional teamClaudia Badell
Meetup TestingUy | Uruguay, Montevideo | 13th December 2016
Abstract
In this talk Claudia will tell us some of the actions that have been applied to incorporate testing as a team strategy, in the context of a cross-functional team fully dedicated to developing a product. Claudia will also share some lessons learned during this process.
Duration: 45 minutes
Bienestar Financiero al servicio de su jubilación anticipada
Pago de su 🏡
Estudio de sus hijos
Directamente a tu cuenta bancaria
Con Tesorería Auditoria Jurídica comercial
Administración de carteras
Apalancamiento Financiero
Desarrollo de tu marca personal
Acceso a Desarrollo de varias industrias
Cuentas bancarias
Estructuras Físicas en USA y en América Central
Avalado por Bolcomer
Puesto de Bolsa Comercial
Turismo
Y mucho más
Link de registro
https://business.myinfinity.global/maurod8/
https://therusnetwork.com/
Contacto:
https://goo.su/pzm1fja
UnityNet World Environment Day Abraham Project 2024 Press ReleaseLHelferty
June 12, 2024 UnityNet International (#UNI) World Environment Day Abraham Project 2024 Press Release from Markham / Mississauga, Ontario in the, Greater Tkaronto Bioregion, Canada in the North American Great Lakes Watersheds of North America (Turtle Island).
UnityNet World Environment Day Abraham Project 2024 Press Release
Reporters' Lab demo at NICAR12
1.
2. WHO WE ARE
• Directed by Sarah Cohen, Knight Chair
• in Computational Journalism
• Based at Duke University’s Center for Media
• and Democracy at the Sanford School of Public Policy
• in Durham, N.C.
• Four components of the lab:
• Adapt existing technology for public affairs reporting
• Produce news and reviews about tools for reporting
• Contribute to interdisciplinary research to aid reporting
• Make obtaining public records easier by working with
journalists and the government
4. HOW WE REVIEW
The Reporters’ Lab aims to produce reviews that are consistent,
independent, fair and, above all, useful for a reporter with little
time or patience for technical details.
We use full versions of products against a curated set of documents
and tests so you can compare apples to apples and figure out
what’s worth the money, how hard it will be to learn, and how long
it might take.
Whenever we can, we contact companies to address specific
product critiques and include their responses when they’re useful
to users.
We don’t let companies read the reviews in full or approve or
reject content.
5. HOW WE REVIEW
Components of Reporters’ Lab Reviews
Document Sets
Tests
Products
Test Results
Reviews
Tutorials
8. TIMEFLOW
• TimeFlow is a visual tool for reporters looking to organize and
analyze historical data on long-term stories
• Developed for the lab by Fernanda Viégas and Martin
Wattenberg at Flowing Media
• Open source and free (code is on GitHub)
• This is an alpha release, so there are some bugs
11. THE PROBLEM: RECORDED MEETINGS
• You’re assigned to live tweet a recorded government
• The video is two hours long, but the pieces relevant to your story
take up about five minutes
• You rewatch the video, get what you need, publish the story and
move on
• But what if later you want something else from that video?
12. THE SOLUTION: VIDEO NOTEBOOK
1) Get the video file of the meeting
2) Upload your file
3) Add the video to the Video Notebook
4) Import your tweets, Storify or live blog
5) Sync them with video
6) Watch video with notes, jump to certain spots in the video,
search or add new notes
7) Watch it later or export information to a spreadsheet
13. FUTURE ENHANCEMENTS
User specific functionality
• More user control
• User page with upload information
• Privacy controls for videos and notes
• Note filtering (notes just from you or a specific source)
14. FUTURE ENHANCEMENTS
Note functionality
• Analysis
• Entity extraction
• Sentiment analysis
• Timeline view
• Better imports! More sources!
• Integration with a “tweet saver” project
• Allows reporters to save tweets locally for a long time
• App would constantly scrape your Twitter timeline to
archive tweets
• Then we can import tweets easier (with a hashtag, for
example)
15. FUTURE ENHANCEMENTS
Other enhancements
• Audio
• Currently accepts only video (MP4, YouTube)
• Hope to add audio (mp3, OGG)
• Mobile
• Get around YouTube’s flash limitation to optimize for
phones and tablets
16. CONCLUSIONS
• Currently just a proof of concept right now!
• Want to help test? Have feature ideas? Let us know!
• Contact info@reporterslab.org or charlie@reporterslab.org
• Eventually, The Video Notebook will be free and open-source
17. QUESTIONS?
Contact the lab
• Charlie Szymanski
charlie@reporterslab.org
@charlieisatwork
• Tyler Dukes
tyler@reporterslab.org
@mtdukes
• General questions
info@reporterslab.org
• Twitter
@ReportersLab
• Facebook
facebook.com/reporterslab