Have you ever tried to understand what is some company actually doing, from the software engineering point of view?
Let´s take a company named Finbourne (finbourne.com). Finbourne website states that: “At FINBOURNE we liberate your data, making it accessible across the investment chain. Our solutions restore control and confidence, empowering everyone from emerging hedge funds to established global institutions.”.
Well, it looks the company provides data processing and data delivery. However, from the engineer´s point of view, that is still very vague. You wouldn´t expect a financial company to speak engineering language on it´s first page, right?
So how do we actually check which kind of software Finbourne creates?
Open Source Community to the rescue. It turns out that Finbourne has a GitHub account at github.com/finbourne The account is “verified”, which makes it (most probably) credible.
Now, let´s take a look at the GitHub repositories of the Finbourne.
At the page a investment data platform called Lusid is mentioned.
Tech is only mentioned on the front page if it is really important. So, let´s check if there are repositories related to Lusid and filter them by Java language usage
I have chosen the “lusid-sdk-java-preview” as it presents the latest features in the Lusid´s SDK. The github.com/finbourne/lusid-sdk-java-preview.. file is quite simple, so the best way to understand the project is to fork it and take a look.
As you can see, the project has been recently updated.
Here comes the easy part. I need to check which branch is normally used to development and try to build it. From the git history we can see that both master and develop branches are on the latest codebase. I will select “develop”.
Profit! The project builds and now I can actually start investigating and probably contributing (why not?):
As usually, lets add maven wrapper and gradle scan to the project:
Sorry for not taking screenshots, but basically I need to add 2 things to the project, just to make it look cleaner: maven wrapper and gradle scan plugin.
Now let´s add gradle scan plugin to the project.
Well, a pull request has been raised:
And a build scan hass succeeded. I can already see some problems there, but we will leave it for the future articles. gradle.com/s/xld4m4satpzoc
