Skip to content

Instantly share code, notes, and snippets.

View skyzyx's full-sized avatar
👾
OOICU812

Ryan Parman skyzyx

👾
OOICU812
View GitHub Profile
@skyzyx
skyzyx / homebrew-gnubin.md
Last active April 24, 2024 00:04
Using GNU command line tools in macOS instead of FreeBSD tools

macOS is a Unix, and not built on Linux.

I think most of us realize that macOS isn't a Linux OS, but what that also means is that instead of shipping with the GNU flavor of command line tools, it ships with the FreeBSD flavor. As such, writing shell scripts which can work across both platforms can sometimes be challenging.

Homebrew

Homebrew can be used to install the GNU versions of tools onto your Mac, but they are all prefixed with "g" by default.

All commands have been installed with the prefix "g". If you need to use these commands with their normal names, you can add a "gnubin" directory to your PATH from your bashrc.

@skyzyx
skyzyx / README.md
Last active February 28, 2024 20:45
Modern macOS Releases (i.e., not "Classic")

Modern macOS Releases (i.e., not "Classic")

Version Codename Release Date Time as Current Release
10.0 Cheetah 2001-03-24 6m
10.1 Puma 2001-09-25 11m
10.2 Jaguar 2002-08-24 14m
10.3 Panther 2003-10-24 18m
10.4 Tiger 2005-04-29 18m
10.5 Leopard 2007-10-26 22m
@skyzyx
skyzyx / README.md
Last active January 6, 2024 23:39
Parman tacos

Parman Tacos

Serves 3–4, depending on how hungry everyone is, usually with some leftovers.

If you've never had them before, try them as-made at least once before making changes. They are NOT your traditional Mexican-inspired tacos. DO NOT start putting hot sauce, sour cream, or guacamole on them, or you will insult the chef. THESE ARE NOT THAT KIND OF TACO.

BEFORE YOU START COOKING: Read the entire recipe and instructions first so that you know what's coming. THEN, go through the recipe a second time as you perform the steps.

The history of this taco recipe…
@skyzyx
skyzyx / engineering-roles.md
Created December 11, 2017 19:58
Engineering Role Definitions

Engineering Role Definitions

Note: Although the levels may be different, these tend to map pretty cleanly to similar hierarchies at Google and Microsoft, but they have no correlation to hierarchies outside of the "club" of elite companies (Microsoft/Amazon/Google/Facebook, etc. on the west coast, Bloomberg/Goldman/HFT firms, etc. on the east coast).

People with 10-15 years of software engineering experience interview all the time at these companies, but they may not be fit for much more than a junior engineering role (SDE I or SDE II, depending on which company you're looking at).

Junior Engineer/Intern:

  • Is essentially a new and inexperienced (below the level of Amazon/Microsoft/Google engineers) junior engineer.
  • Attending college for computer science, or really good at teaching themselves from books and online tutorials.
@skyzyx
skyzyx / README.md
Last active November 1, 2023 16:41
Alternate CPU Architecture Identifiers

Alternate CPU Architecture Identifiers

I work with Linux in Docker on the daily. And the people and machines I support have a blend of Intel/AMD and ARM/Graviton/AppleSilicon chips.

And the thing that bites me regularly is that different operating systems return different values for uname -m, even when they're the same thing.

The Problem this Helps With

  • We have users on macOS, Windows, and Linux.
  • We have a blend of worker laptops using both Intel/AMD and Apple Silicon CPU architectures.
@skyzyx
skyzyx / ffmpeg.md
Created November 29, 2020 01:43 — forked from steven2358/ffmpeg.md
FFmpeg cheat sheet
@skyzyx
skyzyx / README.md
Last active September 7, 2023 20:40
Priority Definitions

Operationally, P1, P2, and P3 have very specific meanings.

  • P1 means all hands on deck. Drop everything else and work on this. Don’t eat, don’t sleep until it’s handled. This has an open P1 in your operations tracking system.
  • P2 means that there is some impact, but not really for customers. P2 is like a P1, but for internal-only services. It’s also to get everybody to put eyes on a specific problem. This has an open P2 in your operations tracking system.
  • P3 is important, but not quite an outright fire.

When I’ve run app dev teams, I’ve treated them similarly, but not quite at the same level.

  • P1 - Urgent means don’t work on anything else until this is done. If someone else asks you to do something, they have to wait. It is a sprint-breaker, meaning that it takes priority over all other sprint tasks.
  • P2 - Very High is lower than a P1, signifying give this ticket your priority, even if it’s not the only thing you’re looking at. It is a sprint-breaker, meaning tha
@skyzyx
skyzyx / single.html
Last active February 27, 2023 04:21
Hugo Partial for Generating the Table of Contents
...
{{- partial "toc.html" . -}}
...
@skyzyx
skyzyx / rca.md
Last active December 8, 2022 19:32
Internal (not customer-facing) Root Cause Analysis (aka Post-Mortem) template

[20XX-XX-XX] Service Name downtime

  • This is a blameless Post-mortem.
  • We will not focus on the past events as they pertain to "could've", "should've", etc.
  • All follow up action items will be assigned to a team/individual before the end of the meeting.
  • If the item is not going to be top priority leaving the meeting, don't make it a follow up item.

| | |