Skip to main content
Software Engineering

Return to Question

Question Protected by gnat
edited tags
Link
Jim G.
Jim G.
  • 8k
  • 3
  • 37
  • 66

Refactoring code smells in ASP.NET Web Forms Code Behind Files: Is it risky? Is it wise? Is it a waste of time?

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

Given a long methodlong method with Pac-Man ifsPac-Man ifs, would it be wise to:

  1. Break down code blocks into regions.
  2. Then refactor code blocks into methods.

Or would it be best to leave it alone?

Would it be risky?
Would it be a waste of time?

In the absence of automated unit-tests, I'm trying to understand the risk-reward relationship associated with this manuever.

Given a long method with Pac-Man ifs, would it be wise to:

  1. Break down code blocks into regions.
  2. Then refactor code blocks into methods.

Or would it be best to leave it alone?

Would it be risky?
Would it be a waste of time?

In the absence of automated unit-tests, I'm trying to understand the risk-reward relationship associated with this manuever.

Given a long method with Pac-Man ifs, would it be wise to:

  1. Break down code blocks into regions.
  2. Then refactor code blocks into methods.

Or would it be best to leave it alone?

Would it be risky?
Would it be a waste of time?

In the absence of automated unit-tests, I'm trying to understand the risk-reward relationship associated with this manuever.

Source Link
Jim G.
Jim G.
  • 8k
  • 3
  • 37
  • 66

Refactoring code smells in ASP.NET Web Forms Code Behind Files: Is it risky? Is it wise? Is it a waste of time?

Given a long method with Pac-Man ifs, would it be wise to:

  1. Break down code blocks into regions.
  2. Then refactor code blocks into methods.

Or would it be best to leave it alone?

Would it be risky?
Would it be a waste of time?

In the absence of automated unit-tests, I'm trying to understand the risk-reward relationship associated with this manuever.