The Weird and The Wonderful

There is a semantic difference between <p> (or other similar elements like <pre> and <dd>) and <br> (and I don't just mean that one is a container tag and one is a separator). It's not just a matter of (ab)using styles to make one look like the other. A paragraph is one group of related text, which may have explicit line breaks (<br> or, if being XHTML compliant, <br/>) within it. <br> shouldn't be used to split paragraphs, any more than <p> should be used to cause an in-paragraph line break, even if you can mess with the styles so that is the appearance. (An exception would be code listings where it's usual to run the whole thing inside one <pre>, even though one could logically argue that it should be one per method.)

"One can write Fortran in any language" Time you enjoy wasting is not wasted time - Bertrand Russel

your not wRONG "You get that on the big jobs."

Whoever set up the spreadsheet originally simply plugged in standard accounting formulas without performing any simplification. Gross Profit Margin is defined as the difference between revenue and cost of goods sold, divided by the revenue: GPM = (Revenue - CoGS)/Revenue The equation in the spreadsheet you were looking at was looking at (effectively): (1 - GPM)\*100 True, it could have been simplified, but there are (at times) reasons for not performing every possible simplification. In this case, to someone who "thinks" in terms of CoGS, Revenue, Margins, etc. the equation given makes a lot of sense. To a programmer (or a mathmatician) it is not very efficient, but to the accountant it provides self-documenting code. This is especially important in Excel, where you can't add comments to the code (cell equation). It appears that they were trying to calculate the proportion of each dollar of revenue that the company spent as expenses.

Probably, the guy copied part of a code that belonged to an IF statement and forgot to remove the BEGIN.. END, he must have thought 'why disturb the code if it compiles well?'

icestatue wrote: We were able to shorten the script to about 12 lines of code when we finished it. :doh: How long these lines were? Greetings - Jacek

Nuh uh. It's a grave accent. :-\

The next time someone tells you that true always returns true I want you to ask that person a question. Ask that person: Have you tested it? Frankly, when I see your code I see an excellent place to put a unit test. ;P

I'll admit to leaving comments behind when I'm designing new stuff but want to be able to refer to the old stuff, but I only leave it there when I forget or get distracted before finishing the new function.

This, ladies and gentlemen, is the Dunning-Kruger effect in action.

fine to me - I can handle a 13. pay check :rolleyes: regards Torsten I never finish anyth...

this made my day

We had this very issue the other day on my team. And several other issues on my previous project related to data binding. Yes, the DGV seems to have been written by an idiot.

Abbreviations.

Ahhh, a Clinton supporter!

Thanks, for the advice... it almost makes too much sense. Why didn't I think of that? I'm never going to put my own code in 'clever code', seriously if I ever write something clever it'll be because I stole the idea. ;P Right now I got what it supposed to be doing, it's exactly the same idea but it has a better structure. I use one "if block" to gather information where the walls are, put the result in a byte and run it through a "select" block where every "case" evaluates the direction of the player. It's more readable and a lot easier (as in, not impossible) to comment on. I'm getting more ambitious now and I'd like to try some ideas for more complex behavior, based on your suggestion. It also needs to be able to run through any given maze, right now I'm 'cheating' because the navigation is tailored to the only maze in the game. The project started as a break from the boring database stuff at the job training center, so I didn't have much time to work on it. The rest of the game is only about 200 lines of code and it didn't took long to write, but to get decent enemies working proves to be quite a challenge. Giraffes are not real.

Interesting approach that dll idea. I think we'll work on that :laugh: "You get that on the big jobs."

Wow...... I would never hire someone who wrote code like that.

JV9999 wrote: but there are far easier solutions for that which are also much more common. Kind of the definition of a coding Horror :) Sort of a cross between Lawrence of Arabia and Dilbert.[^] -Or- A Dead ringer for Kate Winslett[^]

Or even... void F() { Blackboard.WriteLine("I must not use unterminated recursion"); F(); } (Your version was unterminated iteration)