/developer|entrepreneur/i
Always looking for new developer talent, even those with zero experience, as you never know who's got the potential to become a great developer.
This is all good advice, but one thing missing here is establishing a clear outline, in writing, of the developer's responsibilities during various phases of the projects. During the build phase you'll often assume way more responsibility than when something's deployed and operating.
If you do a lot of development work on short contracts it's worth coming up with a break-down of responsibilities at various key milestones. For web properties this might mean outlining:
What domain(s) the customer needs to continue paying for, where they're hosted, and what the renewal cycle is.
What TLS certificate(s) the customer needs to pay for or renew, and how this can be done.
What service(s) are required for the product to operate properly, how much they cost, and what renewal cycles they have, like monthly or annual.
What the support can be provided after the project is completed, and what terms this is offered under. If their site "goes down" are you willing and able to provide emergency support?
What technologies are involved so that if they need to source additional help they know what they're asking for.
The number one thing here is to avoid "albatross" projects that won't go away, they're always having tiny, obnoxious, distracting problems, which can be largely avoided by outlining in clear terms what's a defect you'll fix and what's their responsibility.
It'd be nice if there were free resources for this sort of thing as there are for contracts, but I can't find any off the top.
That's sort of the issue of account management particularly when its too technical for your client to deal with themselves. Setting clear guidelines of services is a good idea I like that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is all good advice, but one thing missing here is establishing a clear outline, in writing, of the developer's responsibilities during various phases of the projects. During the build phase you'll often assume way more responsibility than when something's deployed and operating.
If you do a lot of development work on short contracts it's worth coming up with a break-down of responsibilities at various key milestones. For web properties this might mean outlining:
The number one thing here is to avoid "albatross" projects that won't go away, they're always having tiny, obnoxious, distracting problems, which can be largely avoided by outlining in clear terms what's a defect you'll fix and what's their responsibility.
It'd be nice if there were free resources for this sort of thing as there are for contracts, but I can't find any off the top.
That's sort of the issue of account management particularly when its too technical for your client to deal with themselves. Setting clear guidelines of services is a good idea I like that.