Mika Vale/ software developer

Independent thinking. Practical software.

Software, with
a sense of
direction.

I’m Mika. I explore the space between moving things and useful information — maps, telemetry, and small tools that make complex systems easier to understand.

Explore the work
C# / .NET · TypeScript · GISAlways curious.
FIELD STUDY / 001Route, reconstructed
An abstract map with a route through a lake district A drawn landscape with contour lines, water, a highlighted route and three waypoints. Illustrative geography, not a real journey. 02 / TELEMETRY03 / ARRIVAL01 / DEPARTURELAKE N
A signal becomes a story.Synthetic route · illustrative map
01 — 03
POINTS OF VIEW
Thinking in systemsBuilding for peopleLeaving things clearer

01 / Selected explorations

From raw data
to a clearer picture.

Small, focused design studies. Each starts with a question and ends with something you can reason about.

◈ TRACE / EVENT TIMELINEDEMO DATA
Journey startedPosition acquired
Signal interruptedKeep the last known state
Back in viewEvents reconciled

Signal quality Sample

Missing data is information, too.

Telemetry / Interface study

Trace

A quieter way to read a vehicle’s journey. Bring positions, device events and gaps into one timeline — without pretending every coordinate tells the whole story.

C# & .NETPostgreSQLMaps
Read the design note +

Store the device timestamp and the receive timestamp separately. Late packets should correct the timeline, not rewrite what the operator knew at the time. Mark uncertain stretches explicitly, and avoid drawing a confident line through a long signal gap.

Source→Observe
understand first→Explain

Desktop / Workflow study

Small tools. Less guesswork.

A desktop diagnostics concept that turns scattered network checks into a readable sequence. State, timestamps and evidence belong together.

WPFAsync workflows
Read the design note +

A useful diagnostic should distinguish “not checked”, “unreachable” and “checked successfully”. Keep long operations cancellable, retain the last result, and make it clear when that result was collected. A spinning indicator is not a status model.

Astronomy / Personal tool study

A notebook for clear nights.

An observation log built around what you actually saw: sky conditions, instrument, eyepiece and a few words worth remembering.

Local-firstSimple data
Read the design note +

Keep the original observation alongside structured fields. Seeing and transparency are different conditions; magnification alone says little about the view. Export plain text and CSV so the notes remain useful without the application.

02 / Field notes

A few things
I build around.

Working principles, not a manifesto.

01

Offline is a real state.

Keep the last good configuration. Show its age. Let a failed refresh remain a failed refresh, rather than turning it into a broken application.

02

Maps need a sense of uncertainty.

A line on a map is an interpretation. Sampling intervals, accuracy and missing messages deserve to be visible, not smoothed away.

03

Good tools explain themselves.

Prefer specific states over generic errors. Show what happened, when it happened and what the user can do next.

03 / Behind the notebook

Curiosity is
the common thread.

I like practical systems: the ones that connect a physical world to a screen, and a confusing situation to an understandable next step.

This notebook lives at the intersection of desktop development, geospatial data and observation. Sometimes the subject is a device on a map. Sometimes it is a faint object in the night sky. Either way, the interesting part is learning to look carefully.

Main tools.NET · SQL · TypeScriptOutside the editorMaps · Telescopes · Field notes

Mika Vale is a creative alias. The projects shown here are independent concepts and interface studies, using illustrative data.