Skip to content
CN2.DEVBUKYA NARESH

ABOUT / IDENTITY / 001

I THINK INSYSTEMS.I BUILD WHAT'SPOSSIBLE.

I'm Bukya Naresh. My interests span quantitative finance, intelligent automation, software engineering, data infrastructure, and computational decision-making.

I explore how these disciplines connect — and how complex ideas can become useful, measurable, and increasingly automated systems.

SCROLL TO EXPLORE

SECTION / 002THE WAY I THINK

I DON'T JUST LOOK AT THE PROBLEM.I LOOK AT THE SYSTEM BEHIND IT.

I want to understand why something happens, which variables influence it, how its components interact, and what would make a solution reliable. Whether the subject is a market, a data problem, a piece of software, or an AI workflow — the underlying logic comes before the approach.

Ask what the actual problem is before reaching for a tool.

What causes it? Which variables matter? What information exists? What assumptions are being made, and what could fail?

SECTION / 003CAPABILITY ARCHITECTURE

DIFFERENT DISCIPLINES.ONE CONNECTED DIRECTION.

I work toward connecting financial understanding, quantitative reasoning, software, data, and intelligent automation. Select any discipline to see what it means, the problems it addresses, its status, and the work that supports it.

CAPABILITY

Quantitative Finance & Research

Mathematical and data-driven investigation of financial questions — strategies, risk, and the evidence behind them.

PROBLEMS IT ADDRESSES

  • Strategy hypotheses and how to test them honestly
  • Backtesting, simulation, and the limits of historical results
  • Risk, drawdown, and performance measurement
RESEARCH DIRECTIONREAD THE RESEARCH
SECTION / 004FROM THINKING TO EXECUTION

IDEAS ARE THE BEGINNING.SYSTEMS MAKE THEM USEFUL.

One process connects the disciplines: reasoning to implementation, implementation to evidence — follow it as you scroll, or select any stage directly.

01 — PROBLEM

Understand the actual requirement before choosing a technology.

SECTION / 005HUMAN DIRECTION · INTELLIGENT EXECUTION

I DEFINE THE DIRECTION.AI ACCELERATES THE EXECUTION.

I see AI as a way to extend human capability — never a replacement for understanding the problem. The objective, the constraints, and the final decision stay human; verification determines whether the work earns trust.

01 — HUMAN INTENT

I define the problem and decide what actually matters.

SECTION / 006WORKING PRINCIPLES

BUILD WITH INTENT.MEASURE WITH EVIDENCE.

The standards I want my work to reflect — not slogans, but the criteria results are held to.

  1. 01

    UNDERSTAND BEFORE BUILDING

    Investigate the problem, its causes, and its constraints before choosing a solution.

  2. 02

    EVIDENCE BEFORE CLAIMS

    Test assumptions, measure results, and state limitations as plainly as successes.

  3. 03

    SYSTEMS OVER SHORTCUTS

    Understand how components interact — not only how a single tool behaves.

  4. 04

    AUTOMATE WITH CONTROL

    Reduce repetitive work without abandoning verification or accountability.

  5. 05

    LEARN THROUGH IMPLEMENTATION

    Connect theory to practice; let failures identify what needs strengthening.

  6. 06

    COMPLEXITY WITH PURPOSE

    Build sophisticated systems when the problem justifies them — never for show.

SECTION / 007THE LONG-TERM DIRECTION

FROM INDIVIDUAL TOOLSTO INTEGRATED INTELLIGENT SYSTEMS.

My long-term direction is to develop the knowledge and practical capability to build increasingly sophisticated systems that connect data, computation, decision-making, and automation — moving beyond isolated technologies toward complete, useful solutions.

QUANTITATIVE SYSTEMS

Complete research and trading infrastructure — from hypothesis to measured result.

A DIRECTION I AM DEVELOPING — PIECE BY PIECE.

SECTION / 008LET'S BUILD SOMETHING USEFUL

DIFFERENT PERSPECTIVES.MEANINGFUL PROBLEMS.USEFUL SYSTEMS.

I am interested in opportunities to apply structured thinking, software, data, research, and intelligent automation to meaningful technical problems. Whatever the perspective, the first step is the same: understand the problem and determine whether there is a useful way to solve it.

BUKYA NARESH

CN2.DEV — QUANTITATIVE DEVELOPER

CONTACT