Lessons learned from maintaining open source projects can be applied within companies, a practice often called inner sourcing.
Use structured issue templates and labels in GitHub to streamline bug reports and feature requests, preventing wasted effort on unapproved work.
Building extensible code requires predicting future use cases, carefully managing breaking changes, and maintaining API consistency.
A well-structured README and a contributing guide are essential for helping new contributors understand, build, and use a project.
Enhance productivity with powerful command-line tools like Oh My Posh and ZLocation, alongside graphical Git clients for complex operations.
Use tools like EditorConfig and Roslyn analyzers to enforce coding standards automatically, saving time and frustration during code reviews.
Evolve unit test naming conventions from long, descriptive sentences to shorter, more direct names that clearly state the expected outcome.
Use Directory.Build.props for shared solution settings and PolySharp to enable modern C# features on older .NET frameworks.
Structure dependencies so that packages only rely on more stable or abstract modules, creating separate packages for optional integrations.
Design patterns should be used as a tool for refactoring complex code to improve communication and structure, not as an initial design goal.
Replace complex YAML pipelines with Nuke, a C# based build automation tool that allows for local execution, debugging, and refactoring.
Automatically detect unintended breaking changes by using snapshot testing on your public API surface with tools like PublicApiGenerator.
Identify performance hotspots with a profiler and then create targeted micro-benchmarks to prevent future regressions in critical code paths.
Keep documentation in sync with code by using static site generators like Jekyll and ensure quality with automated spell-checking tools.
Leverage Dependabot in GitHub to automatically create pull requests for dependency updates, keeping projects secure and up-to-date.
Treat code coverage as a developer insight tool rather than a management KPI and use emojis to add nuance to code review feedback.
Implement semantic versioning and use tools like GitVersion to automatically generate version numbers and release notes from your commit history.
A pre-configured starter kit can bundle best practices for pipelines, issue templates, and API verification to bootstrap new library projects.
ROSEN Technology and Research Center GmbH
Lingen (Ems), Germany
Hubert Burda Media
München, Germany
28:17Hendrik Lösch
25:24Johan Hutting
40:16Roman Alexis Anastasini
26:46Gerrit Stapper
29:38Luís Ventura
29:50Kevin Lewis
25:28Joseph Katsioloudes
30:01Tim te Beek
Jobs that call for the skills explored in this talk.
Dennemeyer Group
Hesperange, Luxembourg
Dennemeyer Group
Hesperange, Luxembourg
Fluency Inc.
San Francisco, United States of America
Blueprint Technologies
Redmond, United States of America
