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.
One of my goals for this year was to play more with Vue “apps” (ie, not simple page enhancement demos) and to dig more into Vuex. I really like Vuex, but I’m struggling with the “best” way to use it, what makes sense with it and what doesn’t, and generally just how to approach it. I figure one of the best ways to get more comfortable is to just build stuff and see what feels right. With that in mind, today I’m sharing a game I built called Lemonade Stand.
Hey everyone, this tip will probably have a very limited audience, but it was a huge deal for me so I wanted to share it with others in case they run into the same issue. In case you don’t know it, Netlify Dev is a way to run the Netlify Platform locally. Which means features like redirects, functions, and more will work locally.