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...

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. 😡

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!!!

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.

*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! *****

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...

When you go to check on how the client is using your software or product

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

worked fine in dev....

!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 :)

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.

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.

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.

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.

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"

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

Coding without propper dev-ops:

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

Yeah, force push it to master!

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.

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.

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

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.

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?

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.

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 ¯\_(ツ)_/¯

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.

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

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..

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.

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.

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...

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...!

*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.

Why do CEOs and higher ups always think development is just some easy quick thing you can spit out in a week? {
"I need a web app that can do X and I want to sell it to make more money!"
} or {
"I want something that can automate this thing here and then I can re-sell it!"
}

Usually, the project is something that already exists and has taken a whole team years to iron out and perfect and to compete with it would be insane or it exists and it's actually FOSS. We're a small MSP, we don't have the resources to make big ticket SELLABLE software.

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 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.

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'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.

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

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

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

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.

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 :)

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

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.

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?

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..

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

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...

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

It exists its just not my job : dev ops

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

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'.

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

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?

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

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.

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).

ops: your dev environment shuts itself down on boot up, something is broken in the boot process and it'd be more trouble to figure out why so you're better off making a new one again

fuck me

and fuck you too AWS EC2 whatever

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

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.

#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?
...

I’m so glad I work at a company without a dev ops... it’s so much smoother and money isn’t wasted on a non engineer, or someone who can’t jump in and assist where needed.

We have a weekly team meeting including the mech, elec and software guys... then we have a weekly open issue meeting per project only those on the project go to. We all know what we need to do individually and we just get it done... no need for the middle man dev ops to divide up tasks and shit.. we hear the issues straight from the product owners and get to work... we don’t have defined structured scrums and burn downs...it’s very agile tho.. much like how engineers 40 years ago achieved things. It’s quite awesome.

I really wish ops communicated more with devs. As a dev I really hate throwing things over the wall. They must hate it too...

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. :)

As a front-end developer who has a firm grasp on web tooling, I still think the sheer amount of knowledge needed for dev-ops/deploy tools is staggering.

For our current project, we connect to three different OpenVPNs:

Our dev OpenVPN (to get Jenkins/Artifactory)
The ops team devops OpenVPN (to get to environment)
The vendor's VPN for single signon

All of them have different keys and one connects to LDAP and uses a password we can't change.

Been applying for jobs lately and despite the years of experience and using the latest toys I’ve been finding it harder than ever to even get a positive response to my CV. One thing I’ve been noticing is that companies seem to now not care so much about frontend skills and more about complex algorithms when the role is ui focused, or to have a demand for dev ops experience. Are we really getting back to the days of thinking that jack of all trades can be experts in everything?

Anyone knows about that one website for dev ops, with tech or edu.net or sth along that line? Url isn’t that long.

Found it through one rant and op seems to be writing a series of tut or articles for data structure.

Now can’t find it back. Greatly appreciate ur help.

I love doing multiple tech things. Development, Ops and security. Why can't people see this as tech experience and not individual subdomain experience. Why can't people switch jobs easily over Dev, Sec and Ops?
Smh.

Hey all.
I have a non-technical question.
I'm a university drop out for financial reasons where i live and i have been working in the field for 8 years as a backend dev and some dev-ops on the side.
My question is what are my chances of finding a good job in europe (italy germany uk france ... Etc) without a degree?
And what is the range of my annual salary on average?

And thank you for your help.

Push a commit to Bluemix DevOps server, it starts deploying

Go out with your partner, become a parent, see your kids grow into adults, become a grand parent.

Blumix still hasn't deployed.

Why IBM? Why?

Me: [Talking about how you are able to create AMI images on AWS using Packer without relying on public AMI images]
Ops: Yeah our AWS version doesn't have that.
Me: wut? ಠ_ಠ

Hi everyone, I’m trying to wrap my head around dev ops but struggling with the whole continuous integration workflow. From my understanding it goes something like the following:
1. pushing a change to some repository (git)
2. Some tool (Jenkins) tries to build it and if it’s succeed, creates a image /container (docker).

These containers are hosted on some cloud service (aws)

Some workflow, walkthrough, or examples would be very appreciate.

TL;DR how much do I charge?

I'm freelancing for the first time; regularly, I get paid a salary.

I'm freelancing as a donation: the hours I put into this work directly translate to deductions in my tax. I don't get paid any money directly.

I'm doing some web-based enterprise software for an organization. Handling the whole process from writing responsive front-end code to setting up the server and domain for them and even managing myself. So full stack plus dev ops.

My normal salary is $31 an hour and at work I do less. I largely do maintenance for existing applications plus some very minor new systems design. I don't do any server management (different team) and I damn well didn't buy the domain names for my company. So I think it's safe to say I'm taking on a drastically larger role in this freelance gig.

My moral dilemma is the organization will basically say yes to any price - because they don't pay it, the government will (up until the point I pay 0 taxes, I suppose)

I've done some minor research on what other freelancers charge for somewhat similar things and I get pretty wildly varying results. I've seen as low as $20/hr but I really doubt the quality of such a service at that price.

I'm thinking around $50 USD an hour would be a fair price. For even further reference besides my actual salary, I will say that I am in a urban / suburban part of Florida, where developers are very hard to find locally.

