Barış Nişancı

In short

I'm a computer engineer and data management engineer, and I build systems where low-level hardware mechanics, data pipelines and modern web architectures collide. That ranges from firmware on STM32 microcontrollers driving industrial motors, to production data pipelines, to type-safe TypeScript monorepos and native mobile apps. What ties it together is architecture: designing clean seams so any one piece of a system can be replaced without breaking the rest.

Focus areas

Three areas where I do my best work — and where I would want to be hired.

Skills

Grouped by the kind of problem they solve, rather than by logo.

Selected work

Four projects that show the range — hardware, automation, product and architecture.

• The Browser Shell

  A working terminal that runs entirely inside your browser, built as three separate layers: the screen you see, the engine that understands what you typed, and the runtime that executes it in the background. None of the three knows how the others work, so any one of them can be swapped out without touching the rest. Adding a brand-new command takes exactly one new file.

  TypeScript · Layered architecture · Web Worker runtime · Monorepo

• Industrial Sim-Racing Hardware

  A high-end direct-drive steering system for sim racing, built from scratch. Direct drive means the motor is connected straight to the wheel with no gears in between, so every bump in the virtual road arrives in your hands unfiltered. Industrial AC servo motors do the pulling, STM32 microcontrollers do the thinking, and custom sensor integration ties the two together — all of it designed and assembled rather than bought off a shelf.

  STM32 · Embedded firmware · Industrial AC servo · Sensor integration

• Instant Quote Automation Engine

  A specialized production web application that calculates pricing directly from technical engineering drawings. The work it replaces is slow and manual — someone reading each drawing and quoting by hand. This does it on the spot, consistently, every time. The hard part was never the interface; it was turning engineering data into logic a machine can read correctly.

  Production web app · Automation · Engineering drawings · Pricing logic

• Mondus

  A native mobile app for strength training, built around progressive overload — the simple idea that you add a little more weight or a few more reps each session, and something has to keep track of that. The priority is speed: logging a set between rounds should never make you wait for a screen. Built natively rather than wrapped in a browser, because the difference is felt in the hand.

  React Native · Native performance · Mobile · Product design

How I work

I usually start by drawing the boundaries: which part has to know what, and which part must not. A boundary drawn well turns a later change from a rewrite into swapping one piece out. That is why I prefer solutions you can build on over solutions that ship fast and then have to be replaced.

Contact

The fastest way to reach me is email. I read everything.