Literally every thing below is IMHO
It's a lot of data in one spot so use the TOC.
- How to Search Google
- Sublime Shortcuts
- Code Readability
- File Organization
- Software Suggestions
- Config Options
- Links
- ⌘ – Command Key symbol
- ⇥ – Tab Key symbol
- ⌃ – Control Key symbol
- ⌥ – Option Key symbol
- ⇧ – Shift Key symbol
- ⏎ – Return symbol
HANDS OFF THE F*&^%ING MOUSE!!!
As a developer your time is a Super Valuable Resource...
So every little thing you can do to increase efficiency will pay vast dividends over the course of your career.
You rarely need to actually touch the mouse. Every time you do you must take your hands completely off the keyboard. Grab the mouse. Go click the thing, then transfer back to the keyboard, find the home-row and finally start typing again...Precious seconds that add up to a huge savings every day.
It won't be easy but start building this skill now. Force yourself to leave the mouse behind. You're better than that mouse. You don't need no stinkin mouse. You have Dev Hands!!!
Also long term mouse usage can lead to RSI which is a seriously legit thing to avoid.
Also worth noting that sublimes ⌘ p is hands down the fastest way to get around a working directory.
Super high on the list of most important things you will learn here.
See rule number 1. Any time you are leaving the keyboard you are losing time.
-
⌘ + t -- open a new tab
-
Enter search terms. The first word of your search should always be the language you are looking for.
-
⏎ -- to search google
-
tab this will take focus from the search bar and place it in the results list. You know you're there because a little blue arrow will appear next to the first result.
-
open the first 5 links into new tabs
- ⌘ + ⏎ -- to open link
- down arrow -- to go to next link
-
Cycle through tabs using
⌘ + ⇧ + {
⌘ + ⇧ + }
-
⌘ + w -- Close unwanted tabs
Super useful ones
- move lines vertically
⌘ + ⌃ - jump to file
⌘ + p + (fuzzy file name) - global search
⌘ + ⇧ + f - duplicate line
⌘ + ⇧ + d - select word (and repeat)
⌘ + d - commenting code
⌘ + / - jump to line
⌘ + p + : + (line number (int))
AKA: DO NOT STRAIGHT COPY CODE!!!!!
Don't just go to the INTERNET and find some answer on StackOverflow to paste into your code. This leads to a problem known as CopyPasta which is what happens when you paste in a bunch of code without having rewritten it for yourself. You forget to change a variable here, or access something out of scope there...... Pasting in code that leads to more time spent debugging is a losing trade.
I'm not telling you to not use code you find at all. What I am suggesting is this.
def some_method_i_will_write
end
# def some_method_pasted_in
# some_logic_i_need.each do |thing|
# p thing
# end
# endPaste the code in and IMMEDIATELY comment it out. Then use the commented code as a reference to build the thing that you are after.
A clean working screen is super clutch.
Basically I think you should always have your windows configured in a 66/33 split between the editor and terminal. Like so
The point being that as a Ruby Dev you are looking at the Terminal A LOT. So keeping it in a spot that is visible all the time is really useful from an efficiency standpoint. Much easier to just glance at your terminal for output as opposed to having to switch over and then find the output.
This job can be very grueling. Your personal sanity is a thing you should be mindful of always.
- Eat well
- Exercise often
- Yoga is great
- Work life balance (after dbc) is super important
- Always remember You are not your Code
- Talk to yourself... A LOT
- They're fragile too.
- A happy pair will allow a much stronger learning environment for both of you.
If it has a BEGINNING it also has an END.
Write the end as soon as you write the beginning and save your self countless hours counting def-end combinations
def thing_func
end
thingy.each do
end
{ }
[ ]Code readability BEATS conciseness 10.times out of 10
This means writing functions that are easy for developers to read. Not just you, but the people that maintain your code down the road.
Don't one line a thing because you want to look cool.
Indentation - OMG do this. All the time. No matter what. Lots of languages are whitespace dependent, meaning you must indent correctly. Better to establish this habit now.
Good habits when it comes to naming and storing files is something that will pay off big time for you in the long run.
Don't keep your files on the desktop.
Spend some time to figure out a good file structure that works for you. Once you make a plan stick to it. Down the road you will have away easier time tracking down projects because they will have been placed in to your structure by some standard of your creation.
Here is a sample of what a well organized file structure looks like.
Main Folder
├── 1Phase
│ ├── 1Week
│ ├── 2week
│ ├── 3Week
│ ├── assesments
│ ├── breakouts
│ ├── general
│ ├── lectures
│ └── phase-1-guide
├── 2Phase
│ ├── 4week
│ ├── 5week
│ ├── 6week
│ ├── assessments
│ ├── guides
│ ├── lectures
│ ├── other
│ └── p-challenges
├── 3Phase
│ ├── challenges
│ ├── lectures
│ ├── other
│ ├── phase-3-guide
│ └── someshit
├── Core_Coaches
│ └── Initial\ prospectus.pages
├── hackathons
│ ├── notes.md
│ ├── pitches.md
│ ├── schedule.md
│ └── team_leads.md
├── hemlock
│ ├── CONTRIBUTING.md
│ ├── Gemfile
│ ├── Gemfile.lock
│ ├── README.md
│ ├── Rakefile
│ ├── bin
│ ├── lib
│ └── spec
├── lectures
│ ├── 1phase
│ └── 2phase
├── other
│ ├── Ruby-Anagrams
│ ├── devbootcamp.github.io
│ ├── hemlock
│ ├── node_sample2
│ ├── react-7guis
│ ├── retros
│ └── rspec_rails_4
└── phase-guides
└── RockDovesCommit early and often
A good starting work flow might be something like:
- Create your branch
- Build test through a feature
- Commit
- Pass all tests for a feature
- Commit
Short and sweet. If you are using sudo to install something on your mac....
You're doing it WRONG
- Ask for help.
- When installing something, check for a homebrew formula as your first option.
Everything in this section should be taken with a grain of salt.
DO NOT go and install everything you see here. Look over, file away, take what works and leave the rest.
- Use Spotlight ⌘ + spacebar to search your system for files and applications.
⌘ + \ is what I use.
Also.... Use iTerm2 instead of terminal.
Get comfy with the pref here.
- Increase buffer size
- Increase Transparency
- Make a jazzy color scheme that works for you and you alone.
- Package Manager
- SideBarEnhancements (ST3)
- Better CoffeeScript
- All Autocomplete
- BracketHighlighter
- Markdown HTML Preview
- GitGutter
- ERB Snippets
- Haml
- JSLint
- PowerCursors
- SublimeLinter
- SublimeLinter-haml
- TernJS
- Theme - Brogrammer
- Tomorrow Color Scheme
The good the bad and the ugly
Pros
- help you see errors in your code
- give you tips on best practices
- easy to use
Cons
- can cause stability issues with Sublime
- others best practices may not always align with your own.
- Flycut (clipboard management)
- Spectacle (window management)
- Dropbox
- Alfred
- Dash
- iTerm2
- PostMan REST Client
- bropages(gem)
- haml
- guard-rspec
- guard-livereload
- guard-spork
- pry-byebug
- pry-doc
- better_errors
- binding_of_caller
- dotenv
- ghrepo
- Sublime (my preference)
- Atom
- VIM
If one of these is not your go to option you are denying yourself valuable resources on many fronts.
- As an OSX user you have a kickass development environment on your computer.
- Not knowing how to navigate that environment can be a serious detriment on the job.
- Sublime in particular has a metric ton of keyboard shortcuts that can greatly increase your efficiency as a dev.
Remote editors like:
- REPL.it
- Nitrious.io
- Coderpad.io
are nice... But come with some distinct drawbacks.
- Great for remote work and demonstrating concepts.
- Using them in a pair environment or on the job is just doubling the amount of work you have to do.
- Don't have access to all the very cool candy that Sublime gives you.
- Only good for single page scripts. You can't program a server in a virtual environment.
- Make it harder to have good git workflow.
- Slows down ability to continuously integrate code.
Your milage may vary depending on how you have your BASH configured.
- control + r == reverse search
- history
- man + / for search
- fn + leftArrow || fn + rightArrow key for front or end of line
alias e=subl
alias be="bundle exec"
alias g=git
alias cl=clear
alias ga="git ca"
alias gpo="git push origin"
alias gph="git push heroku"
alias db:reset="be rake db:drop && be rake db:create && be rake db:migrate && be rake db:test:prepare && be rake db:seed && rails c"
alias rials="rails"
alias gti="git"
alias shitgun="shotgun"
alias shotfun="shotgun"
alias dbc="cd ~/Dropbox/ACODE/DBC/dayJerbs"
alias code="cd ~/Dropbox/ACODE/adBC[core]
# Excludesfiles allows us to set a global list of things to ignore
excludesfile = ~/.gitignore_global
# These are custom color options for the console
[color]
status = auto
diff = auto
[color "status"]
untracked = cyan
changed = green
added = yellow
# Aliases are command shortcuts
[alias]
# lg is now a shortcut for a pretty log with short commit messages
# See the log manpage: https://www.kernel.org/pub/software/scm/git/docs/git-log.html
# for explanations of what these options do
lg = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative
# Shorthand for a less noisy status
s = commit --dry-run --short
# More sensible names for adding and removing files from the readme
stage = add
unstage = reset HEAD
# Edit the last commit
amend= commit --verbose --amend
# one-line log
l = log --pretty=format:"%C(yellow)%h\\ %ad%Cred%d\\ %Creset%s%Cblue\\ [%cn]" --decorate --date=short
a = add
ap = add -p
c = commit --verbose
ca = commit -a --verbose
cm = commit -m
cam = commit -a -m
m = commit --amend --verbose
d = diff
ds = diff --stat
dc = diff --cached
co = checkout
cob = checkout -b
# list branches sorted by last modified
b = "!git for-each-ref --sort='-authordate' --format='%(authordate)%09%(objectname:short)%09%(refname)' refs/heads | sed -e 's-refs/heads/--'"
# list aliases
la = "!git config -l | grep alias"
[user]
email = bootcoder@gmail.com
name = BootCoder
[credential]
helper = cache --timeout=14400