An oral history of financial software

The people behind
financial software.

Real stories from the people who built and maintained financial software.

Careers, unexpected incidents, difficult decisions, and lessons that deserve to outlive the systems themselves.

The collection

Conversations worth keeping.

In their own words.
For the next generation.

The conversation / No. 001

Elaine Richardson

From a chance opening as a trainee programmer to mainframe migrations and live support. Elaine reflects on a career spent working with the systems people depend on.

  • Mainframes
  • COBOL
  • Migrations
  • Error handling
  • Batch processing

“Bank’s back-end systems are full of exception handling, covering the exceptions consultants say will “never happen”, but that will happen day 1 of go live, usually with your biggest, most important customer.”

Elaine Richardson
Read the interview

The conversation / No. 002

Otilia Borges

From COBOL and Assembler at Banco Bradesco to the Collor Plan and mainframe modernization. Otilia reflects on preserving business rules, operational lessons, and a lifetime of learning.

  • COBOL
  • Mainframes
  • Collor Plan
  • Business rules
  • Legacy modernization
  • Generative AI

“When we migrate a system to a modern technology, we must make sure we don't accidentally change its business behavior or compromise the integrity of its rules.”

Otilia Borges
Read the interview

Only interviews approved for publication are listed here.

More than a record of the past

Why this archive exists

Real stories from the people who built and maintained financial software.

Before APIs, cloud platforms, and AI, engineers were already processing payments, reconciling accounts, recovering failed jobs, and keeping critical financial systems running. Much of what they learned never made it into a manual. It lives in the memories of the people who were there.

The FinKore Legacy Archive is a public collection of interviews with those professionals. It preserves their experiences in their own words, including the unexpected incidents, difficult decisions, hidden rules, and lessons that shaped financial software engineering.

This is not a museum of old programming languages. It is a record of knowledge that still matters.

FinKore works to make financial software behavior explicit and verifiable through CoreDoc → Specifications → Conformance → Implementations.

But specifications should not be invented in isolation. Real operational experience can reveal overlooked edge cases, assumptions, and failure scenarios worth investigating.

The archive has two equally important purposes:

  1. Preserve professional history. Recognize the people behind financial systems and make their experiences available to future generations.
  2. Inform better engineering. Identify questions and lessons that may inspire further research and discussion within FinKore.

An interview is not a FinKore specification, a conformance requirement, or proof that a particular technical approach is correct. Any proposed rule must go through the project's usual review and specification process.

The five questions

The interviews follow a short, conversational format. Participants can skip any question or expand on the stories that matter most to them.

  1. Tell us a little about yourself. How did your career as a developer start, and how did you end up working with banking or financial systems?
  2. What are you proud of? Is there a system, project, or technical challenge you particularly remember?
  3. What surprised you? Do you remember an unusual rule, piece of code, or situation that taught you something important?
  4. What changed? Have you been involved in replacing or modernizing a legacy financial system? What was hardest to preserve?
  5. What should we never forget? What lesson would you leave to the next generation of financial software engineers?

These are conversation starters, not a test. We value lived experience over polished or exhaustive answers.

Editorial principles

How we protect people's voices and their trust

Authenticity. We aim to preserve each interviewee's voice, including their opinions, humor, and personal perspective. We do not silently rewrite answers to fit a FinKore narrative. Any editorial introductions, summaries, or interpretations are clearly distinguished from the interviewee's words.

Consent and review. Interviewees review the proposed publication and approve it before it is added to the repository or shared through FinKore channels. Names, professional profiles, and other identifying details are published only with permission.

Confidentiality first. No participant is expected to disclose proprietary code, customer information, internal incidents, or other sensitive material. When a story raises confidentiality concerns, we omit the relevant passage rather than risk identifying people or organizations through partial redaction. Any omission is explained in an editorial note without revealing the omitted details.

Respectful preservation. We do not turn personal experiences into technical claims without additional examination. If an interview inspires an issue, discussion, or proposed specification, we keep that interpretation separate and link back only to material approved for publication.

Corrections and requests. Interviewees can contact the maintainers to request a correction, additional anonymization, or removal. Because Git preserves history, we will review sensitive-content requests carefully and explain what can be changed in the repository and its history. Publication elsewhere may require separate follow-up.

Share your story

Have you worked on banking, payments, accounting, insurance, financial operations, or related systems? Whether your experience involves COBOL, mainframes, RPG, Assembler, modern platforms, or something else entirely, your perspective may help preserve knowledge that would otherwise be lost.

You do not need to answer every question, and you do not need to share confidential information.

Start with the Legacy Interview discussion, or reach out to the project maintainer to arrange an interview privately.

Reading and sharing

Approved interviews are available here in the repository and may also be featured on finkore.dev. You are welcome to share public interview links and credit the people whose experiences made them possible.

The systems may change. The lessons should not disappear.

About the archive source

Interviews are kept as individual Markdown files in interviews/.

New to FinKore?

Experience starts the conversation.

FinKore is an open-source specification for predictable, auditable, portable financial software behavior. The archive preserves professional history and brings real experience into the conversation.

Interviews are personal accounts. Any proposed financial rule follows the project's specification and review process.

Get to know FinKore
View Markdown source ↗Back to the top ↑