Today my current company fuck itself.

We were in negotiations about the end of my contract/mission, I want to quit to create a company around AI.

And the actual chairman said to me "You think too highly of yourself. I could find a tenth of people to replace you so shut up and take what we offer".

30 minutes later they received my resignation. 1h after that, the 15 dev under me resigned (after two year working with us they are clearly under paid). At the end of the day, the Head of product and the two good PO resigned.

This morning I get an email, talking about suing me as I made everyone resigned and asking for a meeting.
So I went to the meeting with a lawyer, they weren't expecting it. Boring legal stuff came after that.

And the funny fact: at the end of the meeting the CIO, chief ops and the SRE resigned as well.... As they didn't want to have the run it without all the team...

Funny day :)

Last month the main product, 90% of the company use it, was launched. And in three months 80% if the IT profiles will be out...

'Normal' people when they get a new phone:
- install whatsapp
- install Facebook (or other social media)
- install regular email app

Me:
- Root phone
- Install app ops
- Install Signal
- Install encrypted email services' app
- Install firewall
- Install devRant

Anyone else like me here?

I have a couple of stories that I think are memorable from co-workers quitting in funny/interesting ways.

1. At one of the first companies I worked at, they gathered everyone to make an announcement that began with, “this is just a reminder, any heavy objects/packages need to be removed through the freight elevators, and cannot be taken through the main lobby.” We’re all thinking OK... why are you telling us this. Next part of the announcement was, “so and so (co-worker) is no longer with the company.” Apparently, which we found out later, the guy either quit/and/or got fired and wheeled his desk chair out the front door through the lobby (keep in mind this is an office on one of the busiest avenues in Manhattan). The whole thing was crazy. That’s the last we ever heard about him.

2. This one was strange. A really quiet dev at one of my previous companies was clearly constantly bored at work (he barely had any responsibility and was pretty much ignored) but the job was pretty cushy. One day, he was out from work, and no one thought much of it. Then he was out another day, then another, and before we knew it, it was like a week. No one knew where he was. Eventually, he sent an email saying he got stuck out of he country or something and he wouldn’t be coming back. Ok... weird, but kind of made sense.

But, one of our ops guys was able to see the ip/location of where he logged on to send the email, and it was right from NYC! So pretty much this guy was just fed up, left one day (with no notice), and just never came back. And then lied that he was out of the country when trying to explain is hasty departure.

Interviewing a candidate for a dev position.

Interview is over and handshakes commence.

After the interview we have a debrief in a room that has hand sanitizer in it (just coincidence).

I squirt some and it comes out like a rocket ship; getting all over one of his resumes we printed. It looks like jizz...

One of the head guys walks in a says:

“I hope he didn’t hand you the resume like that.”

To which one of our ops people, let’s call her Sara, says...

“No, leanrob just REALLY likes his resume!!!”

> I almost fucking died from laughter

So at work today my coworker overlooked my laptop running Linux with i3.

Coworker: How do you live with this?

Me: What do you mean? This is customized to work with Git and my IDE efficiently while I do dev ops with my server.

Coworker: Your mouse barely works and you operate this thing totally on keyboard shortcuts. Linux will never be a serious platform.

Me: I'm not saying you or anyone at work has to use this, I built an environment to suite my needs. Same as anyone. I thought you liked consumer choice?

Needless to say we didn't get much further beyond him thinking I was nuts for configuring my server in the cli. I swear I don't understand why I try to explain anymore. 😡

When you are Amazon employee and accidentally deleted half of internet because of S3

When someone found out that a function you wrote doesn't work.

Ranting time;

Yeah so OK this ancient legacy clusterfuck we've been maintaining and keeping alive finally broke. And even though I'm very pleased with both being right, and the well deserved right to say I TOLD YOU SO, SO MANY MANY FUCKING TIMES to all in management, it's the definition of hate to work 18 hours a day to fix the shit someone else built, that they refused us to refactor. Ah, but wait; there's more! Everyone thinks it's our fault (R&D), because historically it was our department that built the system. Ten years ago. So sales and support are now all over us, those responsible for us being in this mess are either gone or so high up in management that they refuse to take part.

Taking the fall and blame and workload, for something we warned repeatedly about, but were refused to do something with, because shiny features and new apps is what is important!

I'd understand it if the numbers were red, but they arent!! We are growing so fast it was inevitable!

I fucking hate companies who dont listen to their devs..... also companies who places ops on dev shoulders.

Yaaaargh! Also; two developers means twice as fast? No? Fuuuuuck!!!

We've got a team of around 20 developers and the most junior of them all is a interesting specimen.

The kind of person who thinks they a 'expert' in anything and everything and is constantly trying to school our senior developers who have 20+ years experience behind them.

The sort of person that spends 15 seconds googling something he has never heard of before, but now that he has skimmed 1 page on Google would classify himself as a 'expert' in said topic.

He comes into my office yesterday and proclaims that it has been decided by himself that he no longer wants to be a developer anymore and wants to do Ops/Infrastructure, then starts rambling on about how he is a Kubernetes expert.

I asked what experience he had with Kubernetes and his response was "I watched a webinar they did last night" to which I asked if he had ever actually used anything to do with Kubernetes in his life.

"No, but I'll watch a few YouTube videos and will then be more than qualified" he says

Followed by him telling me that we'll be moving all of our current Docker Swarm clusters into Kubernetes.

