bncmn
- installed linux (ubuntu) the first time 15 years ago
- switched to arch 4 weeks later
- studied computer science without AI
- hate to take orders from machines
- learned kubernetes the hard way
- platform/devops teamlead @ Raitec GmbH
- H-J-K-L is my love language
Sessione
What happens when your terminal setup grows from a few aliases into the place where real work happens?
This talk is a field report on building a CLI-native workbench container: a reproducible environment for my everyday terminal work (development, GitOps, tmux, zsh, Neovim and other small tools that make command-line work productive).
The focus is not the finished container, but the journey: why the environment exists, which design principles emerged, where the sharp edges were, and what changed along the way. We will look at context scaffolding, persistent environment folders, build-time Neovim problems, helper and tool discovery, and the balance between personal dotfiles and a shared toolbox that you can bring from home to work.
This is for every command-line cowboy how is or want to become in love with containers. From homelabbers, hackers, to platform engineers, linux admins and everyone who has ever thought: "I just want my shell, editor, credentials, and cluster tools to be reproducible without turning my laptop into snowflake infrastructure."