Clean code, Better Standards
13 Feb 2025
Coding Standards and The Approach to Clean Programing
Previously, My 314 class learned Type Script programing through a online editor "TypeScript Playground"
This week, we moved into a open source editor called VS code. Immediately, I noticed a difference between
the two. TypeScript Playground has a built in compiler, flexible when inputing data, and much easier to
navigate. In comparison, When initially setting up the IDE for visual studios, there are many additional steps
to write in TypeSCript. It is required to add Extensions to the environment. Those Extensions being:
ESLint: Program structure format
HTML Boilerplate: HTML template
HTML CSS Support: User Interface customizations for HTML
And other extensions added to the environment
After the extensions were initialzied, I attempted to use Visual Studios. Unfortunately, I ran into a problem
when I tried to use ESLint. In the terminal, to check for errors with ESLint, I had to use command "npm install"
but the npm did not read in the terminal as an active part of the extension. For a couple of hours, I researched to remedy
the issue. I looked through Stack Overflow, Chat GPT, and any youtube vidoe that can help me use npm on VS code
I realized a bit later that I needed to instal Node.js, after installation everything seemed to work in order.
As I began to work on my typescript homework, there were some noticeable differences. While TypeScript playground was
a lot faster to compile and show the partial errors, VS code gives suggestion for quick fixes. An example being, indent errors
or missing semi-colons. If there is a larger error, it would list in the enviroment a link, although some of those links
will not guarantee fixes for compile erros if the code is wrong. VS code is a bit different, especially with coding standards but a benefit
towards structured coding which keeps everything neat. When dealing with code from other developers, if their code is unorganized and not noted
correctly for proper explanations, it would take more time to complete an assignment. ES lint is helpful tool when fixing errors
It is greatly added benefit when using type script while making sure when transfering it to JS the the code is clean and excutable.
In conclusion, There are some differences in using TypeScript Playground and Visual Studios. I believe the biggest hurdle for VS code
is setting up the extensions. Although the actual functionality of Visual Studios is user friendly. Indentation and correct structure
is imperative when using type script. I did realize that when using TypeScript Playground. It is good practice when coding not just in
in typescript but in other languages as well. I enjoyed using Visual studios, but I'm still barely scratching the surface of using VS
and my opinion my change in time.