Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
#!/bin/bash | |
open_database() { | |
DB_PATH=`lsof -Fn -p $PID| grep "\.sqlite$"` | |
open ${DB_PATH:1} | |
} | |
PID=`pgrep $1` | |
if [ -z "$1" ] |
Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
import React from 'react'; | |
import debounce from 'utils/debounce'; | |
class EmailInput extends React.Component { | |
checkEmail = value => { | |
// only check if the field passes Yup email validation first | |
if ( | |
!this.props.form.errors[this.props.name].includes( | |
'invalid' /* or whatever your error message is*/ | |
) |
module Auth0 | |
( AuthenticationState(..), AuthenticationError, AuthenticationResult | |
, Options, defaultOpts | |
, LoggedInUser, UserProfile, Token | |
, showLock, showLockSignal | |
, mapResult | |
) where |
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE Version 2, December 2004 | |
(http://www.wtfpl.net/about/) | |
Copyright (C) 2015 Mario Mendes (@hyprstack) | |
Copyright (C) 2015 Ivan Fraixedes (https://ivan.fraixed.es) | |
Everyone is permitted to copy and distribute verbatim or modified | |
copies of this license document, and changing it is allowed as long | |
as the name is changed. |
Hello there fine madam or sir!
I have a short quiz for you. It won't take long.
By the way, don't worry if there are questions you can't answer. Lots of people will be struggling along with you, so don't feel bad. You're not alone.
Let's begin!
Do you recognize the method for which this is the (simplified) source?
# Download desktop-resolution wallpapers from http://psiupuxa.com/ | |
# into the current directory. | |
require 'nokogiri' | |
require 'open-uri' | |
require 'openssl' | |
require 'uri' | |
# Disable SSL verification. Ruby SSL cert bundle isn't installed on Windows by default. | |
OpenSSL::SSL::VERIFY_PEER = OpenSSL::SSL::VERIFY_NONE |
Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118
Your problem with Vim is that you don't grok vi.
You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).
The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:
0 go to the beginning of this line. y yank from here (up to where?)