In the heart of software development, in the city Brno, we launched a blog about IT.
Let's say that the ETL tool PDI isn't very suitable for dynamic data processing. But you could probably say something similar about other ETL tools. At the end of the day, you need to tell the software how to transform the data. It is only logical that we also have to define the data structure.
Jira is a popular issue tracking tool and is also used in many businesses as a business process management system (BPM). Sure, there are more suitable tools like jBPM, but Jira is much more user-friendly. And even though it's less feature-rich regarding BPM options, it can be easily extended using plugins written in Java language.
When I started to work in CloseIT, I was eager to understand how the app works. Usually, I try it by trial and fail. On the other hand, each build takes time and it disturbs my workflow. I was wondering if there is a way to make it faster. It was my first work experience with Spring framework, but it didn't take a long time to find people with the same problem, and that's how I found the devtools from Spring.
The number of models your organization must manage is increasing every year. Models are often registered in tools like Excel that are excellent for a particular type of task but are certainly not ideal as inventory tools to track current status, search for different criteria, or manage a variety of workflows associated with the model's life cycle.
When we started with the implementation of IFRS9 standard, we had about a year to design and come with working and hopefully an extendable and robust solution. Since most of our developers are comfortable with Java and we built other projects using this language, the decision to built a core of application on Java Spring framework was easy.
As a Java developer, you don't need to know internal details of JVM most of the times. The virtual machine is not a trivial piece of technology and learning internal details can be scary. But there are times, when you find something interesting in the logs, which seems to be important. Like the message: CodeCache is full. The compiler has been disabled. Try increasing the code cache size using -XX:ReservedCodeCacheSize=
For our internal purposes and also for several of our customers we either introduced or used Atlassian JIRA. We see this tool as an amazing platform which can serve purposes of software development teams but also to entirely non-IT related projects. One of the small problems that we faced was rendering a screen of an issue with many subtasks. Simply to get an overview of all the subtasks which belong to a common parent means lots of clicking to the parent and then another subtask.
My question targets not only desktop software but also mobile apps, web applications, and websites. Seems like software is getting worse and it won't be better. And I just have to start my rumble with the worst - mobile apps.
When we started using MongoDB in our projects, I was very confused by aggregations. But I wrote so many of them at this point, I actually enjoy putting them together. At least I enjoy it more than writing SQL queries. Yet there is one thing I have to process for a while in my mind every time - how to do null checking and field existence checking.
We have created a unique solution for recurring stress tests in credit risk Raiffeisen Bank International, which allows us to define our own test scenarios for simulation of portfolio development and calculations of individual Risk Parameters RWA or ECL. Our application was successfully used for EBA stress tests in 2018 and continues to be extensively used for other stress testing needs by internal or required controllers.
In early 2018, a new methodology for the calculation of provisions for Expected Credit Losses (or ECL) under IFRS9 for the banking sector came into force. Our team was tasked with implementing a solution for the retail credit exposures of Raiffeisen Bank International (RBI). The calculation is used to check the plausibility of results provided by each RBI subsidiary bank.
Internal workflows are often defined very strictly, but not supported by appropriate tools. Data and documents are distributed via emails or shared folders, where there is clearly no single-source-of-truth. Keeping the deadlines between the teams is complicated because it creates ambiguities in which state the workflow is actually located and who is responsible for it.