Ukunika abasebenzisi uncedo, akukho ukuxhaswa 
 
 TL;DR: Ukuguqula iingxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo. TL;DR: Ukuguqula iingxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo. Iingxaki ezijoliswe 
 
 
 
 
 
 
 
 
 
 
 I-User Confusion and Frustration Akukho isinyathelo esebenzayo esekelwe Jargon Technical Iingxaki ezincinane ezisetyenziswa Ukutya I-Error Recovery Iinkcukacha ezincinane Ukunciphisa ukubaluleka kwamakhasimende Imiyalezo Generic Ukukhangisa Izixhobo ze-Code Smells https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xx-we-have-reached-100 https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxxiv https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xv https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-vi-cmj31om https://hackernoon.com/how-to-find-the-stinky-parts-of-your-code-part-xxvii Ukucinga 
 
 
 
 
 
 Zibonisa zonke iingxelo zeengxelo zeengxelo kwi-codebase yakho ezisetyenziselwa iingxelo ezifana ne-"Oops", "Yintoni efanelekileyo" okanye "Ukuza ingxelo" Ukuguqula iingxelo ze-generic ngeengxelo ze-specific of what happened Ukongeza imiyalelo esebenzayo enikezela kubasebenzisi ngokufanelekileyo into yokusebenzela inkxaso Ukusetyenzisa i-logging ye-internal efanelekileyo yokufaka iinkcukacha zenzululwazi zokusetyenziswa kwe-developer Ukongeza iingcebiso ze-monitoring ukuhlaziyisa i-team ye-development xa iingcebiso ziyafumaneka ngokushesha Sample Ikhodi Kwiintsuku function processPayment(paymentData) {
  try {
    // Too broad try catch  
    validatePayment(paymentData);
    chargeCard(paymentData);
    sendConfirmation(paymentData.email);
  } catch (error) {
    // Generic error message shown to user
    return {
      success: false,
      userMessage: "Oops! Something went wrong. Please try again.",
      error: error.message
    };
  }
}

