David 'Epper' Marshall depperm

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

There are always 24 hours in a day.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).

This tutorial demonstrates how to use Google Apps Script to:

Create copies of the Google Sheet in the desired destination folder automatically at set intervals.
Append the time stamp with each backup file's name.
Adjust time trigger for backing up every day/hour/minute.

	function get(obj, path, def) {
	var fullPath = path
	.replace(/\[/g, '.')
	.replace(/]/g, '')
	.split('.')
	.filter(Boolean);

	return fullPath.every(everyFunc) ? obj : def;

	function everyFunc(step) {

	/**
	* K.jpg's OpenSimplex 2, smooth variant ("SuperSimplex")
	*
	* More language ports, as well as legacy 2014 OpenSimplex, can be found here:
	* https://github.com/KdotJPG/OpenSimplex2
	*/

	public class OpenSimplex2S {

	private static final long PRIME_X = 0x5205402B9270C86FL;

	So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

	Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

	* Off the top of my head *

	1. Fork their repo on Github
	2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

	git remote add my-fork [email protected]