Work / Engineering in practice

Useful systems.
Inspectable code.

Applications and tools built around actual problems. Explore a repository, or look inside the engineering approach behind the work.

Public source

A closer look at the code.

Three reviewed repositories.
Implementation, context, and source.

Curated public source reviewed . Repository descriptions are not claims of production availability.

Engineering approach

Three disciplines. One mindset.

Clear responsibilities, repeatable workflows, and useful outcomes.

/ 01

Built to scale. Designed to last.

Cloud.

Turning complex infrastructure into a foundation you can build on.

  • Azure
  • AKS
  • Networking
  • Infrastructure as code
Look inside the approach

Architecture with a reason.

Start with reliability, security, cost, and the actual workload—not a shopping list of cloud services.

Reproducible by design.

Make environments understandable and repeatable with Terraform, Bicep, ARM templates, and reviewed deployment workflows.

Ready for the day after.

Work through private networking, DNS, AKS connectivity, and observability. Operating and troubleshooting the environment are part of the architecture, not the afterthought.

/ 02

Beyond the prompt.

AI.

Connecting intelligence to useful context, real tools, and real problems.

  • Azure OpenAI
  • Agents
  • RAG
  • Python
Look inside the approach

Context before confidence.

Retrieval and useful source information matter just as much as the language model.

Tools with boundaries.

Separate reasoning from authorized actions. Keep humans in the loop when the consequence matters.

Something you can inspect.

Build evaluation, source visibility, and failure handling into the application experience.

Inside PlagiarismGuard
/ 03

Less repetition. More possibility.

Automation.

If a workflow keeps coming back, it probably deserves to become code.

  • PowerShell
  • GitHub Actions
  • Azure DevOps
  • APIs
Look inside the approach

Reusable over hardcoded.

Turn provisioning and operational work into parameterized PowerShell and Azure CLI workflows, instead of maintaining copies with environment-specific values.

Make the safe path easy.

Use explicit scopes, validation, and confirmation around GitHub and Microsoft Graph operations. A useful shortcut should not hide a risky action.

Pipelines you can debug.

Build and troubleshoot Azure DevOps and GitHub Actions workflows with clear failure handling. Design for partial failures, rate limits, and safe retries.

Inside GitSecureOps

Build together

Have something worth building?

Working on an AI idea, a cloud problem, or a workflow that deserves better tooling? Tell me what you’re exploring and where we could collaborate.

  • Practical AI prototypes
  • Cloud & developer automation
  • Open-source tooling

An unfinished idea is a good starting point.

Go somewhere interesting.