How ivo-donchev/talks works
Main Components
• A top-level “Talks Repository” container that holds all the talk-related content.
• Within each event’s container, identify components like “demo code”, “configuration files” (e.g., requirements.txt, setup.cfg, .gitignore), and possibly “slides” if they are included in the demos (the README implies that slides are intended to be part of the talks).
Relationships and Interactions
– Concurrency demonstrations (multiprocessing, multithreading, coroutines) are a repeated pattern across several demos (DevBG.* and EuroPython).
– Web application demos are segmented into backend (often Django-based, with additional configurations like asgi.py, wsgi.py, settings.py) and frontend parts (notice the Next.js sub-folder in some Django meetups).
• Although there are no runtime interactions between demos, from a design perspective it’s useful to show that the repository is “modular” with each folder encapsulating a specific demonstration or talk.
Architectural Patterns & Technologies
• For the Django-based projects:
– Illustrate the classic Django MVC (or “MTV”) separation where you have models, views, templates (or even API endpoints) and controllers (urls, middleware, etc.).
– Indicate that each Django project includes configuration layers (e.g., settings) plus possible integrations with frontend projects (Next.js).
• For the Next.js components:
– Show the separation between server-side configuration (next.config.js, tsconfig.json) and client-rendered components (pages, app directories).
• Concurrency demos:
– Highlight the fact that many of these demos come in “class-based” versus “function-based” versions for both multi-threading and multi-processing.
• Common configuration files (like requirements.txt, setup.cfg, and .gitignore) as supporting infrastructure that ties the demos together.