function handleError(res, error) {
  // Exposing HTTP 500 to users
  res.status(500).json({
    message: "Internal Server Error",
    error: error.message
  });
}
 Ngoku function processPayment(paymentData) {
  try {
    validatePayment(paymentData);
    // This catch is specific to payment validation
  } catch (error) {
    // 1. Identify all generic error messages in your codebase
    // that use terms like "Oops", "Something went wrong", 
    // or "An error occurred"    
    // 2. Replace generic messages 
    // with specific descriptions of what happened
    // 3. Add actionable guidance telling users 
    // exactly what they can do to resolve the issue
    // 4. Implement proper internal logging 
    // to capture technical details for developers
    logger.error('Payment validation failed', {
      userId: paymentData.userId,
      error: error.message,
      stack: error.stack,
      timestamp: new Date().toISOString()
    });
    // 5. Add monitoring alerts to notify 
    // the development team when errors occur frequently    
    alerting.notifyError('PAYMENT_VALIDATION_FAILED', error);
    if (error.code === 'INVALID_CARD') {
      return {
        success: false,
        userMessage: "Your card information" + 
        " appears to be incorrect." +
        "Please check your card number," + 
        " expiry date, and security code."
      };
    }
    return {
      success: false,
      userMessage: "There was a problem validating" +
      " your payment." +
      "Please try again or contact support."
    };
  }

  // You should break this long method
  // Using extract method
  try {
    chargeCard(paymentData);
  } catch (error) {
    logger.error('Card charging failed', {
      userId: paymentData.userId,
      error: error.message,
      stack: error.stack,
      timestamp: new Date().toISOString()
    });
    alerting.notifyError('CARD_CHARGING_FAILED', error);
    if (error.code === 'INSUFFICIENT_FUNDS') {
      return {
        success: false,
        userMessage: "Your payment couldn't be processed"+
        " due to insufficient funds. " +
        "Please use a different payment method" + 
        " or contact your bank."
      };
    }
    if (error.code === 'CARD_EXPIRED') {
      return {
        success: false,
        userMessage: "Your card has expired. " +
        "Please update your payment method with a current card."
      };
    }
    return {
      success: false,
      userMessage: "There was a problem processing your payment." +
      " Please try again or contact support."
    };
  }

  try {
    sendConfirmation(paymentData.email);
  } catch (error) {
    logger.error('Confirmation sending failed', {
      userId: paymentData.userId,
      error: error.message,
      stack: error.stack,
      timestamp: new Date().toISOString()
    });
    alerting.notifyError('CONFIRMATION_FAILED', error);
    return {
      success: true,
      userMessage: "Payment processed successfully,"+
      " but we couldn't send the confirmation email." +
      " Please check your email address or contact support."
    };
  }

  return { success: true,
          userMessage: "Payment processed successfully." };
}
 Uhlobo 
 
 [x] Manual Ukhuseleko ️ Oku refactoring ukuguqulwa umzimba kwaye kulula ukuba uqhagamshelane lokubhalisa kunye neengxelo ezisebenzayo yokubhalisa. Ukunciphisa iinkcukacha ezininzi ezininzi ezininzi ezininzi ezininzi ezininzi ezininzi. I-Risk ye-Breaking Changes ihamba njengoko utshintshe ukuphucula ukuqhagamshelwano kwamafutha ezikhoyo kunokuba ukuguqulwa i-core business logic. Yintoni i-Code yinto engcono? Uyakwazi ukunika abasebenzisi izixhobo ezisetyenziswayo kunokuba ukutshintshwa. Uyakwazi ukuvelisa i-user experience enokuthi ukunika i-feedback emangalisayo, efanelekileyo kunokwenzeka, ngaphandle kokufunda i-tech jargon. Umdlali uyazi ukuba iingxaki zangena kwaye uyazi iingxaki zangaphambili zayo. Uyafumanisa iingxaki ngokugcina iinkcukacha zobuchwepheshe kwi-logs ngelixa iindaba ze-business-friendly kubasebenzisi. I-team yakho ye-support inokufumana ulwazi olufanelekileyo ngokusebenzisa i-logging ye-structured. Uyakwazi ukuyifaka kwimibuzo ye-system ngokucacileyo nge-monitoring i-alerts ngaphambi kokufumana kubasebenzisi. Uyakwazi ukugcina iinkcukacha zobuchwepheshe ngaphandle kwabo, kodwa uqhagamshelane ukuxhaswa kweemibuzo ngokukhawuleza. Yintoni i-Bijection? ️ Ngaphandle kweengxelo ze-"Oops" ezininzi, isisombululo yakho ibhalisele kwiimeko ezininzi ezibonakalayo ezibonakalayo. Umxholo we-Error Messages kuquka ulwazi olufanelekileyo malunga neengxaki kunye nenkqubo yokulungisa. I-Real World Umbhali we-casher ayikwazanga "Oops, kukho into engabikho" xa ibhokisi lakho lithunyelwe - bafumana inkinga elifanelekileyo kwaye zixazulule izixazululo. Le refactoring ifumaneka i-software model kunye iimfuno ze-error communication, okwenza i-system engapheliyo kunye ne-friendly kubasebenzisi Ukucinga Ukucaciswa ✔️ Uya kufuneka uxhomekeke ukuba unxibele iinkcukacha ze-system sensitive enokuncedisa iingcali. Zonke iingxaki ziya kufuneka ziyafumaneka generic ngenxa yobugcisa (njenge iingxaki ze-authentication). Ukongeza, ukuvelisa iingxelo zeengxelo ezithile kufuneka ixesha elide lokuphuhlisa kunye nokuvavanya iingxelo zeengxelo. Refactor nge AI 
 
 I-Suggested Prompt: 1. Khetha zonke iingxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo ze I-Suggested Prompt: 1. Khetha zonke iingxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo zeengxelo ze 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 Without Proper Instructions 
 With Specific Instructions 
 
 
 
 ChatGPT 
 ChatGPT 
 
 
 
 Claude 
 Claude 
 
 
 
 Perplexity 
 Perplexity 
 
 
 
 Copilot 
 Copilot 
 
 
 
 You 
 You 
 
 
 
 Gemini 
 Gemini 
 
 
 
 DeepSeek 
 DeepSeek 
 
 
 
 Meta AI 
 Meta AI 
 
 
 
 Grok 
 Grok 
 
 
 
 Qwen 
 Qwen Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga I-Pilot I-Pilot Ngaba Ngaba Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga Ukucinga iintsuku ️ 
 
 Ukucaciswa Umgangatho 
 
 [x] I-Intermediate Iimveliso ezihambelana https://hackernoon.com/refactoring-014-how-to-remove-if?embedable=true Yintoni https://hackernoon.com/fail-fast-philosophy-explained-si963vk9?embedable=true https://www.morling.dev/blog/whats-in-a-good-error-message/?embedable=true https://ulrikapark.wordpress.com/2021/05/03/are-you-sure-people-get-happy-about-your-oops-error-messages-or-does-it-lower-their-trust-in-your-software/?embedable=true https://www.sonarsource.com/learn/error-handling-guide/?embedable=true Iimali Umbala Yintoni URyan McGuire I-Pixabay Le nqaku iindawo ye-Refactoring Series. https://maximilianocontieri.com/how-to-improve-your-code-with-easy-refactorings?embedable=true

The code in this story is for educational purposes. The readers are solely responsible for whatever they build with it.

Winner of Noonies 2020 for the award Hacker Noon Contributor of the Year - REFACTORING.

Refactoring 031 - Ukunciphisa i-OOPs

About Author

IZIMVO

ZIJONGE IIMPAWU

ELI NQAKU LINIKEZELWE KU

Related Stories

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps