HR people working in tech companies, let's talk about them...

*phone rings and I pick up*
HR Lady: Hi, this is [name] from [company]. I'm calling you regarding your application you submitted [some date 2 months ago!].

Me: *realizing that I've applied 2 freaking months ago* Hmmm OK....

HR Lady: Yes, well, we asked for your GitHub account, but you seem to have forgotten to provide it.

Me: *open up the email and see that I've sent them my GitLab account* Well, I have the email right here and I did send you a git account. I mean, it's not GitHub specifically but it's a GitLab account, pretty much the same thing, you should be good with that.

HR Lady: OK, let me put you on hold for a minute.

*2-3 minutes passes*

HR Lady: Hi sir, I've asked my colleague [which I suppose is another HR] and he told me that they're not the same thing, we cannot proceed until you give us the right link, you need to send us a link to your GitHub account.

Me: I mean, they aren't the SAME EXACT thing, but both companies provide essentially the same service, it's like Messenger and WhatsApp. Look, I'm pretty sure that if you give this to another programmer they'll be fine.

HR Lady: No, Messenger and WhatsApp aren't the same thing. Sir, please stay polite. We need a GitHub account not a GitLab account.

Me: *mumbling* Oh boy.... M'am, it's OK, I don't need the job anyway, I've found something. Two months is a long time and I needed something quickly. Thank you, have a good day.

SYS_ADM: We have something important on the internal GitLab?
ME: Please tell me it is working
SYS_ADM: I take it as yes...

Github bought by Microsoft.
GitLab migrating to Google.

I Already didn't use github but I'm a - that'll change soon - gitlabber.

Post alternatives in the comments please!

I had a huge epiphany on Friday... not all developers enjoy coding.

Discovered when they brought down 2 of our environments, well told them what was wrong with the changes in their code that caused the environments to break, gave them links directly to the file in the gitlab repo that needed to be updated, and...

They fucking went home. The change would’ve taken all of about 30-45 seconds to update and they fucking left.

This person’s team lead come storming in pissed off because her manager is furious about 2 environments going down and preventing everyone else from being able to deploy their changes.

We provide the exact same details to the team lead about what needs to be changed, and advise that her team member took off....

30 mins later, her manager is storming up to us (devops/sre) livid as hell.

Explain the situation for a third time... manager is like, why can’t you guys fix it?

Look here you dense motherfuckers, we can fix the code. We can be the plumbers that clean up your shit. But what value do you gain as a developer if you don’t understand how the systems work and you keep pushing shit in?

Made the changes, fixed the environments, done right? Wrong.

The original developer made more changes not knowing what would happen and thoroughly fucked the environments again.

This dumb-fucking dumpster fire of a dude then sends us a slack message. “It’s down again, can you fix it?”

Our manager steps in and tells us to send him a link to the logs and have him fix it himself!

Thank goodness we have a badass manager.

Send logs, send repo file links (again), and send line numbers in the logs to try and help just a bit more. Dude goes almost the whole day without fixing it, environments are down, other devs are pissed, we throw this dude to the wolves. His manager starts to head over and was about to talk with my team lead when our manager steps out of his office and tells him the in’s and out’s of the situation and that our job isn’t to play log parser/error fixer for the developers. This dude that’s breaking the environments needs to be the one to fix the issue and his team lead should be aware of the problems and should have been able to correct his errors before it ever came to us.

The amount of hand-holding we do is ridiculous.

(Disclaimer, this one guy making some mistakes doesn’t sound too bad, but this is actually a common occurrence for like 40% of all of our developers)

We literally have interns still in college running circles around some of our full time devs. I know I’m not a developer, but for anyone that’s new-ish to developing, when you see shit like that please don’t lose hope. Those ass-hats got into programming purely for a paycheck, not because of passion.

Stick with it and your greatness will know no bounds 👍

As for you craptastic dipstick lickers, FUCK YOU!!! Go back to school and learn how to give a damn.

NO MICROSOFT FOR FUCK SAKE NO!

I have a fucking 15inch screen and that left side menu is eating 25% of it! IF you gonna throw in a new "Creative" design, make the damn menu re sizable, NO I DO NOT WANT TO HIDE THE LABELS AND MEMORIZE YOUR STUPID ICONS!