This was news to me (I'm head of infrastructure and operations)

I needed a good giggle, so I asked why we would get rid of our exisiting Docker infrastructure that's got a 100% uptime over the past 2 years and has worked without failure. It's truely been a dream.

He says "Because it's shiny and cool and better"

The nest afternoon he comes to me and says "When I move everything into Kubernetes I am going to convert everything into micro services"

He says that he watched a YouTube video the night before on microservices and has decided that it's what we need to use for a particular project.

(It's a simple php website that gets 100 hits per day)

Hopefully his boss will notice that he is producing no output soon. Don't want to tell the manager that the guy he hired delivers no work and lives in a fantasy land.

"your not touching the infrastructure. Ever"

Ops it happened again 😂😂

C'mon people! Spread the word! "The cloud" is not "just someone elses computer", it's a completely different way to compute!

I'm so tired of the oversimplifications done trying to explain the consept. The massive amount of work, sweat and tears put into the orchestration, automation and abstraction layers to deliver truly elastic, scalable and self healing infrastructure, applications and services deserves a fuckload more respect than "just someone elses computer"!

Hosting and time-sharing have been with us almost as long as we have had computers (mainframes etc), but dismissing the effort of thousands upon thousands of devs and ops people to make systems robust and automated enough to literally being able to throw a wrench in the engine any time during production and not have the systems suffer is fucking insane!

The whole reason the term "cloud" is so fitting is not just because it was coined from the cloud-shape used in technical and non-technical drawings and illustrations symbolising the internet, but also because of the illusion of magic it gives the end-user not being able to see "whats inside the music box".

All those fancy terms...

"Almond, I thought you said the cause of the outage the other week was that our server crashed?"

"The Tomcat server crashed, yeah. Not the physical server." (And you won't give me the time or budget to spin up any kind of redundant one, but that's besides the point...)

"Ok, but I've spoken to ops and they say none of the servers have gone offline in the last month?"

"Yup, the physical server was fine, it was the Tomcat server running on it that crashed."

"...so the server didn't crash?"

"We're mixing terms here. There's two things that can be referred to as the server. One is the physical machine, and one is an application running on it. The physical machine was fine, but
the application running on it crashed."

"What?! It's a very simple question. Did the server crash, or didn't it?!"

🤦‍♂️

Our working hours are from 9 to 6 which is the standard in Malaysia (I'm not malaysian )

Yesterday I came in around 10AM and my boss took me to his room as soon as I arrived.

Boss: If you were in school and you come late what do you expect to happen ?

Me: get punished, I'll compensate by working an extra hour today.

Boss: well our clients aren't available at your extra hour and I'm struggelling with a big client you're supposed to ship the rest of his site and golive today and he's freaking out

Me: yh well his site is done it just needs final QA before going live.

Boss: oh its done already?, cool cool. Anyway you shouldn't be late you're not Malaysian and being late doesn't run in your genes like them.

*ops manager (Malaysian) walks in*

*boss confused*

*ops manager looks him in the eye*

*boss looks at the ground*

* me giggling while walking to my desk*

Boss's son (who, despite being 19 and having no formal education or experience, was head of the technical team, consisting of one ops guys, one part-time web developer, and one part-time data entry/programmer) brought a cross bow to work. Just strolled in with it one day and took it back to his office, walking past all the visibly uncomfortable employees. One of the marketing ladies said to him "wow that's a bit scary" but it had no effect. He also wore a trench coat and kept a flying squirrel in a sock in his pocket.

At another place (not doing dev work) I had my manger tell me to type more slowly to get all my hours in, as I was promised 20/wk but they had about 3 hours of work for me to do. I quit after a month.

I hate people... I hate stupid people even more...

A person asked on slack about where download a Programming Language server called Railo. The official site is no longer up because the software was forked and acquired by a new company.

I suggested just to download that fork since it's more stable. They said no, they needed to mimic their production environment. Makes sense, so I left it alone since I couldn't help further.

Another person on slack asked which version of Railo they need. The OPs response was, "Oh whatever version you have."

My response was... "WTF... the latest version of Railo is 4.3 and the fork is 4.5... the only difference is the new name and a couple of security fixes. If you want to mimic production then you need the exact copy.. otherwise, the fork will be your best bet."

Nope.. I need Railo... any version. They say again.

!rant
I must be dreaming .... Honestly! I am with a client that knows what he wants and has no problem to express it in clear words. They understand my tech talk and talk back in tech as well. We are on the same page regarding best practises. They envy my work and have really good ideas and express constructive criticism. What is going on here? I must be in a parallel universe or something?
Okay, one downside... Coffee is not free but a cup is 20ct, which is quite alright imho anyway. Oh, the even bigger downside... Things have been so constructive that my time there is almost over since shit got actually done in the most efficient way ever!

*production is down*
Ops: At 5pm? On a Friday? *checks deploy history* God! Who did the deploy
Dev: It was a small patch, a tiny patch. It shouldn't have....
Ops: Deploy on a Friday evening?
Colleague: I didn't think it would...

Ops (on the outside) : *takes a deep breath* Its okay Dev, we can fix this. Don't worry

Me(in my mind) : for fuck sakes! Are you fucking kidding me?*** **** *** god damn it! *****

Me: I need 4gb of RAM for the server
Ops: who told you that?
Me: it is a minimum recommended setting for the software stated on their website
Ops: at the moment you you are not even using that much RAM
Me: maybe because no one is doing anything on the server ಠ_ಠ

Not me, but a colleague questioned himself for a while over this one. He simply forgot a semicolon when doing some server maintenance:

sudo yum remove application1 sudo yum remove application2

This didn't just remove application1 and 2, it removed sudo and yum too. One slightly embarrassing call to the ops team later, we had to replace the box.

This, ladies and gentlemen, is why you should automate your server maintenance!

Arrived today, hyped!

I have real-world experience with MongoDB, MySQL, Firebase, and caching with Redis.

A colleague in ops recommended this book a while back and I thought I'd give it a whirl to better understand what other options I have available.

The top two:
* the laziest intern ever!! He lived 100m from the office but was always late for the daily. Even managed to forget his fucking laptop at home!! His mommy had to wake him up!!! He was so useless that I thought he was on the first year of his bachelor's degree and later the team said to me that he had finished it.

* some frat bro, got an internship thanks to daddy inside my ops team. He managed to insult everyone in his first week!!
So I had to tell his daddy, that his son will work under the office support team and will be in charge of the first level support for his branch. Daddy fired his son sorry as after two weeks!!

I was recuited to do devops work for a client. The project started in late '14. Until mid '15 I was forced to just sit there and do nothing. And I mean nothing. The ops team needed my help but the project lead didn't allow that (endless discussions). Somewhere around the end of '15 I could start to work and quickly learned that I had to report to two leads that couldn't disagree more on what to do and how to do it. I also learned that the companies mentality is "Clean me but don't get me wet". So the ops team demands a lot but is really uncooperative with everything. So I am currently sitting between three grindstones and everything I do is worthless. Because nobody agrees with anybody and I cannot fulfill my job for which I have been hired: Make ops more efficient because they are drowning in manual work. My job is further complicated by the following facts: This company uses no standard whatsoever but their own. Thru this they have created a Rube-Goldberg-Machine. But they think their system is the greatest in the world and the only one that makes sense. Which makes automation pointless because it is not maintainable. They call it diversity and they say that it is the clear reason why automation is not for them even though they schedule meeting after meeting in which they discuss about how to automate things. But in general they do just block everything useful and sabotage my work. And behind my back they make me the reason for the fail. Every real decision is blocked anyway. Also the ops guys think they are the leetest in the world. And everything they invent is above and beyond. If you ask them why they have over 400 VLANs for example (in a company of unter a thousand employees) they stutter and stumble because they cannot explain their complicated shit. They also change their decisions like underwear. Another really "kewl" thing they just did: They hired a devops engineer and everybody loves him. During the interview he said that he has no prior experience with devops whatsoever and it will take him around six month to get started on the basics of devops. I could go on for hours here about the insanity of this company that in my opinion will cease to exist within the next 5 years, if you ask me.
Long story short I am getting out of there by the end of march and will be on sabbatical shortly after because I am burned out. And I mean burned out. Not like "Oh I am burned out". I mean really burned out, with health problems and everything. Another external guy got out here last month because of the same health conditions.

Ops person: “Hey! Can you come fix this? I‘m trying to add a user and it keeps giving me an error saying that the phone number must be unique. What’s the ETA on a fix?”

Me: 😓

Let me tell you how shit flies in Aerospace&Defense companies in certain place in on earth

1. Your dev. PC is isolated from the internet. You can not download any software/library etc directly. "Legal" way takes literally days and you must all effort for it to work. I will not discuss the details of legal way but it is not asking IT team to download it for you, you do it yourself.

2. You use an archaic requirement standard that is somehow used by all other similar companies too. These companies f*ck each other in the arse when they are working on projects together(hiding details from each other which is necessary most of the times etc.) but they were kind to each other when it came to share shitty req. standard.

3. When you try to switch to new requirement standard, you waste weeks only to amend the old one, because everyone is using old one for all projects, so changing it would upset old guards in the company(which are people works in same project for 10 years, no personal development)
4. You came 1 minutes late, you fill the "minutely permission" form.

5. You already work long hours per day and they remove your small breaks during day, because developers use those breaks longer than intended(I wonder what might be the reason...)

6. A technology can not be adopted into current projects even it has objective advantages proven many times in the outer world, because old guards(developers), IT team and configuration management guys(poor man's dev ops role sometimes) can not change their ways.

I hate this shit...

Frequently used answers :)

UI developer - I think API is not working
Backend developer - Front end is not sending the request correctly
Tester - Testing! Testing!
UI/UX - As per android/ios standards...
QA - Let me check one more time
PM - Let us have another meeting and get on the same page
Dev-Ops - It's very complicated you know
CTO - We're working on a next-gen solution
Founder - Let us build something that no one has built, something similar to what google...facebook...

Cridits: My EX-CPO

TLDR: There’s truth in the motto “fake it till you make it”

Once upon a time in January 2018 I began work as a part time sysadmin intern for a small financial firm in the rural US. This company is family owned, and the family doesn’t understand or invest in the technology their business is built on. I’m hired on because of my minor background in Cisco networking and Mac repair/administration.

I was the only staff member with vendor certifications and any background in networking / systems administration / computer hardware. There is an overtaxed web developer doing sysadmin/desktop support work and hating it.

I quickly take that part of his job and become the “if it has electricity it’s his job to fix it” guy. I troubleshoot Exchange server and Active Directory problems, configure cloudhosted web servers and DNS records, change lightbulbs and reboot printers in the office.

After realizing that I’m not an intern but actually just a cheap sysadmin I began looking for work that pays appropriately and is full time. I also change my email signature to say “Company Name: Network Administrator”

A few weeks later the “HR” department (we have 30 employees, it’s more like “The accountant who checks hiring paperwork”) sends out an email saying that certain ‘key’ departments have no coverage at inappropriate times. I don’t connect the dots.

Two days later I receive a testy email from one of the owners telling me that she is unhappy with my lack of time spent in the office. That as the Network Administrator I have responsibilities, and I need to be available for her and others 8-5 when problems need troubleshooting. Her son is my “boss” who is rarely in the office and has almost no technical acumen. He neglected to inform her that I’m a part time employee.

I arrange a meeting in which I propose that I be hired on full time as the Network Administrator to alleviate their problems. They agree but wildly underpay me. I continue searching for work but now my resume says Network Administrator.

Two weeks ago I accepted a job offer for double my current salary at a local software development firm as a junior automation engineer. They said they hired me on with so little experience specifically because of my networking background, which their ops dept is weak in. I highlighted my 6 months experience as Network Administrator during my interviews.

My take away: Perception matters more than reality. If you start acting like something, people will treat you like that.

Dear Product Owners,

If you tell me how I need to architect my software again I'm going to ask you to provide a network topology of the architecture you want me to build.

I'll also need you to request the new servers, work with the ops teams to setup credentials, provision the NAT, register the domains and document the routes that the proxy will need to use.

then I'll need you to hook the repo up to our non-existent pipeline so that I can make sure I won't do all that testing I already can't do.

I hope you're paying attention, because that framework you told me I needed to use is going to be a pain to setup correctly.

after you're done with that, please attach any documentation you shit out to the ticket you never created.

Enragedly yours,
Looking for a new job

PS: get fucked

worked fine in dev....

Sold the company and started working fulltime at a company in a different sector a year or so ago.

Today one of the ops people comes up and says that someone is on the phone asking for me.

One of my old clients apparently had a question about their site. Turns out that they tracked me down on LinkedIn, and called my new company's public line just to see if I would be available to help them out.

Fortunately the new powers that be took that one in their strides..

ops, the haiku:

i built the pipeline
that the devs kept asking for.
it never got used

Interviewed at a pseudo-startup (not quite a startup, but later realized run and organized like one) where the VP of dev ops seemed eager to have me in. I sent him my code sample and he said he'd schedule an onsite. Weeks went by without a peep.

Being persistent, I kept emailing, figuring the environment still might be worth the apparent lack of interest... Eventually the dude told me he'd been away on "travel" and he didn't check his mail. He said come on by if I was still interested...

I went in and met with a couple people on the team, interviewed (I think) well and he said he'd be in touch. Another two weeks -- nothing. I emailed again, he said they hadn't reached a decision. By this time, I'd pretty much written it off. I never heard anything back. No good, no bad.

Moral of the story, don't waste your time on anyone who doesn't respect it enough to give you theirs.

!rant

I've been struggling for the past year with:

Dev work
Ops work
"Management" work

This last month I made a decision, I don't give a fuck anymore and just gonna do my dev work which is the one I'm paid to do.

Never been better. Its healthy whem you let all those fucks go away :)

Should a developer really have to be a jack of all trades? I write code, but at work I feel like I am always getting pulled into sysadmin debacles. I am not a sysadmin or an ops person. I am a developer, not a systems guy.

If you want me to be a systems guy, then train me to be one. You hired me to write code, not to troubleshoot shitty IBM Application Servers.

Conversing with developers can be frustrating.

Here is a good one from today. 2 people 1 women (let’s call her W) and one man (let’s call him M)

W: “Hey guys! Our team is looking for lots of great developers. Front end, back end, data, dev ops. At above market salaries with a great team! Reach out to me is you want to chat. I would love to hear from you.”

Translation: I have a great offer and want to help others achieve and strive in their careers.

M: “also, guys/less-gendered-alternative plz” proceeds to chastise this women about using the word guys.

Translation: I have no level of social awareness, but I have a need to feel big and important. So I’ll take offence for those who aren’t offended to make me feel better about my lack of fucking personality.

————

I’m not really concerned about opinions about the gender issue. It isn’t about that.

It’s just tiring dealing with these people’s bullshit.

It’s time to grow up folks, stop arguing on the fucking internet.

————

I also once saw a developer chastise 2 women we worked with while we were out for drinks for the exact same thing; using the word guys.

He was so busy “defending” them from themselves that he ended up making them uncomfortable and then they left.

He was saying “don’t exclude women” while fucking excluding the only women there.

What a fucking douche.

At the beginning of April there were 9 of us in Ops, come May there will only be 3 of us left. :/

They've left because they disagreed with some the CTO was trying to do and he fired them, or just because they hate him. Every week it's a new game of "Who's going this time?".

hi! I'm your friendly neighborhood sysadmin/operations bastard. I also write mostly okay python, ruby, and c.

This is called devrant because it's where you go to complain about devs, right? /s

anyway, hello!

If I recognize someone by their username or remember their name.. it's usually a bad thing because they're on my mental blacklist for fucking up Production....

Ahh life in IT Ops...

My client's using some legacy server side software. I set it all up nice and isolated with proxmox, tunneled it through cloudflare, got the folks to do their install on a windows vm, passthrough their licensing usb. Hosted GLPI on it too (system inventory) and so on.

Wait for it. Windows Server refuses to accept local or domain passwords. WTF. Even went ahead and did a Utilman reset on it which lets you use an admin cmd prompt to the login screen where you could reset the password. Insane that it was even possible, but no good.

Client blamed linux for it, I switched over to Windows Server on baremetal. I setup Hyper-V thinking it should be just as capable as KVM.

Nope.

Guess what, you can't pass through usb for licensing (the legacy software). MOFOS DECIDED TO install it baremetal. I couldn't even get hyper-v to create a decent virtual network. It keeps changing all my network adapter settings. I COULDN'T EVEN PASSTHROUGH PCIE NETWORK CARDS.

This feels like an eternally stagnated, mossy soup of abandonware.

FUCK YOU WINDOWS. You've been sore pain the ass for EVERYONE.

Wouldn't it be great if the comments posted by an OP would be highlighted in some way? Like a small subtle dot behind the name of the OP in the comment?

I often find myself scrolling to the top of large topics because I have to look up the OPs name :o

Tonight do not forget to raise a glass to Ops, oncall developers, DBAs and devops, field engineers, warehouse operators. Thanks to them, we can afford to meet the new year properly.

They are working tonight so we wouldn't have to.

Cheers

Just another normal conversation as a Kubernetes Operator

So... I've got a confession to make.
I'm no longer a Dev. After the disaster that was my last commercial gig, I went and got a sec Ops role... And I love it. It's just technical problem solving and explaining all the way.
Don't get me wrong, I still love to code. But that's exactly the thing. As a commercial developer employed by corporations, I spent close to 80 % of my time not coding, but in useless meetings, or trying to figure out just what my colleagues thought was "common sense", reverse engineering their work and documenting how to get it running, etc. Basically, fixing shit for braindead academics with next to no real world experience.
Now, when I code, I get to do it on my own terms, with my own stack and as much comments and docs as I want to have. I own my time, and the only ones that are allowed to interrupt me is the local fire department.
I can do what I'm fucking passionate about and leave the rest for the useless people.

Web, Desktop, Mobile, Front, Back, Ops, Data, etc. Why is there so many cool possibilities ? ! I can't decide.

MARKETING IS A MENACE FOR SOCIETY and a large waste of time and resources.

Imagine that for some very stupid reason people were allowed to steal cell phones from unsuspecting victims and sell it on open market legally, tax invoices and all.

One could create a business like this. Steal some lad's brand new $600 iPhone and sell it for $280, because why not?

That is marketing. A company goes and makes a phone for lets say $180. Add in taxes, shipping and development costs, and we get to $300. Put some real nice profits on top (let's say 40%) and we get to $420.
The last 180 are the cost of marketing for society.

Today some stupid marketing conmen goosesteps into my lab and says that we must use Tensorflow and in-memory databases and multicloud redundancy and, I kid you not, "profound learning".
WE HAVE A FREAKING LOGISTICS OPS APPLICATION.
"We are putting it on the brochure, those technologies are set to sell well in our core market, and improve employer-branding" says the conmen.

A request for a feature is one thing, a request for an whole other technology because some snake-oil salesmen read the term in some clickbait rag and thinks that some starry-eyed moneyhead will pay extra because the brochure says "NOW WITH 2X MORE TECH!" is just an assault on society.

!rant
TODAY WAS A SUCCESS!
-learned how to forward ports
-hosting a minecraft server
-made that stupid HP stream USEFUL
-i actually feel good about myself

note: modded server. You'll need Mantle (1.7.10), Tinker's Construct (1.7.10) and Ultra Block Compression (1.7.10).

pretty sure whitelist is disabled. the max is 50 players, not sure how good the connection will be. be nice to the ops, YoungWolves and Mehrsun

ip: 66.243.225.51
(default port)

again please be polite, the two OPs are not techy at all, but very nice gals

Hotest bug: a server in Vietnam kept going offline then popping back a few seconds later. While logged on I couldn't find anything wrong, so eventually I decided to go check on it. It turns out the aircon in the server room situated right above the server has started leaking, so the ever-helpful ops people onsite has wrapped the whole rack in plastic, covering all vents. Surprisingly hard to kill, old HP servers...

Coding without propper dev-ops:

These are the shittiest five lines I've ever read in my life!

Yeah, force push it to master!

Just saw a role advertised for a front end developer. Skills required amongst other things·
· Integrating with middle-tier microservices such as NodeJS

· .NET Core (2.1+), C# 7.0+ and JAVA

· SQL Server, T-SQL, MySQL

· Azure Dev-ops

There are other standard and expected front end requirements but want someone with 4+ years experience

Salary £19,000 - less than two thirds of the national average salary for non UK folks.

Applications: 0

Hmm I wonder why

I see a lot of people with shitty interactions with recruiters, but I have the chance to work with one to get into what I want to do (net ops incident response) if I call this recruiter.

Backstory: friend applied for a position, got offered this morning (not going through a recruiter) AS recruiter called him for another position within same company. Friend explained situation, but said someone (me) might call recruiter to talk.

Job would increase salary by minimum of 25% and is much closer to what I want to do. Even if I'm still on call, it's a larger team and I'm interested in the stuff.

How do I not get screwed by recruiter? And am I am ass for applying when I know it's < 1 year and I'd be leaving my team down 2 people (so at half capacity)? And do I care?

I accidentally started a reindex on a collection that had 14 million records in the middle of the day. Caused an outage in a major portion of our applications for about 3 hours. Worst thing was that once I pressed enter, I realized that it was for the production database, and not the staging database like I intended. I immediately went to go tell the dev ops lead, and he basically said, "whelp, let's just sit back and watch the world burn. Not much we can do about it"

// First rant
currentUser.Post(new Rant("

Quick question here, not a rant (sorry).
I heard that you need a lot of math knowledge to become a developer. Is this really true? I don't see where the math comes into play while programming (especially complex stuff). I've been studying C# for quite some time (few years) and I consider myself fairly good at it.

Never came across the need to use !basic mathematics in my projects.
I know that to study computer science at an university requires a certain result in maths, but is that all you need math for? Getting into uni?

Could somebody explain this for me? I'd really appreciate it.", "maths,university"));

Operations: Can you exclude some user records for the website? These are obsolete and we don’t want users to access these anymore.

Me: So what are you using to indicate the record is obsolete?

Ops: We changed the last name field to say “shell record - do not use.” Sometimes it’s in the first name. Actually, it gets truncated to “shell record - do not u”.

Me: A…text field…and you’re totally ok with breaking user accounts…ok ok cool cool

Not cool 😳😬🤬 I’m not causing more chaos because your record keeping has gotten messy

Killed the backend production db of my app with a dev ops guy for 20 hours.

The emails I received were not the nicest of all time.

This is how Over Ops blog forces its visitors!! As a result, closed the freaking blog!!

Fuck my company. Let the technology people work with technology.

I work at a small company who constantly brings in people who are absolutely useless. The project manager requires me to take items out of azure Dev-ops into an excel because he will not take the time to understand how a board works. The business analyst hands bullshit requirements in formats which no one but him can understand under the pretense that the Devs and architect can ask him when they feel like it. The CEO wants a power-point which again the technical teams have to prepare for him because the project manager or BA will not have time for it. However they make sure to gut the estimates handed over by the Dev team and introduce unfeasible deadlines.

Meanwhile the client has zero problems as the work still somehow gets done due to people in the Dev team overextending. Goddam leeches wasting mine and my teams time doing bullshit.

Never buy crappy, consumer-grade SSDs for use in production servers/RAIDs. This might sound obvious but at the company I used to work for, through a series of bad decisions by management and cheapness, we ended up with the cheapest consumer SSDs you can imagine powering all of our storage.

This turned into a nightmare spanning years of failed hard drives and a continues cycle of ridiculousness. Drive failed after a few days, gets taken out, sent back to manufacturer and then replaced with another equally crappy drive destined to fail within days/weeks.

Our ops people were going to the data center multiple times per week to replace failed drives. Lesson I learned: cheaping out on system-critical hardware and software can have long standing consequences and in the end usually doesn't end up actually saving money when you account for time employees have to spend dealing with issues that result from it.

porra; caralho; toma no cu.

this fucking shit xamarin. I wish the ass who programed the xamarin vs2017 integration to go fuck off.

srsly, I just want to fucking code this fucking fucker VS2017 keep shitting all around me

first I was gonna install it. didn't install because no memory left. fair enough, my fault there.

cleaned 35 gbs.

finish installing VS, with xamarin. FIRST GOD DAMN TIME I create fucking project, 2 fucking errors and 3 warnings. I DIDN'T EVEN TYPE A COMMA.

ok, tried fucking it. it seems to be conflict between version of Android and xamarin forms. fucker you it shouldn't be like this. anyway.

tried downloading the updated Android version.

it failed at 80%! what error you ask? missing fucking space ok, fuck that thing is huge, ok, my fault again. uninstalled all programs I was not using, all projects I'm not current working on. more fucking 30GB free. tried again. ANDROID IS TOO FUVKING HUGE CAN'T INSTALL IN 30GB!!!

Ok. instead of updating android, gonna downgrade xamarin, can't downgrade. ok gonna remove and install an early version.

unistalled. CAN'T FIND XAMARIN DLLS.

I was like, fuck this project, gonna start a new one. ok, all seems fine, for some weird reason. Except no. I try adding a new page, ops, APPARENTLY VS2017 CAN'T LOAD A GODDAMN .XAML

Ok, I can create a .cs page. done, except now I get a fucking timeout error. fuck.

I search the internet for a workaround, see a guy saying I could manually add a .xaml + .cs by creating this files and then adding them to the proj file.

did it. I go again, everything seems fine. but now I can't freaking reference the damn page.

I'm fucking losing my mind here.

In the mean time I have to turn in this project at the end of the week AND I CAN'T FUCKING OPEN THE GOD DAMN FREKING PROJECT PROPERLY!

FUCK. MY. LIFE.
FUCK XAMARIM AS WELL
FUCK VISUAL STUDIO
FUCK MICROSOFT
FUCK THAT DAMN SSD
FUCK THAT BOSS WHO THINK THAT A 128GB SSD IS ENOUGH
FUCK IT ALL...

For the past 45 days I've been the sole developer of a standalone Java application and doing some ops only, now I'm getting back to the spaghetti php bullshit they call code and for the past 5 minutes I could fell the depression striking back...

Rant time. So, me and a few classmates finally finished and handed in a website for a web development class a few days ago. Before we handed it in, we had a meeting with the professor to discuss what we still needed to do.

Us: Are we missing anything?
Prof: Nope. Looks good. Just make sure you have stylus implemented.
Us: Cool, thanks.

We got our grade back today. We didn't do as great as we'd hope, and here's one of the comments that the professor left us:

"You forgot to implement all of the CRUD operations. -4"

WHAT THE **** IS THAT? We asked you if we were missing anything, and you said no. You reminded us about stylus, which we looked at ONCE in a 13-week class, but you failed to remind us that we needed all of the CRUD ops?

I'm getting really tired of those dumbass programmers that do not understand shit and then come to me when production breaks. (I am also a programmer, not really a DevOps engineer, but I'm the least worst at DevOps stuff, so it's my job...).

We're programming some kind of document management tool. Today we had a release, and one of the new features is to download all of your documents as a zip file, which is asynchronuously generated. When it's done, the user gets a mail with the download link to the zip file.

The feature works basically, but today it broke our production service, as somebody was running a test of it.

Turns out all the documents are loaded into memory to be zipped. So if you have 2 gigs of documents, a container with memory restrictions in that area will crash.

I asked the programmer who reported this «ops problem» to me, why he didn't just shit the files into a temp foler in order to zip them in there.

He told me that he wanted to do so, but did not know how to mock this for a unit test, and therefore went to the in-memory «solution», which was easier for him to mock.

For fuck's sake, unit tests and mocks are fucking tools, not ends in itself! I don't give a fuck about your pointless mocking code when the application crashes!

When I got to deal with such dumbasses, I'd prefer to mock those motherfuckers with a leaky bucket of liquid shit, which basically accomplishes the same task from my perspective: dripping shit all over the place and make everything suck as fuck.

To all the Java Teams that died during the fucking Mobile Civil War, We salute you!

1. Millionaire 2011
2. Splinter Cell: Double Agent
3. Dragon Ball Z Saiyan Fighters
4. Moto Girls
5. 24 Special Ops
6. Thor: The Dark World
7. Kung Fu Panda
8. Worms 2011: Armageddon
9. Asphalt 4: Elite Racing
10. Resident Evil - The Missions
11. Ghost Recon: Future Soldier
12. Spider-Man 3
13. Need for Speed - Undercover 3D
14. Contra 4
15. Rambo on Fire
16. Fast and Furious 6 
17. Counter Strike 3D
18. Men in Black 3
19. X–Men Origins: Wolverine
20. WWE Legends of Wrestlemania 3D
21. 3D Fight Night: Round 4
22. 3D Ultimate Rally Championships
23. Assassin's Creed
24. Zuma
24. Die Hard 4
25. 3D WWE Smackdown Vs RAW 2009
26. Prince of Persia 3: The Two Thrones
27. 3D Fight Night: Round 3
28. Super Mario Bros
29. Bruce Lee - Iron Fist 3D
30. Naruto Adventure: A New Apprentice
31. FIFA 2011
32. James Cameron's Avatar
33. Racing 2: The Real Car Experience
34. King Kong
35. Gangstar City
36. Iron Man 3
37. XIII 2: Covert Identity
38. 4x4 Extreme Rally 3D
39. Real Football Manager 2013
40. Splinter Cell: Conviction
41. 2008 Real Football 3D
42. Assassin's Creed 2
43. Hummer 3D
44. American Gangster
45. Real Football 2009
46. 3D Football: Real Madrid 2010
47. Xtreme Dirt Bike
48. Tekken Mobile
49. A Good Day to Die Hard
50. The Amazing Spider-Man 2
51. Asphalt 3: Street Rules 3D
52. GTA IV Mobile
53. 3D Contr Terrorism
54. Real Football 2015
55. The Amazing Spider-Man
56. Contra 4 (2009)
57. Mortal Kombat 3D
58. Bad Girls
59. Assassin's Creed: Brotherhood
60. Need for Speed: Hot Pursuit 3D
61. God of War
62. PES 2009 (Pro Evolution Soccer)
63. Ultimate Street Football
64. Assassin's Creed: Revelations
65. Prince of Persia: The Forgotten Sands
66. 3D Super taxi driver
67. Gangstar 2: Kings of LA
68. Asphalt 6: Adrenaline
69. Assassin's Creed III
70. Danger Dash
71. Real Football 2014
72. Gangstar - Crime City
73. Gangstar 3: Miami Vindication
74. Modern Combat 4: Zero Hour
75. Zuma's Revenge!

We know you guys did your best but the world is a fucking shit hole. We still remember your hard work!

76. Mission Impossible 3
77. Gangstar Rio: City of Saints (I guess these were your last days at work. Well-done guys!)
78. Real Football 2010
79. Real Football 2011 (Real Soccer)
80. Real Football 2012
81. PES 2011 (Pro Evolution Soccer) 
82. Ultimate Mortal Kombat 3 (My Favorite)
83. And those missing the list.

WE SALUTE YOU ALL!!! ∠(^ー^)

List of shit my superior said and wrote in the project:

1. Prefer to write "pure" SQL statement rather than ORM to handle basic CRUD ops.

2. Mixing frontend and backend data transformation.

3. Dump validation, data transformation, DB update in one fucking single function.

4. Calculate the datetime manually instead of using library like momentjs or Carbon.

5. No version control until I requested it. Even with vcs, I still have to fucking FTP into the staging and upload file one by one because they don't use SSH (wtf you tell me you don't know basic unix command?)

6. Don't care about efficiency, just loop through thousands of record for every columns in the table. An O(n) ops becomes O(n * m)

7. 6MB for loading a fucking webpage are you kidding me?

Now you telling me you want to make it into AJAX so it'll response faster? #kthxbye

them: welcome new project members, this is our CI/CD pipeline which is completely different from the rest of the company, there won't be any great knowledge transfer, we just expect you to be able to know and use everything. but also, we expect you to work on your tasks and don't waste any time.
me: okay, so my tasks aren't going as fast as expected, because I need to invest some learning so i can set up my project correctly.
later: some help would be nice, i'm stuck right now
coworker: *helps me to fix my problems, which were partly due to misconfigured build servers* i know it's a lot, and unfortunately, for this topic sources on the web aren't so good. i can really recommend this book, this will give a deeper understanding of the topic.
me: okay, yeah i mean, tbh, i'll read the book if the project invests some time for me so i can learn everything that's required, but this won't happen. also, some initial workshop on the topic or anything would have been nice.
coworker: well, i mean, i am a software developer. for me, it is normal that i learn all that stuff in my free time. and i think that's what the PM expects from us.
me: okay, that's fine for you, i mean, if i'm interested in a topic, i will invest my private time. but in this case, PM would just expect me to do unpaid labor, to gain knowledge and skills that i can use in this specific project. i'm not willing to do that.
coworker: ...
me: ...

it's not that i don't want to learn. the thing is that there isn't any energy left by the end of the day. i'm actually trying to find some work life balance, because i don't feel balanced right now, haven't felt since i started this job.
also, this is only one of several projects i'm working on. it's like they expect me this project has top priority in my life. if it wasn't so annoying on different levels, maybe i'd have a more positive attitude towards it.

also, at the moment i find it fucking annoying that i have to invest so much time in this dev ops bullshit and this keeps me from doing my actual work.

if they are unhappy with my skills, either they can invest in my learning or kick me out. at this point, either is fine for me..

DevOps is less of Dev and more of Ops. #FML

Ops, it happened again 😁

Morning from London, nerdmigos.
Happy Coding, Ops, Testing or whatever COOL shit your doing today.

People who don't ++ OPs, nor comments or add anything of value on social media / thread.

Please.
What is your purpose but self projection?

Not sure how to handle this one. My new company gave me a surface laptop to do dev ops work.

16 gigs of Ram but only a 256 SSD?

Nothing is installed so far except for MS office and acrobat and I am already running into memory issues.

My last work machine had 1TB HDD and 128 gigs of RAM (i know overkill but I could have several VM’s up and running at once).

What the fuck? Apparently the CTO ordered this piece of shit.

Also no mirco SD card like other models so I have no idea how this is going to fucking work.

I no longer work for a startup company. On Monday I’ll start work for a real company, one that values project managers and their infrastructure. As a DevOps engineer, I value the IT resources that power my old companies SaaS platform. My old position is not being back filled and they’re hiring a full time dev instead of and Ops engineer. They have chosen to proceed with zero employees who know Azure or the platform their own software runs on.

Word to the wise when choosing to work for a startup. Ask these questions:

- Do they have a dedicated product manager/owner , who isn’t also the CFO?

- Do they value infrastructure and their IT resources ?

- Do they have decent powered laptops to work with?

- Do they have too much technical debt because they’re always building new features ?

- Do they work 18 hour days because they set poor work/life boundaries ?

- Who handles Support tickets , and what’s a typical support issue like?

- Do they have a branching and merging strategy? Don’t accept “we’re too small” as an answer! It’s a trap that they don’t want one.

Fuck Shibboleth and its documentation, fuck examples for configuring it, ops sorry they have no examples at all so fuck them, fuck SAML fuuuuck!!!!! And I almost forget FUCK JAVA

Today is Day Two of my Dev Ops Internship.

The only tasks I have been assigned today is GDPR compliance training, which I did not realize could be stretched out into so much repetitive detail.

I also sat in a meeting with a dev who committed his artifact builds to git and now needs us to remove them for him.

Also, I keep getting called Dylan. My name is not Dylan.

In my current company (200+ employees) we have 3 guys who deals with everything related to service desk (format computers, fix network issues, help non-tech people...)

The same team is responsible for the AWS accounts and permissions, Jenkins, self hosted Gitlab... anyway, DevOps stuff.

Thing is: only one of them have enough DevOps background to handle the requests from the engineering team (~15 people). Also, he usually do anything "by hand" clicking trough the AWS interface on each account, never using tools like Infrastructure as Code to help (that's why I started to refer to his role only as Ops, because there's no Dev being done there).

Anyway... I asked my manager why that team is responsible for both jobs, despite the engineering guys having far more experience with those tools. He answered with a shamed smile, as he probably questioned the same to his manager:

- Because they are responsible for everything related to our Infrastructure.

Does it make sense for anyone? Am I missing something here? In what universe this kind of organization is a healthy choice?

If they followed my suggestion and went straight to debugging the server issues they would have been solved it from week 1 and everyone would have thought the migration had a minor performance hiccup. In fact, we have already done such at least twice before and nobody batted an eye.

Instead they self-labelled the migration a failure on first error, setting the stage for apologizing to the client, and put themselves on the spot for a whole staging / production signoff, replication / backup worfklow, almost a blue-green "seamless" deployment reminiscent of DigitalOcean.

Well they're not DigitalOcean, and anyone who has spent any time understanding users knows they will not participate in "new system" tests long enough to find or report issues.

So of course the migration stretched out to almost three months up until the whole reason for the migration - the rapidly escalating risk of the old provider disappearing - hit like a freight train and now they have to go through the problem of debugging the server like I told them to on week 1. Only this time they've set the client mindset against it, lost any chance of reverting, have had grave risk for data loss, and are under pressure to debug other people's code in real-time.

This is why I don't trust devs to do ops. A dev's first solution to any problem is to throw tech at it.

Every time I feel Im getting my act together (at work) there is some AWS service which I know nothing about and that totally kicks my asss

Geeez the dev ops side of things is a total void for me..

!rant

Original posters (OPs) should be referred to as original ranters so that the abbreviation is OR

A coworker changed the application deployment process. He told all three of the other developers who need deployments, but not me. We sit six feet away from each other and I've run/managed deployments for a year longer than him.

His new process doesn't work and he's blaming the dev ops team for not following it. The new process clearly doesn't fit their workflow and never could have.

The lack of deployments have caused production issues and he still won't ping dev ops to remind them about the deployment because "it's not in the new workflow".

He's been painting dev ops as incompetent at the last three retrospectives without having ever personally reminded the deployment guy.

Ugggh.

Thoughts on forced emergency support?

I am with a company I generally like a lot but there are some things I generally despise about it. Like forced emergency support.

I am not good at it, I don't claim to be.. I generally struggle with anxiety, stress and depression, I specifically avoid roles that require on-call service .. I'm a senior level software engineer.

I find it very frustrating to be expected to be on-call from 7-7 in support of infrastructure I did not architect, did not code and basically know nothing about. They provided me with a ten minute discussion about ops genie and where to find internal support articles for my training and that's about it.

Last night I received an ops genie alarm and acked it as I was instructed to do, I went around the system looking for the alarm cause and basically had no idea what to do except watch our metrics graphing praying there wouldn't be an outage. Fortunately the alarm was for our load balancer scaling operation, it was taking a bit longer than usual ... Sigh of relief. Stay up til 6am and fall asleep..

Wake up to a few messages from various people asking why I didn't do this and that and it took me every inkling of my being to remain cordial and polite but I really just wanted to scream and say a bunch of shit that would probably get me fired.

What the actual fuck?

Why expect someone that has no god damn clue what they are doing to do something like this? Fuckin shit training and no leadership to mentor me and help me get better at this role, no shadowing, no regiment ..

#confused and #annoyed

Thoughts? Am I a bitch? Is it unreasonable for me to expect my job duties stay in line with what I'm actually good at!?

Thanks.

Today was a SHIT day!

Working as ops for my customer, we are maintaining several tools in different environments. Today was the day my fucking Kubernetes Cluster made me rage quit, AGAIN!

We have a MongoDB running on Kubernetes with daily backups, the main node crashed due a full PVC on the cluster.

Full PVC => Pod doesn't start
Pod doesn't start => You can't get the live data
No live data? => Need Backup
Backup is in S3 => No Credentials
Got Backup from coworker
Restore Backup? => No connection to new MongoDB

3 FUCKING HOURS WASTED FOR NOTHING

Got it working at the end... Now we need to make an incident in the incident management software. Tbh that's the worst part.

And the team responsible for the cluster said monitoring wont be supported because it's unnecessary....

Just needing somewhere to let some steam off

Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.

For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.

Introducing Rancher

We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.

Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.

As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.

Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.

Follow-up on yesterday's rant.

Boss hired dev-ops team to restore data from the broken server image. They said it may be completely impossible. Which will probably make clients want to kill us considering it's an government agency.

I wonder how large the contractual penalties will be considering they are almost completely incapable of working without the system and it's going to be few days until anything will be fixed.

Oh well, since no one bothers me it seems it's currently not my problem and I'm free to code ¯\_(ツ)_/¯

What browsers do front end devs here normally test on? I test on Firefox and Chrome because...that's all I use, but what about Edge/Safari or god forbid IE11?

I'm more familiar with backend dev ops so my testing consisted of checking Firefox a lot. :P

Consulting/contracting for a company, and their lead developer/ops guy quits without warning. This leaves me as the only one with the somewhat technical know how but without access to do anything to move any changes to production....

After a rough exit from one company, I was diverted into Ops just to continue to have food on the table and keeping the lights on. This, over time, unfortunately made me more or less unemployable as a dev again. Got stuck in that place 13 years doing almost no professional coding.

During the last 5 years I took courses, got side jobs writing articles and tutorials, went to interviews and generally worked hard to get the fuck out of ops and into development again.

After getting to choose between level 1 customer support and quitting in a re-org, I quit without having a new gig. I got a lucky break through someone I'd worked with earlier to start a junior position working on some legacy systems with legacy tech.

After all that work late nights churning away using up my passion for coding, I now can't make my self pick up even Advent of code or Hacktoberfest... My passion is dead... I hope I get it back, but for now I fill my spare time with my guitar...

*Finished the deploy*
*Dusts collar*
"Easy pesy"
Few hours later
*slack tone*
Production inaccessible! Blackbox crawler failed with message 5xx.
And that was the day little Charlie learnt dev-ops is not fun and thrilling.

I coded part of feature 2 months ago.

Left it to help frontend guy a bit, deal with fire after release. ( we’re missing frontend integration tests and every release is pain in the ass ).

My backend code coverage is about 80% so not much can go wrong at this point.

So I added more code today and it looks like new feature is working but don’t know what the code I added 2 months ago exactly do.

The only thing I know is that it definitely needs refactoring ...

Being only backend dev / release manager / administrator/ dev ops in project is painful I need to deal with everything on my own 😔

At least client doesn’t care if it’s done in one week or in one month right now.

Our agile scrum team has finally shattered into two parts.
On the one hand we have front-end guys.
On the other hand we have backend- /dev-ops guys.

The FE guys don't care about the BE guys business.
They don't join pairworking and only noticing things that went bad, when a Backend guy has caused it.
Goodbye fullstack dev-ops team...

I really dislike that arrogant basterds.

Frontend Hobo-Bitches...!

I've only been here for 1 month for my new position in Ops, and I already miss software development!

All I do everyday is just typing commands on the terminal.
If I am feeling fancy, I may create a script or two (that's the closest thing I have to writing code).

I hope I can get more interesting thing to do in the future. If not I can't see myself doing this in long term. It's OK for occasional tasks or added responsibility but I don't want to do it as my main job.

Avoid ACPICA if at all possible. It's one garbage tier cluster fuck of bad design, horrible documentation and downright misleading and wrong code

It's meant to consist of an ASL compiler, disassembler, debugger, dumper, various user space utitilies and a kernel resident OSPM implementation *if* you can figure out what belongs to what. Even just compiling this pile of trash is a mystery in itself. Think you need the source files in source/common? EEEEH, wrong. Well, at least partially since most of them seem to be for the user space stuff..? Other ones *are* needed on the other hand. At least the disassembler and/or debugger and/or dumper components seem to reference them. Not that I could figure out how to compile those anyways. The real path to your goal seems to be to ignore a seemingly arbitrary subset of source and header files until your linker stops complaining

There's also a bunch of configuration defines, some of which *you* define, some defined *for* you, based on again others. Of course most of them do stupid shit. Enabling the debugger automatically enables debug logging. Enabling the disassembler force enables debug allocation tracking... What?

The code itself isn't of much help either. Looking in "os_specific/service_layers" you find what looks to be reference implementations of acpica functions in certain os' like windows and unix. Of course I had a look because AcpiOsReadMemory is supposed to read physical memory and I don't know how I would even implement that. But hey, osunixxf.c (xf for interface... of course) should tell me. I'll let you see for yourself in the attached image. Apparently it does fuck all and just returns AE_OK. No error, no logging, no nothing. Just ok. As you can imagine, AcpiOsWriteMemory doesn't do much more either.
...okay so maybe physical memory accesses aren't actually used and these functions are some sort of relic from past times? Nope! They are absolutely necessary for doing low level device interaction. WTF. So finally I went to the linux source and checked how *they* implemented them, and just as I thought, these functions are anything but no-ops...
...So for what fucking reason do these stupid interface implementations even exist but to purposefully mislead you?? They aren't used for fucking anything! As far as I know Windows doesn't even *use* ACPICA and Linux have their own fork with working implementations... They just sit there, just to tell you how to NOT do it

So that's some of my thoughts about ACPICA. Note that I haven't even used it as a library yet, I just got it to compile and link and it already fucked with me this much.
There's also so much more I didn't mention like that you *have* to modify the acpica source in order to get your own platform header working (else #error) eventhough the docs explicitely instruct you not too but you get the point

Don't use ACPICA if you don't have to. Save your sanity for something that's worth it

"Without ops, it's just code"

Saw a devOps engineer at work wearing a shirt with this quote

The useless, recently hired nightmare of an ops manager has been fired! Huzzah!

Getting real tired of all the ops people referring to themselves as devops

"If your ops team insists on running WebSphere, tell them to call my grandparents! They can help." 🤐

So we called out our project manager and tech leader, who sent out an email last Friday to our bosses and stakeholders a project schedule - which we never knew about until we saw it in our inboxes - that showed we had already completed development and would go on to UAT testing by next week.

Except if you look at our agile board we have 3 weeks of dev tasks left and a couple more for testing and QA. Then our dev environment is shit because the deployment steps in TeamCity were not properly done by Dev Ops. And we still don't have a UAT environment created, much less tested out. And the project manager is about to go on a one-month vacation. Great!

So we replied back with all the aforementioned information (less the swearing and name-calling) and sent it out to the same recipients, including our bosses and stakeholders.

That was such a fun Friday afternoon.

Web Ops Director: [looking at a screenshot of changes she had requested] This looks good. Oh by the way, revert that red color for heading text.

Me: I’m not reverting anything because there’s nothing for me to revert. I didn’t touch that text color. The website has always looked like that.

Director: [shocked pikachu face]

Not a fight I was involved in but one I observed. A junior dev on my team and a server ops guy had major personality conflicts. One day the server ops guy had enough and physically went after the junior dev. I was senior but still pretty new to my own career and had no idea how to handle it. Server guy got fired soon after. I was glad I didn’t have firing power and that he didn’t even report to me anyways.

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.

It’s a bit of a coin toss for me but probably the first sysadmin I worked with Dave, I was a software engineering graduate and tbh he scared the sh*t out of me when I first met him but when he learned I actually enjoyed doing ops stuff, he really took me under his wing taught me so much and I’ll be forever grateful to him for that

I'm currently founding a startup right after graduation. As the CTO with no employees at the moment I'm like every position in the company related to dev and Ops. It's the biggest challenge I've faced as a dev so far. Though I really learn a lot and grow mature pretty fast and it is challenging in a good sense from a technical perspective, I'm facing hard personal problems like insecurity in decision making, doubting my skills since I'm definitely no senior and a mid to high effectiveness to stress.

I've mixed feelings about the pure speed and developments right now, but the good side of things is far more exciting then the bad side is frightening.

What truely pisses me off though, is the missing time to spend here on devRant. FUCK. FML.

Have a good (REST) weekend.

When will Dev and Ops lay down their arms and embrace as brothers? This war has destroyed too many lives already.

Let's play a game.
Dev-ops roulette, loose it all or walk away a lucky boi.

Run this command
sudo [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "You lucky boi";

So I landed a senior linux admin job in August, moved to a new city, and signed a 2 year contract for them to pay my moving expenses. I took an employee survey in October, not knowing anything. As a department (all ops and devs), we reviewed the results as a whole with HR.

Now HR is coming to our remote office tomorrow (4 hours away).... to be continued...

404, Swag not found 🥲

I got sick and tired of waiting (4 years) for the debugging ducks to be re-stocked in the swag store, so i made my own.

Yes, I’m a front end developer and the domain redirects to an Etsy shop because I’m too fucking busy carrying the entire company that i work for on my back to develop my own custom one.

I’ll get around to it once PMO/Design/Marketing ops and Business get around to doing their jobs themselves.

Spotted a new feature that had just recently being completed: "Disable all Logging due to noise". What.

Us on the Ops team just died a bit inside...

I was almost through with a mission on Modern Warfare 3 special ops after being killed a million times but then windows update couldn't fucking wait! Seriously wtf???!

On this episode of “My Work Life” we will once again find that the code is fine, the DBAs just did something brainless again.

So... I'm a DevOps engineer and I received an email from boss today wanting me to do "tech Ops" for next few months, basically tech support because they are having a shortage and too much tickets that they can't handle. *Palmface*

How does a person learn all these Dev ops/backend/frontend/mobile apps technology? I've been using Vagrant + Django mostly and I feel I'm so behind when people talk about AWS EB, Node, React, SASS, Less. Whelp

When a data scientist thinks that if his algorithm is o(n) then it's really o(n) and it doesn't matter that he placed synchronized everywhere , connected to the db multiple time with huge in memory ops inside the transaction , wrote a file and downloaded something with http client . After all it's o(n) right mister I'm a scientist genius ?!?!?

I'm frustrated with an abundance of different *Ops we're having right now. You can spell a random word followed by "Ops", and it's probably a thing. I get that Ops people in general are important but when there is stuff like GitOps, MLOps, FinOps, it gets confusing pretty damn fast. There's no value in all these titles besides "duh" usually, since Ops are just Ops in most situations. They kinda can slap a tracing tool or two on top of your code base but in general they just do Kubernetes (with whatever's hip like Jaeger, etc.) nowadays and that's it. Hell, even "DevOps Engineers", for a majority of cases you'll encounter, are basically just Ops with a misleading prefix since it's just a way people call them nowadays for whatever reason.

I’m currently working with a devops team in the company to migrate our old ass jboss servers architecture to kubernetes.

They’ve been working in this for about a year now, and it was supposed to be delivered a few months back, no one knew what’s going on and last week they manage to have something to see at least.

I’ve never seen anything so bad in my short life as a developer, at the point that the main devops guy can’t even understand his own documentation to add ci/cd to a project.

It goes from trigger manually pipelines in multiple branches for configuration and secrets, a million unnecessary env variables to set, to docker images lacking almost all requisites necessary to run the apps.

You can clearly see the dude goes around internet copy pasting stuff without actually understanding what going on behind as every time you ask him for the guts of the architecture he changes the topic.

And the worst of all this, as my team is their counterpart on development we’ve fighting for weeks to make them understand that is impossible the proceed with this process with over 100 apps and 50+ developers.

Long story short, last two weeks I’ve been fixing the “dev ops” guy mess in terms of processes and documentation but I think this is gonna end really bad, not to sound cocky or anything but developers level is really low, add docker and k8s in top of that and you have a recipe for disaster.

Still enjoying as I have no fault there, and dude got busted.

Was once interviewing for Ops support roles looking after multiple websites wrote in java, rails, php with some rest apis, apache, varnish and more....

We were also starting moving towards automation and devops practices so we needed to expand...

We have a great CV from someone who had all of the technologies and chef mentioned on their CV so we were positive....

Invited to interview and something wasn't right..... I dropped a "so you mentioned a few different languages on your CV, can you talk me though some of the applications you've looked after and what languages they were written in, etc?"

His reply.. "yes I looked after a lot of applications and helped people with them in English"

Me "oh.. Okay.... So those apps which software languages were they... You mentioned things like Java and Php and automation tech like chef?"

Him "well yes they were all sorts of things but I predominantly looked after the apps that were wrote in English... Didn't deal with any wrote in java or chef... Just English"

Me ".... Does anyone else have any questions?"

Safe to say we didn't offer him the job....

As a dev, knowing some basic sh** about your infra comes in handy, esp when it's Saturday afternoon and you realise your Thursday release f'd up some obscure integration

*sends email to ops manager to explain nuget & git (yes, he is THAT guy)

*his reply "what's nuget?"

Ooooooooh! Why don't you open Google and do a fucking search you amazingly stupid twat!!! In what fucking era do you live in? What the fuck are you doing at work everyday, besides complaining about how time consuming your useless mundane tasks are? Take some of your undeserved salary and go educate yourself, you useless sack of shit! FUCK!

*meanwhile... Little grin on my face. *Shift+delete email.

To all you dev-ops people, y'all are doing God's work. Thanks from this dev.

When companies don't understand what DevOps is and don't know how to implement it.

I hate when the term DevOps gets slapped onto a traditional Ops or sys admin team and they call it a day.

It's become the new agile.

Last few months have been quite calm. Nothing to really rant about. The egocentric asshole PM (see my past rants) left the company, so things have been better at work. I thought that there would be so much chaos because of all the roles that he had (project manager, engineering manager, lead developer, dev ops) but we managed to keep things running smoothly, which shouldn't have been a surprise for me, but I was a bit scared at first. Relieved, because well... the egocentric asshole left, but a bit scared either way. Anyway, everything has been fine. I'm pretty much the lead frontend developer now, even tho there's no official structure or hierarchy, everyone just keeps looking up to me for help and guidance. I've received a good pay raise. Work has been interesting and challenging. All's well.

This all coincided with me deciding to take a little break from devrant, and the lack of ranting material kept me from coming back. I just dropped by to say hello and check how devrant is going. I hope you are all doing well :)

Deployments, a limerick:

there once was an ops guy from New York,
who was working on deploying a fork.
the docs were weak
the code memory leaked
in a half hour all of production was borked.

I see people posting about ops. I wish we had our own operations team :(

when operations team doesn't install nano because it is the wrong way to edit text ಠ_ಠ

My company has hired and fired 3 Engagement Managers (people who host events, refill snacks, etc) since I'm started here, and I'm starting to think People Ops is either

1) Cannot hire someone good
2) Is toxic and causing the people to leave
3) Hire and fire before their 90 days are up

It sucks that right when I think we got someone good, they give them the boot. That should not be a norm or acceptable to go through 3 managers in 9 months.

I just want some hosted VCS. I don't want to run this myself. I am a developer. Not an ops guy.

its two years since ive told a story here but lets go.

we got a new client, who is revamping their infrastructure. i gave some tasks to 2 dev ops guys (i am not devops). they were primarily bash scripts that needed to be altered. (ofc i can write scripts it takes a moment, its their jd)

after a week of chasing them around, getting no result from them, i end up doing it myself because client needs it and the company needs this client. for one task, they told me it does not apply to the component we were working on. (it did, and i did it)

we have a meeting with higher management, they asked me how did i implement it, i show my entire working, my backtracing etc (everyone knows this is how you approach huge system, component focused strict deadline task). it was infuriating how they approached it by trying to understand complete system in one week. i asked them why they hadn't taken component specific approach. they said they tried but failed because..

[this because is the whole reason for the rant, because i believe this because should be a fire-able offense]

..because we were not using VS code to find things in files

HOW IS WHAT TEXT EDITOR YOU USE OR DON'T USE AN EXCUSE

ARE YOU GUYS GETTING THIS?

me: I need to install Firefox for automates test
ops: no
me: need it to run tests PO wants tests
ops: you can't as it is a desktop app
me: I need it because our selenium tests depends on it
ops: Firefox needs 200 other packages can't install
me: can I use Docker? and docker'ise Firefox
ops: ... some silence...
me: please
ops: it will complicate things
me: ಠ_ಠ

Small chaotic startup that never grew up (15 years atm).
Hosts/maintains a number of apps/sites for various customers.

At some point, someone decides that a CMS would be usefull to maintain the content across all products. Forgoing all sense, reason and the very notion of "additional maintenance and dev" it is decided that one should be built in-house.

Fast forward a number of years.

Ops performs routine maintenance on prod-servers. A java-patch accidently knocks out one of the pillars a 3rd party lib the CMS uses for storing images. CMS basically burst in to flames causing a.... significant incident.

Enter yours truly to fix the mess.
Spend a few days replacing the affected 3rd party lib. Run tests on CMS in test and staging environments. Apply java-patch. All seems fine.

When speaking to frontenders and app-devs, a significant hurdle present itself:
All test/staging instances of all websites/apps/etc ALL USE PRODUCTION CMS. Hardcoded. No way around.

There is -no- way to properly test and verify the functionality of any changes made to the home-brewed CMS.
My patch did indeed work in the end.

But did the company learn anything? Did they listen to my reasoning, pleading or even anguished screams for sanity?

No.

Me working on html/css updates for a banner message.

Web Ops Director: [slack] Hi! nice to e-meet you! I was talking with the Mgr of Product. He thinks it would be great if the banner message updates were on the site right away instead of having to wait 10 minutes for the cache to clear after updating the banner content in admin. Can you add that to your ticket?

Lol that’s a load of crap. 1) Product would have just told me himself and 2) Product would never pull this bullshit of bringing a ticket out of scope like you’re pulling right now. And 3) My spidey sense says this is a red flag 🚩.

Me: [in words web ops will understand] That’s going to a lot of time. And it would keep your content updates from making it to the weekly release. 😁

My boss is being a stupid cunt. To give you a background we were facing issues with our Collections system. First week December 2019, I and a colleague of mine came up with a new efficient collections architecture. My colleague and I started to Code and create automation scripts mid December and completed it in First week of Jan 2020. This PoC version was supposed to be just between the Dev team(App Dev and Back end, also one from the Ops side to verify the data). I did not receive any feedback on the actual collections system and the data integrity but during this time all they’ve done is take meetings with no real outcome. I raised this and the only email I got is data is looking fine when I know it is not.Now in First week of Feb, he is stressing us to go ahead and deploy the architecture in Production and we have not done any Code Review, Static Code analysis, any real tests on Code and deployment scripts. Have not discussed any metrics for our dashboard and alerting. I have no idea how to handle this cunt. I have even asked for resources to atleast productionalize the code and move ahead the deployment and still no out come. I’ll go in a meeting with him in an hour, I will be very blunt and tell him that whatever he is doing is a foolish way and maybe resign in couple of weeks

I'm in a team of 3 in a small to medium sized company (over 50 engineers). We all work as full stack engineers.. but I think the definition of full stack here is getting super bloated. Let me give u an example. My team hold a few production apps, and we just launched a new one. The whole team (the 3 of us) are fully responsible on it from planning, design, database model, api, frontend (a react page spa), an extra client. Ok, so all this seems normal to a full stack dev.

Now, we also handle provisioning infra in aws using terraform, doing deployments, building a CI/CD pipeline using jenkins, monitoring, writing tests, building an analytics dashboard.

Recently our tech writer also left, so now we are also handling writing feature releases.

Few days ago, we also had a meeting where they sort of discussed that the maintenance of the engineering shared services, e.g. jenkins servers, (and about 2-3 other services) will now be split between teams in a shared board, previously this was handled only be team leads, but now they want to delegate it down.

And ofcourse not to mention supporting the app itself and updating bug tickets with findings.

I feel like my daily responsiblities are becoming the job responsibilities of at least 3 jobs.

Is this what full stack engineering looks like in your company? Do u handle everything from app design, building, cloud, ops, analytics etc..

I read so many (amazing) sysadmin/ops stories, does that make this place devOpsRant? 😜

I love how our industry has invented such important sounding yet meaningless job titles...

Developer, software engineer, software architect, developer evangelist, dev ops engineer, systems analyst, quality assurance engineer, code monkey...

Me: [jira comment] We have similar text for the mobile version of the site already. [includes screenshot of what site looks like now] Are you sure about this?

[radio silence for a few hours]

Me: [slack] I want to follow up.

Web Operations: What’s the issue?

Ooh k. Slack messages can have a tone.

Me: I just want to confirm we’re not repeating copy.

Web Ops: We’re not.

I complete the ticket and submit for review. The C-suite for my department reviews.

C-suite: [to web ops in JIRA comment] This looks weird. Is this right? [sends screenshot of my work because there is repeated copy, like I said there’d be]

Web Ops: [in JIRA comment] Oh, I thought X was questioning the request. X changed the wrong text.

C-suite: The website has always looked like that. You’re looking at X’s screenshot for the current website. Look at the screenshot I sent over.

Later, I complain because web ops was completely unprofessional with the comment about “questioning the request.”

C-suite: Web Ops is working hard. It’s our busy season and it’s their first time dealing with it. You know, I’m going to teach them some css and html so they can make content changes in the CMS and they’re not sending over changes so often and bothering you.

Me: [to myself] 🤨 wtf so it’s ok for web ops to treat me like dirt. And in writing. And with service that’s version controlled—JIRA emailed web ops comment to me. And lol no 😂 on teaching them how to code. That’s such bullshit. We all know you’d never allow them to edit the CMS because they’d fuck up the site. And they wouldn’t do edits anyway because it’s beneath them. And idk how this relates to web ops gross behavior.

A few days later.

Me: I was offered a job elsewhere. Here’s my two weeks notice.

C-suite: Can you push back your last day? It’s our busy season.

Me: Nope. Bye Felicia.

Ok so I studied Computer Science in college, even got my pretty little associate's degree saying I didn't eat shit.

Decided to work in ops and not as a dev because life finds a way

End up being asked to write code at work anyway because I know enough to not break everything

We heard you like security so we put antivirals in your docker containers despite the fact that we made you have antivirals on your machines running the docker containers.
And we won't allow to use root just in case you want to disable the av. And we don't care you need it for the docker 😂

This is how I was played when wanted to use docker containers to avoid dealing with OPS.

Some time passes, my team is going to have independent cloud infrastructure.
Doing corporate politics is challenging...

As the head of the Web Operations team of my college, I managed to compose quite a convincing pitch on college mail, as a call for interns for the team during the summer. The basic idea I explained to people was that even if you aren't a pro, you can still try and apply: you have one week to impress me with your CSS/JS/PHP skills(Really basic stuff in the problem statement; I didn't even make all of it compulsory), and encouraged them to start from scratch, cuz that's how I made it last year.
Last year they had around 30 responses in 7 days - I got 42 responses in 7 hours itself. I could shut down the portal cuz of far more than enough responses, but where's the fun in that. ;)
I'm not a good programmer, I'll admit, but I certainly benefitted in this field of being the head of the web ops team with knowledge and experience my non coding friends keep sharing with me. Not having a lot of code buddies didn't turn out to be so bad.

It's not much of an achievement, geez, there's literally everything left to be done for a whole year, but well, good start!

we want you to be
- full stack developer (you do everything front end, back end)
- dev ops/SRE (you can sort out the deployment CI/CD pipeline, cloud platform services AWS/GC/Azure whatever)
- architect (you can design the software as well)
all in 1, you gotta be multiple roles/departments
good luck getting this experience on the job (hell in a startup is not for everybody and certainly not for me)

also why the fuck companies who aren’t startups ask for this idk

not sure if i missed any roles/competencies so far , don’t forget you need like >=3 years of experience possibly in every field for entry roles and more for anything higher than that

Today is the first time in my life that I've received an all-caps corporate email from some team running ops.
Funny how someone thought this might make it clearer when all acronyms in our company are all-caps, making it a very intensive read which does everything except bring the important point forward..

Today was my first day in OPS room.
Fucking felt weird!
Literally only 1% understood I guess.
Luckily seniors were there with me.
I hope, soon will understand more ;)

Who the hell hardcodes their localhost ports in a web.config without updating the release config to the correct production URLs? And why doesn't our ops team pick up on this shit before clicking their fancy deploy button? And why in holy heaven do we even have a pre-production server if it isn't an exact mirror of production?

God help me, I need a drink.

It exists its just not my job : dev ops

Suffering from our first service outage since I've been at my new job.

Guess when it happened? While we have TOO MANY projects going on.

When you have too many pots on the stove, you're bound to forget the smallest, most crucial detail.

Our customer accrues vacation time in January. The retirees will take all of their vacation starting in January and retire when they get back. This year, their ops teams have multiple retirees. Some software we support now runs on abandoned servers.

My coworker had something go seriously wrong in the financial software over Christmas and there is nobody to call to help him access or fix the running application.

When the ops team needs to go through a 5 step "protocol" over a couple of days, just to open a damn port in the firewall, so that our CI server can access the local GitLab server..
Seems like the migration of the last couple of projects from SVN to Git is going to take a little longer than I expected..

Ops wants to use an untested feature in production

Dev points out the high risk of doing so, and refuses to be accountable to any fallout

Ops gets bitchy and demands that Dev activate the feature

Ops executes the feature

Production breaks over the long weekend (Canada)

Ops complains to Management

Dev is blamed by Management

