var allDataSimulated = new List<FeedSearchTransactionLogResult>
{
new FeedSearchTransactionLogResult(next++),
new FeedSearchTransactionLogResult(next++),
new FeedSearchTransactionLogResult(next++),
new FeedSearchTransactionLogResult(next++),
new FeedSearchTransactionLogResult(next++),
...
new FeedSearchTransactionLogResult(next++)
};

Is that a Java code ?
If so, there is 1 syntax error (eh, wait... 1001 errors), as the 'add' method in the java.util.List interface does not start with an uppercase 'A'. It won't compile like that.
C'mon 'magic' developer, take your keyboard and correct all of these lines (without search and replace, it'll be the punishment).

Is that a Java code ?
If so, there is 1 syntax error (eh, wait... 1001 errors), as the 'add' method in the java.util.List interface does not start with an uppercase 'A'. It won't compile like that.
C'mon 'magic' developer, take your keyboard and correct all of these lines (without search and replace, it'll be the punishment).

probably c#. it's basically the same as java but everything starts with an uppercase :-)

I love the html comments in this one. It reminds me of the times when my programming teachers would tell me I don't have enough comments in my code. This was usually after I had turned in code that had comments that described what was going on or the code itself was self documenting.

I love the html comments in this one. It reminds me of the times when my programming teachers would tell me I don't have enough comments in my code. This was usually after I had turned in code that had comments that described what was going on or the code itself was self documenting.

ISTR that this is what is expected if you are taught to program using the pseudocode paradigm. You start by writing the comments, which state what the program is to do. You then insert the actual code, leaving the comments in place.

I'm not sure whether it's an effective way to teach programming to those who are temperamentally unsuited to be programmers. I'm pretty sure it's a crap way to teach it to those who are suited. I'm also fairly sure it's a successful cop-out by poor teachers.

No, but thank you for playing. (The value expected by one call is not available until after the other call is done, which is pretty much the definition of a data dependency.)

Curiously the variable next++ doesn't create a data dependency between one execution of .Add() and the next. The data dependency caused by next++ is between one *call* and the next. Granted, the .Add() method of a container is unlikely to spawn a thread just to do the addition, but it *could*.

It would be trivial (ha!) to replace the 1000 (1001?) next++'s with the numbers 0 to 999 (1000?), thus eliminating next++ as a source of data dependency.

The data dependency between successive executions of .Add() is the container itself, and the actual addition is likely to be mutexed / synchronised, and therefore not parallelisable.

I'm not sure whether it's an effective way to teach programming to those who are temperamentally unsuited to be programmers.

TRWTF is that temperamental is pronounced tempermental, thus destroying any chance of winning a spelling bee.

No, TRWTF is that anybody feels it is worth having competitions like spelling bees. In a language where spelling and pronunciation are more closely linked than in English, you can know how to spell unknown words just by hearing them. French has half the problem that English has, in that while spellings usually have unique pronunciations ('ch' is troublesome), pronunciations often have ambiguous spellings, especially for a native English speaker like me who has a hard time distinguishing the subtle variations of 'u' and 'ou' - a final "eh" sound can be spelled at least ten different ways. I find it very hard to read "phonetically equivalent French" (where you use a series of letters that would be pronounced the same as some word or other) because I read French using the same "look-say" technology that I use in English.

I'll just use my patented YOSPOS language that's a random mashup of other languages that are inferior to mine in every way. I don't like what the original program is doing so whatever it was trying to accomplish is wrong. The correct thing to do is to write to the console and use AutoHotKey to copy and paste into Notepad.

At some point I'll add in some error checking to make sure the number of lines is equal to the function name by storing the variables in unused fields on the included $1000 PDF printer that was last updated in 1997 and only works on Windows XP x86 with less than 2 GB of RAM.

I love the html comments in this one. It reminds me of the times when my programming teachers would tell me I don't have enough comments in my code. This was usually after I had turned in code that had comments that described what was going on or the code itself was self documenting.

At least you DID learn the difference. My syllabus for my students bolded and italized "useful" in the requirement for programs that read "Must include USEFUL documentation."

Useless documentation is worse than no documentation in the sense that it's a distraction. On my computer's hard-drive is an archive of some "professional" code that has a long poem inserted in a function header. SRSLY... a poem.

When I wake up, (when I wake up),
Well I know I'm gonna be
I'm gonna be the man who wakes up at ten A.M., (Yeah I know)
When I go out, (when I go out, )
Well I know I'm gonna be
I'm gonna be the man who gets to work at one P.M., (who?)
If I get drunk, (If I get drunk, )
well I know I'm gonna be
I'm gonna be the man who gets drunk down at the pub, (yeah) Yes!
And when I get fired, (when I get fired, )
well I know I'm gonna be I'm gonna be the man who leaves this crappy code with you

But I would log 500 lines
And I would log 500 more
Just to be the man who logged a thousand lines
To fall down at the door