In the heart of amazing software development, in the city Brno, we launched a blog to share our thoughts.
The software during the development cycle will go through many stages. It usually starts as a source code in IDE, different pars will be executed in unit tests, maybe even whole components will be tested. It’s somehow packaged (compiled) and deployed to some server (staging, production,…). That is a very rough lifecycle which is not applicable in all cases, but at least during my time in CloseIT, many projects followed it.
When I started putting together my first AWS SAM project, I was confused with the project structure - as always, when I’m starting new project with new technology. You can easily make a bloated project where code is duplicated in each lambda function.
The current pandemic has revealed the importance of remote work. While this might be a seamless process for professions like programmers, with their setup already prepared for remote work, the situation may have been a bit different for professionals involved in model governance and model risk management.
Here we go again. The last day of June and you can read interesting topics from the development world that we have read this month.
In CloseIT, we have a channel on Slack where we share interesting development YouTube channels, blog posts, articles, etc. with each other. Here are our DevTips from last month.
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.