Start of Bitmaker Journey

This week was exciting for a few reasons. I’ve been looking for a group of like minded people that I can work on projects with. Bitmaker offers that and so much more.

I thought this week was going to be mostly review but I’m starting to get more confident with the concepts I thought I already knew. There were some challenging assignments near the end of the week that provided a deeper understanding of Ruby and OOP. I also learned that “two heads are better then one” when I tried to build a Mars Class in Ruby. Right away the problem seemed too complex to do but once some friends and I started talking about it we were able to build it no time. Collaboration makes things easier and its fun. 

Also – free beers on Thursday….wooo

Are Coders Worth it?

This is an awesome article. “Web start-up companies are like play-companies. They stand in relation to real companies the way those cute little make-believe baking stations stand in relation to kitchens.” There are many shitty ideas being pursued by talented people and investment money going to ideas that “look good.” 

I think its necessary to know the tech side when starting a business but that’s only one part of the problem. Understanding who your customer is and what problem your solving are much more interesting then a a cool looking software platform. 

JavaScript Countdown Timer

My girlfriend and I are planning a trip to Montreal in a couple weeks and I’m out of town until then. I thought I would create this for her. In doing so I was able to practise using the Date() and Math() objects. The code is below,

 

var countdown = function () {

var future = new Date(2014, 4, 8, 13, 0, 0, 0);  //trip date
var now = new Date(); //time right now
var difference = future – now; 

var days = parseInt(difference / (86400000));
var hours = Math.floor((difference – (days * 86400000 ))/3600000);
var minutes = Math.floor((difference/1000 – (days * 86400 ) – (hours *3600 ))/60);
var secs = Math.floor((difference/1000 – (days * 86400 ) – (hours *3600 ) – (minutes*60)));

 

//add a zero is only one digit appears

if (days < 10) {
days = “0” + days;
}
if (hours < 10) {
hours = “0” + hours;
}
if (minutes < 10) {
minutes = “0” + minutes;
}
if (secs < 10) {
secs = “0” + secs;
}

document.getElementById(“timer”).firstChild.nodeValue = days + ” : ” + hours + ” : ” + minutes + ” : ” + secs; //used to display countdown on page

}

var playKiss = function() {
document.getElementById(“playsound”).play();
}

document.getElementById(“heart”).addEventListener(“click”, playKiss, false); // display when page loads

window.addEventListener(“load”, setInterval(countdown, 10), false);

 

The code can be cleaned up but it gets the job done. She liked it. 

Take Your Pick

Here’s something I whipped up the last couple of days. This is made up of three pages – make picks, location and profile page. The picks page using drag and drop HTML5 so you can pick a winner. When you choose a team some audio of fans cheering plays which I thought was pretty funny. There is also a form that lets you choose three players. Press update picks and this data is stored locally. You can view the picks by clicking on the view picks button which takes you to the profile page. 

The profile page is a dashboard showing various leaderboard and picks. i added some SVG and canvas elements for effect. 

The map page is used with Mapbox. I’m still getting used to the API but right now I have geolocation set up so the user can see their position on the map. When a user clicks of a pin information on that pin appears. I added some JS to the buttons on the left hand side. When you click on the buttons the corresponding sports games appear. After added overflow to this section you can scroll through the options. 

The idea behind this is that I’d like to see what bars are playing what games at any given time. Why doesn’t that exist yet?!

Learn Thinking and The Scientific Method

This is taken from the Lean Startup. In hard to understand some of the terms out of context but the jist is important. 

This is the pattern: poor quantitative results force us to declare failure and create the motivation, context, and space for more qualitative research. These investigations produce new ideas – new hypotheses – to be tested, leading to a possible pivot. Each pivot unlocks new opportunities for further experimentation, and the cycle repeats. Each time we repeat this simple rhythm: establish the baseline, turn the engine, and make a decision to pivot or persevere. 

 

Hypotheses – Create Test – Experiment – Collect/Analyze Data – Rinse and Repeat