Computers generally don't really mind how you have defined your variable names, structured your data, and named your functions in your program, it all gets tran

Computers generally don't really mind how you have defined your variable names, structured your data, and named your functions in your program, it all gets translated into a memory adres and machine code. Ofcourse code needs to work, and getting things done is important, speed of development is part of running a business. But a program should also be readable & understandable, and maybe re-usable by a an other human being. I don't think this implies you need to use OOP, but one of the nice characteristics is, that is has defined data and operations for a particular object. Achieving a high development speed right now, without to much structuring and human readable & understandable logic in your code, won't do much harm right now. Till someone asks you to change something in a working program. Than re-reading and understanding to much unstructured code, at that time, kills development speed, which can block a much needed functionality. And I personally think it is this building & launching of functionality that your users will care deeply about. But, still I think there is a sweet spot, somewhere (between spaghetti and fully structured systems) http://cdn-media-2.lifehack.org/wp-content/files/2013/05/THE-WORLD-DOES-NOT-REWARD-PERFECTIONISTS.-IT-REWARDS-THOSE-WHO-GET-THINGS-DONE.-2-1024x682.jpg http://cdn-media-2.lifehack.org/wp-content/files/2013/05/THE...