At least do what Gitlab did, a nice small menu that DOES NOT EAT HALF THE DAMN SCREEN!

Oh, did I say anything about sub menu hell that pops up whenever your mouse hover over any of the items on the left? Yaaa... that goes to a brand new rant!

About slightly more than a year ago I started volunteering at the local general students committee. They desperately searched for someone playing the role of both political head of division as well as the system administrator, for around half a year before I took the job.

When I started the data center was mostly abandoned with most of the computational power and resources just laying around unused. They already ran some kvm-hosts with around 6 virtual machines, including a cloud service, internally used shared storage, a user directory and also 10 workstations and a WiFi-Network. Everything except one virtual machine ran on GNU/Linux-systems and was built on open source technology. The administration was done through shared passwords, bash-scripts and instructions in an extensive MediaWiki instance.

My introduction into this whole eco-system was basically this:
"Ever did something with linux before? Here you have the logins - have fun. Oh, and please don't break stuff. Thank you!"

Since I had only managed a small personal server before and learned stuff about networking, it-sec and administration only from courses in university I quickly shaped a small team eager to build great things which would bring in the knowledge necessary to create something awesome. We had a lot of fun diving into modern technologies, discussing the future of this infrastructure and simply try out and fail hard while implementing those ideas.

Today, a year and a half later, we look at around 40 virtual machines spiced with a lot of magic. We host several internal and external services like cloud, chat, ticket-system, websites, blog, notepad, DNS, DHCP, VPN, firewall, confluence, freifunk (free network mesh), ubuntu mirror etc. Everything is managed through a central puppet-configuration infrastructure. Changes in configuration are deployed in minutes across all servers. We utilize docker for application deployment and gitlab for code management. We provide incremental, distributed backups, a central database and a distributed network across the campus. We created a desktop workstation environment based on Ubuntu Server for deployment on bare-metal machines through the foreman project. Almost everything free and open source.

The whole system now is easily configurable, allows updating, maintenance and deployment of old and new services. We reached our main goal for this year which was the creation of a documented environment which is maintainable by one administrator.

Although we did this in our free-time without any payment it was a great year with a lot of experience which pays off now.

Business Continuity / DR 101...
How could GitLab go down? A deleted directory? What!
A tired sysadmin should not be able to cause this much damage.
Did they have a TESTED dr plan? An untested plan is no plan. An untested plan does not count. An untested plan is an invitation to what occurred.
That the backups did not work does not cut it - sorry GitLab. Thorough testing is required before a disruptive event.
Did they do a thorough risk assessment?
We call this a 'lesson learned' in my BC/DR profession. Everyone please learn by it.
I hope GitLab is ok.

Every day I get more convinced, that companies are only hiring the mentally disabled to their marketing departments.

Gitlab now spams ads constantly in my Facebook feed, because "I have visited gitlab.com".

If I have visited it, I am clearly already using it, stop annoying me please.

i'm starting to consider taking back what i said about gitlab... ARGGHGHGH

That feeling when you upgraded an internally used library from TypeScript 1.8 to 2.5 getting rid of the typings dependency and fixed its bug highlighted by the upgrade and all tests are green -- that feeling would not be rantworthy.

Realizing on trying to publish the new version that the master branch is not the actual master branch but a branch called 0.3 is. Of course I cannot merge my changes back there.

I don't mind a different main branch name. Yet don't call it a version, that's what tags are for. And for all that's holy, please set the proper main branch in your bitbucket / GitHub / gitlab so that I can find out easily.

Now I've wasted half a day and if you're looking for me: I'm gone searching for the motivation of doing the same shit again for the "main" branch.

!rant

I haven't used CI/CD to actually deploy an app. But I really want to automate all of that in my company. We use gitlab, so the logical thing is to use Gitlab's devops(?). Anyone who can guide me on an adventure for starting on CI/CD? Not sure if I need to give any more info, please let me know

Git, GitLab CI, and Python's SetupTools are pain, hell, and they ruined my day. I can't get my project onto PyPI because it constantly errors out. Ugh.