James Wickett

@wickett

Sr. Engineer at Signal Sciences (), proponent of rugged devops, creator of , and author of the gauntlt book: Hands-on Gauntlt

Austin, TX
Joined May 2008

@wickett is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @wickett.

  1. Are you using a Last Gen WAF? Now is the time to switch to

  2. Got up at 6am to start the brisket smoking...

  3. RT : Dear OS X: I'm gonna be Not Properly Ejecting disks for the rest of my life. Shut your pie hole about it and cope.

  4. RT : …founder "shift the position of security to enabling velocity"

  5. security change fraught with cultural unrest unpreventable

  6. thanks and for adding in this article DevOps Weekly is the best devops news source period

  7. rewind: Security in an Agile and DevOps World /cc

  8. New Year’s Resolution: Bring Security to the DevOps Party

  9. RT : Struggling with terms? check out our latest post on the language of DevOps

  10. On night 2 of reading Narnia to my oldest and it seems to be a hit

  11. Really excited to be working with at

  12. Retweeted

    . four new employees today maybe you are next

  13. Retweeted

    Using To Deliver Security Tools by : via the agile admin blog

    Embedded image permalink
  14. SecCasts Panel w/

    Translated from Italian by

  15. RT : New post from “Security in an Agile and DevOps World”

  16. RT : CFP: DevOps Connect: Rugged DevOps RSAC

    Translated from Romanian by

  17. Retweeted

    There’s just three days after today left on our Call for Papers for Lone Star PHP 2016! Get those proposals in now!

  18. James Wickett followed , , and 16 others
    • @carlobonamico

      Java Architect, DevOps, Ansible, AngularJS, music & mountains enthousiast

    • @nVisium

      Appsec consultants specializing in mobile & web application services, including code remediation, training, assessments and secure development.

  19. Retweeted

    Our own will be on talking security automation and devops

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·