Work and engineering decisions

Each case covers the context, the problem, what I was responsible for, the decision made and the documented outcome. Technical detail goes as far as possible without exposing client code or data.

The platforms were built in my work through Oxeanbits, for the company's clients. They are not direct personal contracts with each organization mentioned.

Platforms in production

Web systems built and evolved as part of a team, in my work through Oxeanbits.

Technical depth

Problems where the solution depends on language design, parsing and cross-platform integration.

C++ · WebAssembly · Compilers

Parsec: one formula language shared across platforms

Library development; individual WebAssembly version

When each platform interprets the same formulas on its own, the same calculation can produce different results.

Engineering decisions

Choices about readability, context and AI use that I carry from one project to the next.

Side projects and talks

Smaller public work that complements the cases.

  • victorcorcos/components-hierarchy (external site)

    A tool built on madge to inspect React JSX component relationships. It helps understand dependencies before changing an interface.

  • victorcorcos/pom-converter (external site)

    A Python macOS port of a song converter, based on analysis of the original Windows program. An example of investigation and interoperability.

  • victorcorcos/clean-code (external site)

    Principles, examples and signs of code that is hard to maintain. It grew out of the talks and applies to AI-generated code too.

  • victorcorcos/skills (external site)

    Reusable AI agent skills for Claude Code, Codex CLI and OpenCode: staged planning, review, BDD testing and bug investigation.

  • victorcorcos/winning-investments (external site)

    A personal Python project that applies strategies described by well-known investors to the Brazilian stock market. A programming exercise, not financial advice.

  • 2021 · Why Clean Code and BDD matter in automated tests

    Computing Week (SEMCOMP), UFBA · representing Oxeanbits. Why BDD matters in automated testing, with practical examples of tests that describe behavior.

  • 2024 · How to clean your code: Clean Code principles

    Computing Week (SEMCOMP), UFBA · representing Oxeanbits. Clean Code principles presented through code examples.

Does one of these problems look like yours?

Share the context and what needs solving. If it is a good fit, we can talk about development or technical consulting.

WhatsApp

+55 71 99705-3401

Opens WhatsApp with a starter message you can edit. Nothing is sent automatically.

You can also find me on GitHub and LinkedIn.