Overnight releases are a thing of the past... or they should be. They create more problems than they solve for organizations, and a little bit of learning, time commitment, and infrastructure tuning can put them firmly behind any organization.
Over the past few months I’ve been on the outside, looking in, on a rushed technology M&A process
Too often in the current technical job landscape, hiring managers and recruiters are looking for a genius level polymath, someone good at everything thrown at them, even if they have little or no experience at it.
Imagine this: you are staring at a sheer cliff. In order to prosper, you must get to the top of the cliff. The question posed is: how do you get to the top of the cliff?
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.
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.”