AboutPowerShell -eq ❤
SkillsPowerShell, PowerShell, PowerShell, PowerShell, PowerShell, PowerShell, PowerShell, PowerShell
Joined devRant on 1/9/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Latest dark theme news:
- GitHub got dark theme!
- Facebook mobile finally released their dark theme.
Dark theme everywhere!4
I just finished reading the last chapter of the DevOps Handbook, its an eye opener, but not an easy read. And still recommended.
I've been reading this book for the past year and a half, little by little. It was hard since I started understanding why my work was so frustrating (I'm in System-Cloud-Ops position). The book made sense, while the work did not, it got harder since the book provides solutions, but whenever I dicussed any solutions with management they dismissed everything.
I started to initiate improvements by myself:
Prioritizing tasks I thought were more important to improve the way of work - do now and ask questions later... I got yelled at, I got my managers angry, but afterwards more often then not they admitted I was right.
To make it possible I worked overtime and on weekends, trying to prove a better way is possible, by implementing a long term solutions to solve problems instead of workarounds, automating a lot of stuff, creating labs, preparing presentations and documentation.
Time and time again I tried to pitch more ideas related to DevOps but the managers didn't care...
I know now my burnout started 8 months ago slowly, my hairline started receding, I started clenching my teeth (the doctor said stress was the cause) which was very fainful.
I continued to work but I noticed I was also more cynical, frustrated, and tired.
In the process I neglected myself.
So finally after 2 years and a half I quit my job, to focus on myself, at least for a little while.
I hope in my next job will be better.4
My deparment manager said to me that I'm the first person he encountered that has a fetish for writing documentation.
In the context of the conversation I felt he was mocking me, that he doesn't understand why its important, and I why feel obligated to do it (everything was a mess when I joined the team 2 years ago).3
I guess that is bound to happen when working in an open space.
People at my team love playing music from the computer speakers and talk loud. I moved to another corner of the office where people are not playing music aloud and talking less passionately :)
I bought noise canceling headphone, but i figured i don't like to put them on for a long time.1
Background: I'm proficient at PowerShell, I was told that I got hired to my previous job (as DevOps engineer) mainly because of that skill.
Few months after I started I wrote a script to automate some processes. My boss saw the script and told me that it was too complicated, and that I should make it more simple.
Now I'm all into clean code, meaningful names, small functions.
So the code was readable and maintainable.
I asked him in what way is it complicated. He didn't know exactly. (Later I figured that he didn't know of some of the (built-in) cmdlets and functions I used.)
He raised his hand high and made a gesture and explained that I'm "that high (skill? enthusiasm?)", then lowered his hand to a lower position to mark the bottom line, then raised it up half way up and said that he wants me here - in the middle.
After that he added: "This is not Microsoft! and we don't own the 3 other buildings that can be seen from our office window" and pointed at the window.
I was surprised by his comment, I didn't know how to respond.
I've got more stories to share about that workplace.
I can't believe I stayed at that place for 1 year and 2 months.16
I'm proud to be part of this community ;)
Thanks for the swag stickers.
My laptop is waaaaay cooler now!