I hereby claim:
- I am aniketpant on github.
- I am aniketpant (https://keybase.io/aniketpant) on keybase.
- I have a public key whose fingerprint is 2F57 2455 ECDD FD7D A4C0 1146 474B 065D 2C94 E490
To claim this, I am signing this object:
# generate a lowercase UUID | |
uuidgen | tr '[:upper:]' '[:lower:]' | |
# generate a random number between min and max | |
awk -v min=7000000000 -v max=9000000000 'BEGIN{srand(); print int(min+rand()*(max-min+1))}' | |
# copy to pasteboard after trimming endline | |
tr -d '\n' | pbcopy |
scutil --set ComputerName "Tekina" | |
scutil --set HostName "Tekina" | |
scutil --set LocalHostName "Aniket" |
#!/bin/bash | |
usage() { | |
cat << EOF | |
Usage: $0 [OPTION]... COMMAND | |
Execute the given command in a way that works safely with cron. This should | |
typically be used inside of a cron job definition like so: | |
* * * * * $(which "$0") [OPTION]... COMMAND | |
Arguments: |
I hereby claim:
To claim this, I am signing this object:
# Hello, and welcome to makefile basics. | |
# | |
# You will learn why `make` is so great, and why, despite its "weird" syntax, | |
# it is actually a highly expressive, efficient, and powerful way to build | |
# programs. | |
# | |
# Once you're done here, go to | |
# http://www.gnu.org/software/make/manual/make.html | |
# to learn SOOOO much more. |
package main | |
import ( | |
"encoding/json" | |
"fmt" | |
"io/ioutil" | |
"log" | |
"net/http" | |
) |
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
<html> | |
<head> | |
<title>Select styles with CSS only</title> | |
<meta name="viewport" content="width=device-width, initial-scale=1"> | |
<style> | |
body { | |
background-color: #fff; | |
font-family: helvetica, sans-serif; | |
margin: 4% 10% | |
} |
#!/bin/sh | |
# Some things taken from here | |
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
# Set the colours you can use | |
black='\033[0;30m' | |
white='\033[0;37m' | |
red='\033[0;31m' | |
green='\033[0;32m' |
// ---- | |
// Sass (v3.3.9) | |
// Compass (v1.0.0.alpha.20) | |
// ---- | |
$baseColor: #FFCC00; | |
@for $i from 1 to 5 { | |
#mainbody :nth-child(#{$i}) { | |
border-color: adjust-color($baseColor, $green: ($i - 1) * 1); |