Frequently Asked Questions

What kinds of projects do you usually work on?

I primarily work on web applications, internal tools, dashboards, e-commerce platforms, and product features.

Most of my work involves improving or extending existing software, although I'm equally happy to build new products from scratch.

Do you work with existing codebases?

Most projects involve joining an existing codebase. I take time to understand the architecture, existing patterns, and technical constraints before implementing new functionality.

Do you work on short-term projects?

Some engagements last a few days, while others continue for several months. I'm happy to help with one-off features, ongoing product development, or long-term partnerships.

Do you work with fixed scopes or ongoing development?

Some projects have a clearly defined scope, while others evolve over time. I'm comfortable adapting to either approach depending on what makes the most sense for the project.

Do you work with incomplete specifications?

Not every project starts with a detailed specification. I'm comfortable working through ambiguity, asking questions where needed, and helping shape technical solutions as requirements become clearer.

How do you estimate projects?

I prefer estimating once I understand the problem.

Smaller tasks can often be estimated quickly, while larger projects usually benefit from a short discovery phase to identify unknowns, technical constraints, and reduce surprises later.

How do you communicate during a project?

I work asynchronously by default.

You'll receive updates at minor and major milestones throughout the project, along with any questions or blockers that require your input.

If regular meetings make sense for the project, I'm happy to schedule them in advance.

Can you work with my existing tools and workflow?

I'm happy to work within your existing workflow, whether that's GitHub, Slack, Linear, Jira, Notion, Trello, or another project management system.

Do you write documentation?

I document important implementation details, architectural decisions, and anything that helps future development, onboarding, or handover.

Do you provide support after launch?

I'm happy to continue supporting a project after deployment, whether that's fixing issues, shipping improvements, or helping with future development.

Is my project kept confidential?

Yes. Confidentiality is my default approach, regardless of whether an NDA is in place.

Unless we've agreed otherwise, I won't publicly reference your company, product, or project.

If we're working together outside of a white-label arrangement and you're happy for me to showcase the work, I'm always grateful for the opportunity. Otherwise, any project featured on this website focuses exclusively on the engineering challenges, architectural decisions, and outcomes. Client names, identifying details, proprietary information, and implementation specifics are removed or anonymised.

What if you don't think you're the right fit?

I'd rather be honest upfront than commit to a project where I can't provide the level of quality it deserves.

If I know someone who's better suited to the work, I'm happy to point you in the right direction.

What's the best way to get started?

Reach out with a brief description of your project, what you're trying to achieve, and any relevant context.

From there we can discuss the requirements, decide whether we're a good fit, and determine the best way to move forward.