Once, when I was working in one small company, I was offered to conduct an interview with a candidate for the QA engineer position. At that time I did not have experience in that, and naturally, the first thoughts were "What to ask? It is necessary to re-read urgently all the literature on testing! What to do?"
Most people think that time spent in traffic jams or on long trips is kind of lost time, but now a lot of new things appeared to make use of that “waiting” time. For IT-specialists the most interesting and useful occupation will be podcasts. Let's see what podcasts are there on IT-topics, which may be interesting to professional audiences, both developers and managers, system administrators and the rest of IT-specialists.
Mostly everyone noticed already that changing and evolving of modern IT industry is happening so quickly that it became harder to keep up with it. It feels like even if you’re studying all new technologies they seem mushrooming too much. And also the rate of appearance is approximately equal to a disappearance of them for the majority forever.
On many occasions the most common fixing suggestions are to clear your cache and cookies if you want your browser to work effectively and without delays. In most of the cases clearing out your cache and cookies is not only a crucial problem-solving step, and it may really sound like you just need “to restart”, but it can be a great solution altogether.
In many companies, unfortunately, underestimate the influence of the static test on the quality of the final product. At first, let's start with terms to understand differences between static and dynamic testing. In contrast to dynamic testing, static testing finds causes of defects and help to prevent future failures. It often has a goal to educate team and new team members. Static testing is done before the dynamic test and accordingly, errors found at this stage costing us less.