Excited to announce that I’ve been invited to be a panelist on the Front End Happy Hour podcast 🎉! I’m humbled & honored because the other panelists are people that I look up to this industry. Can’t wait to explore all things front-end this year on the show.
I was invited to be a guest on the Front End Happy Hour podcast to sip some fancy drinks & talk about Ember.js with a panel of smart people/friends. It was my first time being on a podcast and it was a ton of fun. Check it out & subscribe in your favorite podcatcher.
I was fortunate again this year to be selected as a speaker for dev.Objective() conference in Minneapolis, MN.
A few months after I started working with Ember.js & Ember Data at my new job last June we began a project to upgrade both. There were parts that were a breeze and others that were quite tricky. This talk walks you through some of the challenges we faced and how we solved them as well as how we began to prepare for the Ember 2.x architectural shift. Hopefully this talk will help save you some time when you decide to upgrade your Ember web application.
Here are my slides:
I also gave this talk recently at Milwaukee JS, a meetup I help co-organize.
Here is a video of that talk:
This is the first time in the history of me trying to get a domain name that I got exactly what I wanted :).
The Docker Toolbox assumes SSL (https) to connect to a registry. However, if the certificate is signed by an unknown authority it will fail with this error:
certificate signed by unknown authority. Putting my company’s internal certs in the cert store that Docker uses should fix this, however, many attempts to do so were unsuccessful. There just isn’t any clear documentation on how to do this for OS X (El Capitan v10.11.2) that I could find.
As a workaround you can specify that Docker should use an insecure registry with a flag. In an earlier version of Docker where Boot2Docker was used, I ended up finding I could run the following command to use an insecure registry (yes, I know this is dangerous but it’s an internal registry and not accessible to the outside world).
boot2docker ssh "echo $'EXTRA_ARGS=\"--insecure-registry myinternaldockerregistry.org\"' | sudo tee -a /var/lib/boot2docker/profile && sudo /etc/init.d/docker restart"
With updates to Docker for OS X this no longer worked. Again I couldn’t find any clear documentation on how to get certs to work with docker nor how to use an insecure registry. Finally I figured out that this works:
docker-machine ssh default "echo $'EXTRA_ARGS=\"--insecure-registry myinternaldockerregistry.org\"' | sudo tee -a /var/lib/boot2docker/profile && sudo /etc/init.d/docker restart"
Hope this helps someone else. If anyone knows how to get Docker to recognize internal certs please do share.
I was fortunate in May of 2015 to have been selected to give a talk at dev.Objective() conference in Minneapolis, MN. It was my first time speaking at a conference and it was a really positive one. Everyone was nice and supportive.
Here are my slides from the talk:
For one of the sites I work on, SiteCatalyst (Adobe Analytics) is used to gather metrics. This library needs to be included inside the
<body>. This was problematic when I wanted to use grunt-contrib-jasmine to run my Jasmine unit tests headlessly with PhantomJS & Grunt (aka from the command line) since by default it generates a spec runner with all referenced JS in the
That’s when I read about using Jasmine Templates. This seemed like the solution but the documentation and getting to a working solution wasn’t super straight forward.
AppMeasurement.min-x.x.x.js) and a non-minified version (
The trickiest part in all of this was remembering to put
./tests/ instead of
tests/ as the path to load the template module so it loaded from the current working directory.
Here is what my code ended up looking like:
This is a presentation I created for work in 2012 about HTML5. At the time it was being used as such a buzzword so I wanted to tell the story of the web and demonstrate why it matters and how it can be used to both a technical and non-technical audience.