Steve Calla (he/him) stevecalla

Objective: Document data types knowledge using Markdown

When you've worked towards a goal in the past, what systems or tools have been helpful for you in accomplishing that goal? How could you adapt those same systems/tools to use while at Turing?
- Steve Calla - I use a variety of systems and/or tools depending on the end objective. Whether in a team or individual environment, my first objective is to understand the goal with as much clarity as possible. Secondarly, I attempt to understand the timeline and key deliverables. Subject to that macro level information/overview, I break down the goal into smaller pieces again either in a team or individual environment then I create tasks necessary to complete each piece or section. I typically attempt to complete the goal ahead of schedule to allow for review and improvement if possible as I providing for some space to re-think or review allows for improvement or the ability to exceed the goal.
As you start this new career, what is one of your strengths and how do

Mod 1 Week 1: Understanding your strengths (status = COMPLETE)

Answer the below questions in a separate gist and link them into your career journal using this template:

Week 1: [Link here to your gist]

Week 1: [Link here to your gist]

If you will not be able to complete your journal this week, please provide an update for the Career Dev team on when you'll have it completed here:

Week 2: [Link here to your gist]

Week 1: [Link here to your gist]

If you will not be able to complete your journal this week, please provide an update for the Career Dev team on when you'll have it completed here:

Week 2: [Link here to your gist]

Note: Mod 4 Prompts will be provided to you by your Career Specialist at that time.

Week 1: [Link here to your gist]

If you will not be able to complete your journal this week, please provide an update for the Career Dev team on when you'll have it completed here:

	// Port, host and auth token of Redis server might be defined as environment
	// variables. If not, fall back to defaults.
	var redisPort = process.env.REDIS_PORT \|\| 6379,
	redisHost = process.env.REDIS_HOST \|\| '127.0.0.1',
	redisAuth = process.env.REDIS_AUTH \|\| null,
	redis = require('redis');

	// Since we are waiting for the error event, we don't have to check for errors
	// individually after each Redis command.
	var onError = function (error) {