How rares8921/personal-projects works
Begin by identifying the “top-level” categories
• Artificial Intelligence – projects for satire detection and OCR.
• Assembly Programs – for example, Conway’s game of life.
• Automata Theory Programs – various automata implementations.
• C++ Projects – several projects such as Ethereal Eclipse (a game), Image Editor, Mini Command Prompt, etc.
• Java Projects – a large set of applications that range from GUIs (e.g., Chess, Calculator, Tetris) to utility tools.
• Python Scripts – small utilities on drawing, image compression, coding challenges, etc.
• Web Projects – full-stack or frontend applications such as a Chat Bot, MicroSocial Platform, and others.
• Under “Java Projects,” create blocks for individual projects (Chess, Pacman, Tetris, etc.) since they are built with a similar architectural mindset (often following an MVC or modular component model).
Out internal architectures where applicable
∘ Frontend components (views, CSS, JavaScript assets, and templating files).
∘ Backend components (controllers, models, services, and database migrations).
∘ External integrations (such as ML components or APIs).
• In the C++ projects, such as Ethereal Eclipse or Image Editor, highlight modules dealing with game logic (e.g., entity, GUI, asset loading) or image processing (filter layers, tool components) respectively.
• For Java projects, identify common patterns such as Multi-threading, event handling, and UI modules (e.g., controllers, resource files) that reflect a modular or Maven-based architecture.
Architectural patterns
• Look out for common design principles mentioned in the README – object-oriented design (especially in C++ and Java projects), modularization, event handling, and (for web projects) the separation between front- and back-end.