Fabric
– add plugin to tons of third party services

Crashlytics
– 18 billion crashers per month
– used on 1.3 billlion android devices
– non fatal iOS error loggings
– support for unity
– tvOS support

answers
– show you live the events on you app
– 198 billion sessions per month
– support OS X and tvOS
– launch day experience: show summaries such as “successful release”, “low adoption”, etc

digits
– phone number verification
– find friends using phone numbers
– use email verification to switch from email login to phone login
tvOS support
– voice fallback; if after a minute the sms did not go through, send a voice call

mopub
– ad exchange
– can add custom ads from your partners
– video ads

twitter kit
– add native video

twitter
– 1 billion unique visitors
– 40% smaller js library
– curator.twitter.com: collect tweets by topic or user;
— curated collections have an id, which you can embed in any page to show the curated results

gnip
– twitter data
– see want people think of you product or related products
– Harvard used twitter data to track tweets about food poisoning to see places that make people sick
– each tweet has 65 fields; lots of data about the users

public search vs gnip
– gnip has better searches and filters
– gnip has replay to search streams back in time
– gnip searches all tweets back to 2006
– search every public as it is created

audience api
– pull statistics about a group of user ids. minimum of 10,000 ids
– can summarize interests, gender, etc of users

==

travel app powered by fabric and gnip

– list ten most tweeted attractions in a city
– show images and tweets about attractions
– show graphs of tweets per day

==

Ticketmaster

GA crash metrics were delayed several days
Twitter crashlytics can report crash within minutes

Ticketmaster mobile apps crash less than web apps during big on sale events because of the detailed crash data

disable new, buggy, slow features during large on sale events to reduce the number of crashes

use analytics to give dev team a score board
– add tracking to features so devs can know how users are using features they made

currently 57% success, 43% failure when users login;
– login failures are critical during large onsale events
– ticketmaster will simplify the log in process

Rollout new features to a select number of users
– use crash data to catch bugs before wide release
– use launch day experience data to make any adjustsments before wide release

– create by a consultancy for rapid development
– devs moved from Sails.js to Trails.js because Sails.js development has slowed down. e.g No plans to upgrade to Express 4.
– Trials is built with ES6

– 1.0 beta is not ready for production
– production-ready 1.0 will be release in April

– currently supports express and hapi as the server, and waterline as the ORM. There is planned support for koa, bookshelf, and sequelize.
– core of Trails is pretty basic. It’s up to users to add Trailspacks for additional features such as servers and ORM.
– When you create a model, Trails automatically sets up the GET, POST, etc endpoint
– when you want to change a model, edit the schema, and restart the server. The db will be updated.

– speaker: Dave Moore

8th Light
– consulting firm from Chicago
– just started L.A. office. About 10 people.

SCNA – usually in Chicago
– first time in L.A.

craftsmanship – do something really well

many people are entering dev world
– they don’t have formal training
– apprenticeship helps train people

deadline vs craftsmanship
– when you jump into existing codebase, how do can you be practice craftsman?
– clients and bosses don’t know what is possible
– up to devs to tell them what is possible in order to make quality code
– it’s ok to cut scope in order to achieve quality code

Why L.A. for the conference?
– Santa Monica have lots of startups; some are craftsman, some want to play with new toys to build cool stuff
– OC is more enterprise
– Downtown mix of startups and enterprise, plus government contracts
– there isn’t strong software craftsmanship in LA

About the conference
– organizers handpicked the speakers who have good reputation
– must-see speakers include Uncle Bob, Gary Bernhardt “destroy all software”,

The Analytics Edge Mar 3, 12 weeks, MIT

Through inspiring examples and stories, discover the power of data and use analytics to provide an edge to your career and your life.

Programming for Everybody (Python) Feb 2 – Apr 28, University of Michigan

This course aims to teach everyone to learn the basics of programming computers using Python.

An Introduction to Interactive Programming in Python Feb 13 – Mar 20, Rice

This two-part course is designed to be a fun introduction to the basics of programming in Python.

Data Visualization and Infographics with D3.js Mar 16 – Apr 26, University of Texas

This course consists of an in-depth discussion about the principles of info graphics and data visualization, and how they apply to the real world.

Go Places with Spatial Analysis Mar 4 – April 15, Esri

This Massive Open Online Course (MOOC) is for people who know something about data analysis and want to learn about the special capabilities of spatial data analysis.

But more importantly, this was the first time I participated in a hackathon with a team. In our team of seven people, only two of us knew each other before the hackathon; the rest were total strangers. It was really cool two watch a group of strangers–each with a different skill set and skill level–come together, and contribute what they could in order to finish the app.

Even though I’ve been coding in javascript for less than a year, I was the senior programmer on the team. One of the programmers was half-way through a bootcamp, and the other team member dropped out of a bootcamp and was learning on his own. It was kinda neat being able to share what I knew with others.

As always, one of the biggest challenges when dealing with analyzing data is finding a suitable data set. After looking at beer, exoplanets, and artwork, I decided to use the menus from New York Public Library’s menu collection.

After working with sql, MongoDB, and Neo4j, I think cypher is my favorite querying language. Maybe it’s my visual background showing through, but I think it’s so freakin’ cool that the cypher query language is made of nodes and arrows.

Data is fun!

I made a simple CSS3 Animation as my first Code Pen. Who knew that dots and lines could be so difficult…and so much fun.

Suggestion 1: ‘this’

Some online posts suggest using ‘this’ to access a global variable when there’s a local variable with the same name.

var a = 'global context';

function test() {
  var a = 'local context';

  console.log('local a: ', a);
  console.log('this a: ', this.a);
}

test();

// local a:  local context
// this a:  global context

‘this.a’ accesses the global variable, ‘a’ accesses the local variable. That’s exactly what we wanted. Everything is great, right?

Nope!

There are multiple ways to invoke a function in Javascript. The most common way is just to call the function, e.g. test(). Another way to invoke a function is with call or apply. When we use call or apply, we can pass in an object.

Look what happens when we invoke test using call.

var a = 'global context';

function test() {
  var a = 'local context';

  console.log('local a: ', a);
  console.log('this a: ', this.a);
}

 var testObject = {
   a: 'object context'
 }

test.call(testObject);

// local a:  local context
// this a:  object context

Unlike the first example, ‘this.a’ now refers the object context instead of the global context.

Why?!

For test(), ‘this.a’ returns ‘global context’. When a function is invoked by itself, ‘this’ refers to the global context.

For test.call(object), ‘this.a’ returns ‘object context’. When a function is invoked with call, ‘this’ refers to the context of the object that is passed in.

A third way to invoke a function is a method call.

var a = 'global context';

 var testObject = {
   a: 'object context',
   test: function() { 
        var a = 'local context';

        console.log('local a:', a)
        console.log('this.a:', this.a)
      }
 }

testObject.test();

// local a: local context 
// this.a: object context 

For testObject.test(), ‘this.a’ returns ‘object context’. When a function is invoked as a method of an object, ‘this’ refers to the object that the method belongs to.

We are using the exact same code for the test function, but depending on how test is invoked, ‘this.a’ can refer to either the global context or the object context.

Please don’t use ‘this’ to refer to a global variable inside a function.

Suggestion 2: window

Some online posts suggest using ‘window’ to access a global variable when there’s a local variable with the same name.

var a = 'global context';

function test() {
  var a = 'local context';

  console.log('local a: ', a);
  console.log('window a: ', window.a);
}

test();

// local a:  local context
// window a:  global context

‘window.a’ accesses the global variable, ‘a’ accesses the local variable. That’s exactly what we wanted. Everything is great, right?

Again, nope!

window.a works if you run the function in the browser, but what if you run the function in an environment that doesn’t have a browser?

// runs code on Node server

var a = 'global context';

function test() {
  var a = 'local context';

  console.log('local a: ', a);
  console.log('window a: ', window.a);
}

test();

// local a:  local context
// ReferenceError: window is not defined

Node server doesn’t have a window, so you end up with an error when you use ‘window.a’.

Please don’t use ‘window’ to refer to a global variable inside a function.

Conclusion

So back to the original question: how do we refer to a global variable from inside a function when the function has a local variable with the same name as the global variable?

Simple recommendation: Don’t do it!

Because there are multiple ways to invoke functions (test(), test.call(), testObject.test()) and multiple environments to run Javascript (browser, server, etc.), there is no consistent way to refer to the global variable when there is local variable with the same name.

If you need to refer to the global variable, then don’t redeclare the variable inside the function. Give the variable inside the function a different name.

var a = 'global context';

function test() {
  var b = 'local context';

  console.log('a: ', a);
  console.log('b: ', b);
}

test();

//  a:  global context
//  b:  local context

That’s a whole lot of words for a simple ‘no’ answer. I hope this post either clears things up about how Javascript works or makes you more confused about how Javascript works.

I ain’t gonna lie. One of the reason’s why I anxious to get a job is so that I can narrow down the scope and figure what to learn next.

languages

1. Python
2. Ruby
3. Swift/iOS

things I want to try

4. 3d printing
5. accessiblity
6. book – seven databases in seven weeks
7. Bootstrap
8. CSS preprocessor – SASS, LESS, or Stylus
9. data science
10. Docker
11. Ember
12. Internet of things using JavaScript
13. Ionic/Phone gap
14. Leap Motion using javascript
15. machine learning
16. Meteor
17. new HTML5 elements – video, audio, canvas, geolocation
18. postgres
19. React.js
20. Redis
21. reponsive design
22. SVG
23. web components
24. WebGL/Three.js
25. WebRTC

things I’ve tried and want to dig deeper

26. Chrome extensions
27. css3 animations
28. D3
29. MongoDB
30. Neo4j

online courses -tech

31. algorithm intro
32. computer science intro
33. data science intro

online classes – fun

34. biology
35. calculus
36. chemistry
37. neuroscience
38. physics
39. quantum physics

other

40. Alfred’s Teach Yourself Piano
41. Richard Feymann’s Lectures on Physics
42. so many science/math related books that I want to read

Oh boy, was I wrong about that.

While to most people, MVP means aiming to be the best, in the coding world MVP means aiming for the minimum, as in minimum viable product.

Instead of aiming for fully functional, awesome code every single time, you should aim for a functional, simple code and keep iterating on the code until it become awesome.

Advantages of the MVP, iterative approach

1) You have working code at every step of the process. The in-progress code of might not have all the fancy doodads as the final code, but at least you have working code that will get you to where you want to be.

2) You can work on multiple simple things at the same time instead of working on one big thing. If you only work on one big thing, you have no idea if the various parts will work together. if you work on multiple small things at the same time, you can test to see how the various parts will interact with each other.

3) By aiming small, if you discover that something doesn’t work, you can throw out that small chunk of code and quickly try something else. It’s a lot less stressful to walk away from a small chunk of code than to walk away from a mountain of code that you spend tons of times on.

In conclusion, by doing less at each step, you end up being able to do more.