Amateur Programmer habits

1. Including comments

Using an IDE

1. Including comments
Don't be silly.  Commenting is a useful distraction to ward against those who have no idea what they're doing if they should happen to sort through your code.

I once asked a guy who thought he was the dogs bollocks how he would build an online chat application. He started getting really enthusiastic about building a Java server with doodah framework business logic dongles attached to adaptors that rumbulated, he then went onto draw a diagram had a several lines with insert latest buzzwords interjected at certain locations.

The whole thing sounded like a 6 month project.

I said why dont you just implement the rfc for irc and connect to and ircd.

He looked at me like I just crushed his soul.

>>3
I believe he was just trolling you, good sir.

3.Thinking the goto is a terrible statement and should never be used

>>6
Djikstra wasn't an amateur.

harmful != never

>>7
What's a dickstrap?

>>4
Hey, that's a pretty good idea. I'll do that if I ever have to program an online chat application.

Thanks, /prog/! I'm just a newcomer here, but I'm finding this forum very useful!

Always commenting out code like they'll forget how to do something if they delete it.

>>9
It's not dickstrap you retarded, it's Dijkstra. In Dutch means dickstrap.