JuniorLearnsToCode

This blog post is inspired by Ministry of Testing Bloggers Club  topic idea for April 2021, the goal of the post is to describe only three skills which are important for testers and explain why! For me personally, by reading blogs from different authors, I noticed that there is always something new and unique to everyone's perspective - even when people are covering the same topic! Aside from broadening your horizons it is also a good way of learning (you do get a certain level of repetition) and benefit from viewing things from another angle, which is always a good source of thinking material! So without further ado, I will list my top three skills bellow. 1. Communication I often list this one as skill number one whenever someone asks me what to I think about the most important skill for a tester. But why? Communicating effectively is important for almost any role in IT, but, for a tester it is a must, as a tester may be often viewed as the harbinger of bad news so it is vital fo...

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...

What is DevOps and Why do we Deed it? The current technological and economical state of the world makes DevOps pretty much inevitable and quite a necessity. The traditional software development approaches do not allow the business to have as much flexibility (as the DevOps philosophy does) and more importantly, companies that implement DevOps practices can be a step ahead of their competition and also have the ability to make counter-moves against their competitors more rapidly, when required. For example, let's say your competitor releases a very compelling feature on their web app, and they get a lot of traction and positive feedback from their customers - resulting in more sales, in order to retain your existing user base and to attract new customers, you would need to respond quickly to this, develop a similar feature of your own, in the shortest time-frame possible, while at the same time, making sure that the new feature goes in and out of your pipeline as quickly as is can b...

In this post, I plan to share a few tough on mentoring others.   I may not be the most experience of all IT people, I got around six years of total experience, at the time of this writing in 2020, however, very often at various job roles, I have been tasked with mentoring other team members. It seems like most people tend to avoid the extra responsibility that being a mentor brings - just think about it: you have your own daily job duties and on top of that you get an additional burden of having to make somebody become a productive team member, often going from zero to hero. When you got patience and friendly personality people tend to volunteer you to be a mentor for new team members. At first, I somewhat vexed by this - why do I always have to be the one responsible for onboarding the newbies and holding their hand? After a little while, I realized, that while mentoring can be cumbersome and demanding it's also a very valuable experience - even though this sounds like a complete ...