Jenn Leaver

@jennleaver

Leading Product Docs .

Bloomington, IL
Vrijeme pridruživanja: svibanj 2009.

Tweetovi

Blokirali ste korisnika/cu @jennleaver

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @jennleaver

  1. Prikvačeni tweet
    27. svi 2016.

    I've watched this at least a hundred times and it still hasn't gotten old: Cold Game At The Spelling Bee

    Poništi
  2. 1. velj

    You can't have big dreams if you have no way to execute on them. I've got big dreams for docs at GitHub. And Zeke and Sarah have shown me that they're possible. It's been an incredible lesson to learn.

    Prikaži ovu nit
    Poništi
  3. 1. velj

    If you're leading a docs team, push for dedicated engineering help. If you're an engineer or PM and you see that a docs team doesn't have dedicated help, push to get them that help. The work is complex and important.

    Prikaži ovu nit
    Poništi
  4. 1. velj

    Without dedicated engineering, without Zeke and Sarah, we wouldn’t be where we are today. We’re set up for success. We feel confident. We know that our work is worthy of receiving help from other people. They gave our team hope.

    Prikaži ovu nit
    Poništi
  5. 1. velj

    Their work inspired trust on our team. For the first time in my career, I knew there were engineers who deeply cared about this work. It’s such a simple thing - knowing that you have support, that you’re not alone - but it changes everything.

    Prikaži ovu nit
    Poništi
  6. 1. velj

    More than anything though, having dedicated engineers on docs meant that for the first time ever, writers had engineers who intimately understood the needs of our team and spent their time thoughtfully working to make things better internally for writers and externally for users.

    Prikaži ovu nit
    Poništi
  7. 1. velj

    Zeke, along with Sarah Schneider, a writer-turned-engineer, redid all our back-end tooling. Their work made the writer's work easier, enabled us to internationalize , set the foundation for new initiatives, and gave us the first iteration of a new design.

    Prikaži ovu nit
    Poništi
  8. 1. velj

    Back in late 2018, reached out to me - from a different team! - and mentioned that he wanted to help us with localization. It was the first time in my entire career that an engineer had ASKED to help. That conversation changed the entire docs experience at GitHub.

    Prikaži ovu nit
    Poništi
  9. 1. velj

    Docs teams are often left to do all of this themselves. People think that the job of a tech writer is non-technical, but that’s not true. Tech writers are often engineering their own tooling solutions and sites with minimal or no help from anywhere in the organization.

    Prikaži ovu nit
    Poništi
  10. 1. velj

    Writing docs is complex. You need tooling that can handle single-sourcing, versioning, variables, reusables, localization, the ability to pull in automated content generated elsewhere, etc. And all of this content needs to make it onto a site that has a great info experience.

    Prikaži ovu nit
    Poništi
  11. 1. velj

    A couple years ago, the docs team at GitHub wasn’t in a great position. We’d outgrown our tooling, both in terms of the number of writers using it and the complexity we’d introduced with new products. We use GitHub for everything and have a “docs as code” philosophy.

    Prikaži ovu nit
    Poništi
  12. 1. velj

    I was working on reviews this week and keep coming back to something: how important it is for docs teams to have dedicated engineering help. So here’s a story about the impact engineers have had on my team.

    Prikaži ovu nit
    Poništi
  13. 24. sij

    Every time I see [sic] in a quote, I die of second-hand embarrassment. Can you imagine the shame of having your mistake passive aggressively pointed out FOR ALL TIME?

    Poništi
  14. 17. sij

    So folks in tech, reach out to tech writers on your teams. Ask how you can help. Add visibility to their work. Include them in your thank you’s. Help them in their work the way they’ve spent their careers helping you in yours.

    Prikaži ovu nit
    Poništi
  15. 17. sij

    I’ll never regret going into documentation as a career. I love what I do. And this isn’t a subtweet of anything. This is just a moment of being real - that this invisible work matters and that it’s hard to fight when there’s no finish line in sight.

    Prikaži ovu nit
    Poništi
  16. 17. sij

    I guess this is why you need to do work that you really love. Because even when the disappointments are heartbreaking, they’re still worth it.

    Prikaži ovu nit
    Poništi
  17. 17. sij

    I applied to a job once that asked for people who gave a damn. It resonated with me because I do. When I got into this field, if I’d have known that I’d spend my entire career fighting perceptions, I’d have still done this. It would just be easier if I didn’t give a damn.

    Prikaži ovu nit
    Poništi
  18. 14. sij

    Years ago I read Barthes’ “The Death of the Author” and I think that’s why I don’t take criticism of my work personally. The moment you release something to the world, you can’t control people’s reactions to it or assume they’ll consider your motivations. You just do your best.

    Poništi
  19. proslijedio/la je Tweet
    13. sij

    For people who still don’t think the work we do at The is needed or important. I will probably leave out of meetings or hang up on phone calls this year when people swear they still don’t get what’s happening to people (especially after I’ve explained).

    Prikaži ovu nit
    Poništi
  20. 10. sij

    I have also been in Oxford - working with the docs team here on all things GitHub. 🙌🏻 My pic of Oxford for the week looks a little different than though...

    Poništi
  21. proslijedio/la je Tweet
    1. sij
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·