Hello Cosmin,

So we sent your comment to Code Valley and thought that we would give them a chance to reply to you…and they did!

Here it is:

“Hi Dee,

Thanks for giving us the courtesy of responding to your listener’s comments. You guys over there at The Bitcoin Podcast seem to be of that rare breed of person who won’t immediately dismiss an idea without at first doing some “due diligence.”

I’ve addressed each of the listener’s concerns below.

(1) “This guys not a programmer” – Incorrect. Noel’s first position in industry was “Software design engineer” (EE was the CS of the day). He also has a Masters in Computer Systems Engineering. In short, he has spent his whole life in software.
(2) “..he should have known that what he wants to realize is just a fantasy” – Incorrect. What Noel “wants to realize” has already been realised (http://codevalley.com/documentation – see ‘Technology status’). The evidence of its reality is our corporate webserver and the entire supply-chain of more than 1000 vendors that were used to construct it. It was Noel’s intention to only emerge from stealth-mode once we had achieved proof-of-concept.
(3) “Every software is different, it’s not like you have a factory where each product that is created is the same and it’s created on a conveyor.” – Incorrect. While every software (program) is indeed different, they share a large portion of design knowledge (otherwise your listener would have a very difficult time switching to a new project upon the completion of his current one).
(4) “A module cannot be used on any software product, but can be sold for a specific set of software in order to be incorporated, for that is codecanyon.” – This statement is irrelevant, as this technology does not rely on or use modules of any kind. Even a cursory glance by your listener at our website or white paper would have revealed the use of design-contributions (indirect code-contributions) rather than modules (direct code-contributions). Unlike code-contributions, design-contributions can be applied to any project in the design-domain and even *future* projects in the design-domain. Also, unlike code-contributions, design-contributions naturally protect the developer’s intellectual property and scale beautifully. We consider design-contributions to be a vastly superior form of contribution over that which can be achieved by delivering a module of code.

May I suggest you ease your listener’s concerns by directing him to our white paper. If, as he asserts, this idea is “really stupid” he might be kind enough to point out the flaws in its thesis. I suggest he start with the last two sections of the paper which offer strong justifications (“well defended” in the words of a senior software industry figure) of the technology. These sections are based on Fred Brooks’ Silver Bullet criteria and the properties of industrialisation, respectively. This white paper was released in early September 2015 and we have yet to receive (or be made aware of) any flaws in its arguments (not to mention our implementation of the technology works rather well).

Thank-you again for the giving us the opportunity to respond. Please don’t hesitate to get back in touch if you require any further information.

You’re doing fantastic work with The Bitcoin Podcast.

Cheers,
Julie”

We hope you continue to enjoy the show, and we will try to do better about getting experts on to assess the guests we have on the show.

Cheers, buddy!

We thought so too! We are in for some amazing times if networks like Code Valley gain a lot of traction.