Change is always hard. Humans are creatures of habit, we feel comfortable and safe when we are operating within our established (predictable) patterns. That is why people resist changes, even the ones that are good for them! Getting someone to accept that a change is needed can be tricky, it will generally involve analyzing the situations and doing some persuading. If you can convince others that a certain change will bring them a certain kind of tangible benefit, people will be more open to accepting it. So let's see how would that look in terms of software testing! As testers we often are arguing for more resources for testing, more time, trying to convince the management to give us the blessing to do more automation, to try out new approaches to testing, and to implement improvements to our testing process. So let's say we propose to change the testing process in our company, how would we go about implementing those changes? Assess the Situation First of all, get to know th...
I recently passed this exam, after some light-core studying, over maybe three to four weeks, I wasn't preparing all that intensively but considering what is recommended by a lot of people. I prepared more than I needed to prepare, I like to play it safe. A lot of people have been asking me how I prepared for the exam so that gave me the idea to put together this blog post with a few tips. Since this is an entry-level exam it's not too hard, compared to more specialized certification exams. It covers the basic cloud literacy and basic knowledge about Microsoft Azure, its services, and products. If you're new to IT or planning a change of career, this might give you a nice boost of confidence, if this is the case it makes take you a bit more to get acquainted with all the terms that will be new to you, but a few weeks of studying should suffice. On average, one or two weeks should be ample enough to prepare for this exam. The exam topics (at the time I'm writing this) are...
We often hear that everything is a matter of perspective and in light of that notion I have to admit that there was a time in my career when I wanted to give up on testing. Due to having seen testing in a wrong (and rather shallow) light, I pondered hard about leaving it for good for a career in web development. So, let us get into the meat of things. Now, when I talk to people I offer hear them describing me as someone who enjoys testing and is genuinely passionate about software quality. So how was it that I found myself in a situation where I wanted to quit being a tester if I love it so much? It was many years ago, and while I can't disclose exact details, I can talk about it in general terms. This blog post is in part inspired by my personal experience and also by observations I made while talking to lot of testers trough the time - and most of them relatively similar experiences to share, from some point at their career. It is my hope that by discussing things such as this on...
Comments
Post a Comment