ℍ𝕂-𝟞𝟝

  • 0 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2024

help-circle







  • about laws in general

    Terms of Service aren’t laws. Breaking them is not illegal. It’s like using the waterslide while sitting and not lying on your back. In fact, it’s explicitly legal to use an adblocker and control what happens on your device in both the EU and the US. There are ongoing debates whether the surveillance required for blocking adblockers is legal in the EU.

    Google does break laws all the time by the way, and is holding a monopoly. If people had to pay for Youtube, alternatives would spring up overnight, but since you can still watch Youtube free, they can’t.

    Also, I’d be the happiest person if Google finally figured out how to block people with adblockers completely, so that the majority of people would wean themselves off of one of the world’s biggest disinfo peddlers.











  • Usually what I would do is start with a baseline summary, and then either dive into a step-by-step on how you would go about solving the problem, or just ask if they want a deeper explanation.

    The big secret of tech interviews I found was that if the interviewer should actually be on your side. From their perspective, the point is to fill the vacancy as soon as feasible and if you can’t cut it, they will have to sit in the same chair yet again. If you are not sure what kind of answer they need, like “Should I cover everything like I’m explaining it to a new user”, you can just go and ask them, they should be happy to help. To me, it would even present professionalism, that you are trying to tailor your response to your audience.

    Of course, there are always going to be weirdos who when they get the thinnest veneer of power, will either mess with you for the sake of it, or “show off their 1337 h4x0r skillz”, but my advice to that is that just stay unfazed, and do your best.

    And all in all, it’s going to be a numbers game, in every interview round. Rejections don’t mean shit when HR departments insist on collecting hundreds of CVs before calling in and hiring the person who applied first anyway. Even if you get in, and don’t get selected, it doesn’t even mean that the other candidates were better, it’s just someone jumped the bar earlier. Keep trying and good luck! BTW feel free to bother me with stuff relating to this, I’m happy to answer if I can.


  • You are bringing up good approaches and you would have been hired if you could explain how you would start to troubleshoot some of those issues.

    The answer to the problem that this team ran into was that you can actually run out of inodes in a filesystem if you have a very large number of relatively small files, and that might show up as failed writes that can make a program like a DBMS say “the disk is full”.

    Regarding getting hired though, I have no idea about the market and pay nowadays especially wherever you are. I hope it’s good for you, it was certainly good for me in the 2010s in Eastern Europe, but I’ve heard it’s shit everywhere these days.


  • I worked as a DBA for a while, I got into it by getting into a niche database system (Apache Cassandra) at a startup for a PoC and then the local megacorp was desperately needing someone with that experience.

    The day-to-day was mostly these things:

    • Organizing and educating outsourced teams in India for routine maintenance tasks, mostly by writing “do this then this” style docs for them
    • Act as L3 support when stuff broke - this one was rare, I was once paid a day of overtime because someone messed up a migration, took the whole global system offline, and I had to sit there see stuff come back again when they fixed it
    • Write automation for automated deployment into Microsoft Azure, imagine writing Ansible code and Terraform
    • Make architecture diagrams and plans and help debug developers’ harebrained attempts at using the database for things that it was not made for, but they wanted it on their CV

    It was a very slow job, with nothing to do all December - since there was a code freeze - for example. That said, it’s essential to understand Linux on a deeper level to be a DBA, like one interview question was “you have a 2TB disk with 400 gigs of data on it, yet the OS is complaining that the disk is full, what is the likely issue and how do you debug it”.