@noop you really do no ops

Jesus christ I need my VP and CIO to get their hands out of Azure and GCP and just let me work.

Yes, governance and security and IAM are big deals. That's why you have infraops people like me to deal with that.

I'm literally working with one hand tied behind my back because just about every button press or CLI command I need to do my damn job as a professional cloud fluffer requires me to go bother an executive and ask permission to pretty please can I deploy a new container, can you go press the shiny button? No not that one, move your mouse up...up..now UP..ok over lef-no..can I have mouse control? Sigh fine, do you see where it says "Approvers", no that says "Release Pipeline"

Look I actually kinda like this job, I do, in as much as when I have something to do I get left the fuck alone to do it. Meetings are minimal, aside from the odd days when one of our app services decides to yeet itself into the river Styx, there's little distractions.

Yeah, developers do dumb shit but that's probably best left to the notion of job security and never talked about again less they go to HR and complain that the ops guy was very stern and direct and made the developer take some accountability for their work product.

AND YET

It's so intergalactically stupid that I have to go ask permission just to do ops tasks by the same people barging down my goddamn door asking why the ops task isn't done yet.

"Because you won't give me permissions in GCP to actually DO anything".

Okay. Rant over. Time for lunch. Good meeting, see you all at the holiday party.

There is this developer talking to an ops guy behind me and I was tuning them out until she suddenly said, "Are you tweeting? .. While I'm talking to you?"

