Skip to main content

Atom, My New Code Editor

Recently I started looking into a couple code editors for school. There were two that caught my attention; Atom and Visual Studio Code. After playing around with both of them, I decided to stick with one. Overall, they do similar things, but my decision is solely based on my bias. I personally am not a fan of Microsoft's software so I was not motivated to experiment with Visual Studio Code.
Atom is a free to use code editor and can be downloaded at The interface by default is dark, and it looks really nice in my opinion, but it can easily be changed by going into Settings>Themes
It is really easy to customize it to how you want it to look. There are many things that can be changed, one controversial one being the spacing between tabs.
It is really easy to get started with Atom. As soon as you start the program, you are greeted with a welcome page and we can easily start to edit anything we've been working on.

The best part about Atom is that it has extra packages that can be installed. These packages let's the user customize their experience to their specific needs. I personally have worked a lot on C++ and there are many packages on Atom that makes programming in C++ so much better. I come from a basic editor called TextWrangler so I am not used to being spoiled with autocompletion. It is amazing how powerful this tool is. It knows what classes are available to use, even though I just created them myself. It's just amazing.

Atom is just customizable in every aspect. There are packages that give beautiful themes, preset settings for the editor, etc... There are so many customizations and combinations of things a user can do with Atom.

To top it all off, it even has spell check for the English language, this allows the programmer to document their code with minimal spelling mistakes.

Overall, Atom is one of the best code editors I've seen. It is really lightweight, it looks beautiful, and it is very simple to use. I am glad that I have been introduced to this editor and I look forward to using it for my future projects.


Popular posts from this blog

Fixing Bugs Again

I started working on Open Source Projects again and I had a difficult time getting started again. A big part of my problem was not having enough storage on my computer. After moving some things around and deleting files and programs I don't use, I was able to clone a couple projects and I was finally ready to start running them and replicating the issues.  This time around, I worked on three projects; Thimble, Brackets, and Balrog. The bugs that I fixed for Thimble turned out to be fixes on Brackets so the pull requests were made there but referenced from Thimble. Overall, getting started was much easier than last time because I already had the experience and possibly the necessary files on my system to begin. After being assigned a couple bugs, I began to work on them and I have made a couple pull request for the fixes. They have passed all tests and I am just waiting on it to be accepted and merged into the actual project! That is my goal. I will need to follow up if anyth

Second Attempt At Fixing Open Source Bugs

In my second attempt at fixing open source bugs, I want to prove that I have grown from the first attempt. My first attempt was fixing a single bug, requesting a pull request, and getting approved! My goal this time around is to work on more than one bug, I plan to work on 2-3 and my ultimate goal is to get all of them approved! There is no better satisfaction than getting approved!  Since I was working with Mozilla projects before, I decided to stay in that bubble and work on Thimble/Brackets. I have currently asked to work on a couple bugs like this  and this  and once I get the okay to do so, I will begin to try to fix them. As of right now, I am still researching for more bugs to work on, but at the time of this blog post, I do not have any backups.  Due to the strike, a lot of things are altered in my schools semester. Surprisingly, all my teachers were very accommodating and they dropped tests and assignments and overall, it's making the end of the semester less over


Documenting everything is extremely important. It gives everyone the information they need whenever they need it. Github makes it very easy to have beautiful pages written in markdown rendered automatically. It's nice and easy to do. Creating a README in the root of the project is common practice and is even automatically rendered when the project is open in Github, under all the file names. I've been looking at quite a few different projects and they all have README files. It usually includes an introduction to the project, how to set it up, how to run it, how to contribute to it, major credits to people, etc... Essentially, it holds important information about the project that anyone has access to. Along with the README file, we can comment on our actual code so hackers who read the code can know what does what. It allows the creator to recall what they wrote in the past and it invites new people to understand what has been written. It is really important that comments are