Turning the tables in Ghana

I already wrote about my interest in various philanthropy topics, one of them is being helping out people in Ghana. The easiest way for me to do that is to employ IT resources from there. There can be several reasons why an organization might choose to work with an IT company in Ghana, some of them include:

  • Access to skilled and talented workforce: Ghana has a growing pool of skilled and talented IT professionals, which can provide an organization with access to a high-quality and cost-effective workforce.
  • Cost-effectiveness: Working with an IT company in Ghana may provide cost savings compared to other regions, due to factors such as lower labor and production costs.
  • Location advantage: Ghana is well-connected to the rest of the world, making it a convenient location for an IT company that is looking to operate in a central location in Africa.
  • Government Support: The Ghanaian government has been actively encouraging IT businesses and providing them with the necessary support to help them succeed.
  • Growing IT industry: Ghana’s IT industry has been growing rapidly in recent years, and there are a number of well-established IT companies in Ghana that have a track record of delivering high-quality products and services.
  • Increased Quality of Service: IT companies in Ghana have developed reputation for providing good quality IT services and Solutions that is comparable to developed countries.

As with any business decision, it is important to evaluate the risks and benefits, as well as to conduct thorough research and due diligence on the specific IT company you are considering working with, to ensure that they have the necessary capabilities and resources to meet your needs. When it comes to Accra, the capital of Ghana, it is the home to a growing number of IT companies. These companies provide a wide range of services and solutions, including software development, web design and development, mobile app development, IT consulting, and digital marketing. Some of the well-known IT companies in Accra include:

  • Softtribe: This is a Ghana based IT services provider which specializes in enterprise software development. Softtribe has clients across West Africa region, providing software development services to companies in various sectors such as Manufacturing, retail, banking and telecommunications
  • Zara Studio: Zara Studio is an Accra-based full-service IT agency providing digital solutions, such as web design, digital marketing and software development. The agency have a reputation of delivering high-quality digital solutions to local and international clients.
  • BlueCrest: BlueCrest is one of the largest IT firms in Ghana, providing IT solutions to clients in the banking, telecommunications, and oil and gas industries. The company’s services include software development, IT consulting, and systems integration
  • Black Pepper Technologies: Black Pepper Technologies is a software development and consulting firm that specializes in providing IT solutions to clients in the financial services, telecommunications and e-commerce sectors
  • MEST Ghana: MEST is an organization that helps in building scalable technology companies in Africa. They have an incubator program in Accra and help entrepreneurs grow their startups by providing funding, mentorship, and training to promising software development companies
  • Tech Needs Ghana: This is an IT company that specializes in providing digital solutions such as Website development, Mobile App development, and Digital marketing services to companies in Ghana.

These are some of the IT companies in Accra, it’s worth noting that there are many more IT companies with various sizes, capabilities, and focus areas. So, it is important to research, evaluate the options and conduct due diligence to ensure that the company you choose is the right fit for your IT needs.

I did the right due diligence, and found a company, which is not among the list above: turntabl.io. So why did I choose them among all the other choices?

Beside everything above applies to them (skilled and talented workforce, cost effectiveness, location/timezone advantage, government support, growing industry, good QoS), their ‘secret’ weapon is their CEO, Sam Moorhouse.

Sam Moorhouse, CEO of turntabl.io and James McLeod, Director of Community at FINOS and The Linux Foundation, Founder of London.js, all of us showing off amazing beards 🙂

Sam has a distinguished career – worked at Morgan Stanley and Citi as senior developer, and for 7 years, been training developers at many companies as part of the company Mallon Associates. That latter skill was what made it possible to train up 100+ developers in his Accra based office, with the help of Mallon, and with the help of many employees of large financial institutions, who flew to Ghana and was teaching the batches of developers there, in person.

