I build things, fix weird systems, and occasionally adopt problems that probably were not supposed to become my responsibility.
I'm a software engineer in Rotterdam, the Netherlands, with C# / .NET as my strongest home base.
I enjoy getting dropped into an unfamiliar or poorly documented systems, figuring out where the actual problem lives, and owning the result.
I prefer hands-on engineering over management-as-an-identity. Architecture and technical responsibility are great; spending the entire week in meetings is considerably less legendary.
main class Software Engineer
main hand C# / .NET
quest type Complex & poorly documented systems
passive Learns unfamiliar systems quickly
alignment Working software and measurable outcomes
| Project | What it is |
|---|---|
| Engineering Portfolio | Production systems, integrations, preservation work and interactive software — with commercial work sanitized where confidentiality requires it. |
| Twitch Package Visualizer | A local-first browser tool that parses Twitch data exports and turns them into useful stats without uploading the archive anywhere. |
| Anubis / A1 Taal Café | A privacy-conscious Dutch speaking coach using multiple speech-recognition passes, consensus and supportive evaluation. |
| Phoenix Project / Nekrova | A volunteer game-development project that grew into a playable Unreal Engine prototype, technical leadership work, and a useful lesson in sustainable scope. |
More case studies live in the project archive.
Core
C# · .NET / ASP.NET · C++ · TypeScript / JavaScript · Flutter / Dart
Backend / integration
REST · SignalR · Azure Service Bus · Azure Functions · SQL Server · Redis · MongoDB · JWT
Systems / tooling
Linux · Docker · Git · CI/CD · Nginx · PowerShell · Bash
Interactive / game development
Unity · Unreal Engine · Android · iOS
- Understand the system before worshipping the stack. The right fix is often one layer away from where the symptom appears.
- Prefer boring reliability over clever fragility. Clever is allowed when it earns its keep.
- Build for operation, not just the demo. Deployment, monitoring, failure modes and maintenance are part of the feature.
- Treat confidentiality as engineering work. Public case studies describe architecture, ownership and outcomes without leaking customer data, source or secrets.
- Keep making things. Production software, preservation work, tiny tools, game systems, weird experiments - useful curiosity compounds.
- Portfolio: https://harleyknd1.github.io/portfolio/en/
- Twitch Package Visualizer: https://harleyknd1.github.io/twitch-visualizer/
- GitHub: https://github.com/harleyknd1
- LinkedIn: https://www.linkedin.com/in/harleylafeber/