AcademyAcademyWritten by practitioners across the industry. Clear, useful, and free of filler.
Liquidity risk moves in hours, and no single team holds the full picture. Here is who runs the position, who challenges it, who signs off, and why coordination is the real control.
Transactional leadership gets dismissed as cold or mechanical, but in treasury and regulatory reporting it is often the most professional thing you can offer your team. This post explains what it actually is, where it earns its place, and where you need to add something else.
Constants prevent silent bugs, make regulatory thresholds explicit, and transform magic numbers into readable code. Learn how to use them properly in finance calculations.
Variables are how you store and update positions in Python, just as you track them in a treasury system. Learn to assign, name, and update variables so your finance code is clear, maintainable, and reflects real positions.
A direct, weighted comparison of Tableau and Qlik Sense for finance and analytics teams in 2026, covering architecture, AI, governance, cost, and implementation realities. Vendor marketing will not give you this; a practitioner will.
Liquidity risk is not one number but five distinct risks that feed each other under stress. This post breaks down funding, market, contingent, intraday and structural risk, and shows how a small problem chains into a crisis.
Bass's four component model of transformational leadership gives finance and treasury managers a concrete framework for moving teams through regulatory change and uncertainty. This post breaks down each component with specific examples from treasury, risk, and regulatory reporting work.
Print is your window into what your code is actually doing. In finance work, where a single error cascades through reports, print is not optional—it's your primary tool for validating logic before it goes live.
Good comments signal assumptions and protect your code from breaking when someone else reads it. Learn when to comment, what to say, and how to build the habit so your code is safe to hand over and clear enough to audit.