Skip to content

Instantly share code, notes, and snippets.

View pykong's full-sized avatar
🎯
Focusing

Ben Felder pykong

🎯
Focusing
27 followers · 22 following
View GitHub Profile
@pykong
pykong / open_in_sublime_merge.nemo_action
Last active December 22, 2019 16:20
Put under ~/.local/share/nemo/actions/
[Nemo Action]
Name=Open in Sublime Merge
Comment=Open in Sublime Merge
Exec=/opt/sublime_merge/sublime_merge -n %F
Icon-Name=sublime-merge
Selection=any
Extensions=dir
Quote=double
@pykong
pykong / open_in_sublime_text.nemo_action
Last active December 22, 2019 16:20
Put under ~/.local/share/nemo/actions/
[Nemo Action]
Name=Open in Sublime Text 3
Comment=Open in Sublime Text 3
Exec=subl -n %F
Icon-Name=sublime-text
Selection=any
Extensions=dir
Quote=double
Mimetypes=text/plain
Dependencies=subl
@wojteklu
wojteklu / clean_code.md
Last active May 3, 2024 08:55
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules