content/day-1/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Day -1
-weight: 3
+weight: 2
 ---
 
 TODO:

content/day-2/05_broken-tech.md

@@ -1,70 +0,0 @@
----
-title: Tech is broken and AI won't fix it
-weight: 5
-tags:
- - rejekts
----
-
-<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
-
-## Recruitment & Staffing
-
-> The background for this talk is a very bad experience in this sector
-
-- "We want someone opinionated" -> No you don't
-
-### We don't know how to recruit engineers
-
-- How many rounds of interviews?
-- Technical tests?
-    - Not allways show your real worlds skills
-    - Many different kinds that usually don't fit (telling a junior)
-    - Other fields don't do this
-- Is there an accurate feedback loop?
-    - The anwer to the qustion "how was the interview process" usually depends if there is an result and the kind of result
-- Many just try to follow fang
-    - Plot twist you are not fang, you are a small company
-    - Mostly tests resilience and not really technical skills
-
-### We're not very good at training for the future
-
-- Many companies "only recruit senior engineers"
-- Junior engineers are sometimes viewed as a cost center
-- But they are important:
-    - Force seniors to explain stuff better
-    - Force collobaration
-    - Are a bit like the usual clueless customer
-
-## Teamwork
-
-- Depending on the team size and skillset the requirements for leadership change (Lead Engineer vs Engineering Manager)
-- Don't hang up on stuff like "this is our team's senior/junior engineer" - everyone servers a role that changes depending on context (everyone is )
-
-### Agile is broken
-
-- The core of agile is about 
-    - Individuals&Interaction > Process&Tools
-    - Working Software > Documentation
-    - Customer collaboration > Contract negotiation
-    - Responing to Change > Following a plan
-- Agile never planned for all of the meetings
-- If you have to have standups: Keep them short with rules
-
-## Bias
-
-- Everyone has biases and uncontious biases
-- Example: The doctor test "I went to the doctor" -> Most people assume a man
-- AI results in the same stereotype "Draw a doctor" -> While man with glasses
-- Reality usually contradicts these biases
-
-## Coding
-
-- In the old days we copied from stackoverflow, now we let ai do the copying
-- If GenAI uses LLM it bases everything on past code, will we reach a point where noting is new?
-
-## What can we do
-
-- Be an empathetic human (by gut feel or just by asking others)
-- Develop engineers
-- Never say something is shit
-- Treat AI as an unreliable colleague (never assume it's allways right or wrong)

content/day-2/06_geo-distributed-clusters.md

@@ -1,55 +0,0 @@
----
-title: Geographically Distributed Clusters: Resilient Distributed Compute on the Edge 
-weight: 6
-tags:
- - rejekts
----
-
-<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
-
-## Background: The state of cloud in mauritius
-
-- Cloud native is more cloud naive
-- Government treated cloud as bad for a while
-- People know AWS but not the cloud native ecosystem
-- Bad uplinks due to sea-cables that tend to get broken from time to time
-- Only one local cloud service provider and the big providers are "an ocean away"
-
-## The Solution
-
-- Idea: Use multiple homelabs across the island as availability zones or multi-cloud
-- Goal: Orchestrate everything through kubernetes
-- Plan: 3 Homelabs with at least 3 Nodes each that join one big cluster
-- Tech: Longhorn Storage, Tailscale for connectivity
-- Converns: Latency, Power-Cuts, Bandwidth, IP-Rotation
-- Prod use: A startup wanted to use this for their workload and needed
-    - Tailscale exit nodes for external services
-    - GPU nodes for AI-Workload
-
-## Q&A
-
-- How is ingress handled (by me)?
-    - Migrate the control plane to the cloud provider and use their static IPs.
-    - Ingress allways starts at the cloud and routes over 
-- Why tailscale?
-    - Fairly reliable
-    - Pretty simple
-    - Handles routing
-- How are you planning on scaling this setup?
-    - More friends aka more homelab locations
-    - Utilize Tailscale
-- How are you handling image distribution?
-    - Bandwitdh is not that limited (200 Down)
-    - They just host their own registry for stuff
-- What about the neighboring islands? -> Cool ideas
-- How big is your local cloud community? -> 15 People at smaller meetups and 1600 at the yearly dev meetup
-- How do you handle security in your setup?
-    - This is not the primary concern for the government
-    - Most locals banks/insurers have inhouse servers or stuff on aws
-    - Most of the time security is an afterthought
-- What kind of hardware are you running on and how do you aquire it?
-    - The second hand market is not really a thing (or rather expensive).
-    - They usually just import stuff themselves
-    - Most Nodes are Dell Optiplex or Lenovo Thinkcenters
-- How does longhorn perform over the 200mbit connection? -> Surprisingly good
-- Is Starlink available? -> No and the government does things linke "let's shut down socialmedia before the election"

content/day-2/_index.md

@@ -1,13 +1,16 @@
 ---
 archetype: chapter 
 title: Day -2
-weight: 2
+weight: 1
 ---
 
-This is the first day of Cloud Native Rejekts and the first time of me attending this event.
+Yes that is a negative day.
+Why? Because the numbering of the days is based on KubeCon instead of the trip.
+Why? Ask the sleep deprived version of me who started his trip to London at 3am...
+
+But this is the first day of Cloud Native Rejekts and the first time of me attending this event.
 
 ## Talk recommendations
 
-- Handling large scale migrations: [The Cluster API Migration Retrospective: Live migrating hundreds of clusters to Cluster API](../02_clusterapi) 
+- The Cluster API Migration Retrospective: Live migrating hundreds of clusters to Cluster API
-- Handling lrage number of clusters: [CRD Data Architecture for Multi-Cluster Kubernetes](../04_multicluster-crd)
+- CRD Data Architecture for Multi-Cluster Kubernetes
-- How to hire, manage and develop engineers: [Tech is broken and AI won't fix it](../05_broken-tech)

content/day-3/_index.md

@@ -1,11 +0,0 @@
----
-archetype: chapter 
-title: Day -3
-weight: 1
----
-
-Yes that is a negative day.
-Why? Because the numbering of the days is based on KubeCon instead of the trip.
-Why? Ask the sleep deprived version of me who started his trip to London at 2am...
-
-## What h

content/day0/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Day 0
-weight: 4
+weight: 3
 ---
 
 TODO:

content/day1/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Day 1
-weight: 5
+weight: 4
 ---
 
 TODO:

content/day2/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Day 2
-weight: 6
+weight: 5
 ---
 
 TODO:

content/day3/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Day 3
-weight: 7
+weight: 6
 ---
 
 TODO:

content/lessons_learned/_index.md

@@ -1,7 +1,7 @@
 ---
 archetype: chapter 
 title: Lessons Learned
-weight: 8
+weight: 7
 ---
 
 TODO: