Skip to content

Instantly share code, notes, and snippets.

View sciencefixion's full-sized avatar

Rion sciencefixion

45 followers · 104 following
View GitHub Profile
@kevin-smets
kevin-smets / iterm2-solarized.md
Last active October 31, 2025 08:25
iTerm2 + Oh My Zsh + Solarized color scheme + Source Code Pro Powerline + Font Awesome + [Powerlevel10k] - (macOS)

Default

Default

Powerlevel10k

Powerlevel10k

@lfender6445
lfender6445 / gist:9919357
Last active October 8, 2025 09:24
Pry Cheat Sheet

Pry Cheat Sheet

Command Line

  • pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)
  • pry -r ./config/environment.rb - load your rails into a pry session

Debugger

@iandouglas
iandouglas / README.md
Last active August 26, 2024 17:38
Intro to Co-Authored Git Commits

Intro to Co-Authored Git Commits

Why

In student projects, I commonly look at contribution graphs to see how much code they worked on, to get an idea if one student is doing more work than others on the project. This can be used for coaching and performance grading.

How

Start with your ~/.gitconfig file in your home folder. Add these lines:

@megstang
megstang / feedback_from_me.md
Last active August 25, 2021 20:16
Project Feedback (Mod 1 && Mod 2)

Project Feedback

Directions

  1. For every partner you have, make a copy of this gist
  2. Fill out the copied gists with feedback for each group project partner (one gist per partner)
  3. Send us your feedback for each partner using the form posted in slack/assignment tracker (one submission per partner)
  4. Individually slack your partners the link of the gist you filled out for them
  5. Spend some time reviewing your partner’s feedback that they sent you
  6. Get on a video call with your partner(s) for the in person partner retro to discuss feedback.