Head Coach Mike Riley signed a new 1-year extension last month to push his current deal out to 2020. And University President Hank Bounds indicated there would be further contract extension discussion at the end of the season. It is important for recruiting efforts to show that the University is committed to the coaching staff in place. However, the timing on the announcement of this particular contract extension is particularly puzzling. It seems strange to have not waited a week or two for a couple of potential wins on the schedule.
First to 50 wins? Take the over? Will the Ducks get to 70? Or will the game even happen because of air quality? Smoked Duck with a side of Smoked Cheesy Corn? Lot of question hang in the air, sort of like the smokey particulate hovering over Autzen Stadium because of the wildfires in the area. There is no guarantee that the game may even happen, but we can still speculate.
In the Husker’s 43-36 win against Arkansas State, the new 3-4 scheme and Bob Diaco’s first effort at the defensive helm were only supposed to be an off-season bullet point in the list of things announcers, media, and pundits talk about leading up to the first game of the season. It could have been easy to just chalk up the elastic Husker defensive effort to the first game of season jitters and learning adjustments to the new system. It would have been simple to move on to the Ducks from there. But then a not-so-simple thing happened (or did not happen), Defensive Coordinator Bob Diaco did not talk to the media after the game.
There are Blackshirts. There are team captains. There were already Thursday night college football games, and there will be Friday night college football games (which is weird). Husker gameday is Saturday. The long slog through the off season is over. So now the Arkansas State Red Wolves come into town as a team expected to contend for the Sun Belt. This is a game that the Huskers are supposed to win, but the line has moved from 19 down to 14.5 (depending on where you look). So what will happen?
It certainly has been years since I dug deep into the off season analysis of my favorite sports team, and it will certainly have to wait one more. I always love watching the Huskers on game day Saturdays (now with new and improved Fridays!). But this year, my excitement during the off season was spent looking forward to 2018 and beyond, not 2017. When facing both good and bad challenges in life, I set ,y mind to the worst possible and best possible expectations and use a mental range finder for what are the likeliest possibilities in between. I have not picked up the 2017 Phil Steele College Football Preview to bury myself in the statistics, because I did not need it to see this team has a very narrow band for what is likely to happen this season.
Open office plans are yet again in the news as Apple’s new headquarters building plans initially included open office spaces for the engineers along with many stories of the frustrated employees being asked to work there. As someone who’s been working in a creative environment that embraces the collaborative space, there are times I find value in it. But I also work on the technical side of an agency which requires heads down time to get things done. I just remarked to someone today that a big pair of headphones is the modern day equivalent of a closed door to an office since nobody has doors anymore. I’ve never been one to listen to music to try and drown out the noise, but learning I need to find a way to focus an hour or so once a day. So I started looking at some options that might go well with some white noise or music.
Continue reading “Headphones for the Open Office”
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”.
Continue reading “Apply Software Development Practice to Application Configuration”
I’ll be posting some notes, slides, and additional information here after I’ve completed my talks at Detroit.Code() this week. Thanks to the whole Amegala crew at https://amegala.com/