Knowledge
Knowledge
Technical reasoning and practical methods for architecture, operations, and handover.
This section separates why from how: the principles explain architecture decisions, while the approach shows the process. Both provide guidance without replacing an analysis of the specific project.
How openness, repairability, documentation, and clear dependencies support robust IT.
→ApproachFive steps from the initial assessment to operational handover.
→Architecture and network reviews: making decisions robustA practical guide to architecture and network reviews: assess functions, dependencies, operability, and handover systematically.
→Planning robust site connections: dependencies, fallback and handoverA practical guide to site connections: make dependencies visible, assess fallback paths and hand over operations in a traceable way.
→The IT nerd as a mindsetWhy scepticism, persistence, curiosity, and technical integrity matter in complex IT projects.
→