dotLou

1. Import GPG keys from 1password/keybase/etc. (public & private!)
2. brew install gpg gpg2 pinentry-mac
3. echo "pinentry-program $(which pinentry-mac)" | tee ~/.gnupg/gpg-agent.conf
4. Restart the agent (something like pkill -TERM gpg-agent and then a new terminal)
5. Test it out echo test | gpg -e -r EMAIL_GOES_HERE | gpg -d (replace EMAIL_GOES_HERE with email of target key)

idelem

javascript:(function() {

function copyToClipboard(text) {
    if (window.clipboardData && window.clipboardData.setData) {
        /*IE specific code path to prevent textarea being shown while dialog is visible.*/
        return clipboardData.setData("Text", text); 

    } else if (document.queryCommandSupported && document.queryCommandSupported("copy")) {
        var textarea = document.createElement("textarea");
        textarea.textContent = text;

jahfer

module MyLogSubscriber
  def sql(*args)
    trace = caller
    Rails.backtrace_cleaner.remove_silencers!
    Rails.backtrace_cleaner.add_silencer { |line| not line =~ /^(components)\// }
    puts Rails.backtrace_cleaner.clean(trace)
    super
    puts "---------------"
  end
end

wojteklu

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