📄 key notes from diagram as code

https://pretalx.devconf.info/devconf-cz-2025/talk/KDBZQ3/

- if more than 10s are required to read your diagram then simplify it
- in v1 approach there is fundamental issue with consistency of multiple diagrams because it’s like text
- v2 approach is about using code instead of text for diagrams. Like code or scripts

#conf #devconf

📄 OMG i can become root! Keynotes

https://pretalx.devconf.info/devconf-cz-2025/talk/LXBAUV/

- UAG(use after free) attack still actual in 2025
- use modern language = there’s no the problem
- at least there 3 techniques to mitigate problems in c/c++
- however it’s better to detect it. Hopefully there are some methods to do that
- and prevent


#conf #linux #devconf

📄Playbooks or Makefiles: choose your trade offs before it is too late

https://pretalx.devconf.info/devconf-cz-2025/talk/KFLFFZ/

- simplicity is crucial
- sometimes makefiles are too complicated
- ansible is too chatty and verbosity is higher. But it’s easier to understand what’s happening
- the future is: boring to write, difficult compile easy to read
- if you have problem and use regex than you have two problems now
- the same applicable for ansible
- the tool depends on the context

#conf #devconf #linux #ansible

📄How a hit on the head made me into a better leader (Management lessons learned from a health emergency)

https://pretalx.devconf.info/devconf-cz-2025/talk/KSRNMN/

- Even if you are unhappy with your manager, don't hit him or her on the head.
- surgery and week in hospital is enough for the retro
- Listen to that headache. Gather data and use them.
Set up meaningful SLAs. Make sure you know when to take action based on alerts, and that you also know what to do with them.
- Fishbone vs. Five Whys
Issues rarely happen
because of one single root cause, but rather because of a combination of different factors. Limiting your investigation to one path increases resolution time and decreases user happiness.
- Three-dimensional risk management.
- Remove silos
- Mapping knowns and unknowns. Put your knowns and unknowns on the table.
It will help with ideas what to do next.
- Al as a diagnostic tool

#devconf #conf