# data[].attributes.body
An AR app using UnityARFoundation where you visualize parts on your car in AR. You're then able to capture and share screenshots of your modifications.

# data[].attributes.headline
Figure out how to do front-end testing in JS / Web Development

# data[].attributes.subject
Figure out how to do front-end testing in JS / Web Development

# data[].attributes.body
see: chai, jasmine...

# data[].attributes.body
With asynchronous execution :

# data[].attributes.body
http://www.datamuse.com/api/

http://rhymebrain.com/api.html

# data[].attributes.body
That'd be kinda helpful for front-end web dev

Think about it. The design guys that know the screen sizes by heart did this back when you actually needed to know the resolution of each screen. Nowadays there are things like ReactNative and others that facilitate that.

# data[].attributes.body
sites.google.com

# data[].attributes.body
javascript 3D rendering

# data[].attributes.body
https://web-design-weekly.com/2014/11/18/viewport-units-vw-vh-vmin-vmax/

# data[].attributes.body
https://css-tricks.com/viewport-sized-typography/

# data[].attributes.body
for handling dates and times in javascript

# data[].attributes.body
Use Firebase to replace GearHost

# data[].attributes.body
Ruby on Rails
Python

# data[].attributes.attachment_link.readable_text
Finding better boundaries

Let's revisit the 73-m elevation boundary proposed previously to see how we can improve upon our intuition.

Clearly, this requires a different perspective.

By transforming our visualization into a histogram, we can better see how frequently homes appear at each elevation.

While the highest home in New York is 73m, the majority of them seem to have far lower elevations.

Your first fork

A decision tree uses if-then statements to define patterns in data.

For example, if a home's elevation is above some number, then the home is probably in San Francisco.

In machine learning, these statements are called forks, and they split the data into two branches based on some value.

That value between the branches is called a split point. Homes to the left of that point get categorized in one way, while those to the right are categorized in another. A split point is the decision tree's version of a boundary.

Tradeoffs

Picking a split point has tradeoffs. Our initial split (~73 m) incorrectly classifies some San Francisco homes as New York ones.

Look at that large slice of green in the left pie chart, those are all the San Francisco homes that are misclassified. These are called false negatives.

However, a split point meant to capture every San Francisco home will include many New York homes as well. These are called false positives.

The best split

At the best split, the results of each branch should be as homogeneous (or pure) as possible. There are several mathematical methods you can choose between to calculate the best split.

As we see here, even the best split on a single feature does not fully separate the San Francisco homes from the New York ones.

Recursion

To add another split point, the algorithm repeats the process above on the subsets of data. This repetition is called recursion, and it is a concept that appears frequently in training models.

The histograms to the left show the distribution of each subset, repeated for each variable.

The best split will vary based which branch of the tree you are looking at.

For lower elevation homes, price per square foot is, at $1061 per sqft, is the best variable for the next if-then statement. For higher elevation homes, it is price, at $514,500

.

# data[].attributes.attachment_link.title
A visual introduction to machine learning

# data[].attributes.attachment_link.description
Let's revisit the 73-m elevation boundary proposed previously to see how we can improve upon our intuition. Clearly, this requires a different perspective. By transforming our visualization into a histogram, we can better see how frequently homes appear at each elevation.

# data[].attributes.body
this looks awesome...

# data[].attributes.attachment_link.title
Casetify Apple Watch Band (42mm) - DIGITAL WOODLAND CAMO by Ron Hardy

# data[].attributes.attachment_link.description
We're redefining a modern classic. We know things can get scuffed when you're constantly on the move, so we especially designed this saffiano leather Apple watch band and Apple watch strap for your active lifestyle. Perfectly fits all new Apple Watch Series 3, Apple Watch Series 2 and Apple Watch Series 1.

# data[].attributes.body
- Try to start out by hitting the api to capture data about your own photos and display that data graphically using something like google charts ui kit
(likes over time or something)

# data[].attributes.body
I'm now more aware of branching and stashing in git.

Commands to remember:
- git merge <branch>
- git checkout -b <branch>
- git stash
- git stash apply
- git stash list

# data[].attributes.body
Was looking at some stuff for Interfaces as a property on a class...but I get it:

You'd use an Interface as a property when you want that member to adhere to a contract. This property's getter can return any type that implements this contract. Allows for flexibility of types while ensuring the contract is followed.

# data[].attributes.body
a UI kit for quick web building (minimalistic web ui controls)

# data[].attributes.body
figure out how to practically use it as a web server

# data[].attributes.headline
Looking for a responsive website designer

# data[].attributes.subject
Looking for a responsive website designer

# data[].attributes.body
something like rocket cake but a little more developer friendly

# data[].attributes.body
C++ UI tool

-- Try to get back into C\C++  (lower level languages) using codeblocks and a C++ UI framework