Stalled builds
Articles on
stalled builds.
Someone else started this. Now what?
A website that has been nearly finished for months is really common, and it is very fixable. Usually the person who knew it best moved on, not much got written down, and nobody wants to be the first to pick it up.
These articles are for exactly that moment: what to ask the last developer for, how to tell what state the code is really in, and why starting again is rarely the cheapest option. They are written for business owners with a stuck project and for agencies with a build that needs another pair of hands.
When you would like someone to pick it up, that is website implementation. We will get there.
2 articles
- Picking up someone else’s codebase: the first two days Taking over someone else's codebase? What I do in the first two days, before changing a single line, and why the honest report matters more than the estimate.
- The last ten percent: why builds stall at ninety A website project stuck at 90 percent is rarely stuck at the hard part. It is error states, empty states and the admin work that never shows up in a demo.
Other topics
Stuck on something
that is not here yet?
Tell me what the site is and what is going wrong. You will get a plain answer, whether or not you hire me.
- Within 12 hoursA reply
- Within 2 working daysA written scope and a price
- OrThe name of someone who fits better