I Apologise for yesterdays rant against VB.NET
-
Well it kind of is VB's fault, it's deliberately pitched as 'easy' and therefore attracts rubbish and inexperienced developers. Any production system in VB is likely to be crap.
What I can't get over is how easy it is to write Cr@p that compiles!!!
-
The problem I have with VB is that it is a old languages, designed fro non-programmers, that has been elephanted about with so many times to fit a modern paradigm (and it shows) that what you end up with has too much legacy stuff: weak typing, ON ERROR RESUME NEXT and so forth. What this end up with is a modern language that is pretty good (if too verbose and imprecise sometimes) that encourages poor programmers to code badly, and rewards that by working. Until... C# and so forth discourage that - I'm not saying you can't write good code in VB (you can) or bad code in C# (oh yes, you certainly can) but it's a lot easier to think you are a coding god and write cr@p in VB than it is in C#...
I must have been really bad in a previous life to have sort this out... :)
-
I must have been really bad in a previous life to have sort this out... :)
I think you're pretty bad in this one as well.
speramus in juniperus
-
I think you're pretty bad in this one as well.
speramus in juniperus
Java programmers... ;P
-
Java programmers... ;P
How very dare you! :laugh: As a mater of fact, I prefer Java to C# despite being proficient in both. When I fathom out why, I'll let you all know.
speramus in juniperus
-
How very dare you! :laugh: As a mater of fact, I prefer Java to C# despite being proficient in both. When I fathom out why, I'll let you all know.
speramus in juniperus
Nagy Vilmos wrote:
When I fathom out why, I'll let you all know.
Gin...
It was broke, so I fixed it.
-
Hi All, With some late night hacking and a little sleep (too little!) I have one the darned things working (I think!) and have a closer handle on what is broken with the other (Yayyy me!). I now accept it was a case of blaming the tools unfairly as I realised yesterday. Sorry VB the problem is your programmer are made up of many different types :rolleyes: and will build with some bugs and then offer a way of shutting them up with nasty fixes.:~
Posts about VB has a tendency to stir things up a bit as you saw first hand. :-D Glad you were able to sort things out on one of them, good luck on the rest. Think of this as a learning experience. and learn to keep your mouth shut when it comes to VB +5 for having the seeds to start this thread. :thumbsup: :beer:
It was broke, so I fixed it.
-
Hi All, With some late night hacking and a little sleep (too little!) I have one the darned things working (I think!) and have a closer handle on what is broken with the other (Yayyy me!). I now accept it was a case of blaming the tools unfairly as I realised yesterday. Sorry VB the problem is your programmer are made up of many different types :rolleyes: and will build with some bugs and then offer a way of shutting them up with nasty fixes.:~
C# welcomes back repentant sinners !
If you seek to aid everyone that suffers in the galaxy, you will only weaken yourself … and weaken them. It is the internal struggles, when fought and won on their own, that yield the strongest rewards… If you care for others, then dispense with pity and sacrifice and recognize the value in letting them fight their own battles." Darth Traya
-
Hi All, With some late night hacking and a little sleep (too little!) I have one the darned things working (I think!) and have a closer handle on what is broken with the other (Yayyy me!). I now accept it was a case of blaming the tools unfairly as I realised yesterday. Sorry VB the problem is your programmer are made up of many different types :rolleyes: and will build with some bugs and then offer a way of shutting them up with nasty fixes.:~
You beat me to it. I was going to go back to your other post and mention all that you have mentioned. Don't stress about what you said before I am sure we have all been there. I sure was! Funny thing too was I was working on a VB6->VB.Net project. This software was written in the mid 90s where standards were yet to be... standardized. There were many a time where each programmer's input over the years have muddied the waters quite a bit. Some condition statements being always true for whatever reason or always false. Or comments stating to make sure to put "that" back in. Whatever "that" refers too I still have no clue. So you are not alone in your frustration. Remember this one thing. Always keep putting one foot in front of the other and I am sure you will complete your project. Or in the words of Dory from Finding Nemo, "just keep swimming!" Happy coding! :)
-
You beat me to it. I was going to go back to your other post and mention all that you have mentioned. Don't stress about what you said before I am sure we have all been there. I sure was! Funny thing too was I was working on a VB6->VB.Net project. This software was written in the mid 90s where standards were yet to be... standardized. There were many a time where each programmer's input over the years have muddied the waters quite a bit. Some condition statements being always true for whatever reason or always false. Or comments stating to make sure to put "that" back in. Whatever "that" refers too I still have no clue. So you are not alone in your frustration. Remember this one thing. Always keep putting one foot in front of the other and I am sure you will complete your project. Or in the words of Dory from Finding Nemo, "just keep swimming!" Happy coding! :)
One the things I have learnt from this whole elephant is to get better & deeper explanation of what 'it' has to do and proper bug/wish lists I have the one part working now (all that is was originally told I had to do). The best bit is the 'Well it worked when it was left with you' the reply was 'It swallowed the errors, and carried on it said it had completed when the awkward tests weren't done', 'Make it work!!', 'I am trying...', 'it worked when X left it', 'No it didn't, it just glossed over the facts', which led to the post yesterday. :)
-
One the things I have learnt from this whole elephant is to get better & deeper explanation of what 'it' has to do and proper bug/wish lists I have the one part working now (all that is was originally told I had to do). The best bit is the 'Well it worked when it was left with you' the reply was 'It swallowed the errors, and carried on it said it had completed when the awkward tests weren't done', 'Make it work!!', 'I am trying...', 'it worked when X left it', 'No it didn't, it just glossed over the facts', which led to the post yesterday. :)
Then you had it rough! :) You're going to laugh at this. Before I drastically improved the software to what it is now. There were moments when running a report the users had to hold down the enter key because of the 10,000 error messages that popped up. The users got so good at timing how long they had to hold down the enter key. If they held it down for too long the "ReRun" report would be selected. That led to another 10,000 error messages to cycle through. :laugh: Talk about passing the "testing phase".
-
Hi All, With some late night hacking and a little sleep (too little!) I have one the darned things working (I think!) and have a closer handle on what is broken with the other (Yayyy me!). I now accept it was a case of blaming the tools unfairly as I realised yesterday. Sorry VB the problem is your programmer are made up of many different types :rolleyes: and will build with some bugs and then offer a way of shutting them up with nasty fixes.:~
That was an apology, sound like so further complaining, apology not accepted
-
That was an apology, sound like so further complaining, apology not accepted
Sorry!
