Read on Twitter
But come, why is it that in Nigeria,we don’t like to do things by the books and insist on it. If I am to blame @favouroncode for having been allegedly fraudulent. I will also blame developers for not protecting themselves.
Get a lawyer or a lawyer friend who you can call...
1/ https://twitter.com/favouroncode/status/1297227618673205251">https://twitter.com/favouronc...
Get a lawyer or a lawyer friend who you can call...
1/ https://twitter.com/favouroncode/status/1297227618673205251">https://twitter.com/favouronc...
...in situations like this. Verbal guarantees without a contractual backup is nothing but a dream!
Also, have standards and procedures and never betray them no matter what!
In my freelancing days, I have met clients who are speak from both sides of their mouth...
2/
Also, have standards and procedures and never betray them no matter what!
In my freelancing days, I have met clients who are speak from both sides of their mouth...
2/
...and there is mostly a mismatch between their actions and their words.
I have been very very broke too but I never compromised on my standards which are as follows:
1) Everything MUST be in writing and signed before I start research/coding work. Contracts must suffice.
3/
I have been very very broke too but I never compromised on my standards which are as follows:
1) Everything MUST be in writing and signed before I start research/coding work. Contracts must suffice.
3/
2) I WILL NOT help you develop your pricing/business model. You MUST employ someone else to help you develop your business model/ strategy and hand over the details to me so I can translate this to code as business logic(I will speak about this later in this tweet thread)
4/
4/
3) I DON’T do rush work (a.k.a we need this app done and hosted in the next 1/2 weeks. We are out of time and we have to launch before so so date), Ever! Even if I am as broke as anything. That client will have to take that rush work elsewhere.
5/
5/
4) My payment schedule is ALWAYS broken down into Agreed Milestones/Deliverables (1 or more) based on the scope of work. Once the scope work is agreed on, only a maximum of 3 change requests can be made per Deliverable. The 4th change request will incur an additional charge
6/
6/
5) The scope of work is costed per task under each Deliverable and is based on level of difficulty times the estimated amount of time I will spend on that task.
e.g:
UI Design implementations in HTML/CSS/JS is costed per screen and a group of screens form a Deliverable.
7/
e.g:
UI Design implementations in HTML/CSS/JS is costed per screen and a group of screens form a Deliverable.
7/
6) Where a Non-Disclosure and/or a Non-Compete Agreement is to be signed and be effected, the client MUST also provide a period of time when this will no longer apply and under what conditions I am no longer bound by such an agreement.
8/
8/
7) I always separate my workmanship costs from tooling costs (e.g. Payment integration, SMS, Email, APM, logging, DB backups, PaaS / IaaS / CDN services). This helps me as it helps the client. However, it helps me more.
Dear Devs, it’s important to have standards while doing your thing. It makes you look and be professional.
If a client smells/knows that you are just making stuff up as you go along (a.k.a you don’t have your shit figured out thoroughly). They’ll mostly want to take advantage!
If a client smells/knows that you are just making stuff up as you go along (a.k.a you don’t have your shit figured out thoroughly). They’ll mostly want to take advantage!
