marlomajor

How to Start a Medical Startup

My Story

• GluCase
• Accelerator
• Funding Process

Why should I Start a Medical Startup?

• My experience with health tech and humans
• Health remains one of the more unfulfilled tech spaces in the world

marlomajor

ROUGH DRAFT YUHHHHHHH

## Write User Stories like a 12 year old

#### My Story
* Twitter With Brother

#### What makes a 12 year old better than current developers at writing user stories?
* Talk about how many users on net are around 12
* Write a user story like a user by going to a website similar to yours etc

marlomajor

Array Prototype Methods

I understand that functions in JavaScript can take any number of arguments.

True

I can describe the similarity between blocks in Ruby and anonymous functions in JavaScript.

True

marlomajor

Throughout the module (and your journey to Google enlightenment while working on IdeaBox2.0) you may notice a few different ways that JavaScript code is being written.

That might have something to do with something called ES6 and ES5

Fork this gist and answer the following questions:

• What is ES6? -ECMAScript 6, is also known as ECMAScript 2015 and is the new standard for ES. It is the first major update since 2009 with ES5. Several major changes have been made to the language, including, but not limited to the following: -Arrows - functional shorthand using =>. Share the same this as the surrounding code. -Class - single declarative form allowing for more interoperability -Enhanced Object Literals - I do not know what this means.

marlomajor

##Leap My code: here

• Responder #1 (here) - This approach is significantly more simple than mine. The creater uses a one line function that includes an or/and operator and returns true.
• Responder #2 (here) - This programmer assigns an anonymous function to a variable. Afterwards, she uses an if/elseif/else statement to check for each occurence.
• Responder #3 (here) - This programmer also used an if else statement to accomplish the same task. Main difference is that the first statement is a check to make sure the year is divisible by 4. The nested if statement then checks for the other functionality.
• Responder #4 (here) - This programmer uses one if statement to check for di

marlomajor

Summary

Sandi Metz rules were all interesting and clearly demonstrated that simple is usually better. The rules were that classes should have no more than 100 LOC, methods should have no more than 5LOC (including if/else statements), a controller should instantiat only one method, and that methods should have no more than four parameters passed into the method.

Hardest Rules to Follow

The hardest of Sandi's rules to follow will be keeping methods to <= 5 LOC and instantiating only one object in a controller. My methods are typically not refactored well and extremely long, simply because I'm trying to get my thoughts on the page and rarely have time to refactor. Concerning the one object controller, its just not something I'm used to doing. But getting used to instantiating only one object feels as though its something I can eventually get used to. The hardest rule for Thoughtbot to follow (the only rule they ended up reverting to "Rule 0" for was the four method arguments rule. In rail, form_for and li

marlomajor

Which sections were interesting?

I love the chapter on Functions. I ended up taking copious notes on this chapter. It has helped to clarify a ton of misconceptions to me

Which sections did you totally skim?

I only skimmed the end of Functions, I think it was titled "Named Parameters" as I didn't think that I could relate to it much. I still took notes on this part however, I will come back to it I'm sure.

Do you think the reading was valuable?

This reading is helping me to Speak Javascript...literally. It is super valuable. But probably only after having built several JS projects. To newcomers to module four, I can see how it would be less valuable, as they probably don't have much context

Which topics were notably confusing?

marlomajor

What is something you learned that was particularly suprising/interesting?

I've used many of the topics covered in this tutorial already, but didn't realize the impact they had for the JS language. For example, being able to change an objects properties at any time was interesting.

What was something you already knew?

Pretty much the beginning of this tutorial was all review, especially after reading Speaking Javascripts chapters first.

Was there anything you feel as though you still don't understand?

This is a comment made in class and I've seen this at a meetup. But what's the difference between getter and setters? Also, what is addBack used for?

marlomajor

JavaScript Functions

I can explain the difference between function declarations and function expressions.

• YES. Pretty pumped about knowing the difference also. Fixed a huge problem in my Gametime project because I was using a function expression when I should have been using a declaration.

I can explain what the value of this is in a normal function.

• Yes.

I can explain what the value of this is when called from the context of an object.

• Yes.

marlomajor

**Step One**: Watch [Sorting Algorithms in JavaScript](https://www.youtube.com/watch?v=uRyqlhjXYQI)

**Step Two**: Fork this gist.

**Step Three**: Respond to this question in your fork: "What are some of the balances and trade offs between different sorting algoritms?"

The question of which sorting algorithm should be used versus another depends on the goal of the project one is trying to solve. Our main concern with sorting algorithms are with how long it takes to complete the algorithm and also how much memory the algorithm uses. Bubble sort is a simple sorting algorithm, often used for teaching first lessons on algorithms. It's easy to understand as a visual, simple to pseudocode for a beginner, but slow in actual processing and low on the memory usage. So just in this one case alone, the positives for bubble sort are that it's simple to learn and uses little memory, but also requires a lot of time to run. Depending on the goal, the balances and trade offs one makes on sorting algorithms is dependent on