One of the first things I remember when I got my new job as a manager is the constant flow of congratulations, emails, smiley faces, likes, endorsements and even a salary raise together with a slightly bigger office.
In the world of enterprise software development we can see a steady tendency in moving business logic from the database tier to the application tier. Many factors influenced this, but the main one, in my opinion, is portability. Modern applications must be able to work correctly on different operating systems, desktop and mobile devices, support interfaces with dozens of upstream and downstream systems, and, of course connect to different databases. For portability Java is, de facto, the number one programming language. But databases have been here for ages, they are being transformed and adopted for enterprise architecture and enhanced with lots of useful features.
There was an ongoing discussion on the Internet on when to create .NET assemblies in an application and when not to. There was also another debate on what constitutes a layer and what constitutes a tier. The discussion of the latter issue had to be postponed, and today I want to talk about when you need to create assemblies.
A standard learning process has an interesting feature. Once we decide to learn something new, we start reading textbooks, attending courses and obtaining new knowledge by all available means. After some time we say “Enough!” to ourselves, give up education and move on to the practice (in the early stages of the theory there are some simple practical problems to solve, but they have no significant value).
On the 23rd of May Soft Labs and Luxoft Training hosted Dev Labs 2015, the first online English conference for Java developers where more than 210 people from countries such as Russia, Romania, Poland and Ukraine took part.
Why do we as testers spend so much time with functional requirements? What about the rest of the requirements which are numerous and important as well?
Many of us have faced the challenge of choosing the optimal technology to develop a software product. The importance of this task cannot be underestimated. After all, the technology you choose will ultimately determine the funding that will be spent on development and have a decisive influence on the fate of the product itself. I know of some cases where choosing the wrong technology made a key and very labor-intensive internal system of a company virtually unsupported and it eventually led to the project being abandoned. And these types of situations are not that uncommon.
There are many situations when you need to assess a project but the time you are allocated is not enough. Below are a few ideas on how you can find the extra time, so you do not have to reduce the quality of your assessment process.
Are there any KPI which affect the personal interests of the manager but can also lead to a win-win situation? The answer is no. Once there are KPI’s that affect the interest of the manager we will surely have a situation where the manager must choose between his interests or the interests of the project. And most will choose the former.