Everyone laughs, including her. She adds, "I don't know whether to be offended or impressed."

Me: your SSH wrapper is breaking how Ansible works
Ops: try to use Ansible in another way
Me: your SSH wrapper is breaking how Ansible works
Ops: try to use Ansible in another way
< This goes on for two weeks >
Me: can we please not use wrapper
Ops: we use it to manage ssh keys
Me: this is breaking basic ssh functionality
Ops: OK we are setting up a weird convoluted way so you can run your Ansible playbooks.
Me: ... < doing "it is at least something" dance >

I've been wondering for a while about something...why do so many devs complain sooo much when they have to to stuff not related to their main area of expertise.
I like learning and trying everything if I have the opportunity...backend, fronted, database, dev-ops, crypto, networking, virtualization...I stuck my nose in everything...but I see a lot of people moaning and despairing when they are thrown out of their comfort zone.
Like why...it's interesting... it's not always sunshine and rainbows but knowing something new in IT is never gonna hurt you...who knows maybe someday it's gonna help you get out a tight spot or land that awesome job you wanted.
Ok I'm done 😁

Ha! Our Ops Support DBA Manager just asked (tongue in cheek) "if we are now supporting MS Access, too?" To which of course, the answer is no. Business user who install Access on their desktop and use it for business, get to provide their own support. As their Dev DBA, I'll be more than happy to help them migrate their data to SQL Server, Oracle, or Teradata, depending on the Use Case for the data. But, no, we don't support Access. Ever.

