As I looked up in shock from my desk I saw myself sitting across from me…my colleague was testing his new face verification algorithm wearing a mask of my face. Zen masters have talked about finding yourself, but I’m pretty sure this was not what they intended. When my heart rate slowly returned to normal I decided it was probably best to drink decaf for the rest of the day. Now I expect that the mention of decaf is strike-1 for many of you coffee aficionados, but it was fancy decaf if that makes it any better (I expect not).
The SSR (Server Side Rendering) allows to use to generate dynamic HTML pages – content of these pages is not-known while application is building. The main characteristic of this application is that it can be run on the client side (browser) as well as on the server side.
Continuous integration (CI) is the practice of frequently merging working copies early in the developing process. Among a wide variety of testing disciplines, performance can boost development process as part of CI.
Performance tests consume lots of memory, CPU and the machine resources in general. By itself, performance is expensive. But, you can do much for free. By using JMeter as the main performance tool and continuously integrating everything on Jenkins, great results can be accomplished.
Allow me to start this with a quote from Charles Dickens.
No one is useless in this world who lightens the burdens of another.
This pretty much sums up the job description of a business or systems analyst. Especially in a fast-paced, dynamic, ever-changing modern enterprise development environment. Why is that so?
Let’s break our quote and statement down to some simpler elements, let us analyze it.
Well, the job title does not give you much insight on what the person doing it actually does, at first glance, doesn’t it? Unlike developer – where someone might think (and would not be wrong, to a point) that a person doing it types code, solves logical problems with it and builds applications in specialized tools – analysts possess more of a soft skills package.
According to VersionOne’s last State of Agile report, Scrum and Scrum hybrids make up for 70 percent of practical applications of Agile. While comparing methodologies, methods and frameworks (Scrum is a framework) is a bit of an apples and oranges activity, the fact is that Scrum is the clear winner in the Agile ecosystem.
But, what exactly are the reasons for Scrum’s popularity and clearly superior adoption rate?
As is often the case, the reasons are many and complex.
Most code starts out as a monolith. This was my experience as well while working on a self-service application for a big telecommunication provider. Idea was to have a separate application where we will expose a lightweight REST API for our modern frontend (Angular 1 at that time). This consumer services application was supposed to be a bridge between CRM and SOAP powered web services and a lightweight client application that we developed using Angular. Without knowing full boundaries of our domain or the extent to which it will grow we started exposing REST services and it seemed like a good approach.
So what is a monolith?
How does team see tester?
Testing is often seen as a destructive activity. So, the role of the tester sometimes can be really specific. In some cases, tester won’t fit in the team easily. Developers sometimes think that tester is against them and that could produce problems. The software tester needs to convince the rest of the team that her/his part is really important and to have good communication with them and in a nice way prove them that he is not their opponent. Tester plays on the same team, just with different duties.