• 0 Posts
  • 59 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle

  • An interview is an opportunity for both of you to decide if it’s a good fit. Unfortunately the seeker is usually happy to accept anything. Lying is counter productive. They only want to hear any reason that you picked their workplace. Consider it structured small talk and focus on your energy.

    I generally say: "let’s be realistic, I’m not passionate about what your company does. I am here to trade my time for wages and I have heard good ones about [company name].

    Elaborate by mentioning something from their website to appear engaged and interested. Say you were a perfect fit because you meet all the requirements, talk about a friend who works there, mention using their products or services, or just mention that it’s close to your house and will be a short commute. Ultimately this is a soft question that is just to get a quick idea of each person applying.





  • US Sr SRE (devops) checking in: I would personally recommend the networking path. Caveat: A good engineer will know the background of both (curl, telnet, Iam, security groups, cidrs, domains)

    Devops was mostly automating the stuff in between the other teams; and most of that is working out of the box these days. Most repos already have their Jenkins and docker files. How much admin are you expecting on serverless? Most people are pivoting to app support (ticket queues) or supporting managed services (on call).

    As far as my day to day:

    • Troubleshooting incidents and walk ups
    • Answering pages (read restarting things)
    • Groovy Jenkins build pipelines
    • Cdk applications
    • Ruby configuration management
    • Parameter/secret management
    • Reading error messages for devs
    • Yaml/xml linting
    • Assisting in load testing
    • Changing settings to make the application more stable. Ex: db connections, memory
    • Cloud UI/clis

    Pros: I do a lot of different things, we get downtime because we need to respond to things immediately, I don’t have normal project/sprint planning. I have the keys to the kingdom. Higher pay than most other devs. I hack things together, I don’t need to design workflows.

    Cons: I am on call, I am the silliest clown (I get hardest problems), I need to understand a lot of moving pieces, sometimes when things break, there is a lot of pressure on you to find something hard. I regular have to Google “bash variable syntax” because I’m coding in 15 languages. Interviewing for jobs is impossible because no 2 positions are the same








  • Grab a 4 free AOL disk from blockbuster, use 3 of them as frisbees. Take the last one home and spend 10 minutes waiting the interface to install. Plug in the phone line and hear a series of beeps and schreeches before being greeted by an early robotic voice saying “welcome!” And often “you’ve got mail”.

    Afterwards you follow a guide to sign up for a mail account and a text like document with links to AOL platform tooling like chat rooms and search tools. You started looking for urls everywhere wondering what hidden gems you’ll find in the virtual world and what kind of content was on cereal websites or Nickelodeon. There was a massive learning curve for multimedia, but you had a lot of pen pals from chatrooms. So much porn spam. Nabisco had an awesome gaming site



  • On a very specific note, I don’t run my Plex server in a container. I have a docker compose setup with 20+ apps, but Plex is on the bare metal OS because it’s kinda finicky and doesn’t like nas. You also need to setup the Plex API to claim the server as the container name changes. This is my stock Plex config if it helps

    plex:
        image: lscr.io/linuxserver/plex:latest
        container_name: plex
        network_mode: host
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Etc/GMT
          - VERSION=docker
          - PLEX_CLAIM= #optional
        volumes:
          - /home/null/docker/plex/:/config
          - /x:/x
          - /y:/y
          - /z:/z
        restart: unless-stopped
    

  • It’s built on the shipping container parallel. In order to transport objects you obfuscate anything not required for shipping a container.

    • What’s inside the container doesn’t matter. The container has everything it needs to run because the ship/host is responsible for the overhead.
    • containers move. Containers are setup to run by themselves, so you can move it from one ship to another. This means you can use your container doesn’t care if it’s in the cloud or a shipping vessel
    • As soon as you open a container your stuff is there. It’s very easy to onboard.
    • Most importantly though, your shipping container isn’t a full boat by itself. It lives in a sandbox and only borrows the resources it needs like the hosts CPU or the boats ability to float. This makes it easier to manage and stack because it’s more flexible


    • VLC media player is the gold standard
    • Open broadcasting software / stream labs for broadcasting and studio management
    • Ffmpeg for video editing
    • Yt-dlp for downloading video
    • audacity MP3 editing
    • Plex / jellyfin / Stashapp for media server
    • Pixlr for cloud photo editing
    • Yarn / chocolatey / Asdf / node / poetry - package management
    • Flaresolver, pihole, home automation, nginx
    • Qbit-*arr for file sharing
    • Massgrave for windows activation
    • Filezilla for ftp (upgrade hosting)
    • Depending on bullshit level: discord, Google workspace offers custom domain Google accounts
    • Anything past that I write for myself or find a project with a dockerfile