The resources I have been enjoying from turntabl clearly went far above and beyond of my expectations. When it comes to them working as a group on open source projects of ours (like Arriving to… Crossroads | Dotneteers.net, see https://turntabl.io/crossroads/), or working as team augmentation on various tasks, they did deliver with ease, elegance, and professionalism. This is what you get if you engage with them – which I highly recommend, whether you are looking for new resources or help in open source projects, next to everything else above – you will have the ability to feel like you are giving back too. So, this is how the turn tables 🙂

Morgan Stanley at the Open Source in Finance Forum NY’22

As you saw in the previous post, Open Source in Finance Forum NY’22 | Dotneteers.net, I was at the Open Source Finance Forum, representing the Open Source Readiness and leading the discussion on the Open Source Program Office’s private session. But I wasn’t the only person present at the event from Morgan Stanley – we have had a wide range of presence from our side this time:

My manager, Dov Katz, was part of the opening Keynote:

Open Source in Finance Forum – Opening Remarks – Gabriele Columbro, with Dov Katz & Rob Moffatt

My coworkers, Stephen Goldbaum and Rita Chaturvedi leading multiple discussions at the event:

The Current State of DEI and Path Forward – Jevon Beckles, Chitra Hota, Nick Fuller, Rita Chaturvedi
Exploring Open Reg Tech with the LCR – Stephen Goldbaum
Modernize Regulatory Reporting: Get Ready for T+1 Settlement
Morphir Integration with Scala – Damian Reeves, Stephen Goldbaum

So, I am looking forward to 2023’s OSFF events, hopefully being able to present once again on them with some fun topics 🙂

Open Source in Finance Forum NY’22

After presenting at the 2021 version of the Forum, it was inevitable that I want to be back – it was an energizing experience and wanted to feel it once again! 🙂

So, I submitted a topic (open source standardizing for the metaverse), and waited for the green light – which never came; this was a topic seemingly too early to be discussed on such forums – I am a firm believer in mixed reality and open source, so it is just the question of time to have interest for such 🙂

But I had a way back – for the first time ever, OSFF matured enough that to have next to the multiple tracks with amazing sessions, they added an EXPO!

11 of FINOS’s own projects, the Common Domain Model, the Compliance Horizon Scanning, the DevOps Automation, FDC3, Financial Objects, KDB+, Morphir, Open Source Maturity Model, Symphony Workflow Developer Kit, Timebase and the Open Source Readiness SIG were joined by the sponsor’s booths, resulting in a huge influx of people between the sessions and during the longer breaks to check out what we can show – I took this picture before the first big hit of people arrived, because after that I never had the time to take another 🙂 :

So, how this is relevant to me? Because I happen to be the co-chair the Open Source Readiness SIG, along with the amazing Elspeth Minty of RBC, Care Delia of Red Hat and Brittany Istenes of Fannie Mae, with the huge help of Rob Moffat, Jim St Clair and the energy bomb James McLeod. Even more – as the co-hair, I got to lead the FINOS Banks Only OSPO Roundtable. As the event is run according to Chatham rules, I cannot tell much more details about the roundtable beside the anonymized meeting notes at GitHub.

Another Session on “Why Going Open Source?” – Peter Smulovics, Morgan Stanley

Back in November, I had the luck and opportunity to get back to some level of normalcy for just a day – I got invited to present at Linux Foundation’s Open Source Strategy Forum about, wait for it, Open Source. What was it about? Here is the blurb:

It is always appropriate to challenge the need for a project to be open source, given the lack of foreknowledge of anyone else having a desire to use a platform versus the other possible options or their own proprietary one. While companies have the desire and the capability to support this if it comes to be, it’s not the primary motivation. With a foundational architectural aspiration of a pluggable platform, it’s important for it to be possible to selectively choose components from open source and if needed, from commercial vendors that make sense given your requirements. There is no reason for a company to own every line of code or to find something available that tries to meet all the needs. Vendors will always yearn to get their foot in the door and being open source accelerates and simplifies partnerships through increased visibility and collaboration without the red/yellow tape or proprietary integrations or NDAs. We have already seen this model work successfully with our projects as ongoing collaborative efforts with vendors to use and extend simply for their own (sales) demos to others.

So, without further ado, here is the recording:

Another Session on “Why Going Open Source?” – Peter Smulovics, Morgan Stanley

The success of this presentation lead to another small success – more about that later on 🙂

Arriving to… Crossroads

And another project just got opensourced by my team, this being called ‘Crossroads‘. It is a small nifty tool that enables to do something similar as self contained .NET Core applications are making possible – just this supporting other technologies than .NET Core, like Node.js applications or applications using more than one technology.

Crossroads itself is a .NET Core commandline tool, a kind of packager for developers. As mentioned above, this is a generic solution to host any application within Crossroads package executable and further launches application’s executable. Developers will specify arguments such as name, icon, version etc. for branding during the package generation. The specified argument name will be used to rebrand the internal application as needed.

So, in a nutshell, Crossroads allows you to:

  • create an executable package
  • customize your package with a name, icon, version and other attributes
  • run applications through crossroads generated package

Please, let me introduce

Another day – another open source project from my team, this time a small nifty tool called “please”, akin something that already been mentioned in one of the ADRs (ADR003):

- We would depend on using an eng/Dependencies.props file instead of having the versions of Nuget files
repeatedly entered into the csproj files
- We would use automated tooling to achieve the maintenance of Dependencies.props file

So, in the end, not only these, but a bunch of other small functionality has been added to this swiss knife of a tool that you can just ask to do stuff, nicely 🙂

It can easily:

  • Consolidate nuget packages across a solution, or only a subset of them
  • Keep package versions in a central props file and maintain that file
  • Move and rename projects
  • Clean up in case you manually moved and renamed
  • Clean up <Compile Remove="..." /> items, with or without globbing
  • To find stray projects
  • To remove ‘junk’ from solution directory
  • To change the PATH variable (useful when working with dotnet tools)
  • etc.

Using AD…what? ADR?

And the ADR for using ADRs is there in ComposeUI/adr-001-use-adrs.md at main · morganstanley/ComposeUI (github.com)


If you are watching the new repo, you might have spotted that the first few PRs are about adding a set of “ADR”s, Architecture Decision Records.


So you could ask, why? You could ask the same question, why a project is using X instead of Y – actually a new person joining a team definitely going to ask the question, why you using Entity Framework and not NHibernate? And believe me, most likely you would hand wave and say “for historic reasons” because you would absolutely not remember anymore. And that’s generally very unfortunate.

Documentation. Yes, I’m also a developer, and I also hate writing documentation. Who doesn’t hate that? Actually, I think, above a given age, when you are being told ‘documentation’ you do have a particular picture in your mind, which is books and books of lot of pages, probably bound together using twines called project documentation while still using Rational Unified Process or Microsoft Solution Framework like I did? Or the other way around, yes, there are tons of documentation, scattered among different systems, hosted off the code, in wiki or something – gets outdated the day you write it, not part of the source control, not structured (or rarely), therefore, why to write it at all, again?

So, documentation, why hate it, but can it be done better? I don’t think I ever started to like writing documentation, believe me. But writing Architecture Decision Records, following a certain scheme in them and keeping them in the same git as my code – that’s more of my liking, believe me. So, just to summarize, an Architectural decision is a software choice. One that addresses either a functional or a non-functional (like project structure – or the fact you do write ADRs!) requirement that is architecturally significant – framework choices, programming languages you choose, OSes you target, data storage, communication patterns, persistence, validation, logging, telemetry; you just name it. Of course, you should not take the term “architecture” too seriously or interpret it too strongly. I mean, look at not-that-recent update of ThoughtWorks’s radar when talks about ADRs: Lightweight Architecture Decision Records | Technology Radar | ThoughtWorks – they went from ‘trial’ in 2016 and speaking about evolutionary architecture to a mainstream adopt in just a few years. And they also suggest to store them in version control instead of wiki/website. Let me finish it with the sentence from the Radar: “For most projects, we see no reason why you wouldn’t want to use this technique.” So, our http://github.com/MorganStanley/ComposeUI is not different 🙂

Ok, so, where is the project?

I got a few people coming back to me after reading the previous post, Going opensource – why?, asking, OK, so, where is the project, how come the repo GitHub – morganstanley/ComposeUI is still empty?

I might have not written it clearly enough OR you might have not read clearly enough the previous post (most likely the former), so this time the idea is that the project would be developer in the open instead of playing a magician’s role with a rabbit and a hat – we wouldn’t just pull up a finished project without the reader understanding the steps we took to arrive to it, rather each discussion, each wrong idea, etc would be also developed and showed in the wild open.

I hope this helps regards some people who quickly just clicked through the link at the top of the previous post, waiting to see the actual project – yes, this is not exactly the case here 🙂

Going opensource – why?

Small update on Ok, so, where is the project? added as a separate post 🙂


I suppose you haven’t spotted yet – we just created a new opensource project, GitHub – morganstanley/Compose . It might worth explaining the why behind that choice.

It is always appropriate to challenge the need for a project to be open source, given the lack of foreknowledge of anyone else having a desire to use a platform versus the other possible options or their own proprietary one. While we have the desire and the capability to support this if it comes to be, it’s not the primary motivation. With a foundational architectural aspiration of a pluggable platform, it’s important for it to be possible to selectively choose components from open source and if needed, from commercial vendors that make sense given your requirements. There is no reason for a company to own every line of code or to find something available that tries to meet all our needs. Vendors will always yearn to get their foot in the door and being open source accelerates and simplifies partnerships through increased visibility and collaboration without the red/yellow tape or proprietary integrations or NDAs. We have already seen this model work successfully with other projects like desktopJS as ongoing collaborative efforts with vendors to use and extend simply for their own (sales) demos to others. While it is naïve to think they aren’t also doing this to make it easier for us to choose their platform. It has proven the usefulness of open source being successful in other ways than just marketing, recruiting or reuse by others. It is also a tool to better work with the industry to outsource or “buy” features off the shelf that give a commercial momentum with faster delivery. Having this project in the open is also useful to drive the roadmap of some companies by adding use cases that finserv developers need and expect.

Open source also provides us with innovative methods to explore different avenues of staff augmentation – e.g. working in an open manner eliminates the onboarding needs as well as associated overhead resulting in immediate participation and contribution.

A tangential benefit of being open source is keeping us free of binding ourselves unnecessarily to internal tooling and processes and implementation. By using off the shelf build infrastructure and GitHub capabilities we will be able to swiftly adopt and leverage industry leading DevOps tooling.

So what does open source mean to me? Whether you are operating on the cloud or on premises, you want to spend most of your time on solving the business problems in front of you, not on re-inventing the wheel of algorithms, APIs, pipelines, deployment and so on. Fortunately, we get to stand on the shoulders of giants by relying on robust well-maintained open source libraries or specialized vendor software, when appropriate. Most of the popular modern solutions work equally well on the cloud and in an internal infrastructure. In our view, .NET developers should be working on problems that are critical to the functioning of the company, and it’s the job of projects like this one to enable that focus by providing the functional foundational building blocks. We do help finding and creating the robust solutions to the generic problems so practitioners can remain focused on the aspects that are specific to their business. By developing battle tested code, harnessing the brain power within the OSS community and building relationship with selected vendors, we are able to provide the best-in-class tools and libraries for all .NET Developers. This amounts to less custom code scattered across, that becomes a technical debt, and results in an easier learning curve for anyone joining a firm – like ours.

Where customizations are required of other OSS projects, we promote contributing those changes back to the project on the firm’s behalf – this is in line with the overall firmwide OSS strategy.

We are doing .NET Core – .NET Core itself is a fairly young technology and the usage of it is also at the very beginning of its journey. Our mission, our approach and our thinking will evolve as .NET Core adoption matures and as the subject itself evolves. This will always be a collaborative effort and we do invite input from all of our constituents. This input allows us to be better informed and to better understand the needs of practitioners around the world. My group, my team will strive to be a resource for .NET Core expertise on desktop, cloud, software, vendor needs, advanced techniques, academic research and related topics. But for this, we need to go open source 🙂