See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
import "./formik-demo.css";
import React from "react";
import { render } from "react-dom";
import { Formik, Field } from "formik";
import Yup from "yup";
import classNames from "classnames";
// Input feedback
FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.
Picking the right architecture = Picking the right battles + Managing trade-offs
brew cask install \ | |
caskroom/fonts/font-3270-nerd-font \ | |
caskroom/fonts/font-3270-nerd-font-mono \ | |
caskroom/fonts/font-abel \ | |
caskroom/fonts/font-aboriginal-sans \ | |
caskroom/fonts/font-abril-fatface \ | |
caskroom/fonts/font-acme \ | |
caskroom/fonts/font-allura \ | |
caskroom/fonts/font-anonymouspro-nerd-font \ | |
caskroom/fonts/font-anonymouspro-nerd-font-mono \ |
# Ignore all | |
* | |
# Unignore all with extensions | |
!*.* | |
# Unignore all dirs | |
!*/ | |
### Above combination will ignore all files without extension ### |
This gist is a fork of the gist from this blog post.
This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
using mocha/chai/sinon for node.js unit-tests? check out my utility: mocha-stirrer to easily reuse test components and mock require dependencies