Tell me what you are building

Product builds where one person needs to own the schema, the API and the interface, and rescue jobs on apps that got slow or fragile. I am a poor fit for pure frontend implementation against a finished design system — you want a specialist for that, and it will cost you less.

Both. Solo on smaller builds, embedded with an existing team on larger ones. On a team I default to taking the least glamorous part of the system, since that is usually where the risk is.

Weekly rate for open-ended work, fixed price where the scope is genuinely fixed. I will tell you which one your project is, and I will say so if I think you are better served by someone cheaper.

A call, then a short written scope with the assumptions and the things explicitly not included. If we proceed, week one is discovery and a decision log, not code. That week has saved every project I have run it on.

Yes. Everything in Learn, Tips and Lab is free to use in anything, commercial included, without attribution. If it breaks something, that one is on you.

Yes, and it is often the highest-value thing I do. A few days reading a codebase and writing up what will hurt in six months costs a fraction of a build and frequently prevents one.

Some. I take on a small number of one-to-one sessions, weighted toward people making the jump from tutorials to production systems, since that gap is where I lost the most time myself.

Within two working days. If a week passes, the message went missing — send it again, I will not be annoyed.