This week I yet again made little progress on GeoToast. I started watching a Vue.js course on Udemy called Vue JS 2 - The Complete Guide (incl. Vuex). Made some progress on that, but I also spent a lot of my free time goofing off. Watching Netflix, surfing the web, etc… So this coming week I need to focus on making major progress on the front-end of GeoToast. I will put aside watching the Vue.
For the client side development of Geotoast, I have decided to go for Vue.js rather than Angular or React. I have no specific rationale for it other than that from everything I have seen about Vue so far it just seems to make more sense to me than both Angular or React. Vue does not get nearly the amount of attention that Angular or React does, but it still has a flourishing community and plentiful resources are available for learning Vue.
This week I have made little progress on GeoToast as I have traveled to Tokyo (where I will stay for the next month), and have also done a bit of sightseeing. I am settled in, so this coming week should see progress again. My plans for the coming week is to be able to serve the HTML/CSS/JS of a toast from my API, and then be able to inject it into the DOM of a web page.
Things I learned Rename Refactor in VS Code In last week’s update I alluded to the fact that I miss many of the refactorings which is offered by Visual Studio and Resharper. One good find this week is that VS Code at least has Rename Symbol functionality. As explained by the VS Code Documentation: Some languages support rename symbol across files. Simply press F2 and then type the new desired name and press Enter.
I have been working on GeoToast and one of the things I needed to handle was returning a response when model validation fails when calling any of my API endpoints. I am also using Fluent Validation for my model validation which I talked about in my previous post, but that has no bearing on this blog post. This blog post deals with ModelState and FluentValidation ultimately updates the ModelState so whether you are using normal data annotations attribute validation, or Fluent Validation, this will work the same.
Welcome to This Week in GeoToast (TWiG) #1. To keep myself honest with working on GeoToast, I thought it would be good to write a weekly progress of my work on the project, as well as the good and the frustrating things which I experienced this week. The Good JWT integration is super easy To secure the API for GeoToast, I am using JSON Web Tokens (abbreviated as JWT and pronounced as “jot”).
Two books I have read at the end of 2016 which have shaped a lot of my current thinking are So Good They Can’t Ignore You and Deep Work, both by Cal Newport. I picked up a lot of tips from these books, but for me the two main things which stood that I want to work on are the following: Doing deep work. In other words, I want to set aside time where I can focus intensely on one specific task, without being distracted by anything else.