Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Don't troubleshoot over my shoulder.
Don't point at the screen over my shoulder.
Don't suggest the troubleshooting step I'm currently on, while pointing at the screen and whispering over my shoulder.
Don't think out loud as you are troubleshooting over my shoulder.
1. I like making stuff that I can use again and again later.
2. I can't draw for shit, so it's a way to be creative.
3. Automating/scripting things is a general passion.
Tales From "PM vs Chen"
PM: *Walks up to Chen's cube*
Chen(that's me): *Taking off headphones* "Are we about to have another meeting about the meeting we just had?"
Chen: "Okay. Just checking." *Waits for PM to share his thought*
PM: We're almost done.
Chen: "Yes" *Waits again for PM to share his thoughts*
PM: *While walking away* "Making Progress"2
I swear this is the PM's first time experiencing a scenario where you fix a bug and two more pop up.
"ThIs ShOuLd Be SuPeR sImPlE, gUyS"
PM: Did you start looking into that stress testing tool.
Me: Literally looking into it right now
PM: Ah cool. So you'd be ready tomorrow?
PM: Why not?
Me: I literally started looking at the tool. I can't promise anything.5
The PM asks me almost hourly about my progress on this project. I am slowly training him to ask me through PM instead of face to face.
Meetings are now being taken at my desk through apps like Hangouts Meet instead of the Conference Room.
I'm chipping away, guys and gals....I'm chipping away.3
Pushed some code last night. Can't remember exactly how I wrote my changelog. I think it was coherent? Checked DevRant first.
!rant at all.
Finished my first week in my new DevOps Engineer role. Feels good, and I'm loving the change of pace.1
I have several stories from the same mentor. Programming, networking etc...
2 of my biggest lessons from him:
1. "If it has to be done more than once, it can be scripted".
2. "He who controls the network packet wins".
I wish clients knew what went into building custom features.
"Oh, you can't just turn it on?"
No...I have to write the gah damned feature FFS!
I have two managers outside of the bathroom having an impromptu meeting while I'm blowing it up.
...this is what causes psychological complexes.2
I fucking swear the servers in the data center know when the fuck I'm going on vacation.
YOU CHOOSE TO DIE NOW YOU PIECE OF SHIT!?
It's okay. It is no longer a critical box, but gah dammit.2
What I want to say to this client: You are the reason I am secretly looking for a new job.
What I say/email to them instead: I'll review the changes that were made and make some tweaks to see if it helps relieve the issues you are experiencing.
I start with the broad concept first.
"In the end, the application needs to do <this>. Okay. In order to get to <this> the application first has to know <that>".
Then, I just keep breaking this down until I get to the bits and pieces. I see the forest and then zoom in on the trees.1
I have come to realize that my stress comes from how inefficient my clients use their tech.
I have to stop caring. Is it up? Is it running? Good. That should be where my investment ends.
I shouldn't fear a heart attack or stroke because of some clients' inefficiency.
IT'S JUST SO DAMN HARD.
Co-worker: I started having this issue like two weeks ago.
Me: Two weeks ago? Why are you only telling me now?
Co-worker: I dunno. I just stopped using <program> and worked around it.
Me: Thanks for the notice, man. That helped me tremendously /s -_-
FUCKING PUT IN A TICKRT OR TELL ME THAT THERE IS AN ISSUE.
Boss: Don't be afraid to break things
Me: *breaks things*
Boss: Why did you break things?
I tried something new. Otherwise, I am hitting a wall.
I am but one man. Please remember that I am only human, and as much as I have automated, some things still take time.
I DON'T KNOW IT'S A FUCKING ISSUE UNTIL YOU MAKE ME AWARE OF SAID ISSUE. IF THIS ISSUE GOES ON FOR WEEKS, IT DOESN'T MEAN THAT I AM AWARE. PLEASE, FOR FUCK'S SAKE, LET ME KNOW BEFORE IT BECOMES A HEADACHE FOR YOU. BECAUSE WHEN AN ISSUE BECOMES A HEADACHE FOR YOU, YOY THEN BECOME A HEADACHE FOR ME.2
FUCKING SANGOMA WTF???????
You buy FreePBX and then convert great modules from OPEN SOURCE to Commercial.... I get it. Developers need to eat. But I've reviewed the new features and you aren't adding value. Just hiding precious standards behind a pay wall.
FUCK IT. I'LL CODE THIS SHIT MYSELF.1
My path into development started with my dad. He was a COBOL programmer and would bring his work home to debug by hand. He would explain his thinking and programming concepts as he went through his code.
I then got into Basic, and Visual Basic 6.0 (right before .NET). In high school CS I and CS II consisted of VB.NET and Java, but it also solidified some foundational concepts I was missing; binary, hex, flow charts, etc.
After that though, everything else was self exploration and trial and error. It all came together. I love my path, and it brought me here to devRant via the programming friends I have made along the way.
I have set up my automation through a private GitHub repo.
I know there is puppet, and salt, and Ansible.