← Home

Ivan Matiushkin · Independent contractor · Poland · remote collaboration

Improve or repair existing software

Add a missing capability, fix a reproducible bug or make an existing workflow easier to use.

You may already have useful software. The next step can be a focused change to that codebase, rather than starting again.

Tasks you can bring

An application almost fits, a manual workaround keeps recurring, or a bug blocks daily work. Bring the actual problem; I will check the code, constraints and what a practical change involves.

Describe your taskSee the example ↓

An inspected change in your existing application

What I need

The current behaviour, desired result, relevant stack and any reproducible example. Code access and licence permissions are checked before implementation.

What you receive

A scoped patch or feature, regression tests, a reviewable diff and instructions for release or handover. Wider changes are agreed as separate stages.

How I check the result

A bug can be reproduced before the fix and passes its regression check afterwards; a feature meets agreed scenarios without breaking the relevant existing flow.

Atomic CRM belongs to Marmelab; my example extends its contact import. The Java example fixes one retry failure in Resilience4j. These do not establish experience with every framework or paid client history.

A first stage is a way to start, not a limit on the project. Larger applications and ongoing improvements can be agreed in subsequent stages.

Price and timing are agreed after reviewing your materials, before paid work begins. Contracts and payments can be handled through Useme where compatible with the client. Useme is an intermediary, not my company.

From task description to delivery

  1. Describe the process or current application behaviour. Relevant samples and documentation depend on the task; do not send confidential information.
  2. I check access and constraints. I agree with you on the scope, price and acceptance tests.
  3. I implement the stage, show the test results and deliver the code with instructions.

Before you start

Can you work with my existing code?

I first check the stack, licence, setup and relevant tests. The CRM and Java examples show scoped work in existing codebases; suitability for your application is assessed separately.

How do you check that the change is safe to release?

I agree with you on the affected behaviour, regression checks and release conditions. Access, backups, deployment responsibilities and support are specified for the actual project.