## Other

- the idea of a distribution is to create a user experience
  - you log into your computer and install a program and everything just works
  - or: something doesn't work... what are your next steps?
- you create an experience
- the distribution is that brings all the pieces together: installation, service management (systemd, openrc, initd), kernel updates, support

- lesson: composition
  - functions
  - libraries
  - programs (unix)

- lesson: specifications
  - LSP (open source milestone)

- lesson: caring about features and code instead of maintenance and collaborations

- lesson: users (user experience)
    - what if you diverge from the happy path

- lesson: how to drive change
  - good value proposation (e.g. when breaking backwards compat)
  - risk: can you revert?


- you guessed it, I like small programs

- self-perception/myth

- how to test (on the end users system)
    - tests in CI are garbage
    - tests vs good code

- reverse dependencies <-> me <-> users
- collaboration vs boundaries, communication


- autotools intro?


- mindful about what you don't know


- posix principles and their connection to functional programming (streams)

- navigation

- strings
- collaboration
    - open source politics
    - how to drive change
    - how to handle contributions (contribution experience, PRs, documentation, mentoring,. ..)
    - respect other projects when contributing
    - bus factor
    - enabling and supporting (switching from coding wizard to support role)
    - boundaries vs collaboration

- relationship between industry and FOSS

- feedback from universities regarding Haskell tooling

- project life cycles
- support
- trust, respect, relationship
- working mode in open source
- dealing with expectations

- stability vs. ..
- why is stability an interesting goal?

