class me {
public:
char* name = "Cristian Recabarren Madrid";
char* role = "Founder & CEO @ Flō Finanstic";
char* focus = "Software Architecture | FinTech | Personal Finance";
char* email = "cristian@flofinanstic.com";
char* linkedin = "linkedin.com/in/crecabar/";
char* github_org = "github.com/flofinanstic";
};I'm currently building Flō Finanstic, a personal financial planning platform designed around a simple idea:
Knowing how much money you have is not the same as knowing how much you can spend.
Flō helps people turn the money they already have into a plan for their priorities, commitments and goals, so they can make financial decisions before spending, rather than discovering the consequences afterwards.
The platform is currently evolving through a private beta while I work on its product, architecture and financial domain model.
My main technical focus is the architecture of Flō:
- Framework-independent domain model
- Clear
Domain / Application / Infrastructureboundaries - Dependency inversion around persistence and external services
- Transaction and budgeting domain modelling
- Automated architecture guardrails
- High test coverage and static analysis
- Incremental extraction of framework concerns from the application core
The long-term objective is to make the financial core independently evolvable from the frameworks and delivery mechanisms around it.
Areas of interest:
- Domain modelling
- Clean architecture
- Hexagonal architecture
- Dependency inversion
- Automated testing
- Static analysis
- Financial software
- Distributed systems
I also have a long-standing interest in low-level systems programming, operating systems and software architecture beyond application frameworks.
The source code and technical assets of Flō are maintained under the Flō Finanstic GitHub organization.
Current repositories include:
flo-app— main Flō applicationflo-wp— public website and documentationflo-core— experimental/future framework-independent core
The current architectural refactor is being performed inside flo-app. flo-core is intentionally not being extracted prematurely; the stabilized architecture will determine what eventually belongs there.
|
|
|
- Email: cristian@flofinanstic.com
- LinkedIn: https://www.linkedin.com/in/crecabar/
- Flō Finanstic: https://flofinanstic.com/
- GitHub Organization: https://github.com/flofinanstic



