jrmann100

  brew install --cask app --no-quarantine

  export HOMEBREW_CASK_OPTS="--no-quarantine"

  alias unq="xattr -dr com.apple.quarantine"

  Location: San Francisco, CA
  Remote: Yes, onsite preferred
  Willing to relocate: Yes
  Technologies: JavaScript, TypeScript, React, Express, MongoDB, NodeJS, HTML, CSS, Deno, Svelte, Swift, SwiftUI, Figma, Docker, Git, Python
  Résumé/CV: https://home.jrmann.com/resume
  Email: first name at last name dot com

  Location: San Francisco, CA
  Remote: Yes, onsite preferred
  Willing to relocate: Yes, tech city preferred
  Technologies: JavaScript, TypeScript, React, Express, MongoDB, NodeJS, HTML, CSS, Deno, Svelte, Swift, SwiftUI, Figma, Docker, Git, Python
  Résumé/CV: https://home.jrmann.com/resume
  Email: first name at last name dot com

  Location: San Francisco, CA
  Remote: Yes, onsite preferred
  Willing to relocate: Yes, tech city preferred
  Technologies: JavaScript, TypeScript, React, Express, MongoDB, NodeJS, HTML, CSS, Deno, Svelte, Swift, SwiftUI, Figma, Ansible, Docker, Git, Python
  Résumé/CV: https://home.jrmann.com/resume
  Email: jordan.r.mann.25 [at] dartmouth [dot] edu

  When you run "tmux -CC", a new tmux session is created. An iTerm2 window opens and it acts like a normal iTerm2 window. The difference is that when iTerm2 quits or the ssh session is lost, tmux keeps running. You can return to the host you were ssh'ed into and run "tmux -CC attach" and the iTerm2 windows will reopen in the same state they were in before.