This is the ZVM Labs personal library: books, courses, documentation, articles, channels, and other resources that should be read as part of a learning route, not as a random link list.

Each item should explain: what it is, who it is for, why it matters, and my own note after reading, watching, or completing it. If a resource has not been fully reviewed yet, that should be stated clearly.

How To Read This Page

Entry Format

Each resource is added as its own Markdown file in content/library/. This gives every item a dedicated page, translation, status, topic, level, author note, and link without turning the library into one long table.

New Ukrainian resource:

1
hugo new content library/resource-slug.md

English version of the same resource:

1
hugo new content library/resource-slug.en.md

New resources use the archetypes/library.md template.

Cybersecurity

Security resources should separate learning from actions on real systems. This library should keep resources that explain thinking, boundaries, risk, defense, and responsible testing.

What to add: basic courses on networking, Linux, web security, defensive security, incident response, secure configuration, and security governance.

My evaluation frame: does the resource explain not only an attack or tool, but also the risk, control, safe-practice boundary, and evidence of the result?

Infrastructure And Linux

This track is a foundation for security, automation, and technical administration.

What to add: books and courses on Linux, networking, DNS, HTTP, TLS, shell, system administration, monitoring, backups, and permissions.

My evaluation frame: can I test something hands-on after the resource and explain the result in plain language?

AI And Automation

AI resources should be judged by practical usefulness, result verification, and clear limits of trust in models.

What to add: courses on prompt engineering, AI workflows, retrieval, automation, model evaluation, AI governance, and safe AI use in documentation.

My evaluation frame: does the resource help build a checkable process, instead of just producing more text?

GRC, Risk, And Technical Leadership

This track connects technical facts with decisions, policies, controls, and team communication.

What to add: resources about risk management, governance, controls, audit readiness, privacy, policy writing, decision records, and incident communication.

My evaluation frame: does the resource help translate a technical problem into risk, responsibility, and a decision?

Programming And Technical Writing

This is the base for tools, documentation, automation, and clear materials.

What to add: resources on Python, C/C++, shell scripting, web basics, software design, documentation, editing, diagrams, and publication workflow.

My evaluation frame: does the resource make thinking more precise and the output clearer for another person?

Contribution Rules

Connection To ZVM Labs

The library should support other pages:

This page is not just a list of things to read. It is a map of how external sources become personal thinking, practice, and evidence.