mbigras

Location: Bay Area, CA

Remote: Yes

Willing to relocate: No

Technologies: GCP, AWS, Kubernetes, Docker, Linux, Terraform, Bash, Python, Go

Résumé/CV: https://www.linkedin.com/in/mbigras/ and https://github.com/mbigras

Email: mbigras22+hn@gmail.com

Hello future colleague! I'm Max Bigras and I'm on the hunt for my next Infrastructure/SRE/Production/DevOps Engineering role! I like to work with excellent people and create lasting professional relationships. These are some details about me:

    1. I'm a Senior Infrastructure Engineer with 7+ years of experience. My favorite type of company is a startup looking to level up (50–100 people). I've worked on infrastructure teams ranging from 1–6.
    2. In general, I'm skilled at creating multi-tier, multi-account infrastructure as code architectures and application delivery workflows with Terraform and my speciality is creating self-service workflows by documenting the details; I maintain meticulous notes about my thinking process which I publish internally.
    3. I tend to solve problems which no one else wants to—arcane Docker/Linux gotchas, IAM permissions, networking, CI/CD issues, updating docs—then I automate the solution in code and document the details.
    4. My favorite days at work are when I start to see others solving their own problems in a self-service way by linking to my Slack threads, wiki pages, GitHub discussions.

This is very cool! I like your approach in your README to include many fun and relevant little examples; for example:

You can use [Wren summary option] to update /etc/motd daily, or through the Telegram bot

Bravo! I’ll give Wren a try.

Shoutout to Richard Feynman! I didn’t immediately see his name appear on the page; but once I began reading his words, I glanced at the URL and I see, yes, it is a Feynman lecturer! Lucid and clear; slicing through obscure jargon in a fun and playful—but masterful—way; Feynman totally rocks and is worth reading further!

Precisely that and I couldn’t agree more. I even ditched my case about a year ago—live for today.

The hardest thing is the strain the whole experience puts on my relationships. I already used up all my fiancé’s patience with my chronic melancholy about my perfectly functional but ultimately doomed phone; and end of life hasn't even happened yet.

Seeing iOS 12.5.7 was bittersweet, a glimmer of hope, a reason to hold on.

Please accept my sympathy. I do understand and soon enough I'll be in the same predicament. Every iOS 15 patch feels like a gift. I seriously don't know what I'm going do when iOS 15 becomes end of life; there aren't any modern phones that have my critical—and arguably reasonable—hardware requirements.

Excellent to see a fellow SE user! I still happily run my iPhone SE (1st generation). I might take 5 minutes to boot Notion or run out memory and crash when I try to boot Amazon; but, my EarPods pair instantly—I just plug my 3.5 mm jack in my 3.5 mm port and then I can freely listen to music or do a phone call (works every time)! Also, I can easily swap connections from my laptop to my phone with the same workflow—simple (but sadly not futureproof).

Do the Technical Writing One course [1] and consider Google developer technical documentation style guide highlights [2]. Both those links are about technical writing which is primarily about clarity. Since I started focusing on clarity when writing, I find any writing fun and engaging.

-[1] https://developers.google.com/tech-writing/one

-[2] https://developers.google.com/style/highlights

Thank you for linking this, just made my day!