Mattias Hising
Software Engineer
Action-oriented, business-driven and "people first" Software Engineer. 25+ years of experience building products on the web, apps for mobiles, and games for PC, console and mobile. I prefer Open Source over proprietary software. I love products that solve a real problem for users — and I believe the only way to know if you're actually solving it is to measure it.
Now
-
Reading
"Mina drömmars stad" by Per Anders Fogelström
City of My Dreams (English title). Stockholm, Södermalm, 1860-1880.
-
Listening
Swedish history podcast
-
Playing
Candy Crush
Still fun.
-
Side project
Working on a native app and better live-ops.
-
Watching
A Knight of the Seven Kingdoms
Game of Thrones prequel
-
Thinking
Political science, incentives, and Rawls' veil of ignorance.
-
Running
Arch Linux
btw
Principles
- Titles do not make arguments better.
- If we are not measuring it, we are mostly guessing.
- Teams move faster when information is shared, not hoarded.
- Ship small, learn fast, and let reality win the argument.
- The people who carry the risk should carry the upside.
Built / Shipped
-
Battlefield companion experiences
Companion web/mobile products, telemetry architecture, analytics.
-
Internal tools for experiments and feature testing in game teams.
-
Launch team. Social features in the iOS/Android app (React Native).
-
AAA game and live-ops internal tools
Tooling for playtests, tracking, and faster iteration in game teams.
-
Independent product. Native app + better live-ops.
I work with teams that need a senior engineer / engineering lead to steady delivery and improve decisions.
How I work →Recent posts
- Fotbollsfeber: What I've Actually Been Building
A look under the hood of fotbollsfeber.se — refactoring an old codebase, building a Stryktipset probability engine, and what side projects are actually good for.
- TIL: zoxide is absurdly good
A short TIL on zoxide: a smarter cd, how it learns paths, and a small alias trick that made it fit my zsh setup.
- How I Run a Technical Audit (and What Teams Usually Miss)
A practical look at what a technical audit should cover, where audits often fail, and the outputs that help teams make better decisions.