(Before I begin, a quick note. The iTunes API will randomly throw CORS issues, most likely due to a misconfigured server in their network. To use this in production I’d add a serverless proxy. You may, or may not, run into this while testing.) When I present on Vue.js, one of the demos I show makes use of the iTunes Search API. It isn’t necessarily that exciting of a demo, and I don’t use iTunes very often, but the fact that it has interesting data and does not require a key of any sort makes it a good candidate for simple demos. I thought I’d quickly demonstrate this with Vue.js in the simplest form possible, and then work through some updates to improve the application.
This weekend I was on the road and had some time to build (yet another) application with Vue.js. I don’t think this one necessarily does anything terribly cool. At minimum it was more “exercise” for my Vue muscles and provides another demo I can share with folks. As always though, if you have any suggestions or feedback in general, just let me know. If posts like these aren’t helpful, also free free to share!
For a while now my go to service for hosting static sites “for fun” has been Surge. While I host my blog on Netlify and absolutely consider it the “gold standard” for static sites, I try to reserve my usage there for “real” sites, i.e. not things I’m playing around with or temporary examples. I had heard of Zeit of course and knew of their cool command line deployment, but outside of a few Node.js demos, I hadn’t really thought of it.
I decided to spend my lazy Sunday morning working on a quick Vue.js post. Geolocation is one of the older and simpler APIs you can use with your web browser so this article won’t necessarily be that exciting, but I thought a quick demo of the API with Vue, and a few variations, could be useful to folks. As a reminder, web pages that use Geolocation must be run on either localhost or an https server. This is a security precaution and… let’s be honest - there is zero reason to be using a non-secure server in 2019.
For the past year (ok, nearly a year), I’ve worked as a Developer Experience engineer at American Express. My work there had me interfacing with product owners to help them present the best developer experience possible. This involved everything from simple documentation improvements to helping work on tools to improve developer facing APIs. While I worked with some great people, the role wasn’t a great fit for me. Also, I’ve had some changes at home (good changes!) that will allow me to have a more public facing role, to spend more time on the road, and generally do what I love - help others.
I am incredibly opinionated about technical documentation. While my degree was in English, my focus in college was technical writing. I’ve written over six thousand blog posts and worked on around fifteen books. I am not trying to brag about my ability (which, trust me, can always use the skill of an editor), but rather to provide some context as to why, when I’m testing a cool new utility or API, I judge it based on the level of documentation and how much care (or how little) is put into it.
This won’t be a terribly long post. I had to build a small demo for a friend demonstrating drag/drop along with uploading so I thought I’d share the code for others. Honestly this is mostly for me so that when I need to build this again in a few months I’ll Google and end up back here completely surprised that I had already written it.
A while ago the author of “Progressive Web Apps”, Jason Grigsby, graciously shared with me an advance copy of his book. Things happened and I fell a bit behind, but I finally found time to finish reading the book and thought I’d share my opinion. Progressive Web Apps (PWAs) are easily one of the hottest topics now. I’ve been doing my own part to learn, write, and present, on the topic for about two years now, but honestly feel like I’m still just scratching the surface. It doesn’t help that the technology behind PWA feels like it’s changing every day. Not only do you have new APIs to learn, you have entirely new browser behaviors to figure out as well. It’s a huge topic and one that I think will continue to be talked about heavily for years to come.