"hey, write us a simple interface for this shell script.."
script:
- input must be a file, does not accept loading through stdin/redirect
- accepts relative path input from one specific directory only
- fails if provided absolute path
- even though it fails, it still returns return code 0

and every time we've tried to open up a topic of programming practices we got slammed with "we're ops. you should be glad they're doing at least some scripting"

Working on production issue,
Kind of nervous checking logs and so on...
Ops manager and PO who were looking over my shoulder this whole time start shooting the breeze.

I know what they were trying to do. They are trying to create a relaxed environment.

But the issue is that the talk is very distracting. If you want to shoot the breeze please go somewhere else.

Anyway just did that, asked them to leave. They weren't happy about it. But I really needed the silence.

Note: In this rant I will ask for advices, and confess some sins. I will tell my personal story- it will be long.

So basically it has been almost 2 years since I first entered the world of software development. It has been the biggest and most important quest of my life so far, but yet I feel like I missed a lot of my objectives, and lots of stuff did not go the way I wanted them to be, and it makes feel frustrated and it lowered my self esteem greatly. I feel confused and a bit depressed, and don't know what to do.

I'll start: I'm 23 years old. 2 years ago I was still a soldier(where I live there is a forced conscription law) in a sysadmin/security role. I grew tired of the ops world and got drawn more and more into programming. A tremendous passion became to burn in me, as I began to write small programs in Python and shell scripts. I wanted to level up more seriously so I started reading programming books and got myself into a 10 month Java course.

