iolloyd

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

iolloyd

class Foo:
  def __call__(self):
    print 'you called me'
    
caller = Foo()
caller()

iolloyd

<?php

$zipFile = $argv[1];
$newName = $argv[2];

if (!($zipFile && $newName)) {
   die('You need to specify a zip file to rename and a new filename');
}

$ext = pathinfo($zipFile, PATHINFO_EXTENSION);

iolloyd

One hour a week workout

These two workouts are brief, intense, not for people who enter bodybuilding physique competitions, nor for beginners or ponces that spend more time in the mirror posing with their 'mates'.

Along with a decent, sensible diet, these workouts will make you very big and very strong by most standards. I guarantee it.

Eat well, try to get your protein from normal food, not shakes, maybe augment some of your dishes with some protein powder if you struggle. Some recipe ideas

100% is your target weight. When you are able to hit the 100% set, you must increase the weight by as small amount as possible the next workout. If your gym does not have weights smaller than 2.5 kgs, go buy some. By adding small poundages each time, you can keep progressing without stagnating muuuuuuuuuuch longer.

iolloyd

Issues Management

Github issues are a great way to track ongoing changes in a project, but issues themselves are not meant to be a tool for project management. However, the only thing missing for a minimal means of doing so is the ability to prioritise tasks.

An effective way of doing so is to use a kanban approach by using swimming lanes to indicate the status of tasks and who is working on them.

It's important to know at any time what is being worked on, who is working on it, and what is next in the pipeline to be worked on. Github issues provides the ability to do this using labels and assignees.

A simple method to do this is to create labels for 'next', 'progress' and using pull requests when a task is complete. This is especially useful in smaller teams but can scale to bigger teams. It's usable in remote teams also and is hard to get wrong since there is no added complexity and negates the need to use something like huboard.

iolloyd

## GistList: TODO for coders

iolloyd

Keybase proof

I hereby claim:

• I am iolloyd on github.
• I am iolloyd (https://keybase.io/iolloyd) on keybase.
• I have a public key whose fingerprint is AD3D 3F1E 78E4 1B32 FFFB 85DB F7DE 45D9 01CF 2BF4

To claim this, I am signing this object:

iolloyd

git rev-list --all|tail -n1|xargs git show|grep -v diff|head -n1|cut -f1-3 -d' '

iolloyd

Example 1, the scheduled release.

In this example, we release every 2 weeks.

Regardless of how much work is done, we release at the 2 week marker.

If for some reason we arrive at a point where we have a lot of work before 2 weeks ready to go out, we can optionally do an early release.

Note: This is sometimes called scrumban.

iolloyd

1.7792   16655056  82. Model->__createLinks() /cake/libs/model/model.php:447
1.7792   16656680  83. Model->__constructLinkedModel() /cake/libs/model/model.php:638
1.7793   16657752  84. ClassRegistry->init() /cake/libs/model/model.php:666
1.7794   16668328  85. Model->__construct() /cake/libs/class_registry.php:140
1.7849   16726200  86. Model->__createLinks() /cake/libs/model/model.php:447
1.7853   16733688  87. Model->__constructLinkedModel() /cake/libs/model/model.php:638
1.7853   16734632  88. ClassRegistry->init() /cake/libs/model/model.php:666
1.7858   16922528  89. Model->__construct() /cake/libs/class_registry.php:140
1.7890   16932184  90. Model->__createLinks() /cake/libs/model/model.php:447
1.7891   16938600  91. Model->__constructLinkedModel() /cake/libs/model/model.php:638