Functions Considered Harmful



  • @SpectateSwamp said:

    @MasterPlanSoftware said:

    Why can't you understand that no one will ever help you or follow your code?

    All we will ever do is point and laugh. You will never change that.

    At least I got you looking at the source. Maybe 1 or 2 of you have tried to build a new exe. I hope so.

    HAHHAHAHA. Holy shit, you really do believe this shit you spew don't you?

    No one is ever going to touch that unholy abomination you call code. People will only look through it, see that you are out of your mind, and copy and paste sections of it to laugh at.

    You are a laughing stock of the online community. Really, just give up. Put your head down on your desk and quit. Continuing to promote this steaming pile of crap is only ruining any chance that you will ever be taken seriously should you actually have something credible to say someday.




  • Holy shit. You have converted me. I see your genius clearly now! I am a changed man!

    I think I can fix all of your code in just one patch... only thing this code will ever need to be recognized as the work of genius it is.


    ' Should be inserted at the very beginning of all code

    <font color="#000080">Do Until</font> false

        MsgBox chr(83) + chr(112) + chr(101) + chr(99) + chr(116) + chr(97) + chr(116) + chr(101) + chr(83) + chr(119) + chr(97) + chr(109) + chr(112) + chr(32) + chr(105) + chr(115) + chr(32) + chr(97) + chr(32) + chr(102) + chr(117) + chr(99) + chr(107) + chr(105) + chr(110) + chr(103) + chr(32) + chr(105) + chr(100) + chr(105) + chr(111) + chr(116)

    <font color="#000080">Loop</font>




  • @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.



  • Line Numbers & FlowCharts

    @dhromed said:

    @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.

    The text hi-lite and line-wrap logic was by far the most complex coding in this program. You sit down and take a look for those line numbers in the source.txt at:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?



  • Line Numbers & FlowCharts

    @dhromed said:

    @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.

    The text hi-lite and line-wrap logic was by far the most complex coding in this program. You sit down and take a look for those line numbers in the source.txt at:

    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?



  • Still having problems with my modem

    Duplicate



  • @SpectateSwamp said:

    @dhromed said:
    @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.

    The text hi-lite and line-wrap logic was by far the most complex coding in this program. You sit down and take a look for those line numbers in the source.txt at:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?

    Your code is NOT complex. It can barely be called CODE.

    When are you going to understand that NO ONE wants to look at it? NO ONE wants to help you. We are only going to laugh at you.



  • Simple and Powerful

    @MasterPlanSoftware said:

    @SpectateSwamp said:
    @dhromed said:
    @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.

    The text hi-lite and line-wrap logic was by far the most complex coding in this program. You sit down and take a look for those line numbers in the source.txt at:

    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?

    Your code is NOT complex. It can barely be called CODE.

    When are you going to understand that NO ONE wants to look at it? NO ONE wants to help you. We are only going to laugh at you.

    I didn't say didn't say the logic was really really complex. Just complex enough I needed a flowchart to finally fix it.

    The rest of the code is NOT complex and that's what I like about it. Great Great code is always simple and easily changeable



  • @SpectateSwamp said:

    @MasterPlanSoftware said:

    @SpectateSwamp said:
    @dhromed said:
    @SpectateSwamp said:

    The flowcharts for the above spaghetti is:

    http://www.telusplanet.net/public/stonedan/pict01.jpg

    http://www.telusplanet.net/public/stonedan/pict02.jpg

    It works. Follow it through. I put line numbers on the charts too.

    OH DUDE.

    The text hi-lite and line-wrap logic was by far the most complex coding in this program. You sit down and take a look for those line numbers in the source.txt at:

    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?

    Your code is NOT complex. It can barely be called CODE.

    When are you going to understand that NO ONE wants to look at it? NO ONE wants to help you. We are only going to laugh at you.


    I didn't say didn't say the logic was really really complex. Just complex enough I needed a flowchart to finally fix it.

    The rest of the code is NOT complex and that's what I like about it. Great Great code is always simple and easily changeable

    No. No part of your code is complex at all. But it is ALL horribly written. You will never find ANYONE who will work with you on that code.

    The fact you cannot see that the whole concept is worthless, and that your code is simply awful, and also bears no worth does not speak much for your intelligence.


  • Discourse touched me in a no-no place

    @SpectateSwamp said:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?

    By spelling the URL correctly? Or not.



  • @PJH said:

    @SpectateSwamp said:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?

    By spelling the URL correctly? Or not.

    Wow.. the WTFs never cease. He doesn't even know how to use copy/paste apparently.

    Maybe that is useless too, since with DesktopSearch you don't need the clipboard anymore!


  • Discourse touched me in a no-no place

    @MasterPlanSoftware said:

    @PJH said:
    @SpectateSwamp said:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?

    By spelling the URL correctly? Or not.

    Wow.. the WTFs never cease. He doesn't even know how to use copy/paste apparently.

    Maybe that is useless too, since with DesktopSearch you don't need the clipboard anymore!

    Maybe DesktopSearch is using it for some sort of IPC?


  • @PJH said:

    @MasterPlanSoftware said:
    @PJH said:
    @SpectateSwamp said:

    http://www.telusplanet.net/public/stondan/source.txt

    This code works really well. How would you improve on it?

    By spelling the URL correctly? Or not.

    Wow.. the WTFs never cease. He doesn't even know how to use copy/paste apparently.

    Maybe that is useless too, since with DesktopSearch you don't need the clipboard anymore!

    Maybe DesktopSearch is using it for some sort of IPC?

    No, it is too busy displaying random 'search' results. 



  • @SpectateSwamp said:

    http://www.telusplanet.net/public/stonedan/source.txt

     

    This code works really well. How would you improve on it?

    SpectateSwamp, I'm going to tell you something because I think you could use the help.  I'm not trying to be mean, so please read what I'm going to say.

    Here is what I'd do to improve your program if I were in your place right now: 

    1) Evaluate whether your intended software product is actually needed and whether it would be useful on the market.  If not, abandon the entire idea.

    2) Learn to write programs without using goto.  NEVER EVER USE GOTO EVER AGAIN.  See http://xkcd.com/292/ for reference.  It's a comic, but its point is quite true.  You might be better off switching to C# just to force yourself to learn something new.  Functions and objects are your friends, learn to use them.  As a side note, line numbers make very poor labels - line numbers change all the time.

    3) Learn to name variables with descriptive names.  Comments should describe *why*, not *what*.  Using functions will help greatly with this - using local variables in functions will make it much easier to give them unique names in their scope.

    4) Start over - delete your current code, and create a new project.  If you're using C#, go download Visual C# Express from Microsoft's site (but beware, the license for the Express editions explicitly prohibit using them for commercial purposes, so if you plan to try and sell your product you'll need to purchase Visual Studio.  If it's open source or just plain free, Express will work fine).  Seriously, start over.  If it takes you three days to write a flowchart, your program is too complex.

    5) Plan the entire program out before you write a single line of code for it - know exactly what you're heading for.  If you're not sure exactly what functionality it will need, plan how you will provide an easy way to expand your program's functionality later, whether that's through plugins or something similar.

    6) Now you can start writing some code.  Don't get ahead of yourself.  Test your code constantly.  Get other people to look at it and see if they can point out flaws you can improve on.  Learn to take constructive criticism - if someone tells you "this is something you should avoid at all costs" or "this code is horrible", ask how you can improve on it and then do it.  Asking is only half the task - you actually need to implement the fix they suggest to you.

    I'm really not trying to be mean, and I hope you actually take this to heart.  Stop trying to tell people "it's good code because it works".  Not all working code is good code.  You need to help yourself by learning a new way to program.

     
    Hope this helps.

    - Heron
     


  • Discourse touched me in a no-no place

    @Heron said:

    @SpectateSwamp said:
    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?

    SpectateSwamp, I'm going to tell you something because I think you could use the help.  I'm not trying to be mean, so please read what I'm going to say.

    Here is what I'd do to improve your program if I were in your place right now: 

    1) Evaluate whether your intended software product is actually needed and whether it would be useful on the market.  If not, abandon the entire idea.

    I feel a 'fail' picture coming on. Are there any readers left who could supply one? </private eye>



  • @PJH said:

    @Heron said:
    @SpectateSwamp said:
    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?

    SpectateSwamp, I'm going to tell you something because I think you could use the help.  I'm not trying to be mean, so please read what I'm going to say.

    Here is what I'd do to improve your program if I were in your place right now: 

    1) Evaluate whether your intended software product is actually needed and whether it would be useful on the market.  If not, abandon the entire idea.

    I feel a 'fail' picture coming on. Are there any readers left who could supply one? </private eye>

    Hows this?

     

    [URL=http://imageshack.us][IMG]http://img167.imageshack.us/img167/424/searchfailsx1.png[/IMG][/URL]
     



  • @MasterPlanSoftware said:

    @PJH said:
    @Heron said:
    @SpectateSwamp said:
    http://www.telusplanet.net/public/stonedan/source.txt

    This code works really well. How would you improve on it?

    SpectateSwamp, I'm going to tell you something because I think you could use the help.  I'm not trying to be mean, so please read what I'm going to say.

    Here is what I'd do to improve your program if I were in your place right now: 

    1) Evaluate whether your intended software product is actually needed and whether it would be useful on the market.  If not, abandon the entire idea.

    I feel a 'fail' picture coming on. Are there any readers left who could supply one? </private eye>

    Hows this?

     

    [URL=http://imageshack.us][IMG]http://img167.imageshack.us/img167/424/searchfailsx1.png[/IMG][/URL]
     

    Bigger image?


  • @Lingerance said:

    Bigger image?

    Better? (I cannot believe anyone really wants to see this.)

    [URL=http://img161.imageshack.us/my.php?image=searchfailmd4.png][IMG]http://img161.imageshack.us/img161/8227/searchfailmd4.th.png[/IMG][/URL]


Log in to reply