GitHub
Portfolio · Software · Automation · Technical Systems

Jean Johnsen

Software, automation and technical systems that have to keep moving outside the screen. The goal is dependable operation with less drag between people, process and equipment.

tipatek automation SIMAC Novo Nordisk Adidas / Team Danmark
Selected Work

Projects that remove drag from the handoff

The common pattern is the same whether the output is software or a physical side quest: observe the workflow, identify the friction, and leave behind a more useful layer.

Tooling

jGit

A personal Git client focused on fast state overview and safer daily repo work.

Athlete data

LactateLab

Turns raw lactate data into something coaches and athletes can actually use.

Automation

GF2Discord

Routes form submissions directly into Discord so nothing waits in a dead inbox.

Simulation

SmoothLife

A continuous-life simulation exploring behavior, emergence and algorithmic texture.

Game AI

ZergOnThis

A Brood War bot shaped by timing windows, pressure and real-time tradeoffs.

3D side quest

GPS Outfront Mount

A utility-first 3D print built to stay rigid, ride clean and simply do its job.

Approach

Read the system. Remove drag. Build the useful layer.

Observe workflow
Find friction
Clarify state
Ship dependable tooling

Working principles

  • Understand the real handoff before designing the fix.
  • Prefer explicit state over clever hidden behavior.
  • Make the next action obvious for the person using the system.
  • Keep the layer useful even when the environment is messy.

What I try to avoid

Dashboards that decorate uncertainty, interfaces that hide the real state, and automation that looks smooth until reality touches it.

What I optimize for

Useful defaults, clear states, calm operation and tools that still make sense when people are tired or under pressure.

The best technical layer is usually the one that makes the system feel less dramatic, not more.
Career and Studies

Code, process and performance under one roof

The path runs through software, operations, engineering studies and elite sport, but the underlying thread is still systems thinking.

2025 — now

tipatek automation

Junior Automation Engineer working where software, PLC logic and physical equipment meet.

2022 — 2025

Novo Nordisk

Process optimization and IT projects with a strong bias toward dependable operation.

2025 — present

SIMAC

Technology Management and Marine Engineering in Svendborg.

2021 — 2022

Freelance Software Architect

Hands-on software work with architecture decisions that had to stay readable.

2016 — 2020

BSc Computer Science

University of Southern Denmark, with the technical foundation still visible in current work.

2017 — 2020

Elite Athlete

Adidas and Team Danmark. High-performance structure, pacing and execution under load.

Sports

The athletics chapter is part of the same operating system

Jean Johnsen during his athletics career
2017 — 2020

Adidas, Team Danmark and the 800m years

Before software and automation full-time, there were years of national and international middle-distance competition.

2023 — 2025

BHS-PL Beton Cyclist

Transitioned into cycling after my athletics career where i rode in the danish A category.

Transfer to engineering

  • Preparation matters more than drama.
  • Consistency beats noise over time.
  • Execution under pressure is trainable.
  • Feedback loops only work if you respect them.
Contact

Open loop, low friction

If there is a project, role or problem space where software, process and real-world execution overlap, that is usually where the conversation gets interesting.