Hacker News Reader

Having been a longtime coder in a language that doesn't support Todo tasks (tooling doesn't find them) I've seen double commenting a line as a trick to make them easily findable (it's the fastest thing to type).

It's a personal hack for being able to quickly find them. Ctrl+F //// is a reasonable "Todo" And one which on a single person project I can get away with. Because they are also valid comments persisting past release occasionally happens as (in my case) the second reviewer doesn't know this convention.

Working on a project for the past several months I've left many todos in my code to be reviewed. In most cases by myself when I better understand the problem. I am after all the first person to review my own code.

Thank you for this comment. For todo comments, Satoshi or whoever was used "//// todo: " so it might be for that too.

Personally: I use both!

I've also noticed myself forgetting "Todo:". Sometimes it's the ":" and the tooling doesn't pick it up. If I've really screwed up its "tod:".

Their comments are quite sloppy in other ways, too. They use the `//` on many lines, instead of the common `/* ... */` like:

// Why base-58 instead of standard base-64 encoding?

// - Don't want 0OIl characters that look the same in some fonts and

// could be used to create visually identical looking account numbers.

// - A string with non-alphanumeric characters is not as easily accepted as an account number.

// - E-mail usually won't line-break if there's no punctuation to break at.

// - Doubleclicking selects the whole number as one word if it's all alphanumeric.

//

> The fact that he released the first genesis block on 3rd January 2009 with the sentence of UK Times article is not casual. We can see from the first version of the source code that his network was ready many days before that date. Was he waiting for "fixing issues"? No, he ended up clearly with a release that contained many errors (e.g. amount created in genesis block can not be spent).

Sounds almost more like fair instead of a bug, but nommatter what, time going by between "finishing" and releasing is also more than normal on various levels for many reasons?!

> It's really weird to have both styles on codes, unless there are more people (>= 1) that work on the code or that reviews the code.

Hmm, no definitely no.. either just slacking, or even intentional to mark something?! Maybe you area very clean coder, I do this all the time if not polishing for work..

Could have been so, but deducting like those are proofs is very far fetched .

> Sounds almost more like fair instead of a bug, but nommatter what, time going by between "finishing" and releasing is also more than normal on various levels for many reasons?!

I'm missing something: who says is not normal? Anyway regarding comments and that, the source code is clearly heavily edited and redacted, so I do agree that we can't extract much from comments. I did not understand why HN triggered so much about two/three/four slashes.

> a release that contained many errors (e.g. amount created in genesis block can not be spent)

I was thinking that this may have been intentional.

In that sense there may be a stronger message when creating an unspendable "big" value (reward was 50BTC) than a spendable value of e.g one satoshi.

If one selects code and comments (with //) in most editors, then uses the "comment this block" action, the result is code commented with // and comments with ////. It's more likely this is a result of using a code editor or IDE than a particular style choice.

It seems more some manual stuff: there are ones with three slashes too.

I think in Visual Studio, if you start a comment block with 4 or more slashes and hut return, it will automatically start the sentences after that with 2 slashes so you can write more comment lines. Close with 4 slashes or more to end the block.