
Casey Bisson
3.5K posts

Casey Bisson
@misterbisson
Infrastructure, devops, and security geek. My views are my own, retweets≠endorsement, and all that. Also at https://t.co/nZqbH1aq8i


This is an objection to my tweets about feature flags, decoupling releases from deploys and autodeploys, but..I don't think it makes the point you think it makes. Rolling back past multiple deploys is a bad scene no matter what, but auto deploys aren't the bad guy here.



@starbuxman Joyent's "copilot" and Chef's "habitat" are two examples of working in this direction (habitat goes further than copilot did - essentially building a smart packaging/build system to take a bunch of the load off the supervisor)

Last night we hosted @misterbisson and @devseccon in San Francisco to talk about "Solving the other half of the code security problem". 🌁 Thank you to @snyksec, @stepzen_dev, and @rdegges for creating a great community and everyone who stopped by!








One of the things I occasionally get paid to do by companies/execs is to tell them why everything seemed to SUDDENLY go wrong, and subs/readers dropped like a stone. So, with everything going on at Twitter rn, time for a thread about the Trust Thermocline /1




However PMs are much more likely to do the synthesis themselves and pass on solutions. Often because it’s seen as their job to come up with, prioritise and manage the back-log. So why wouldn’t they?



