Software Engineering

Why software projects become unpredictable when user expectations and developer assumptions diverge, and how lightweight engineering practices make projects easier to steer.

How Kanban boards make work visible, keep tasks small, and give developers, managers, and customers a shared view of project progress.

Git, branching strategies, tags, pull requests, and commit discipline: how a version control system becomes the source of truth for a software project.

How test-driven development turns use cases into repeatable checks, clarifies unit, integration, system, and acceptance tests, and gives teams confidence to change and release software.

How peer review catches bugs before users do, spreads knowledge across the team, and keeps code maintainable through clear author and reviewer responsibilities.

How engineers can use storyboards and wireframes to turn use cases into concrete user flows, UI decisions, and reviewable screens before writing frontend code.

How to ship software with versioning, CI/CD, release artifacts, changelogs, smoke tests, rollback planning, and a repeatable release checklist.

Why floating-point numbers are wrong for prices and money, and how fixed-point integer types in Go eliminate rounding errors in financial calculations.

How to design a strategy interface that runs identically in simulation and live trading — separating business logic from execution so strategies can be developed, tested, and deployed without modification.