Hi CP community. We hired a guy that did this a while ago. It annoyed me then, and now I have a project that I'm refactoring that lo and behold has it as well. Maybe I'm missing some recommended practice (I googled it), and I don't mean to start a war or anything. I just don't see an obvious use for things like this. The message is the same when a socket error occurs...

try
{
DoSomething();
}
catch (SocketException e)
{
Console.WriteLine(e.Message);
conn.connecting = false;
}
catch (Exception e)
{
Console.WriteLine(e.Message);
conn.connecting = false;
}

What purpose in life, universe, code, etc... does a practice like this serve?! (Clarification for all of those who've been giving concrete reasons for catching different exception types. I get that. I do that as well. I'm saying that the guy we hired previously would handle several exception types only to do the same thing as the catch-all block. Literally the same thing. Sometimes he would catch a type only to throw it to the main block doing nothing with the specific type. It bugged the hell out of me. Now I'm refactoring another project that is completely unrelated and I see a similar practice which made my mind wander to here...)

Nailed it!

I think I work in an environment teetering on the edge of toxicity. Our shop follows "strict agile principles" says our leader to any outsiders unfortunate enough to ask about our processes and get a response. Previously we were a self-guided waterfall group which transformed from a ten million dollar company that was eventually bought by an enterprise. Present day, we have added a few more heads; one of which is a "senior" who is baffled by things like string.Format, generics and well most any other concepts beyond Hello-world and IDE features, but he's got 20+ years experience... he didn't get fizz-buzzed or any coding interview btw. But I digress. Now our process is "agile". And by "agile" I mean we subscribe to the following practices: - Sprints vary from 1-6 weeks and are as predictable as the weather on Jupiter - User Stories? I hear the term often, but the team has never actually seen one - Estimation and Planning, we do this sporadically but it has been a while since the last one - Tasks are added to the sprint EVERY day - Need clarification/details on tasks like "Implement Security" and "Improve Performance", ask the product owner - Have concerns about a feature or edict that would be construed as a bad practice or horrible UI layout, take it up with the product owner - There is no official product owner and the tasks above typically come from the leaders or their suboordinates - Retrospectives, i think we've had one of those. - Backlog grooming, thats where you add more tasks right? - Conversations like this happen often: Mgmt: We need to implement feature Y for the release we scheduled 45 days from now (based on no estimates btw) Dev: You told me feature X was priority. We spec'ed out feature X so we could deliver a finished product in 45 days. Which is a priority? Mgmt: Both... (along with a WTF are you asking expression) Dev: Lets assume feature Y takes the same time we think X will. Thats 90 days. You want that in 45 days? Mgmt: Yes, you guys are sharp. You're a great, talented group; you'll figure it out (<- Leadership training) Dev: Talent aside, time is time... where are we going to squeeze this extra stuff in? Mgmt: Wherever you can. Theres always nights and weekends right? - Theres a graph that tracks the burndown for tasks to the end of the sprint. Mgmt is concerned about why it always trends upward and never down. Perhaps its a bug in TFS. Solution: don't estimate something until you start working on it... I could write a novel, but nonetheless. I once wond

I've done this too using the try { InguaralObject.FirstRun(); } catch(Exception ex) { } It works every time!

I had a request come across today that kinda caught me off guard. I work on a project that has devices which have a "Master" and "Slave" designation. It has been that way since before my time. We're now part of a bigger enterprise, and I was told that since we are a "forward thinking and diverse company" I should change the designations in the software to read Primary and Secondary. I'm torn between fighting this "forward thinking" with subtle easter eggs or making my code less offensive (who knew?!). Apparently I am not alone. Little did I know that IDE hard drives also believed in the inherent superiority of one race over another based on a jumper setting... Have you checked for subtle hints of racism in your code lately??? :omg:

You read my mind... unfortunately all that yields is pattern graphs that some poor government sap may construe as art. It is a clever exercise in simulating various ways to lose lots of money.