INDEPENDENT SOFTWARE DEVELOPER · EN / EL

Software trouble?
Let’s make it
work again.

A broken feature, a stubborn bug, a workflow that stopped working. Bring me the problem. I’ll help you understand the next step.

All in writing. English or Greek. No calls needed.

Hi, I’m George. @premiuslol ↗

You’ll speak directly with the developer reviewing and doing the work. Clear scope, written updates, and a fix checked against the problem you brought.

01 / THE WORK

Small repairs.
Carefully finished.

A focused problem is a good place to start. If the work needs a smaller first step, I’ll say so.

  1. Bugs & broken features

    JavaScript, PHP and web issues. Reproduce the failure, trace the cause, and check the fix.

  2. Browser & mobile UI

    Menus, forms and layouts that fail at the wrong screen size. Check the affected view and the surrounding behavior.

  3. Scripts & workflows

    Small automations, integrations and data conversions that stopped behaving as intended.

02 / OPEN TO INSPECTION

Work you can inspect.

Independent project and merged open-source fixes. Inspect the source evidence.

EMBERSTEAD · OWN PROJECT

Making a colony UI usable on mobile

Emberstead is my browser game. Its mobile portrait update reworked navigation, scrolling and panels so the interface was easier to reach on small screens.

Read the mobile update ↗

STELLARLEND · TYPESCRIPT / EXPRESS

Making API errors safer

Hardened API error handling so unexpected failures return safe messages and sensitive request data is not logged.

Inspect merged PR #2152 ↗

LENS · TYPESCRIPT / REGRESSION

Fixing misaligned calculation data

Corrected TWAP outlier filtering to preserve timestamp alignment, with a reproducible regression test.

Inspect merged PR #180 ↗

CREDITRA · RUST TOOLING / CI

Adding Rust workspace checks

Added a CI job for a Soroban Rust workspace covering formatting, Clippy, tests and WASM builds. This is tooling work, not a claim of Rust application development.

Inspect merged PR #1452 ↗

These are an independent project and open-source contributions, not paid-client testimonials.

03 / A CLEAR PATH

From frustrating to understood.

  1. Describe the issue

    Tell me what you expected and what happened. A safe public link is helpful, not essential.

  2. Get a written fit response

    I’ll ask what is missing, suggest a bounded diagnosis, or tell you if it is outside my scope.

  3. Agree the solution

    We confirm scope, price, timing and how success will be tested before paid work starts.

  4. Receive the fix & evidence

    Get the change, verification results and any known limits, ready for written review.

04 / START HERE

Tell me what’s broken.

A short description is enough to start. You don’t need a technical diagnosis.

All in writing. English or Greek. No calls needed.

Sending an inquiry does not book work or create a quote. Scope, price and acceptance are agreed separately.

Include the browser or software if you know it. Please keep private links and client data out of this first message.

Please don’t send passwords, tokens, cookies, private keys, database dumps or private customer records.

Privacy notice. Intake submissions are deleted within 30 days.

Nothing is sent until you choose Send request. Changing language or reloading clears the draft.

05 / FAQ

A few practical questions.

Do we need a call?

No. Briefs, questions, scope and delivery are handled asynchronously in writing. Work that requires live calls or screen sharing is outside this service.

I don’t know what’s causing the problem. Is that okay?

Yes. Describe the symptom and what you expected. If the cause is unclear, we can discuss a bounded diagnosis before any larger repair.

Is the work free?

This is an inquiry, not a free repair offer. If the task is a fit, we agree the price, scope, timing and verification before paid work starts.

Do you use AI-assisted tools?

Where permitted, yes. I remain responsible for reviewing and testing the result. Private code or client data and any AI use are agreed before work starts.

What if it is outside your scope?

I’ll say so, or propose a smaller first step. I won’t accept a task that I cannot reasonably finish and validate.