Alex Elliott

@alexpotato

Dad | DevOps / SRE | Paintball: College, Stats and Coaching, Running Pro Events

Vrijeme pridruživanja: lipanj 2009.

Tweetovi

Blokirali ste korisnika/cu @alexpotato

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

  1. Prikvačeni tweet
    1. sij

    A tweet thread of my tweet threads (we must go deeper!) 😎

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    2. velj

    People need to stop arguing and start making egg salad.

    Poništi
  3. prije 14 sati
    Prikaži ovu nit
    Poništi
  4. prije 15 sati

    In other words, writing things down created a common shared “touchstone” that people can “diff” vs their own mental model. When people realize their mental models don’t align, it’s MAGIC to watch the adjustments happen.

    Prikaži ovu nit
    Poništi
  5. prije 15 sati

    Everyone said “there are multiple things wrong with this documentation.” The kicker: they didn’t agree what was wrong! Eg There were different versions of what Step 3 was. For a 10 year old process that everyone “totally knew how it worked.”

    Prikaži ovu nit
    Poništi
  6. prije 15 sati

    I once worked at a firm that had a Sunday startup procedure where the ENTIRE tech stack came up in a 15 minute window. Something broke during my rotation so I thought: “This seems important so let me wrote this down.” and then I showed it to more senior folks...

    Prikaži ovu nit
    Poništi
  7. prije 15 sati

    Misconception 4: We all know it so why write it down.

    Prikaži ovu nit
    Poništi
  8. prije 15 sati

    Moral of the story: write docs. People will read them (even if they don’t tell you).

    Prikaži ovu nit
    Poništi
  9. prije 15 sati

    3rd example: I’ve written tons of documentation and at times thought: “Is anybody reading this??” And then one of the devs said “I was in a meeting and someone asked ‘who is going to doc this?’ ‘Easy! Alex! We all read his docs b/c they are great’ “

    Prikaži ovu nit
    Poništi
  10. prije 15 sati

    Another example: it’s the middle of a giant outage and the CEO asks “How the F does this work?” And you can say “Here is a quick recap I wrote a few months ago that you can read while I fix it”. Only one person may read it but it was the right person.

    Prikaži ovu nit
    Poništi
  11. prije 15 sati

    “Nobody”, “never”, “always” and “everyone” are big words. If you spend 30 minutes writing a doc that ONLY ONE PERSON reads and it saves them several hours of time. You just saved the company potentially thousands of $$$

    Prikaži ovu nit
    Poništi
  12. prije 15 sati

    Misconception 3: nobody ever reads documentation

    Prikaži ovu nit
    Poništi
  13. prije 15 sati

    You might occasionally get someone who says: “This feels like more work, why should I do this?” To which I answer: “You can do this once and never get asked these question again. Or not, and we can keep pestering you with questions every time a new hire joins.”

    Prikaži ovu nit
    Poništi
  14. prije 15 sati

    Now, think about this from a dev perspective: “Oh wow, I was asked to fill out this skeleton form of docs that asks me all the key questions they want to know! This is so easy, done.”

    Prikaži ovu nit
    Poništi
  15. prije 15 sati

    That’s what developers go through when you ask them “Hey, can you write me some documentation?” Also, developers are not always the best at Confluence etc b/c it’s not their primary tool.

    Prikaži ovu nit
    Poništi
  16. prije 15 sati

    Look at a blank piece of paper. Then think: “what should I write here for some people who are not me but who might want to know something about all of this stuff. I know? Plus, I majored in tech, not biz writing!”

    Prikaži ovu nit
    Poništi
  17. prije 15 sati

    Misconception 2: Developers never write documentation. Aka “I asked for documentation and was sent a giant email chain”

    Prikaži ovu nit
    Poništi
  18. prije 15 sati

    One other item: tools like Confluence etc make writing docs so easy! Plus, once you learn the keyboard shortcuts it feels like a superpower. Think of when you figured out the basics or first played a PC game with the mouse AND keyboard. It’s that cool!

    Prikaži ovu nit
    Poništi
  19. prije 15 sati

    But even if you are writing a “flight manual” it’s worth it. Why? Because docs fulfill so many different roles: Eg they are like mechanized training. Eg 2 they can act as a checklist to make sure things happen in the right order Etc. More on this later.

    Prikaži ovu nit
    Poništi
  20. prije 15 sati

    Docs can also mean “here are the top 5 things you need to know about X” Eg where does it run, how does it start, where are the logs etc. For the person trying to figure this out at 3am, those 5 - 10 lines are a lifesaver.

    Prikaži ovu nit
    Poništi
  21. prije 15 sati

    Documentation can mean lots of different things. If we’re talking about a 700 page NASA flight manual, then sure, docs can take a long time to write and involve serious resources. That being said...

    Prikaži ovu nit
    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:

    ·