Göteborg, Västra Götaland, Sweden
Mattias has been working professionally as a developer for 20 years.
His interest in coding started already in the 80s with the Commodore 128 and the true passion came with the Amiga.
Today he's a partner and senior architect at WCOM, a Microsoft partner located in Gothenburg, Sweden.
He’s also a Microsoft Azure MVP, a Microsoft Developer Technologies MVP and a member of the OzCode Magician community.
Outside work he a father of two, husband of one and contributes actively to the .NET open source community.
Most know there for being one of the lead maintainers behind the .NET foundation project Cake.
Redone to a panel
In this session Mattias will share an opinionated view of what it takes to be a good citizen in the open source community, not only how to contribute, but also how to be a good consumer and maintainer of open source.
These are opinions and advice based on experience gained by years of contributing to and maintaining popular (and unpopular) open source projects.
What are the unwritten rules? How do we communicate with people we never seen or met? What are the pitfalls? What methods, tools and services can make our lives easier? How we reach out with our expectations? – a few among the questions we'll try to answer, raise awareness and trigger discussion around.
Build and release configuration as code has become the de facto way for most continuous build and release solutions on the market today. Most commonly this manifests itself through a custom task-based domain-specific language using YAML or JSON files.
But wouldn't it be nice if you instead of using a markup language, could use a proper programming language, with already well-defined and documented control structures, flow statements like for, white, do, etc.
This session will step by step go through how you using C# can orchestrate your GitHub Actions build and release pipelines.
A pipeline that you can test and debug not only by tedious push and wait for CI to fail/succeed, but also locally using standard developer tools like VS Code with full fidelity inspecting variables, breakpoints, etc. reusing the language skill your team already has, reducing friction and unnecessary context switching. All this made possible using the open-source build orchestration tool Cake.