We are on the cusp of 2019 and the term “DevOps” was coined nearly 10 years ago. The common definition has solidified over time, and is available to anyone who looks - yet the problem exists that somehow, “DevOps” became a cure-all for technology problems and technical debt.
Everyone should know what programming is and the effort that it takes. Everyone should know first aid. Everyone should know how to manage their own finances.
Fewer walls mean more space, fewer cubes and dividers means less money spent by facilities on creating separated spaces, and all of those mean money that isn’t being spent.
When I was younger, I had a manager that would email me at 8pm and try and call if I didn't respond by 10.
Twice in the last six weeks I’ve been reminded that “shit happens.” Things fail, people fail, services fail. None of this is surprising; our existence is built on failure and learning from it.
A month or so ago I ended up in a discussion with a CIO on a flight between Chicago and Toronto and we got to chatting, and he said that his team was 'converting to DevOps' and they were going to hire some 'DevOps Engineers' to help out with that.
I had to read about the unfortunate situation where a sysadmin was overwhelmed by a problem related to his job that was ultimately out of his control, but was so taxing and so stressful that the person in question ended up committing suicide.
In my adult life, I’ve met maybe five or six good recruiters that have worked with me - and I qualify good as “made effort to understand me, the roles that would best fit me, and did the slow play to find me the best job at the best company possible.”
There’s no reason to waste time: the second scariest thing about certification is the process of getting certified itself.