really most web sites i have designed are most NEVER 100% complete

Not that you cant complete it but you just get lazy about it and when the client ask its mostly....No i can complete that even within an hour

are you guilty?

lOl

There are some elements of truth to your statement. I've experienced it

Lol...There's always a tiny bit part that never gets done

Wrong... in programming nothing is ever completely finished there are always updates..

This happens when the customer is a learner and the web developer is Nigerian. Abroad there is a proper business requirements session and a deep scope for the project is established before kick off. We are simply unprofessional about these things and rely on skill instead of proper techniques

voltron:
This happens when the customer is a learner and the web developer is Nigerian. Abroad there is a proper business requirements session and a deep scope for the project is established before kick off. We are simply unprofessional about these things and rely on skill instead of proper techniques

Only but the truth.

It really actually depends on the client...if its a very professional project then it MUST be fully done. Even at that though you might have a better way to have handled a module in the logic of your work...you will just stick to the one working currently while hope to update it later.

For the guy that said only in Nigeria you are very very wrong, a programmer friend who is in Europe shared this with me and admitted he is guilty

Lol... Developers ko bloggers ni?

voltron:
This happens when the customer is a learner and the web developer is Nigerian. Abroad there is a proper business requirements session and a deep scope for the project is established before kick off. We are simply unprofessional about these things and rely on skill instead of proper techniques

Clients' requirements are always complete. Infact in Nigeria, from my own experience, clients' requirements must be completed as they are basically features or what engineers call user requirements.

But we're talking about system requirements here. 99.9 percent of clients in Nigeria do not know what system requirements are and which results in developers not preparing a proposal that covers it.

That being said, system requirements are always and never fully implemented in the whole wide world. Shikena

spikesC:


Clients' requirements are always complete. Infact in Nigeria, from my own experience, clients' requirements must be completed as they are basically features or what engineers call user requirements.

But we're talking about system requirements here. 99.9 percent of clients in Nigeria do not know what system requirements are and which results in developers not preparing a proposal that covers it.

That being said, system requirements are always and never fully implemented in the whole wide world. Shikena

I have been a tech consultant since 2002. As IT Solution providers, you owe your potential and existing clients the responsibility for clarifying their requirements and expanding or streamlining their perception of what they want and what they need. 7 out of 10 clients have a vague idea of what they need but they know what looks like what they want. You are the experts not them. It is your hallowed obligation to provide solutions that don't become a piece of furniture nobody really uses and every one considers incomplete or a failed project. (As many are in Nigeria). You do this by educating your client and reshaping their learner ideas into professional world-class solutions that directly impacts the business in a positive and measurable manner. What happens most times is IT consultants work with vague requirements and they do not present a clear agreeable and superior argument to their clients that this is the way to go. They are either trying to sell their idea or product or trying to rope the client into a dependency so that they can make more money in phases.

If web projects are sent abroad instead of developed locally then it tells on local developers. One major reason I hear often is that local developers are not professional. This is why projects fail. Web developers have to remove their geek caps ang glasses and start thinking like entrepreneurs and business men

voltron:


I have been a tech consultant since 2002. As IT Solution providers, you owe your potential and existing clients the responsibility for clarifying their requirements and expanding or streamlining their perception of what they want and what they need. 7 out of 10 clients have a vague idea of what they need but they know what looks like what they want. You are the experts not them. It is your hallowed obligation to provide solutions that don't become a piece of furniture nobody really uses and every one considers incomplete or a failed project. (As many are in Nigeria). You do this by educating your client and reshaping their learner ideas into professional world-class solutions that directly impacts the business in a positive and measurable manner. What happens most times is IT consultants work with vague requirements and they do not present a clear agreeable and superior argument to their clients that this is the way to go. They are either trying to sell their idea or product or trying to rope the client into a dependency so that they can make more money in phases.

If web projects are sent abroad instead of developed locally then it tells on local developers. One major reason I hear often is that local developers are not professional. This is why projects fail. Web developers have to remove their geek caps ang glasses and start thinking like entrepreneurs and business men

Yes, unprofessionals plague Nigeria's IT world. All you said is totally true which is evident on Nairaland.

But, sadly, that is not what we're talking about here.
You're changing the topic, backing your argument with client-developer relationship and professionalism rather than development processes.

All you pointed out is everywhere, and occurs more often in developing countries. In fact, Indian code monkeys are worst. All they do is write your code exactly as you asked them without giving you any kind of consultation (time is money).

Clarifying clients' requirements is also relative, especially in Nigeria.

