|
I think
doja93 wrote: she, "..wanted to add exception handling.." to her code
already show she has potential, just need some guidance... I've seen very few developers who WANT to add exception handling to their code...
I did this article, readers seemed to have found it informative: Exception Concepts for Business Applications
I'm way over due to continue with a second article, I know...
____________________________________________________________
Be brave little warrior, be VERY brave
|
|
|
|
|
That's the best answer I have seen yet. sometimes writing code is not about making it work, but how to handle things when they don't work.......
|
|
|
|
|
I think this is not real. Understandable you cut the actual do something code but where is your semi-colon after the 'throw e'
I assume you typed this code, maybe you missed an important bit of catch code
Life goes very fast. Tomorrow, today is already yesterday.
|
|
|
|
|
Yoy. At least they used camel casing
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything.
I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
|
|
|
|
|
I like that!
A former collegue of mine had a tendency to use very long and elaborate variable/function/method/property names. One day i invented an unused property called __AVeryLongAndLargelyUnusedProperty_PKA. PKA being his initials. Need i say that i forgot all about it. The thing went into production, until years later PKA one day yelled at me: What the shikes is this?
|
|
|
|
|
Looks very brownfield to me
(yes|no|maybe)*
|
|
|
|
|
public int F ( int Reserved ) ...
|
|
|
|
|
Hmmm, let's improve it!
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
{
if (dontUseThisWeHaveToDeleteThisMethod is bool && (bool)dontUseThisWeHaveToDeleteThisMethod) return;
}
Seems better?
|
|
|
|
|
|
Hockey is the greatest sport in the world.
It's Movember, Mustache competitions are important, as they are to raise awareness for prostate cancer.
And a career like taxes in Canada sounds AWESOME! Where do I apply?!
|
|
|
|
|
GibbleCH wrote: Hockey is the greatest sport in the world.
Boxing is the greatest sport. It gets past all that silly foreplay and you get to see what you came there to see... the fight!
|
|
|
|
|
The most ruthless game I've ever played is Croquet. It looks genteel, but you constantly have to F@*k your opponents as much as possible over to win.
Don't confuse Cricket with Croquet[^]
|
|
|
|
|
I did play croquet in my backyard when I was younger. Maybe that's why I always make miniature golf a full-contact (as far as our balls are concerned) sport.
|
|
|
|
|
Leave my balls alone, would you...
(You're all thinking it, I just had the balls to say it)
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Despite YEARS of development, we would still get a if pressed CTRL + Backspace in Visual Studio anywhere outside the code editor. What's interesting: it happens even in new WPF-y diagramming tools. It seems that Microsoft decided to cultivate the tradition bug.
I ask: How many years do we have to wait yet?
Greetings - Jacek
|
|
|
|
|
I guess Microsoft hasn't realized that there are power users out there who actually use shortcuts...
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
I guess Microsoft keep that bug as a signature of tradition
|
|
|
|
|
I hope he keeps delighting us with his coding horrors as he gets more into programming.
|
|
|
|
|
That is indeed a horror; especially from someone who should know better
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
He's an accountant. Give him a few years as a programmer and I'm sure he'll know better.
|
|
|
|
|
|
da-leak is d bigst horor!
|
|
|
|
|
This[^] is one of the funniest things I have ever read.
|
|
|
|
|
Although I am not primarily a driver developer, I have written a few. The 1st rule is don't put any MessageBoxes in the driver not even while debugging.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
Recently a developer in the team decided to prefix all classes in a namespace with a four alphabet acronym (let's call it DSRS, it's pretty close to what it is). I cannot elaborate how many brain cells have gone dead in me in comprehending the code and telling him to remove that prefix or use something more useful. His answer: people will get used to it and so will new devs... Speechless....
Ashish Kaila
|
|
|
|