Mar 4, 2011 03:42 PM
(This post was last modified: Mar 4, 2011 06:13 PM by Vysse.)
I was thinking we should gather some bad habits and show people the right way of doing certain things have it all in an image that several users could put in their signatures. The first step for this is getting some things to put in that signature so please throw suggestions of what you want people to stop doing when it comes to coding. Here are some things that bother me.
Using timers when unnecessary
Using threads when unnecessary - Zer0Fact0r
Not naming variables and controls
Select Case statements are rarely used
Copying and pasting without regard of understanding the code
Trying to code malware without ever coding anything else before
I think that is it for now so let me grab others opinions...
Bitcoin Address: 1KQCBvevk1sA4wSj7gugv3sf5yjUygAzcv
Mar 4, 2011 03:45 PM
(This post was last modified: Mar 4, 2011 03:46 PM by xSilent.)
Skids will do whatever they want.
You can't stop it, no matter how hard you try. (I've tried threads like these numerous times)
Trying to stop skids from stealing code is like trying to stop a fag from going into a gym shower.
It is worth a shot IMO but you are right there are those who will do whatever anyways... I am just hoping to affect those who do care but cannot learn any better as there is nothing to learn from...
Bitcoin Address: 1KQCBvevk1sA4wSj7gugv3sf5yjUygAzcv
While I support this 100%, this is HF.
'Nuff said.
(Mar 4, 2011 03:49 PM)Ethereal Wrote: While I support this 100%, this is HF.
'Nuff said.
Lol has HF really put their reputation this low?
Bitcoin Address: 1KQCBvevk1sA4wSj7gugv3sf5yjUygAzcv
(Mar 4, 2011 03:50 PM)Vysse Wrote: Lol has HF really put their reputation this low?
HF is where skids come to play.
Mar 4, 2011 06:09 PM
(This post was last modified: Mar 4, 2011 06:10 PM by Zer0Fact0r.)
(Mar 4, 2011 03:50 PM)Vysse Wrote: Lol has HF really put their reputation this low?
It's just reality - at least in the Visual Basic & .NET Framework section.
You should add "Using threads when unnecessary". Seems to be a common misconception around these parts that threads > timers.
(Mar 4, 2011 06:09 PM)Zer0Fact0r Wrote: It's just reality - at least in the Visual Basic & .NET Framework section.
You should add "Using threads when unnecessary". Seems to be a common misconception around these parts that threads > timers.
Parallel programming > threads though IMO.
Mar 4, 2011 06:14 PM
(This post was last modified: Mar 4, 2011 06:15 PM by Vysse.)
(Mar 4, 2011 06:11 PM)Mr. Anderson Wrote: Parallel programming > threads though IMO.
Never heard of parallel programming care to elaborate?
(Mar 4, 2011 06:09 PM)Zer0Fact0r Wrote: It's just reality - at least in the Visual Basic & .NET Framework section.
You should add "Using threads when unnecessary". Seems to be a common misconception around these parts that threads > timers.
Added it in
Bitcoin Address: 1KQCBvevk1sA4wSj7gugv3sf5yjUygAzcv
Mar 5, 2011 12:51 AM
(This post was last modified: Mar 5, 2011 12:51 AM by Ethereal.)
(Mar 4, 2011 06:14 PM)Vysse Wrote: Never heard of parallel programming care to elaborate?
It refers to using multiple threads at one time to complete a task faster. e.g The program needs to complete two calculations, so it spawns another thread to deal with the second, thereby saving time.
One great example of this is Asynchronous sockets. Async sockets consists of having a Main thread dealing with the GUI, a Listener thread dealing with any connections and a worker thread dealing with any commands(i.e Send Data to each Client). If you were to use one thread, the GUI would keep freezing, and the effect would be very ugly and inefficient.
tl;dr - Read it -.-
(Mar 5, 2011 12:51 AM)Ethereal Wrote: It refers to using multiple threads at one time to complete a task faster. e.g The program needs to complete two calculations, so it spawns another thread to deal with the second, thereby saving time.
One great example of this is Asynchronous sockets. Async sockets consists of having a Main thread dealing with the GUI, a Listener thread dealing with any connections and a worker thread dealing with any commands(i.e Send Data to each Client). If you were to use one thread, the GUI would keep freezing, and the effect would be very ugly and inefficient.
tl;dr - Read it -.-
Interesting to know this thank you... I will be keeping this open for a few days and will get a graphic designer to mock something up and then will post the signature for all who want to use :D so keep the habits acoming...
Bitcoin Address: 1KQCBvevk1sA4wSj7gugv3sf5yjUygAzcv
|
