Technology, Sports, Culture talk

Tag: prairie.code

Are You Really Using Kanban or Just Making a List of Issues?

This talk continues to be one of my favorites to give and I just keep getting the chance to present it. I will continue to submit it because it’s just a fun one. The Slides have been uploaded to SlideShare and my notes are mostly included here.

Nebraska.Code() Extended Explanation of Caching

Thanks for everyone attending the Nebraska.Code() Conference. After the jump, check out a previous version of my slides and some notes on the topic I collected. I’ll likely be updating the slides a bit more soon, and will post when that happens on twitter.

Prairie.Code() Software Development for Configurations Session

Thanks for all those who attended my breakout session “Apply Software Development Practice to Application Configuration”. And many thanks again to Amegala. The details and examples in this talk can be found on my original post here: https://tomcudd.com/software-development-practice-application-configuration/

If you have questions or want to continue the conversation, please follow me on Twitter.

Prairie.Code() Kanban Workshop and Breakout Session

Thanks again to the whole Amegala crew for putting together a great day of workshops and breakout sessions. I wanted to make sure to get my notes and the slides up tonight in case anyone is wanting to read up a bit more on Kanban this week. Also included are the links to the workshop exercises and a couple other ones I have looked at in the past.

Apply Software Development Practice to Application Configuration

Ops teams should always strive towards implementing the best application configuration strategy and infrastructure as code solution that will work best for each scenario. However, Puppet, Chef, Ansible, and other similar products may not be the right solution for every project and team. Depending on the DevOps maturity of the team, flexible delivery capabilities needed, feature plugin issues, or off-release work cycles, building a custom solution could be the steps needed get a team from manually editing configurations in production to a fully automated continuous integration pipeline. We want to avoid the scenario where “when you’ve got a hammer, every problem looks like a nail”.

Powered by WordPress & Theme by Anders Norén