JuniorLearnsToCode

The Three Amigos is a software developer approach that is often used in Agile environments. It a highly collaborative development strategy. It places a large emphasis on communication. Perhaps it's biggest selling point is the fact that different experts are working in union, complimenting each others unique skills, thus being able to gain a broader perspective on things. This approach helps out to get clear understanding of the requirements and agree on the "Definition of Done" - what exactly is need to put the story in the "Done" status. Roles Involved in the Three Amigos We need the following roles in order to utilize this development strategy: BA  - the Business Analyst would help ensure that team understands what is expected from the user stories, so the team realizes what business value would the customer receive. In places where there is no BA, the PO (Product Owner) will take place of this amigo. Dev  - the developer can help in understanding the require...

This is another blog post inspired by  Bloggers Club June 2021 - if you are a tester (or interested in testing) be sure to check out the Ministry of Testing, it's wonderful community of smart and helpful people and their forum (called the Club) is great place to get help, get inspired and to discus stuff to stimulate those little grey cells. This month's topic idea appealed to me straight away. I try not to have regrets, per say, but there I decisions from the past that, from today's perspective, I would have made differently. If I could, pretty much only thing I would have done differently is that I would have left support sooner (I worked in tech support for about two and a half years) and gotten into testing sooner. I spent a lot of time trying to find myself, I was learning WordPress and doing freelance consulting, learning Angular, React, PHP, Java, .NET/C# and other development technologies, mostly (but not exclusively) front-end oriented. I recently  blogged about ...

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

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

 The MoT's Bloggers Club always gives me good inspiration for blogging topics. This one is about bugs! A few different "fun" bug-related scenarios come to mind, so I'll jump strait to the point! The Environmental "Bug" This is kind of a false positive bug - it is a bug that is not a bug, per se. We all probably seen something like this, a feature that works in Test but not in the Acceptance environment, for example or if our regression tests suddenly start failing, but there were no code changes introduced to the system under test - rather there was a change in the infrastructure causing our tests to fail. These issues can be very frustrating and hard to pinpoint. The best way to avoid them is to avoid secrecy and to be fully transparent since any change, no matter how innocent may seem can cause unexpected complication in a large complex system. Bug Ping Pong Now this is not the case where some Stakeholder decides that the reported defect is not important e...

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