In the meanwhile I got released from army duty and got a job as a security sysadmin at a large local telco company. Job was boring and unchallenging but it payed well. I had worked there for 1 year and at the same time learned more and more stuff from 2 best friends who have been freelance developers for years. I have learned how to build full-stack mobile apps and some webdev, mainly Android and Node.js. However because I was very inexperienced and lacked discipline, all of my side projects failed horribly, and all attempts to work with my experienced friends have failed too- I feel they lost a lot of trust for me(they don't say it, but I feel it, maybe I'm wrong).

I began to realise I had to leave this job and seek a developer job in order to get better, and my wish came true 6 months ago when I finally got accepted into a startup as a fullstack webdev, for a bit lower wage but I felt it was worth it. I was overjoyed.

But now my old problems did not end, they just changed. My new job is a thousand times harder and more intensive than the old one. I feel like it sucks all the energy and motivation that was still left in me, and I have learned almost nothing in my free time, returning home exhausted. My bosses are not impressed from my work despite me being pretty junior level, and I feel like I'm in a vicious cycle that keeps me from advancing my abilities. My developer friends I mentioned earlier have jobs like I do and still manage to develop very impressive side projects and even make a nice sum of money from them, while I can't even concetrate on stupid toy projects and learning.

I don't know why It is like this. I feel pathetic and ashamed of my developer sins and lack of discipline. During that time I also gained some weight that I'm trying t lose now... I know not all of it is my fault but it makes me feel like crap.

