Tagged: development

One of the most time consuming things for this website, was cleaning up the tags. They used to be an unorganized mess, and I was adding new ones as I was writing new articles. A lot of the tags had a single article. Some were misspells of an existing tag. A strangely disconnected cloud of tags existed, and wasn’t exactly clear what connected where. At some point I just realized this has got to stop.

This is the last article from the Vim Ultimate Editing series. We looked at what makes Vim (in my case neovim) the best editor out there. We’ve analyzed the console support, the awesome UltiSnips, and today we’re looking at having the configuration as a git repository.

We continue today our learning about what makes Vim the ultimate editor. To reiterate, we have three reasons that we were analyzing: First, we looked at the console support. Now, we're looking at UltiSnips, and in the next article, we shall look at the configuration that's checkoutable.

As I mentioned in my previous article, were multiple reasons why I chose Vim over Sublime. I wanted to focus on UltiSnips, but I realized that some ground work needs to be set first. So as the title implies, we're looking today at Vim and multiple file types.

When I had to choose a text editor, four years back it took me about a month to come up with a decision. I wanted to know what is the best text editor, that I am going to use for the rest of my life. This was no trivial undertaking. In the end, I had to choose between Sublime and Vim.

A simple eclipse plugin that allows creating bookmarks and notes, based on the topic you want fixed. Simply add the plugin into your eclipse/plugins folder, then open the view using the Eclipse menu: Window > Show View > Other, and pick RAGE from the list.

The 3rd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.

The 2nd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.

In GermaniumHQ we use git branches and tags for everything. From research, to development, to test, to the actual release. Why? Let me show you how this worked in case of MoPyX - the Python Reactive UI API.

In this 3 part series we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.