Skip to content

Instantly share code, notes, and snippets.

View leeorengel's full-sized avatar

Leeor Engel leeorengel

10 followers · 0 following
View GitHub Profile
@leeorengel
leeorengel / nice-jumper.el
Created May 30, 2016 17:19
quick'n'dirty evil-jumper without evil
;;; nice-jumper.el --- Jump like vimmers do!
;; Copyright (C) 2016 adapted by Martin Albrecht
;; Copyright (C) 2014-2016 by Bailey Ling
;; Author: Bailey Ling
;; URL: https://github.com/bling/nice-jumper
;; Filename: nice-jumper.el
;; Description: Jump like vimmers do! (for older versions of evil-mode)
;; Created: 2014-07-01
;; Version: 0.3.1
@leeorengel
leeorengel / rules.md
Created December 21, 2017 15:55 — forked from henrik/rules.md
Sandi Metz' four rules from Ruby Rogues episode 87. Listen or read the transcript: http://rubyrogues.com/087-rr-book-clubpractical-object-oriented-design-in-ruby-with-sandi-metz/
  1. Your class can be no longer than 100 lines of code.
  2. Your methods can be no longer than five lines of code.
  3. You can pass no more than four parameters and you can’t just make it one big hash.
  4. When a call comes into your Rails controller, you can only instantiate one object to do whatever it is that needs to be done. And your view can only know about one instance variable.

You can break these rules if you can talk your pair into agreeing with you.

@leeorengel
leeorengel / _writing_clean_sql.md
Last active May 27, 2019 01:22
Before and After SQL as an example of writing cleaner SQL

Writing Clean SQL README

A contrived example to show some clean clode practices as they relate to SQL. In particular, the use of:

  • Factoring out logical bits of work into common table expressions (CTE’s) like functions.
  • CTE’s with good variable names
  • Showing a flat structure to what would otherwise be a highly nested set of SQL statements, which become unreadable quickly