Opinion

For the last three weeks I tried to get an eGPU, a Sapphire Radeon RX 580 to be exact, to work. Today’s the day when I’ll stop using anything Radeon, and Kdenlive for the next 10 years. In this quick article I’ll explore why.

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.

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.

As you might remember, we discussed a while back, that having automation for the mundane tasks would yield a great result in the long run. Let's go a bit more on the most mundane of them all: security.

Did you know that if at work you waste 10 minutes each day, for doing some mundane repetitive task, at the end of a working year you would have wasted roughly one full working week?

I have reviewed the Selenium Page Object Model and determined it is no better than the Germanium API in terms of abstracting away low-level locator actions like finding and clicking elements. POM provides no improvement to simplifying the locator strings for the Selenium strategies it uses: xpath, css.

Continuing the previous article with concrete code examples of the ultimate automation achievable in the Germanium stack (Selenium, WebDriver, Germanium, Behave).

Let's talk about the benefits of abstraction and some historical Selenium notes in the context of Selenium and Germanium.

When thinking about integration tests, a lot of people think only about the source code of the tests. Of course, seeing tests like that is not only wrong, but also might prove fatal for your testing infrastructure. Let's see why...