Sorry for the long story. I just feel I need to spill it out and hope to get some advices from you guys who may or may not have similar experiences. Thanks in advance for reading this.

"What is HTTP/2?"
Quote from the web infra/ops team lead supporting us :(

Daily life on this project: tickets are blocked by test env. Fucking impressive server ops team we have here, took a month to add 1 test user.

If we could get a full-time dev ops person for our org, I'd be so happy...

Ops... he took it too personally

My company has a board on Blind (semi-anonymous social network for corporate employees). We're a startup and have had two layoffs in the past two years, with very few pay increases.

I voiced my thoughts about the future of the company. We're pulling in a lot of revenue (millions a month) but still have a crazy amount of costs.

Someone responded that a bunch of our revenue ops people left for other companies. Another person replied the director that left had a good opportunity, thought we'd get another round of funding and that the company has had some purchase offers (with valuation being the big sticking point).

If it's true, it should feel like some job security. I can't help but also wonder if anon is lying so people purchase more of their stock options to generate more runway.

First time getting my hands wet with docker. Ended up fully containerizing my company's project. Never been more proud of miself.

Which sphere is more interesting: Unix DevOps or Java EE?

Is it just me or is the free Azure VM absolutely slow AF?

tech D&D
dev = fighter
ops = cleris
network = wizard
design = bard
dba = warlock
infosec = rogue

it is not mine but i think its great analogy. and because i always choose the warlock

Do you think we should have a Linux black-ops team?
In case we need to execute a `kill -9` in real life.
Like the facebook.

So I’m panicking a lil bit.

I applied to a bunch of summer co ops from like feb 20-25. I haven’t heard anything from any of them yet - not all of the postings have been closed but my first choice posting closed feb 22...

I know it hasn’t been all that long but I’m pretty used to getting responses (non dev jobs) within like a week and I’m scared that I won’t get ANY responses.

Most people started applying for co ops in December, and I know I procrastinated a lot, it’s just unlike regular jobs where u keep applying till u get something, it seems like co op applications shut down by now, 3 months before the summer term.

Did I screw myself over? Is it too late? I’ve never applied to co ops before and I just REALLY don’t want to spend another summer bagging groceries...

OH: We have a DevOps team that does neither Dev nor Ops. An SRE team that are not engineers and a head of SW Dev who said with a straight face today that our Oracle multi-monolithification over the past 3 years was a ‘Digital Transformation'.

I started working at a new company a couple of weeks ago as a Dev/Ops engineer, my first real ops position after years of being mostly a dev with two sys-admin positions sprinkled in.

I should have seen the red warning signs when, during the interview, a developer told me the old devops team was so bad they fired all of them last year. After I started, I learned that all four people on our team were totally new. Three were hired after the last guy from the old team left (without any notice) and one person use to be a developer who was transferred over to this new team (but not to lead it).

#define DevOps team

- dev team that also does ops or vice versa.
- an ops team calls itself devops but does not actually do development :-|
- IT for developers
- or better to call it SRE team?
...

This is true I swear... I once worked on part of a project "optimization" that required, running a job on sidekiq in the background that spawns multiple threaded RPC calls on RabbitMQ (and be I/O blocking) till the jobs are done (or failed) so that it updates the status of the master object (that has the associated objects processed) and sends an email to the ops manager (just a summary email)... instead of using database locks... or dropping the email requirement...

I did it without arguing because I've already quit the job a while ago...

During my recent interview I was explaining what I liked about the company, going in to detail about how I respected the CIO as he, as a software engineer, ran his ops teams like he runs a development team.

When I got home I realized my story wasn't about the CIO of the company but about Benjamin Treynor Sloss, VP Google Engineering, founder of Google SRE.

I had been reading the Google SRE book the night before and completely mixed up my stories!

I wonder if it was in part why I didn't get the job...

Today, my co-workers went nuts about the fact their version of our product doesn't work on the pre-production since everything is fine on their local dev machines ^^

After a quick sighting, I figured out what was going on.
There was a package called from non-dev code which was required as a package for development.

The build plan of the application consists of a task which purges dev-packages within the vendor folder, using composer install --no-dev ^^

So the build plan runs perfectly fine, without a single error, but runtime was yelling about a missing class.

It's a delight to be one of the only guys with dev-ops experience in the whole damn building.

xD

This was in 2001 on a legacy AIX core ops server. I got tired of waiting hours for the last page of a print job to debug totals. So, I added a print menu option to print it to an HTML file on a share served up by a wab server and send me the email link. Took two years to catch on but when it did, we eliminated all nightly print jobs and took the paper budget down by 90%. All because I was too lazy to keep reloading my desk jet with paper to debug reports and I forgot to take it off the menu.

So being in ops, I have certifications in networking and Linux, and am currently working on my Certified Kubernetes Administrator exam.

I've been talking to a few "professional" (they have jobs) devs that I personally know, and with the exception of 1, it seems like version control, automation, networking, and server related tasks are beyond them.

As I want to get into the dev side of things (devops preferably), I feel somewhat overwhelmed at some of the requirements of the job, especially knowing that I cannot take too much of a pay hit as I have a family to support.

My question is this, based on real world experiences with hiring, how much weight do you think knowing your way around networks, cloud, virtualization, servers, and all of the other things ops does when it comes to getting your foot in the door for a dev job?

I've casually looked around, and it seems that getting the foot in from this side is almost impossible.

Hello devrant, so I've been wondering if anyone here breaks things (infosec)? Is there anyone who dabble with building stuff(dev/ops) and breaking them? Need advise whether I should be looking at a devops-y role or a infosec related role in the future. (PS I was in infosec and slowly transitioning into ops/devops not sure yet). Please share your experiences. :)

Applied for summer co-op positions today. First time applying for tech jobs! So much more nerve wracking than applying for random whatever I can find jobs. I’m so scared and imposter-syndrome-y, but I know everyone feels that way... aaaah