DevSecOps
Personal side-projects
A living workspace for secure automation, AI exploration, and open-source experiments.
Presentation :
This space is my personal workshop.
It’s where I test, break, rebuild, and document ideas around DevSecOps, AI, and automation.
Nothing here is polished or final — most of it is exploration turned into code.
Some projects are long-term experiments; others are just quick technical notes that help me think better.
Either way, it’s my way of keeping engineering concrete: build first, refine later.
AI-Tech-Watch started as a simple question: can a language model help me keep up with the pace of tech news without turning it into noise?
So far, it’s a set of scripts that fetch, clean, and summarize information, just to see how far I can automate the “research” part of my daily routine.
CI-Framework is the opposite kind of work — less creative, more disciplined.
It’s my way of building repeatable, auditable cloud environments with clear security and compliance principles.
It helps me think about how infrastructure should be built when you care about traceability and intent, not just speed.
Technical environment :
Most of my work combines three main areas:
Infrastructure and automation, with a focus on repeatability and compliance.
Security and resilience, integrating secret management and observability into the build process.
AI and intelligent systems, exploring how large language models and automation can support everyday engineering tasks.
The stack changes over time, but the goal stays the same:
to design systems that are secure, intentional, and maintainable.
Challenge :
The hardest part isn’t writing code — it’s staying consistent when curiosity pulls in different directions.
All projects lets me experiment, explore, and keeps me disciplined and grounded.
Balancing both is like switching between two mindsets: freedom and compliance, chaos and order.
That tension is what drives the learning.
Summary :
My GitHub is a living archive, not a portfolio.
It mixes experiments, frameworks, and open-source contributions — all evolving in public.
I share it to keep myself honest and to connect with engineers who care about the same things:
building with intention, learning by doing, and securing what we create.
If you’re curious, check back from time to time.
Everything new I build — whether it’s part of AI-Tech-Watch, CI-Framework, or other open-source work — starts here.
More Projects
DevSecOps
Personal side-projects
A living workspace for secure automation, AI exploration, and open-source experiments.
Presentation :
This space is my personal workshop.
It’s where I test, break, rebuild, and document ideas around DevSecOps, AI, and automation.
Nothing here is polished or final — most of it is exploration turned into code.
Some projects are long-term experiments; others are just quick technical notes that help me think better.
Either way, it’s my way of keeping engineering concrete: build first, refine later.
AI-Tech-Watch started as a simple question: can a language model help me keep up with the pace of tech news without turning it into noise?
So far, it’s a set of scripts that fetch, clean, and summarize information, just to see how far I can automate the “research” part of my daily routine.
CI-Framework is the opposite kind of work — less creative, more disciplined.
It’s my way of building repeatable, auditable cloud environments with clear security and compliance principles.
It helps me think about how infrastructure should be built when you care about traceability and intent, not just speed.
Technical environment :
Most of my work combines three main areas:
Infrastructure and automation, with a focus on repeatability and compliance.
Security and resilience, integrating secret management and observability into the build process.
AI and intelligent systems, exploring how large language models and automation can support everyday engineering tasks.
The stack changes over time, but the goal stays the same:
to design systems that are secure, intentional, and maintainable.
Challenge :
The hardest part isn’t writing code — it’s staying consistent when curiosity pulls in different directions.
All projects lets me experiment, explore, and keeps me disciplined and grounded.
Balancing both is like switching between two mindsets: freedom and compliance, chaos and order.
That tension is what drives the learning.
Summary :
My GitHub is a living archive, not a portfolio.
It mixes experiments, frameworks, and open-source contributions — all evolving in public.
I share it to keep myself honest and to connect with engineers who care about the same things:
building with intention, learning by doing, and securing what we create.
If you’re curious, check back from time to time.
Everything new I build — whether it’s part of AI-Tech-Watch, CI-Framework, or other open-source work — starts here.
More Projects
DevSecOps
Personal side-projects
A living workspace for secure automation, AI exploration, and open-source experiments.
Presentation :
This space is my personal workshop.
It’s where I test, break, rebuild, and document ideas around DevSecOps, AI, and automation.
Nothing here is polished or final — most of it is exploration turned into code.
Some projects are long-term experiments; others are just quick technical notes that help me think better.
Either way, it’s my way of keeping engineering concrete: build first, refine later.
AI-Tech-Watch started as a simple question: can a language model help me keep up with the pace of tech news without turning it into noise?
So far, it’s a set of scripts that fetch, clean, and summarize information, just to see how far I can automate the “research” part of my daily routine.
CI-Framework is the opposite kind of work — less creative, more disciplined.
It’s my way of building repeatable, auditable cloud environments with clear security and compliance principles.
It helps me think about how infrastructure should be built when you care about traceability and intent, not just speed.
Technical environment :
Most of my work combines three main areas:
Infrastructure and automation, with a focus on repeatability and compliance.
Security and resilience, integrating secret management and observability into the build process.
AI and intelligent systems, exploring how large language models and automation can support everyday engineering tasks.
The stack changes over time, but the goal stays the same:
to design systems that are secure, intentional, and maintainable.
Challenge :
The hardest part isn’t writing code — it’s staying consistent when curiosity pulls in different directions.
All projects lets me experiment, explore, and keeps me disciplined and grounded.
Balancing both is like switching between two mindsets: freedom and compliance, chaos and order.
That tension is what drives the learning.
Summary :
My GitHub is a living archive, not a portfolio.
It mixes experiments, frameworks, and open-source contributions — all evolving in public.
I share it to keep myself honest and to connect with engineers who care about the same things:
building with intention, learning by doing, and securing what we create.
If you’re curious, check back from time to time.
Everything new I build — whether it’s part of AI-Tech-Watch, CI-Framework, or other open-source work — starts here.