|
Except when your code blocks are catchs in ifs in switchs.
|
|
|
|
|
If you're doing that, you need more help than just a VB.NET End can give.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
While doing linq in VB.NET is possible it is implemented much better in C#.
Eric
|
|
|
|
|
|
I've used LINQ in both C# and VB.net... a lot. Once again, there is no real difference between the two languages. C# has better syntax; it makes you look smarter. VB.net gives you a better idea of what's actually happening; it educates you.
.NET is the magic here. C# and VB.net are just twin languages riding its glory.
- great coders make code look easy
- When humans are doing things computers could be doing instead, the computers get together late at night and laugh at us. - ¿Neal Ford?
|
|
|
|
|
Sander Rossel wrote: There is no finer language on earth in Mordor!
FTFY!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Ash VB durbatulûk, ash VB gimbatul,
ash VB thrakatulûk, agh burzum-ishi krimpatul.
|
|
|
|
|
Pete O'Hanlon wrote: Pragmatic.
Ahem...
if (OriginalPoster == isProgrammerWhoDoesMaintenanceOnOwnCode)
{
OriginalPoster = PragmaticProgrammer;
}
else
{
OriginalPoster = MajorProblemCreator;
}
|
|
|
|
|
Step away from the keyboard, and take a long walk. Rest your mind and your senses. Don't take this stuff we do, too seriously.
|
|
|
|
|
IMHO, a good rule is:
1. Make it work.
2. Then make it work better - run faster, use lesser memory, use better algorithms, etc.; essentially optimize.
Have seen people creating elaborate UML diagrams, only to find shortcomings in the code. In one extreme case, the code (C++) did not run; then the coder globally replaced all private by public , and it ran; throwing away all encapsulation to the wind; fixing this was a nightmare
|
|
|
|
|
Wat be this private thing you speak of?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
The first law of optimization: Don't do it
The second law of optimization: If you HAVE to do it, don't do it yet!
The only real optimization you can do is to replace your algorithm or data structures (or both). That means you go back to square one (not necessarily for the entire system, but for that part you try to optimize), and the two laws above still applies.
|
|
|
|
|
codejet wrote: I just realised that I am one of those people who can write code that works
pretty well. Gratz; it's harder than it appears.
codejet wrote: Question is who/what am I? A pretty good programmer/developer. Must be, based on your second sentence.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Ok, I am going to request that my job title be changed from Applications Developer to Pragmatic Application Developer and will be sure to mention that I am pragmatic in my next interview.
|
|
|
|
|
Depressed? Relax and On Error Resume Next...get it working, then make it work right! In software there's always room for improvement!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Quote: Relax and On Error Resume Next
That needs to be on a t-shirt!!!
- great coders make code look easy
- When humans are doing things computers could be doing instead, the computers get together late at night and laugh at us. - ¿Neal Ford?
|
|
|
|
|
codejet wrote: I'm not always proud of my methods (don't mean methods as in procedures) and design, most of the time I do whatever works. I get my code to work by any means necessary. I guess I am not a programmer/developer
FTFY
Contrary to how academics define programmer/developer in reality the code needs to work.
Sometimes you will be forced to produce under circumstances that are out of your control.
The results may not be pretty but if it works is all that can be expected, not some textbook solution that you do not have the means to produce in the current situation.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs JimmyRopes Designs
|
|
|
|
|
Writing a code that works pretty well is not enough for a programmer. Actually, your ability to write a working code is not relevant in this context.
First, learn OOP and take design patterns course. Apply this knowledge in your new programs. If you are working with classes, make them all singletons. If you are working with WPF, don't write code-behind. In C/C++ mark all variables as register (every real programmer knows that register variables are faster), and make all functions inline.
Finally, you can find that your skills match your official position. You code will not work pretty well at this stage, but let's leave these details for code writers.
|
|
|
|
|
codejet wrote: Question is who/what am I?
This is called a Voight-Kampff machine. You’ve got a little boy. He shows you his butterfly collection plus the killing jar...
|
|
|
|
|
You are like most of the successful professionals.
The best programmers solve problems with whatever is given and provide solutions by any means necessary.
So, you solve problems. Be proud!!
|
|
|
|
|
If you want to find out the history of Aladdin’s Lamp, do you need a Genieologist?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
And if you want to check inside his lamps spout, do you need a Geniecologist?
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
He'll first need to drop his blue genies.
Contrary to popular belief, nobody owes you anything.
|
|
|
|
|
I guess I am nit-picking and ignoring the humor, but it should be Geniealogist. Since it is based off of genealogy.
Brent
|
|
|
|