Colourise old b/w photos with Machine Learning

And as such, for our hackathon in January, our team decided to build a deep learning colouriser tool trained specifically for old Singaporean photos.
An important note here: the point of colourisation is to generate an image with colours that are plausible. It by no means guarantees that the colourised image is an accurate representation of the actual snapshot in time.

awesome work, data.sg.gov

How my CliftonStrengths changed – 2017

For those unfamiliar with the Clifton StrengthsFinder book, it is the result of researching high-performing individuals to see what helped them succeed. I thought it was interesting that the researchers assumed there would be a set of common strengths among all the high performers. Instead, each high performer had their own combination of strengths and weaknesses. The Clifton researchers found those who focused and leaned on their strengths (and minimized their weaknesses) were successful.

I took the Clifton StrengthsQuest long ago and was surprised to find my strengths changed a lot between 2006 and now.

Long ago, I planned to be a pastor and thus inclusion and ‘WOO’ were strengths I used frequently. Now that I’m older, I’m more interested in developing and helping others develop.

Looking at my strengths, it is obvious why I keep asking my friends about their business ideas (input), brainstorming with them (ideation) and then telling them they can do it (activator) and seeing how I can help move it forward (maximizer). Also, I’m less positive than I was long ago- a bit jaded…but I believe in possibility and want to help others move toward it.

A listing of my CliftonStrengths a listing of my 2017 CliftonStrengths

Unloading autoenv based on a directory

AutoEnv is a killer tool that will automatically activate your virtualenv environment based on the directory you are in (based on the contents of a .env file). But what happens when you move out of that directory? Unfortunately, the same environment stays activated until you land in a directory that contains a new .env file.

Simple workaround: place this .env somewhere high in your directory tree (possibly in the root)

if [ -n "$VIRTUAL_ENV" ] ; then
    deactivate
fi

I dropped the above .env file into my user’s root folder, changed directories above my current directory and my virtualenv environment quickly changed. Thanks to kazagistar who suggested the fix!