Wednesday, August 10, 2011

What's up? Innovation to fortification, that's what's up!

It's been a long time since my last blog, for you blog lovers out there. There's been allot of action in the innovation arena, and I've been busy keep on top of it all and giving what I have to the development of it. A privilege, no doubt, but hard work, and price to pay (from time to personal relationships and time).

A few questions that Engineers and Entrepreneurs have, that I'd like to clarify and demystify with a few mouthful of words. From keeping my nose in the grindstone, people (engineers,developers,innovators) are all wondering what's the best way to go forward with it all. There are so many programming paradigms to choose from (object oriented programming, functional, procedural), and so many Engineering models (agile, waterfall, etc). What's the best one engineering model? Which is the best programming paradigm to choose from? Which will ensure a start up companies success in a innovative, ever changing climate? How do you hit a moving target? Which will ensure a company who's no longer in innovation mode however in the process of battling the ever growing competition?

For innovative companies out there that are chasing a new idea, the best way to hit the moving target is to keep it simple, keep it usable, and keep it testable. The best method to go forward with their development is a choose a language with development speed, competitive market value for skills involved in implementation, and purely functional programming. What this does is give you speed (speed over power always wins, according to martial arts discipline), low volume in labor, and frugal budgeting for your fast running out investment almighty dollars/yen/pounds/currency.

For companies out there who have already hit the moving target, got to the market first, it's time to think scalability. What does scalabality mean in the context that it is used here? (In electronics (including hardware, communication and software) scalability is the ability of a system, network, or process, to handle growing amounts of work in a graceful manner or its ability to be enlarged to accommodate that growth from This means fortification of the business, and switching from functional programming paradigm by re-factoring the existing code into re-useable classes, unit tests that cover the rigorous documented test cases, and in turn allow for a well layered application. This scalability can be reached at several layers: software, hardware, architecture.

I look forward in getting your views from business/academia on what your thoughts on bridging the two.

No comments: