Python / project-support

Python project maintenance and development

The previous developer has left, the bot keeps crashing or changing production feels risky? We can start by investigating a specific problem, not promising a full rewrite.

Show me the existing project

Reconstruct how the system works

I look at its components, startup process, data storage and external dependencies. For a specific bug, a reproduction or sanitized logs help. The first job is to distinguish an urgent failure from accumulated technical debt. Those do not always need to be addressed at the same time.

Working code does not have to be new

A rewrite needs a concrete reason. Before changing a module, I identify the affected workflows and dependencies. Sometimes a targeted fix is enough; sometimes a section needs refactoring. A large migration is not the default recommendation. Its cost and risks should be understood before work begins.

Prepare migrations before running them

Changing a database or infrastructure takes more than a command on a server. We need to understand the data, order of operations, backup and recovery path. For AzamiVPN, I migrated a legacy database, introduced a migration workflow and backups, and moved the infrastructure from 3x-ui to Remnawave.

Make failures diagnosable

Without logs and monitoring, a recurring bug can look new every time. Maintenance includes deciding what to observe and how to notice problems. AzamiVPN had one serious external incident over an extended period after refactoring: hosting restrictions broke Telegram connectivity. I restored it through a proxy. This is a specific project history, not an uptime guarantee.

One fix can lead to ongoing development

AzamiVPN started with a payment fix and became a long-term engagement. This allowed me to learn the product and prioritize changes around real needs. You can bring a bug, a feature or a request to assess the current codebase. Support scope and the way we handle later tasks are agreed separately; no arbitrary SLA is implied.

What helps us get started

  • What is failing or blocking development
  • The stack, deployment setup and source-code availability
  • When the issue occurs and whether a test environment exists; no passwords in the first message

Missing something from the list? That does not prevent us from starting. Just explain the situation in your own words.