Details
-
AboutDevOp/Build Engineer, Games Developer in spare time
-
SkillsPowerShell, C#, CSX, Jenkins, and basically everything DevOps and Windows
-
Github
Joined devRant on 5/8/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
My current job at the release & deploy mgmt team:
Basically this is the "theoretically sound flow":
* devs shit code and build stuff => if all tests in pipeline are green, it's eligible for promotion
* devs fill in desired version number build inside an excel sheet, we take this version number and deploy said version into a higher environment
* we deploy all the thingies and we just do ONE spec run for the entire environment
* we validate, and then go home
In the real world however:
* devs build shit and the tests are failed/unstable ===> disable test in the pipeline
* devs write down a version umber but since they disabled the tests they realize it's not working because they forgot thing XYZ, and want us to deploy another version of said application after code-freeze deadline
* deployments fail because said developers don't know jack shit about flyway database migrations, they always fail, we have to point them out where they'd go wrong, we even gave them the tooling to use to check such schema's, but they never use it
* a deploy fails, we send feedback, they request a NEW version, with the same bug still in it, because working with git is waaaaay too progressive
* We enable all the tests again (we basically regenerate all the pipeline jobs) And it turns out some devs have manually modified the pipelines, causing the build/deploy process to fail. We urged Mgmt to seal off the jenkins for devs since we're dealing with this fucking nonsense the whole time, but noooooo , devs are "smart persons that are supposed to have sense of responsibility"...yeah FUCK THAT
* Even after new versions received after deadline, the application still ain't green... What happens is basically doing it all over again the next day...
This is basically what happens when you:=
* have nos tandards and rules inr egards to conventions
* have very poor solution-ed work flow processes that have "grown organically"
* have management that is way too permissive in allowing breaking stuff and pleasing other "team leader" asscracks...
* have a very bad user/rights mgmt on LDAP side (which unfortunately we cannot do anything about it, because that is in the ownership of some dinosaur fossil that strangely enough is alive and walks around in here... If you ask/propose solutions that person goes into sulking mode. He (correctly) fears his only reason for existence (LDAP) will be gone if someone dares to touch it...
This is a government agency mind you!
More and more thinking daily that i really don't want to go to office and make a ton of money.
So the only motivation right now is..the money, which i find abhorrent.
And also more stuff, but now that i am writing this down makes me really really sad. I don't want to feel sad, so i stop being sad and feel awesome instead.1 -
Windows containers with Kubernetes on AWS and Azure are thing now.
What does that mean? Is it now possible to containerize system critical windows 3.1 legacy software from the 90ties (like the ticketing software at Airport Paris Orly) and orchestrate it in the cloud?
Do you know any use cases for Microsoft Windows in the cloud?2 -
My team handles infrastructure deployment and automation in the cloud for our company, so we don't exactly develop applications ourselves, but we're responsible for building deployment pipelines, provisioning cloud resources, automating their deployments, etc.
I've ranted about this before, but it fits the weekly rant so I'll do it again.
Someone deployed an autoscaling application into our production AWS account, but they set the maximum instance count to 300. The account limit was less than that. So, of course, their application gets stuck and starts scaling out infinitely. Two hundred new servers spun up in an hour before hitting the limit and then throwing errors all over the place. They send me a ticket and I login to AWS to investigate. Not only have they broken their own application, but they've also made it impossible to deploy anything else into prod. Every other autoscaling group is now unable to scale out at all. We had to submit an emergency limit increase request to AWS, spent thousands of dollars on those stupidly-large instances, and yelled at the dev team responsible. Two weeks later, THEY INCREASED THE MAX COUNT TO 500 AND IT HAPPENED AGAIN!
And the whole thing happened because a database filled up the hard drive, so it would spin up a new server, whose hard drive would be full already and thus spin up a new server, and so on into infinity.
Thats probably the only WTF moment that resulted in me actually saying "WTF?!" out loud to the person responsible, but I've had others. One dev team had their code logging to a location they couldn't access, so we got daily requests for two weeks to download and email log files to them. Another dev team refused to believe their server was crashing due to their bad code even after we showed them the logs that demonstrated their application had a massive memory leak. Another team arbitrarily decided that they were going to deploy their code at 4 AM on a Saturday and they wanted a member of my team to be available in case something went wrong. We aren't 24/7 support. We aren't even weekend support. Or any support, technically. Another team told us we had one day to do three weeks' worth of work to deploy their application because they had set a hard deadline and then didn't tell us about it until the day before. We gave them a flat "No" for that request.
I could probably keep going, but you get the gist of it.4 -
Ok I completely lost it... Been in a prod issue all week and basically just said the root cause is bc this team is blind....
Use the forest and trees analogy first but they still didn't seem to see it so I sent them this.
And then the chat went silent....2 -
I'm trying out blazor at the moment, building a couple of prototypes. I really need to brush up on my html/css for the view stuff, and of course there are a few gotchas. But other than that, I really think Microsoft has nailed browser apps with this!
Client side, server side, a mix of both, runs in all major browsers + as PWA or Electron.
Wow.
All logic and view manipulation in C#, no JS. And the performance is great.
Just.
Wow.1 -
Convert images to ASCII pictures in PowerShell
https://github.com/off-world/...
sharing my latest side project here as I thought some of you guys maybe will like it.1 -
Oh no, oooooh nononono
they dont delete the branches after a pull request
232 branches? hhhhhhhhhhhhhhhhhhhno
and look at that naming
im intimidated, i dont want to work in this environment. No. NO!7 -
"Oh no this platform is serverless"
I hate this "serverless" term.
How does a cloud platform run serverless?
HOW?!
"yeah but like we don't have to run updates and manage the underlying stuff and can thus deploy stuff serverless"
NO.
THERE ARE ACTUAL SERVERS RUNNING IN ORDER TO RUN THIS PLATFORM.
YOU CANT RUN THIS FUCKING PLATFORM WITHOUT ACTUAL SERVERS.
HOW WOULD IT RUN THEN, ON FUCKING STARDUST?!
IT. IS. NOT. SERVERLESS. AS. LONG. AS. SERVERS. ARE. INVOLVED. AT. SOME. LEVEL.73 -
When a company operates like a startup but they're over 10 years old and they try to do the micro brew lunch thing and be "casual" but they pay you like shit and the boss is a moron.1
-
Our company cooperates with a university in training students. In my time that meant learning about HTML, CSS and OOP in the first semester, so that we'd be able to actually do stuff in the company. Nowadays it means learning none of that crap but instead Racket. "What the flying shit is Racket", you ask? "Oh, it's a functional programming language. It has lots of parentheses!", student says. Well fuck me. Out go 2 days of careful planning what task they should be able to handle, in go 3 weeks of tutorials and explaining basic shit they are supposed to learn in university...1
-
Humanity has reached its peak!
Outstanding move! Deploy it in production 🔥🔥
https://skillprogramming.com/top-ra...6 -
So my CTO comes to me and asks me to checkout the APIs provided by a particular service and see if we can use them.
After two days of research I go to him and tell him that it cannot be done and it doesn’t fit our use case. He tells me research more although I have researched everything required.
So I take two days doing absolutely nothing, send a mail to the developer of the apis and they tell me that it can’t be done.
Now imagine this kind of scenario occurring every three months. RESEARCH MORE.
Why do super senior members of our company don’t trust me. It’s just so random and anger evoking7 -
Holy fuck, the state of npm
Question: "How do I make a GET request in NodeJS"
Accepted answer: "Use the http library it has built in get functions, its quite simple"
I FUCKING KID YOU NOT, THE NEXT 10 ANSWERS: Use this npm library, it's super great ;)22