Blog

This article will try to debate the controversial dilemma of hard and soft skills in the Software Testing field. I’m sure that in any field/industry we may perform we encountered this dilemma at least once. So, which one do we think weighs more: hard or soft skills?

Any software development estimate is based on a combination of effort, time, and costs associated with the project scope. The crux is finding a balance between the client’s or manager’s requirements and the team’s ability to address these requirements in estimating a proposed project.

A product owner is a specialist with a strong understanding of the business as well as the vision, goals and mission of a product. The role of a product owner is central to the development lifecycle, and responsibilities vary depending on the product type and specifics of the development process.

You might be surprised to find out that Artificial Intelligence (AI) is not that modern, as it
has been established as a field of study since 1956 at a summer workshop held on the campus
of Dartmouth College (US).

The pandemic has forced many workers around the world to shift from the office environment to working from home. In trying to limit the spread of the virus, tech companies like Twitter, Google or Microsoft have encouraged employees to stay at home.

Customer service plays an important role in building the brand reputation for your business. Often customers get in touch with this department because they want to address a problem regarding your services or simply ask a question about one of your products.

Some product development teams might fall into the trap of thinking that all customers need the same thing.

Code review is considered to be the #1 practice a company can use to improve code quality. But its benefits extend far beyond that, while its drawbacks can be managed by following best practices guidelines, all of which we are about to explore here.

There are many approaches to how a team should be built, each relying on a different underlying theory. One of the most interesting ones is described by Patrick Lencioni in his book “The Five Disfunctions of a Team”.

We all know that every successful software product starts with a big idea. However, it takes a lot of time, energy and dedication to take that great idea and transform it into a successful product. Most importantly, you need the right technology and architecture to ensure a seamless experience for your end-users…

You’re coming home after a hard day at work.  You throw your bag on the couch and grab the two slices of cold pizza left over since last night (you hope), barely feeling the taste of it. With the last bit of energy you throw the box on top of the pile of other boxes from food delivery you have lying around in your room…

So you are the person in charge of a software project. It may be something small, an MVP (Minimum Viable Product) or a large enterprise project.

You want it quickly, cheap, and without bugs. I’m not even going to say the “pick two” cliche (there, I said it), but the truth is that too often in the industry…