Progressing behind the scenes - pending because of delays in development of major core parts, which can only be performed by the lead developer who created the system in the first place. Although it's the standard in software development, it's very frustrating for both the insiders and the followers and commonly gives a false impression of non-progress. It's however my job to let the partner code as long as it takes and personally take all the public blame and heat. Of course for parts I factually have no control over, but that's a side issue.















Nice drama invoked there. Obviously no lines of thought imposed, no ulterior motive.

Very curious you're repeating our favorite troll's stance of Dennis being an innocent hardworker and me being a parasite con leeching off his mastery and fucking everything up. Rather intricate how this setup has arisen since the beginning of "complaints".

Sentient people of course know there would exist no major crypto undertaking like HEAT without a team, organizational efforts of considerable magnitude that need to be maintained constantly, and highly efficient coordination. Genius system developers commonly do have their quirks that, if serious, lead to high loads and undue responsibility for the co-operators especially at the times we call "invisible progress". But if the coder is potent enough, it's still worth for the partners to stick on and carry through with the responsibility and weight of the bulk of the project!