62

You know what I realized we should always say no for demo driven application development.

We should always ask for enough time do a proper development and if its not enough, shouldn’t write a single line.

Because once we deliver a working demo. Its release ready for them because its FUCKING WORKING..

And trying to explain why this is just a demo and cant be put to production is even bigger pain in the ass than saying no in the beginning.

LESSON LEARNED .

Comments
  • 0
    @Hu-bot0x58 -_- that's too much work. how can you work on three projects at the same time?
  • 2
    That is purely depending on your business style.

    In our team we are going with the demo driven development and we are quite good at it. Always giving a demo to the client within 2-3 days that is to earn their trust and then introduce functionality while giving demo examples. This way you can get feedback before it's too late.

    On the other hand, I see where your point might be but that is purely on the client itself and not the development way. Giving early MVP to test ideas is good, thinking that those MVP are the JOB DONE! is bad :)
  • 2
    Make sure it's ugly. Colours off, ugly fonts, bad spacing. Same for rapid prototyping. If it doesn't look finished, people will believe it isn't.
  • 2
    @Fast-Nop Thats where we fucked things up. We used react and css framework which made the app looking nice. 🙁
Your Job Suck?
Get a Better Job
Add Comment