In this video, I roast some Go code! That is, I review it as if it were submitted as part of a job application screening. I talk about what I like, what I don't like, and how I would do things differently.

Hiring screening optimizes for fast thinking, but IT success depends on slow thinking.

You can't eliminate technical debt. Nor should you want to. But where does that leaev us?

Jillian, Jonathan, Will, and Chuck discuss where the line is between Development and DevOps and what the difference is. They also get into the value of each and when crossover is likely to occur.

Where does technical debt come from? Three main sources.

J. B. Rainsberger offers practical advice on how to "get over the hump" of evolutionary design, and really, how to learn any new skill.

For many of us, code review is like eating broccoli: We know it's good for us, but we hate it. Here are my 10 tangible tips to improve the value of code reviews, and hopefully make them less distasteful.

How do you know that the work you're doing is building on a valid premise?

Often the "obvious" answer blinds us to the "correct" answer.

The thing with agilists is they don't understand that sometimes we have deadlines.

The panel puts their heads together to talk about how to bring DevOps practices into a work situation based where they're not implemented. They discuss the various pro's and con's of specific practices and how to get people on board with adoption.