Fabian Schmied

I'm now employed by SignPath GmbH, still working as a Software Architect on SignPath.io, a SaaS platform for digital code signing, and its on premises version. We employ Domain-Driven Design and the CQRS and Event Sourcing architecture patterns to create a business-relevant, reliable, trustworthy, and scalable product. We're using C#/.NET, Azure, ASP.NET Core, cryptographic APIs, Hardware Security Modules, and SQL Server; blue/green deployments, asynchronous queues, Kubernetes, and REST APIs.

I'm now fully focusing on the Software Architect role on the SignPath team. We are still working on SignPath.io, a digital code signing platform, and its on-premise version. We employ Domain-Driven Design and the CQRS and Event Sourcing architecture patterns to create a business-relevant, reliable, trustworthy, and scalable platform. We continue to use C#/.NET, Azure, ASP.NET Core, cryptographic APIs, Hardware Security Modules, and SQL Server; blue/green deployments, asynchronous queues, and REST APIs.

For six months, I was on educational leave, enrolled at the TU Wien for a set of lectures mostly on social and interpersonal skills. Additionally, I supported the SignPath team as a part-time Software Architect for a few hours per week.

In 2017, my team joined with the SignPath team. Together, we're working on SignPath.io, an online platform for digital code signing. We're using our experiences with Domain-Driven Design, CQRS, and Event Sourcing in order to create a business-relevant, reliable, trustworthy, and scalable platform. We use technologies such as C#/.NET, Azure, ASP.NET Core, cryptographic APIs, Hardware Security Modules, and SQL Server. Blue/green deployments, asynchronous queues, and REST APIs are also thrown into the mix.

In 2013, I changed my job at RUBICON IT, building a new team creating a product aligned with modern software architecture approaches. For it, we researched and implemented the CQRS and Event Sourcing architecture patterns. Together with my team, I worked in both product and project development in an agile and very successful way. Technology-wise, we used C#/.NET, WCF, NEventStore, ASP.NET MVC, HTML 5/CSS 3, jQuery, and SQL Server, among other tools and technologies.

I was one of the two lead developers of the open source "re-motion" enterprise application framework. Notable components that I was responsible for include re-linq (a foundation for building LINQ providers), re-mix (an implementation of "mixins" for .NET), and the TypePipe (a foundation for metaprogramming technologies), all of which can be found on CodePlex and/or GitHub. Working on these components was very low level, involving many .NET/CLR internals, and I learned a lot about framework development.

This was just a part-time job I was doing in parallel to my graduate studies. I maintained an older PHP system for exam registration management, wrote a handbook on the AMD64 assembler, and assisted professors in other tasks.

While studying for a PhD degree, I was tutor for two courses: Distributed Computing with Space-Based middleware and Logic-Oriented Programming (Prolog, CFD).

This was a holiday job in parallel to my graduate studies. I did .NET software development in the financial sector, writing tick data feed import services, and data processing software.

I created software for medical testing purposes for the neuropsychiatric department of the University of Munich with C# (.NET 1.1), Windows Forms, DirectX and ADO.NET.

I began as an intern and then wrote my thesis at the Siemens research institute CT SE 2. We researched aspect-oriented programming in the .NET environment, my specific contribution was a library for analyzing and manipulating .NET metadata from unmanaged code for AOP purposes and a proof of concept for an AOP weaver based on the .NET profiling API.

During a summer internship, I did some Photoplay game machine programming and database engine development with C++.

Aspect-Oriented Programming, Distributed Systems