# Oleg Schalginski

> Oleg Schalginski is an independent technical advisor working with founders, technology leaders and investors on high-stakes software architecture, technical due diligence, transaction-critical systems and technology-asset decisions.

The site is written in English. Positioning is problem-first and evidence-led. The appropriate role, scope and form of engagement are determined only after understanding the actual system. Client names and sensitive operating details are intentionally omitted because much of the work is confidential.

## Core positioning

- [Home](https://schalginski.de/index.html.md): Independent technical judgement for high-stakes software decisions.
- [About](https://schalginski.de/about.html.md): Background, technical depth, working principles and professional positioning.

## Audiences and contexts

- [For Founders](https://schalginski.de/founders.html.md): Moving from fast MVP development to a durable company foundation.
- [For Investors](https://schalginski.de/investors.html.md): Technical due diligence, asset durability, scaling economics and remediation exposure.
- [Critical Systems](https://schalginski.de/critical-systems.html.md): Architecture, runtime behaviour, recoverability and control in systems carrying financial or operational responsibility.

## Evidence and writing

- [Selected Work](https://schalginski.de/selected-work.html.md): NDA-safe evidence from transaction systems, trading infrastructure and institutional financial platforms.
- [Insights](https://schalginski.de/insights.html.md): Essays on architecture, technical risk, AI-accelerated engineering and better decisions.
- [A Working MVP Is Not the Same as a Technology Asset](https://schalginski.de/insight-mvp.html.md): Why a working MVP does not by itself establish software durability, architectural control or investment quality.
- [AI Has Changed What Investors Should Ask About Software](https://schalginski.de/insight-ai-investors.html.md): How AI-assisted development changes the evidence investors need when evaluating software durability, control and economics.
- [More Code Is No Longer the Scarce Resource](https://schalginski.de/insight-code-scarcity.html.md): Why implementation volume is becoming less scarce while architectural judgement, verification and coherent change remain constrained.
- [What Founders Should Verify Before Scaling an AI-Built Product](https://schalginski.de/insight-ai-built-product.html.md): A founder-focused verification framework for moving an AI-built product from rapid validation to durable company infrastructure.
- [Why Passing Tests Does Not Prove Financial Correctness](https://schalginski.de/insight-financial-correctness.html.md): Why conventional test success is incomplete evidence for transaction, ledger and financial-system correctness.
- [Technical Debt vs. Material Business Risk](https://schalginski.de/insight-technical-debt-risk.html.md): How to separate maintainability concerns from technical exposure that can materially affect a business decision.
- [The Architectural Decisions That Become Expensive Only After You Succeed](https://schalginski.de/insight-expensive-after-success.html.md): How to identify architecture decisions whose cost appears only after customers, data, integrations and teams accumulate.
- [Why Independent Technical Judgement Matters Before an Irreversible Decision](https://schalginski.de/insight-independent-judgement.html.md): Why consequential technology decisions benefit from evidence-led judgement that is independent of delivery incentives and internal positions.

## Optional

- [Contact](https://schalginski.de/contact.html.md): How to start a confidential exploratory conversation.
- [Full site context](https://schalginski.de/llms-full.txt): Concatenated Markdown context for the main public pages.