Simple Engineer Notes
154 subscribers
147 photos
2 videos
49 links
Engineering insights from a simple perspective - focusing on DevOps, IaC, OS, automation and solutions without the complexity.

https://www.goncharov.xyz
Download Telegram
πŸ“„Key notes from systemd@meta speach

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

- systems is used everywhere. So there is special team to manage problems & contribute
- use different name spaces for different services
- minimize diff & stay sync with the upstream
- tests are heavy and not all of then can be executed inside containers
- systemd inside systemd is coming
- dbus will be replaced by varlink

#conf #linux #devconf
πŸ‘2πŸ”₯1
πŸ“„ 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
πŸ‘1🀑1
πŸ“„ 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
πŸ€”2
πŸ“„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
😁1πŸ’©1