I have to say, this unit has been my favorite so far. Since the beginning of the semester, we have been programming on GitHub's editors. Which, for anyone who has not tried it yet, is a very painful experience. Effectively, we have been coding blind, eliminating issues through a process of trial and error. This has resulted in the coding process being very time-consuming and inefficient.
Although, when I heard we would be using VS Code, I could not contain my excitement! I was already familiar with their platform and have done many projects with its IDE. In other words, the pivot to using VS Code wasn't difficult for me at all. That is not to say that the whole experience was a walk in the park. The installation of ESLint and the proper extensions was a bit taxing. With it taking many hours and much consultation to properly install Lint on my computer. Although when I finally got it, it opened up a whole new world for me in TypeScript.
Personally, I appreciate the coding standards that are in place with Lint. Also, I have a bit of a type A personality and an eye for aesthetics. So if it means being neater, I'm all for it! I feel that it makes my code cleaner and my work more organized. Additionally, the formatting helps with the legibility of my code. More importantly, the uniformity of my work allows me to better discern logical errors in my programming. Overall, Lint's standards have added a new level of clarity for me and have given me newfound appreciation for regulations. Coming from a Java-based background, I found that Lint's error detections are very similar to JUnit tests. Though, if I had a choice between JGRASP and VS Code for an IDE, I would choose VS Code any day. I appreciate its user-friendly qualities and easy-to-access extensions.
Over this past week, I feel that my programming abilities have gotten stronger. VS Code as a choice of IDE makes my coding process much smoother. Additionally, ESLint’s coding standards provide me with a better understanding of how to structure code. Helping me to improve my computing logic and improve my eye for catching synthetic errors.