In Nigeria, clients most times knows the features he wants (user requirements) but has no idea about the technical details of the implementation.
They come to a developer and present their idea. The developer translates it into distinctive features and objective, gives him time frame and cost. Project gets a go ahead and that's it.
The client doesn't care about the language you use, continuity plan, deployment medium and disaster recovery plan. He just wants to get his project up and running by the time you gave him.

Getting back to the real issue.
System requirements are never vague. They are infact, what developers work with in the Western world. The problem is that they're always changing and goes obsolete numerous times.

When a client requests a change in the user requirements, the technical manager translates it to system requirements and the developers changes the codes directly without a modification to the official document. This happens a lot of time that it becomes a problem (new technologies are actually in place to fix this)

Probably you misunderstood the picture in relative to what the OP means by incomplete.

Always create a model (entity model) of your project, create the class models too and by time you use the entity model to create your database and create all the functions and parameters in your class models. The project is finished

Never start any web project without abstracting the models first

voltron:
This happens when the customer is a learner and the web developer is Nigerian. Abroad there is a proper business requirements session and a deep scope for the project is established before kick off. We are simply unprofessional about these things and rely on skill instead of proper techniques

You should retract this generic statement especially the part in BOLD. So this doesnt happen in the UK or Ghana or India?
It happens everywhere with UNPROFESSIONAL and/or LAZY developers.

NumberOne2:


You should retract this generic statement especially the part in BOLD. So this doesnt happen in the UK or Ghana or India?
It happens everywhere with UNPROFESSIONAL and/or LAZY developers.

retracted after all I I've met professional web developers in Nigeria. It is just that successful ones have similar methods as with unsuccessful ones. The lazy n unprofessional ones make a much more negative impact PR wise than the few good ones

spikesC:


Yes, unprofessionals plague Nigeria's IT world. All you said is totally true which is evident on Nairaland.

But, sadly, that is not what we're talking about here.
You're changing the topic, backing your argument with client-developer relationship and professionalism rather than development processes.

All you pointed out is everywhere, and occurs more often in developing countries. In fact, Indian code monkeys are worst. All they do is write your code exactly as you asked them without giving you any kind of consultation (time is money).

Clarifying clients' requirements is also relative, especially in Nigeria.

In Nigeria, clients most times knows the features he wants (user requirements) but has no idea about the technical details of the implementation.
They come to a developer and present their idea. The developer translates it into distinctive features and objective, gives him time frame and cost. Project gets a go ahead and that's it.
The client doesn't care about the language you use, continuity plan, deployment medium and disaster recovery plan. He just wants to get his project up and running by the time you gave him.

Getting back to the real issue.
System requirements are never vague. They are infact, what developers work with in the Western world. The problem is that they're always changing and goes obsolete numerous times.

When a client requests a change in the user requirements, the technical manager translates it to system requirements and the developers changes the codes directly without a modification to the official document. This happens a lot of time that it becomes a problem (new technologies are actually in place to fix this)

Probably you misunderstood the picture in relative to what the OP means by incomplete.

Thanks for your clarification, I agree with you; System Requirements Change so projects evolve. that is a Project Management reality

Interesting.... Where is dhtlm?

Ok

Procrastination
#GoodDataBest

Am not guilty of it bro..

Hello
Can you people check this
Can it be real?

https://www.nairaland.com/2177653/import-export-market-bigest-africa

H

Please thank God with me. They attacked me at about 2.30am this morning. They came into my room while I was sleeping. I heard their sound as they moved across the room towards me; as I got up, I remembered the scripture that says 'He has not given us the spirit of fear...'. As one of them came at me to attack, I had no choice but to defend myself. I quickly struck! The second one also flew at me. I couldn't believe what was happening. My neighbors heard the chaotic sound that was emerging 4rm my room and were wondering what was going on. I eventually hit the second one too; my hands were stained with blood.They lay still so I wondered if they were still alive, but when I looked at them on the floor, I found out one was still moving, I struck again & this time I hit harder in anger. That's how I killed the two giant mosquitoes attempting to suck my blood ooooooh. To God be the glory

hahaha

how we for make bah b4?

the 1st was v1.0.1

the second was v1.0.2

Lol....am not guilty

Ok

wow... this is currently happening to a work I have now, a website for a ministry ....lol I told d man am done.... a lot to dooooo

This is true.l have fallen victim of this.
A guy designed sms website for n give it to with my login details but i could not login.
It took him some days to fix it.

After that the site could not send sms,it took so days to fix,etc

finally i left the site to waste.