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...
Various types of work attract different kinds of people, some of us like a dynamic work atmosphere, while others function best if things are more predictable and stable. Working for a big enterprise client is a lot different compared to dealing with clients directly while freelancing or working for a SaaS (Software as a service) in which case the company is it's own "client". I've worked in all three mentioned scenarios - currently, I'm working on a big enterprise project, in the past I've worked for several years for a company that was selling its own product and done some freelancing for a couple of years, as well. Bellow I will strive to list the advantages and disadvantages of all three types of jobs, in hope that this may prove useful for people looking for their first IT job. With memes, as always. So let's get started! Working for a SaaS Company Working for a SaaS, Software as a Service company, you usually won't have any interaction wit...
Thank you.
ReplyDelete