- 1Password: Password Manager and Secure Wallet : 1Password extension for Google Chrome
- 45to75 : Character counter for helping to optimize line length (measure) between 45 and 75 characters.
- Apollo Client Developer Tools : GraphQL debugging tools for Apollo Client in the Chrome developer console.
- aXe : Accessibility testing in Chrome Developer Tools
- BuiltWith Technology Profiler : Find out what the website you are visiting is built with using this extension.
- ColorZilla : *Advanced Eyedropper, Color Picker, Gradient Generator
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
-
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the
secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection. -
Use production SSL certificates locally. This is annoying
There are a few JQL syntax bits to get you started:
AND
--- allows you to add qualifiers to a list!= Thing
--- target one thingis in (List, Of, Things)
--- target a bunch of things (Done, Closed, Resolved) typicallynot in (List, of, Things)
--- do not include a bunch of things-1w
--- relative time. You can also use -1d for day"2015/3/15"
--- specific dates
module.exports = { | |
config: { | |
// default font size in pixels for all tabs | |
fontSize: 12.5, | |
// font family with optional fallbacks | |
fontFamily: '"Meslo LG S for Powerline", Menlo, "DejaVu Sans Mono", "Lucida Console", monospace', | |
// terminal cursor background color (hex) | |
cursorColor: 'rgba(255,255,255,.4)', |
Hi, I'm Lorna and I don't use a mouse. I have had RSI issues since a bad workstation setup at work in 2006. I've tried a number of extra hardware modifications but what works best for me is to use the keyboard and only the keyboard, so I'm in a good position and never reaching for anything else (except my coffee cup!). I rather unwisely took a job which required me to use a mac (I've been a linux user until now and also had the ability to choose my tools carefully) so here is my cheatsheet of the apps, tricks and keyboard shortcuts I'm using, mostly for my own reference. Since keyboard-only use is also great for productivity, you may also find some of these ideas useful, in which case at least something good has come of this :)
There's more detail on a few of these apps but here is a quick overview of the tools I've installed and found helpful
Tool | Link | Comments |
---|
It's a common confusion about terminal colours... Actually we have this:
- plain ascii
- ansi escape codes (16 colour codes with bold/italic and background)
- 256 colour palette (216 colours + 16 ansi + 24 gray) (colors are 24bit)
- 24bit true colour ("888" colours (aka 16 milion))
printf "\x1b[${bg};2;${red};${green};${blue}m\n"
#!/usr/bin/env bash | |
function lazygit() { | |
git add . | |
git commit -a -m "$1" | |
git push | |
} | |
function upgrade-nvm() { | |
( |
if &compatible | |
set nocompatible | |
end | |
call plug#begin('~/.vim/plugged') | |
Plug 'airblade/vim-gitgutter' | |
Plug 'altercation/vim-colors-solarized' | |
Plug 'andrewradev/splitjoin.vim' | |
Plug 'ap/vim-css-color' |
#!/bin/bash | |
# Install the Build and Test Dependencies | |
apt-get update | |
apt-get install -y curl build-essential tcl | |
# Download and Extract the Source Code | |
cd /tmp | |
curl -O http://download.redis.io/redis-stable.tar.gz | |
tar xzvf redis-stable.tar.gz |
###Sketch trial non stop
Open hosts files:
$ open /private/etc/hosts
Edit the file adding:
127.0.0.1 backend.bohemiancoding.com
127.0.0.1 bohemiancoding.sketch.analytics.s3-website-us-east-1.amazonaws.com