Backend Software Developer · PHP/Laravel · Python · Linux · CLI tooling · Open Source

Problems become knowledge. Knowledge becomes tools. Tools become open source.

I do not collect repositories. I collect solved problems.

Each project here starts from real friction: something I had to understand, repeat, automate, explain or make more reliable. When a problem returns more than once, I turn it into knowledge. When that knowledge becomes reusable, I try to turn it into a tool. When the tool can help others, I publish it.

GiadaWare is my personal lab: the place where recurring problems become notes, tools and public projects.

• Backend development with PHP/Laravel, Python, APIs and Linux workflows.
• CLI tools, local-first systems, reproducible labs and operational safety.
• Open-source contributions around developer tooling, documentation and Linux ecosystems.

• No automatic updates available at the moment.

Real problems turned into reusable tools, labs and open-source artifacts.

Problem: scripts that move files can become dangerous when they hide their plan.

Project: Smart File Organizer, a Python CLI that organizes files through an explicit plan, dry-run mode and intentional apply step.

Signal: Python, CLI design, uv, ruff, pytest, safe defaults and operational thinking.

Problem: practical knowledge gets lost across chats, notes, files, repositories and memory.

Project: LeLe Manager, a local-first knowledge base built around JSONL lessons, CLI usage and API access.

Signal: backend boundaries, deterministic storage, local data ownership, testing and clean project structure.

Problem: storing knowledge is not enough: useful knowledge must be recalled, tested and reused.

Project: LeLe Quizzer, an interactive terminal quiz connected to the local LeLe Manager knowledge base.

Signal: CLI UX, deterministic question generation, saved attempts and privacy-first reuse of local data.

Problem: Object-Oriented Programming can look like magic when memory, dispatch and layout stay hidden.

Project: OOP-in-C Lab, a C laboratory that models OOP concepts with struct, pointers, vtables and observable output.

Signal: memory layout, polymorphism, function pointers, upcasting and low-level reasoning.

Problem: Git is often used as a sequence of copied terminal spells instead of a mental model.

Project: PyGit Lab, a Python learning lab that reconstructs fundamental Git concepts from the inside.

Signal: Git internals, Python experiments, reproducible lessons and learning by reconstruction.

My working method is simple:

1. start from a real or recurring problem;
2. document it as reusable knowledge;
3. find the smallest model that makes it understandable;
4. build a small and verifiable tool;
5. add tests, documentation and reproducible workflows;
6. publish the project when it can be useful outside my own context.

I am not interested in “just making repositories”. I care about leaving a readable path behind: problem, reasoning, solution, limits and next steps.

PET, Prime Exponent Tree, is where the same method enters computational mathematics.

Problem: integers can be studied not only as values, but as recursive structures generated by prime factorization.

Project: PET represents integers as canonical trees of prime exponents.

Signal: canonical representation, lossless encoding/decoding, canonical JSON, minimal CLI, structural metrics and analyzable datasets.

Repo: gcomneno/pet

I use public learning labs to turn study, notes and technical experiments into reproducible paths.

• Python Fast Track: Python for already experienced developers.
• Web / Laravel Lab: practical Laravel and backend web development.
• PyGit Lab: Git internals reconstructed in Python.
• OOP-in-C Lab: OOP concepts reconstructed in C.
• Yocto/QEMU Mini Lab: embedded Linux, build, boot and BitBake.
• C# / HTML Lab: programming and web fundamentals.
• JavaScript Lab: patterns, TypeScript and tests.
• Cyber-Security Lab: white-hat lab with recon, scripts and lesson learned.

My open-source path is still growing, but it follows the same logic: start from concrete problems, read the technical context and propose small, verifiable changes.

Main contribution in progress:

• yoctoproject/vscode-bitbake → gcomneno/vscode-bitbake

This profile is a moving lab: real problems, small tools, clear documentation and public iterations.