# Visual Studio Code

The Importance of Documented API for UI Components

Documentation is a topic that often splits developers into two or more camps, those who write and those who don't; an irony since both camps rely heavily on documentation with external libraries to utilize and understand it's respective API. So, when is documentation considered 'good'?

Tags

Link

The Trials of The Promise-Centric Input, a Visual Studio Code Story - 2

In a previous post, I went through a retelling of anguish, environmental issues and dead ends while trying to evaluate how a bug such as this was possible. Throughout the process, I kept asking myself and even the other developers, what is the scope? Where could this bug be created?

Tags

Link

Initial Reactions to working with Programmatically Generated UIs in Visual Studio Code

When I first started contributing what I could to Visual Studio Code, I was under the impression that it was written using React. Even while working with the custom drop down component, I was still under the impression there were React Front-end technologies which enabled for the dynamic rendering of various components and functionalities. Only in recent, while debugging and looking for high-level understanding of different scopes, did I realize that Visual Studio Code developed without the front-end JavaScript frameworks such as Angular, Vue, React or even MeteorJS. Without sounding like I just discovered Pluto being once called a planet, this was very left field.

Tags

Link

How I Approach Bug Fixes in a new Code Base

The one thing that Humphrey said which really resonates with me on the topic of bug fixing is summed up as this, '(on bugs) they're easier to understand since the code foundations have already been laid out before you, all you have to do is understand it'. Even at work, I found myself for the past 4 weeks focused on bug fixes to our product prior to the Mobile World Congress (MWC) event, so I was both sick and very well experienced in trial-error approaches towards bug fixing. Here are three concepts / thoughts which I find often result in a step in the right direction when it comes to solving the infamous issue, resolving the ticket, or adding the feature which exists in a different scope.

Tags

Link

Approaching Accessibility with Visual Studio Code

For the last three years, I've grown a passion for extending technologies towards a direction which makes them more accessible for a wider range of users. It took a while to realize what accessibility truly meant in the world of development, software, websites and health organizations. Through the process, I took a course on behalf of my employer at the time to learn the three levels which make up the Web Content Accessibility Guidelines (WCAG) 2.0, A, AA, and AAA. This course took me through so many spirals of knowledge and issue, all-encompassing different scenarios and acceptance criteria for web development. After taking the course, I started to see software design and accessibility very differently. Contrast between colors, element organization, font-sizing even became subject of my mental focus at first.

Tags

Link

Exploring The Inner Workings of Visual Studio Code’s Command Panel

Interesting concept, it’s a very surreal experience to explore and work on a project while using said project as the tool for development and exploration.

Tags

Link

Building Visual Studio Code

Building Visual Studio Code is quite the interesting process, mostly because the dependencies differ in obtainability between operating systems. For this article, I’m going through the process on MacOS High Sierra since it will be primary development machine for upcoming bug fixes, code improvements and contributions to Microsoft’s Visual Studio Code.

Tags

Link