Ay I work with this on a daily basis, so I actually know something about this! :D

Other people are absolutely right, in saying that necessary cookies are allowed, without the consent of users. This isn't just GDPR, but also CCPA, LGPD etc.

If you take a look at for example cookiebot.com (shameless plug), you'll see that there's different categories, with "necessary" being prechecked, and you're unable to uncheck it.

Also: there's other reasons why this cookie banner is not GDPR compliant

Almost 8 months down the line now, and I still absolutely love my job. In some ways even more than when I started

@alexbrooklyn yes

@magicMirror yeah I agree with that. We're very agile where I work, and a fix is usually in place within a few hours

@magicMirror true, but that doesn't matter in this case. This scenario is for the rare "oh fuck" moments, where a bug's gone into production, and the next commit is going to be something that should fix it.

Then you can agree or disagree whether you think that's a good strategy. Personally I think it's better than reverting, when you step back and look at it from a full DevOps perspective, and not just git

@theKarlisK Thank you! That's exactly what I wanted

@Voxera & @magicMirror, thanks for the answers, but I stated in the original post that I did not want to rely on reverting the commit history

@SortOfTested That's exactly the kind of thing I want to avoid

@rutee07 I'm not sure we're talking about the same thing? This isn't something to be run every time, but only if something goes wrong with the deployment

@alexbrooklyn To keep a better history of what has happened in the project. It's not a huge thing, but would really be nice to have

One month update: I'm loving it even more than when I started 😀

I've 'proven my worth' enough that I essentially have enough permissions to lay the entire company down. Not that that's a good measure of performance, but it's a weird feeling, considering I've ever only worked on personal projects before.

Turns out I was right about having a say in the direction of operations. I've already implemented/deployed a bunch of stuff, and my boss sometimes asks me for advice on how something should be done.

So in summary: I don't think I could've asked for a better job.

Finally got rid of them the other day. Something when right, and the transfer to Cloudflare succeeded. I checked with ICANN to be sure, and it did indeed say that cloudflare is the registrar.

Since I paid domain.com 50$ last week, I wanted them refunded. So I contacted their live chat, and it was just a terrible experience. I started by choosing "billing support", and wrote a message saying my domain had been transferred, and that fucker started troubleshooting my domain, saying that it's because the name servers pointed to Cloudflare. Yes you souphead, that's why I want my money back!

Anyway, I got him to read the message again, and he proceeded to tell me that they are still the registrar, and I therefore couldn't get my money back. I had to tell him that I checked on ICANNs website, and that they're not. Only then would he recheck, and accepted that I needed to have my money back, which I then got

@katbreitin honestly not much. Its way more important that ypu have an interest in it, than being extremely knowledgeable.

That being said, there are some common areas that are good to know. You should at the very least know how to set up a ci/cd pipeline. Then it wouldn't hurt to be skilled in at least one cloud vendor, and also knowing how to monitor stuff.

@jtaylor991 i absolutely hate that 'jump-starting' the laptop just worked...

@pythonInRelay that sucks ass. But at least they work as they should in regards to just being a domain registrar, at least in my experience. At domain.com you can't even change your name servers or A records 80% of the time.

Or to be fair, they apparently do have a console that works semi-decently, which I've found found via them linking it to me in a mail, while telling me my domain is about to expire.

I feel you man. I recently graduated with a Computer Science degree, but I've felt like you for a long time. So I got a job as a DevOps Engineer, and it's absolutely amazing

@SortOfTested *was. MacBook build quality was great. And that is talking from experience

@Python just Windows 10. Not even a reinstalled version. But I think Dell is going the MacBook route. Used to be amazing, but build quality is starting to degrade. My colleague got the same model as me, at the same time, and his had a TouchPad that was wobbly. A tech had to come and replace it to get it functioning properly

@totoxto a lot of times it won't start when I press the start button. Happens both from completely shut off, and sleep state. Wifi and Bluetooth is really unstable. I have a Bluetooth keyboard at work, and sometimes I'll have to restart the computer for it to work again (yes it also happens with other devices). And just now the track pad stopped working. Took a reboot for it to work again

@brettski I'm just as excited as you are 😂

@Kashmir i didn't actually get to do a lot of work, but the workplace is just so nice, and great colleagues. I've been hired as a Devops Engineer, and it's clear that I'm going to have a say, in where the direction we're going.

I know that can be dangerous, but I really think I'm going to love it there

It went incredibly well :D

@wonwon0 thanks for the advice, but the 8GB I have now are dual stick

I quite like it too

Definitely vscode

I definitely prefer AWS. It can be more complicated yes, but you can set up an entire eco system up around specific services, and not worry about them being suddenly shut down

I write on medium and honestly I think it has been amazing. They have a great publication and category system, which can help boost your views a lot. My second post ever was a post about let's encrypt, docker and nginx, and it got over 20k views in the first couple of days, because it got picked up by both a publication. I have 3 semi-popular articles, netting me about 10$ a month.

That being said, I think you should start writing when you feel you have something to write about. Medium is like 70-80% bullshit, and there's no need to add to it.

I started like you, just wanting to write because I wanted to write, not because I had something to write about. I have written articles with that mindset, and they have done porely, I'm not proud of them, and honestly I'm thinking about deleting them.

To sum it up: don't focus on writing a lot. Focus on writing something you'll be proud of, and most importantly: something you'd want to read yourself

If you're hosting it on github, I'd recommend github actions. I've used a bunch of CI/CD tools by now, and I think that actions is by far the best

Works pretty great. I've also had to change OS a few times, and exporting/importing a zfs pool is incredibly easy

While I agree MS has done a bunch of amazing things, both MS and Github has said that most of the new features were on the road map even before the acquisition.

Gotta give credit to GitHub too

@RemusWasTaken Sincerely thank you for not being an assbutt, and owning up. As for your last comment you are right. And I do see how my comment can be understood that way. Although I did write "be somewhat sensible", meaning that you shouldn't just down chips and soda.

Also the one-meal-a-day will definitely work. I've been doing it myself for a few weeks now, and I definitely feel all the benefits: Less foggy brain, more energy, and of course weight loss.