Quote from: AlexGR on May 26, 2014, 10:20:48 PM

Quote from: rethink-your-strategy on May 26, 2014, 09:44:09 PM

LOL - this shitcoin is getting the end it deserves.

This is why you should never trust a fucking VB coder. Cryptographers are academics, and they have to be supported by developers who know what they're doing. A one-man-band that can't decide whether he's a developer or a "finance" guy is clearly not suited to cryptography.

The "fucking VB coder" put anonymity on the map of cryptocurrencies and is changing the landscape of crypto. You know why? Because those who can, do. And those who can't => teach. (these are the academics btw). He started a project that was, for all intents and purposes, quite difficult and yet he's pulling ahead on his own, when other coins have 3-10 people "dev teams" who code nothing. I ask these fantastic dev teams on their threads "oh you have a fantastic dev / dev team... right... so what have these fantastic devs coded?" The answer is nothing.

Is Evan the next satoshi? No. Is he the best coder in town? No. Is he the best cryptographer? No. Does he have the paranoia that is REQUIRED to be in this business? No. He's quite aloof in that right, just coding his stuff and not giving a fuck. Does he appear more sloppy than your average coder? Perhaps, but sloppiness is a function of time and stress:

1. Time: People see stuff like version numbers, thread titles or OP not having the right info etc and are rightly upset, but a one-man-show fails due to the constraints of time when trying to handle more than is possible.

2. Stress: I could tell the possibility for an "accident" was quite elevated because my mind's pattern recognition spotted a lot of syntax and context errors in some of his latest messages which would indicate that he was stressed a lot and had fragmented attention. But the error doesn't appear to have come from that, as the code was already running on testnet, so without bugs appearing there the coder doesn't have issues to fix.

The coin got the attention earlier than DarkSend's final launch and hence a lot of pressure to deliver when it's still in development. This has elevated the stress levels due to the press spotlight and contacts, due to pm's, due to emails, due to the coding that must be done for the next phase, due to the monitoring and communication with the community in irc, bitcointalk, darkcointalk, due to the time that it is required to run a pool / answer tickets, and then he also has a personal life that he probably doesn't really enjoy right now due to all the attention. He also has to protect himself from future government invasion, planning contingencies.

Of course he knows that all this is not without a reward (his DRKs value are directly related to his work) so he deals with it but he'll need assistance. If you are slightly paranoid on the project you must select your assistants carefully or you'll have an issue, so "centralization" of responsibilities until you find someone that can assist is of real importance. Hiring extra staff or coders (which he knows and trusts) would probably not be a bad idea, not in coding the main code, but assisting in peripherals or future ideas perhaps. Yet, given that he is "the man" in charge, a lot will still go through him.

All this pressure is actually not necessary if the development time span is spread over a longer duration, but it's all about the fucking pressure due to coinmarketcap #3.

but if you look at the #1 and #2 coins they leave themselves the time necessary to make chances... in fact they are stucked and makes no changes at all... so i think it wouldnt be any problem to scale the event list with the factor 2 or 3 in time... drk still would be the most innovative coin in this market cap position. I suggest to realy work out a plan how it is possible to have a huge user base AND be innovative with hard forks and so such. This is the main problem that costs the other both coins there position in the long run... If you can not innovate any more you die but you need to find a way to do it smooth enought so that the user base can follow... The actual hard fork is an example how it should not be done.