In the heart of software development, in the city Brno, we launched a blog about IT.
I was wondering since I am in a business and since I am in an IT, why these two sectors were seen separately for such a long time. It seems last few years people started realising they can work together. Nowadays, they are many companies based simply on the digital products, look at Airbnb, Uber, Google, Spotify.. without the technology and some algorithms plus great programmers they are nothing.
Let's face the Continuous Integration the development practice that requires developers to integrate code into a shared repository at least once a day per developer. Each check-in is then verified by an automated build, allowing teams to detect problems early.
My two favorite topics just next to the technology are food and design. I love both and I think about both of them most of the time. Therefore, a question appeared in my head: "Does Agile works just for software development or is it a way of workflow management also in any other areas we will choose?"
When you work for sometime on a larger project, you may realize it doesn't perform as well as it did. That is usually expected but sometimes, it just doesn't feel justified. This was also our case and because the performance of the project was important, we had to get our hands dirty with profilers and debuggers. Of course, we found a few bottlenecks.
I used to have startup developing a mobile application. We were two people working hard and at some point successfully, even though we were a big mess. Both of us doing things from design, to coding, to management, to marketing to planning everything needed. Yes, it is a typical startup mess, that we loved.
If you work in FinTech, sooner or later (but probably sooner) SAS data set will get into your project. In a field dominated by one system, there is hardly a place for rejection. Unfortunately, for small companies it is very hard to integrate SAS in their stack. In our projects, we use ETL to gather data from different sources. To be more precise, we use open source tool Pentaho Data Integration.
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.
Having a pet project - a project being developed in your free time - can be a lot of fun. Give me a free week and option between spending the whole time on the beach or the possibility to work on my stuff, I will probably take #2. Don't get me wrong, who doesn't like a vacation? But when as the idle time raises, I'm getting bored and the itch to work on my pet projects grows.
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.