TAKE A LOOK AROUND

03 / Data engineering / Visual interfaces SELECTED WORK

DataFlowX

Think in flows. Work with data.

PROJECT STUDY
2026
INPUT DATASETVISUAL GRAPHPROCESSINGPREVIEWDataFlowXONE CONNECTED SYSTEMINPUT DATASETVISUAL GRAPHPROCESSINGPREVIEWDataFlowXONE CONNECTED SYSTEM
INPUT / PROCESS / APPLICATION / HUMAN CONTEXT
MY CONTRIBUTION

Independent graph interface, frontend state management, processing contracts, and Python data-operation exploration.

PROJECT STATUS

Independent project · In development

01 / THE IDEA

The flow should explain the work.

02 / THE PROBLEM

A sequence of scripts can hide the logic.

Small data transformations often turn into hard-to-follow scripts. A visual workflow should make the sequence, configuration, and output of each step easier to understand.

The visual graph and the executable graph have different jobs. Node positions belong to the interface; operation types, dependencies, and configuration belong to the processing contract.

DataFlowX: data starts with a schemaLoose CSV and JSON papers sit behind a tabular source sheet with named columns and illustrative rows. The known schema is the first input to a visual data workflow.01 / THE RAW MATERIALSOURCE / CSVDATASET / SAMPLEITEMREGIONVALUEANORTH24BWEST18CNORTH32DEAST—ROWS + SCHEMA / EXPLICIT INPUTS
PROJECT CONCEPT / EDITORIAL ILLUSTRATION
03 / THE APPROACH

Make each operation explicit.

A visual data-processing platform connecting a React workflow interface to Python, FastAPI, and Pandas. This portfolio includes a self-contained browser demo using synthetic data.

DataFlowX: a graph with an execution contractA branching pipeline routes a dataset through filter, transform, and group operations. Configuration, validation, and dependency connectors describe the work rather than decorative node positions.TRANSFORMATION PLAN02 / MAKE THE LOGIC VISIBLE01 / FILTERvalue IS NOT NULL02 / TRANSFORMnormalize(value)03 / GROUPBY region / SUM valueVALIDATE FIRSTDEPENDENCY GRAPHCONFIGURE → VALIDATE → PROCESS
PROJECT CONCEPT / EDITORIAL ILLUSTRATION

My part in the project.

  1. 01

    Built a node-based interface around explicit data operations.

  2. 02

    Separated graph layout from operation configuration and execution state.

  3. 03

    Explored graph serialization, validation, and preview behaviour.

04 / THE CONNECTED SYSTEM

A visual graph with an explicit execution contract

A sequence of clear responsibilities. Select a stage to inspect its role in the project.

CONNECTED PROJECTDataFlowX
LAYER 01

Input dataset

A dataset provides rows and a known schema.

05 / DECISIONS & CHALLENGES

The details between the pieces.

01

Keeping drag position updates separate from processing state.

02

Rejecting invalid configurations before execution.

03

Showing intermediate data clearly.

Workflow scope

Node selection / Operation configuration / Graph validation / Sample previews / Workflow serialization

06 / THE PRODUCT FLOW

One sequence.
Clear responsibilities.

A visual data-processing platform connecting a React workflow interface to Python, FastAPI, and Pandas. This portfolio includes a self-contained browser demo using synthetic data.

Dataset → Filter → Transform → Group → Output

01 / THE FLOW

Input dataset

A dataset provides rows and a known schema.

02 / THE FLOW

Visual graph

Nodes describe filters, transformations, grouping, and output.

03 / THE FLOW

Validation

Validate required configuration and graph dependencies.

04 / THE FLOW

Processing

FastAPI and Pandas are the backend project direction; the portfolio runs locally in the browser.

05 / THE FLOW

Preview

Inspect intermediate state and output without hiding validation failures.

07 / RESULTS & CURRENT STATUS

See the steps. Understand the result.

In development. The portfolio demo processes its small synthetic dataset in the browser and simulates execution stages; it does not connect to a production data backend.

WORK IN PROGRESS

Independent project.
In development.

VISIT MY GITHUB PROFILE
DataFlowX: inspect the outputA folded result sheet shows a grouped dataset, a schema checklist, and an export symbol. Intermediate previews remain visible while sample data is processed.OUTPUT DATASET03 / UNDERSTAND THE RESULTOUTPUT / GROUPED DATAREGIONSUM / VALUENORTH56WEST18SAMPLE RESULTSCHEMA VALIDATEDSTEPS INSPECTABLEPREVIEW / NOT A PRODUCTION DATASETINTERMEDIATE STATE / A USEFUL OUTPUT
PROJECT CONCEPT / EDITORIAL ILLUSTRATION

THE TOOLS BEHIND IT

Python / FastAPI / Pandas / React / TypeScript / React Flow / PostgreSQL

Explore the interactive preview

Representative interface built for this portfolio with synthetic data and local browser state.

08 / WHAT GOOD LOOKS LIKE

The goals guiding the work.

Three qualitative design goals for DataFlowX, drawn from the project’s scope and engineering decisions.

DESIGN GOAL / 01LOGIC

Make the steps explicit.

Represent operation types, dependencies, and configuration separately from visual node positions.

DESIGN GOAL / 02PREVIEW

Expose intermediate state.

Let a reader inspect the data between operations as well as the final output.

DESIGN GOAL / 03VALIDATION

Explain what needs attention.

Check required configuration and graph dependencies before processing a workflow.

NEXT PROJECT / KEEP EXPLORINGConnect

Good work starts with a conversation.

WORKSPACE ACCESSCHANNELSSHARED DATAWORKSPACE UIConnectONE CONNECTED SYSTEMWORKSPACE ACCESSCHANNELSSHARED DATAWORKSPACE UIConnectONE CONNECTED SYSTEM
INPUT / PROCESS / APPLICATION / HUMAN CONTEXT