In the heart of software development, in the city Brno, we launched a blog about IT.
Almost out of nowhere, the whole internet is full of advice on how to cooperate within your team remotely. Well, for us, nothing really changes. In CloseIT we are used to working remotely, we are used to solving problems not only onsite with the team but also with clients remotely. So we maybe miss three small ones...
Model governance regulators are moving their focus closer and closer to the qualitative elements of a model – the model governance process. Unfortunately, the regulator also often asks the bank to explain their internal risk mitigation process without the providing the specific guidelines necessary to match the model to the bank’s methodology.
The Agile method Scrum is a more modern way of helping to eliminate Waterfalls' weaknesses. Its biggest advantage is higher project success, immediate client feedback at regular two-week intervals, higher satisfaction of the development team, etc., and, in close connection with the company's values, creates a powerful tool that takes quality and work to a completely different level.
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.
One use-case of our CRM solution is to run custom calculations with custom ETL jobs prepared by the application users. This is a big advantage of CRM because users have better insight to business logic than developers, which are concerned mostly about the technological side of application.
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.
In the previous blog post, I wrote about our problem with JVM CodeCache. This cache is used for saving compiled machine code and if your Java application generates new code on the fly, it will eventually fill.
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.
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.