1. Holy shit I’m doing it! #arduino

    Holy shit I’m doing it! #arduino

    2 days ago  /  0 notes

  2. I will get you He-Man!!!!! Mreaaaaa!!!!

    I will get you He-Man!!!!! Mreaaaaa!!!!

    1 week ago  /  0 notes

  3. Whether you think you can, or you think you can’t—you’re right.
    – Henry Ford

    3 weeks ago  /  0 notes

  4. You have to know how to finish.
    – My Dad

    3 weeks ago  /  0 notes

  5. The Sound of My Crazy Thoughts

    Sometimes, I have crazy ideas… Today, my crazy idea is, if I had a soundtrack, what would it be?

    Let’s say, if there were a video montage of my life, or a certain moment I was recapping during a video playback, what would the music be capturing that moment?

    So, I imagine myself on a stage, presenting another crazy idea, a huge keynote showcasing something fricking amazing, blowing peoples minds left and right as if I were Jonathan Ive from Apple but with not as cool of an accent. Everything goes into slow motion and I drop the best explosion of an idea and people’s heads are exploding with how awesome their eyes were shredded with the beauty in front of them.

    If that moment happened, this would be my soundtrack:

    How The Universe Works Soundtrack

    Why?

    1. I love the universe, the Science Channel and this show!
    2. It’s epic and sounds great when highlighting mind blowing things in slow motion.
    3. Because awesome!

    What is your soundtrack?

    1 month ago  /  0 notes

  6. How To: Heroku Custom Domains using GoDaddy and PointDNS Nameservers

    This post is to help those who are trying to point a custom domain from GoDaddy to Heroku, showing you how to update your CNAME, your Nameservers, and installing a DNS manager on Heroku.

    The best part about doing this, it is all free!

    1) Log into GoDaddy.

    2) Get to your list of domains from the nav bar “Domains -> Manage Domains”

    3) Click the arrow next to the domain you want to update and select, “Manage DNS”

    4) Under CNAME, edit your “www” host. (if you do not have a CNAME yet, create a new CNAME)

    5) A pop up should appear, fill in your host as www, your points to as your Heroku app url, “(your app).heroku.com”, and set your TTL to 1/2 hour.

    6) In your Heroku app, install “Point DNS.”

    7) Add your custom domains to Heroku.

    9) Get your Nameservers from PointHQ.

    10) Go back to GoDaddy to your “Manage my domains” page and this time, choose “Set Nameservers” under the arrow drop down next to your domain name.

    11) A pop up should appear where you need to enter your Nameservers, enter the ones you got from PointHQ as Custom Nameservers.

     

    That is it. Now just set it and forget it for about 24 hours, check your site and you should be all set.

    Thanks for reading.

    1 month ago  /  0 notes

  7. Do All Things With Love.

    My wife inscribed this on a present for me shortly before we married and to this day, they are the words I live by.

    There is no sense doing anything unless you love it. Even if you don’t love something, find something you love about it.

    5 months ago  /  0 notes

  8. I’m trying a new #API design practice… dunno what it’s officially called

    So I am trying this new API design concept. I know it has been done before but I do not know if it has an official name.

    I need your help!

    When you read this and you recognize it and know the name, let me know because I want to learn what it is really called. For now, I am going to call it, Front-End First API Design Pattern, or FEFADP for short… yea, we need a better name.

    What do I usually do when I am building an API?

    Usually, when I design an API, I am inside the guts of the API, vetting out all the details of what the API parts will be. I define the data each endpoint receives and the data each endpoint returns. I work through a lot of the error handling scenarios, figuring out which HTTP response codes to be used and what type of error messages to return.

    After I have all of that figured out, I usually build a part of the app around that endpoint. Sometimes, I leave out the error handling until later but regardless, it is similar to that flow.

    What am I trying this time when building an API?

    This time, I created a bunch of endpoints I know I will need. These endpoints don’t do much, they only return mock data. They also do not do anything to the data passed to each endpoint.

    var mock_section = {

      content: ‘__Some content__’,

      markup: ‘<p><strong>Some content</strong></p>’,

      _id: 1

    };

    .get(‘^/sections$’, function(handle) {

      env.response.statusCode = 200;

      env.response.body = [mock_section, mock_section];

      next(env)

    })

    .get(‘^/sections/:id$’, function(handle) {

      env.response.statusCode = 200;

      env.response.body = mock_section;

      next(env)

    })

    The way I am designing the API is directly from the implementation of the application I am building. I am literally building the client experience where I am implementing services within my app to hit these endpoints and modifying the mock data returned to what I need in the application. I am also adding new endpoints as I hit certain places within the app… ex. After I create a new section, I will need to edit that section. So I create an edit endpoint for that user experience.

    How is this helping me?

    It is allowing me to rapidly change the API design without a ton of time invested in developing it at first.

    It helps me figure out what I need and how I will use it because I do not have everything figured out from the beginning. This has allowed my app development to be more flexible instead of working inside a rigid API which already exists.

    Doing it this way also helps me find ways to optimize accessing data within the API so that I do not create odd scenarios where I would need to jump through hoops before hitting a specific endpoint.

    What is next?

    My goal is to develop the entire app following this design pattern, helping me shape what my API should look and act like. Instead of me guessing which endpoints I will need before building an app, I will know exactly what I need in my API because the app literally defined what is needed. From this, I will build the actual API which receives and returns for-realz data.

    Boomski!

    I will give an update in a bit about how this is going and I am curious on your thoughts.

    Have you tried this before? If so, how did it go?

    That is all,

    Cal - out

    5 months ago  /  0 notes

  9. #apis and My Love for Them

    It’s official, I am obsessed with APIs!

    Every idea I have about an application and how I would solve a problem goes directly to APIs and how I would design them and how it would be consumed. 

    I think in APIs.

    I dream in APIs.

    I plan in APIs.

    There is just something about them which tickles my fancy.

    NOUNS, VERBS, REST… Ohhh yea, that’s how I talk to you!

    HTTP response codes… uh huh, tell me what happened!

    Authentication headers… oh how you give me access.

    That is all.

    Cal - Out!

    5 months ago  /  0 notes

  10. #DartCodeLabs #AngularDart Complete!

    I just finished the #DartCodeLab #AngularDart tutorial! 

    https://github.com/angular/ng-darrrt-codelab

    Man, is it different than what I am used to with #AngularJS. It is a very different style of programming than I am used to but I would not say it is bad, just different. I am intrigued with how #Dart handles things like types, packages, inheritance, dependency injection and some how it meshes with AngularJS.

    I am planning on recreating a version of http://toflexornottoflex.com using dart to consume the API, building AngularJS services and seeing where it goes.

    Thanks #DartCodeLabs for the tutorial, I sure learned a lot!

    Cal - Out

    5 months ago  /  0 notes