I think it might have been the silver bullet that advocated doing the prototype in a language you are not going to use so that it has to be thrown away.
I've always been an advocate of only have one coder, and the best coder, work on the prototype and be give a chance to rework it a few times until they get a second coder onboard. Once multiple coders are on a system the basic core design is set.
My last gig before quitting contracting was taking a database, exporting it into the most unbelievably complex excel spreadsheets where the business could modify the data then upload the spreadsheet. The validation on 60,000 cells coming back in was just a nightmare.
I tried to tell them if we sit down and have a think about this we can make a UI where all the changes could be done in the system. My opinions were ignored.
I've always been an advocate of only have one coder, and the best coder, work on the prototype and be give a chance to rework it a few times until they get a second coder onboard. Once multiple coders are on a system the basic core design is set.
My last gig before quitting contracting was taking a database, exporting it into the most unbelievably complex excel spreadsheets where the business could modify the data then upload the spreadsheet. The validation on 60,000 cells coming back in was just a nightmare.
I tried to tell them if we sit down and have a think about this we can make a UI where all the changes could be done in the system. My opinions were ignored.
Comment