Is $50 too high? Too low? This is a very complicated system with (frankly excessive) security practices and features. Before this they had a handful of excel spreadsheets in a OneDrive folder.

Compare and harmonize the web configs

Oh no someone set execution timeouts to 14 days

Fuck fuck fuckity duck

Hey compare all the web configs of all environments and harmonize them all wtf cmon bruh do your job as a developer

Take them and back them up into svn. What do you mean svn isn't a back up system of course it is well its the only thing we have fuck

What do you mean we have shit logging where people will catch an exception and only print the word exception in the log you can figure it out can't you we have live produxtion issues that hace to be solved now what the fuck

How dare you make a. Mistake copying our shitload of a bloated codebase and configuring our 100s of different options all by fukcing hand what the fuck dude do yoh write anyrhing down?

Please catalogue all the exception mails we are getting but we have no db or error reporting system so they all just plop into tue inbox and thats all ypur fuckjng data figure it out kid

This is a rewarding, fulfilling job whwrw you can be both dev ops and a developer and manage all of our fucking environments of which there are about 15 of all your own with no sort of tool or software to aid you because haha what the fuck we wouldn't make your life easy

Whata that you want to spend time to write stuff or change stuff that will nake it easier fot you fuxk that bruh get back to your biklable tasks like holy shit you thjnk this is a charity ofr aomw shit

Live production issues
Live production issues
Produxtion issues. A ghost in the machine. Find it fix if find it fix it find it fix it cmon why can't you fix it I expect you to spend your day hopelessly pretending to try to solve something you fucker

One of the only peopel able to help you sometimes though hes a bit of an old laxky, yeah hea fucking leaving see ya seeya kid and now we're not hirinf anyone to fuckjng help you no no no managing and monitoring the environments its your jov alll fof them every sngle on do you knkw all the xonfiguraiton values for them yet??

Instead we are hiring a new sales person to fucking make us some more money and we don't need naother seceloper to help you infqct lets have you use this mid end retail computer from 2014 to develop on yeah yeah oh but all our shitty code and visual studip will destry your memory but too bad!! Hahahahahdhsj

Go lice is all you, why sare you so slow

How long will it take
How long will it take
How long will it take
How long witll it tqk2
How long will it take holy shit
Give time estimate for sonethign that I don't fucking know how about it will tqke till fuxk you oxloxk

Works fine in dev, ops problem now.

results << entry.format_results if !Rails.env.production?

Run away from me now motherfucker.

Ok... I am defeated I don't know what else to try...

Do you guys have any experience with ansible vault? I have my SSH password stored on a vault. It's referenced in my host file like this:
-----START SNIPPET-----
[LCL:vars]
ansible_ssh_pass='{default_pass}'

[LCL]
myhost ansible_user=my username
-----END SNIPPET-----

default_pass is stored as a yaml variable in passed.yml that I supply using --extra-vars '@passwd.yml'

When I enter my vault password I get an exception 'non hexadecimal digit found'.

The password is right for the vault, the vault file is in PWD .... I cannot find anything helpful.

Any ideas?

What OS does everyone use, and what kind of dev do you use it for?

I'm using Linux Mint and I do back end and dev ops.

My previous job was Engineer ( Ops part of DevOps), supporting the devs with VMs, configurations, dev and test environments, CI maintenance, DBA, DB-dev and such, it was sexy.
In my current company, I have no technical role, but today's task: build a small webpage in sharepoint in HTML.
And the perv part is: it's still bettet than having no Technical task at all...

DevOps With Ruby and Chef on FreeBSD (and Linux)

I am Ops and Dev by heart. I have always automated *nix systems long before any automation framework was invented because I am pretty lazy. Doing stuff more than once manually is just one time too often for me. Imho Ruby is a really elegant language. The same applies for the tools that are built around it. The Chef ecosystem fits into this with its own elegance and stability perfectly because the server is Erlang driven and the rest is Ruby.
Being a Linux and BSD user since the early 90s I have always loved a *nix system for it's concepts and simplicity. One command for exactly one purpose and everything is combineable like letters are combinable to words in my mother language. I have always loved FreeBSD more though. Imho it is even more focused on simplicity. Because it is a really clean approach of system design that envies a base system and keeps 3rd party separated in a clean way for example. It also values classic UNIX philosophies that most Linux distros these days abandon but which saved my life multiple times through better design and execution that also focuses alot more on stability, fault tolerance and ease of use than any Linux I have come across. The hardcore guys should read "Design and Implementation of the FreeBSD Operating System", compare the readings to the Linux way of things and see for themselves.*

*The author acknowledges that this text is his opinion and just his wet dream alone and may not be of any relevance for the sexual lifes of everybody else

So this supposed dev ops job has devolved into first support.

This shit honestly doesn't even make sense to me

Time to start looking

I need to learn docker. And learn it fast. These deployment/dev-ops issues needs to be tamed

I started as a dev. Because corporate wants to save some money for their bonus they put two jobs into one. DevOps is born. Fuck you!

I AM A DEV! LET OPS DO THEIR JOB! I DON'T WANT IT!

In the middle of a dev ops module in my final college year, and it's caused more frustration than all the other modules combined over my 4 year experience tenure...