Pèmèt itilizatè a ede, pa konfò 
 
 TL;DR: Remplaze mesaj erè vagu ak konpetitif, aksyonab repons ki ede itilizatè rezoud pwoblèm. TL;DR: Remplaze mesaj erè vagu ak konpetitif, aksyonab repons ki ede itilizatè rezoud pwoblèm. Problèm rezoud 
 
 
 
 
 
 
 
 
 
 
 Konfuzyon ak frustration nan itilizatè Pa gen okenn apwòch aksyon Jargon teknik Pifò erè ki pa trete Sòti nan Kòmanse erè Inkomplè enfòmasyon erè Diminye konfyans itilizatè Mesaj jenerik Silenti rezoud Kòd ki gen rapò ak odè 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 Etap 
 
 
 
 
 
 Identifye tout mesaj erè jenerik nan baz la kòd ou ki itilize tèm tankou "Oops", "Ki sa ki te mal", oswa "Ki sa ki te yon erè rive" Remplaze mesaj jenerik ak deskripsyon spesifik nan sa ki te pase Ajoute enstriksyon aksyonab ki di itilizatè yo kèlkeswa sa yo ka fè yo rezoud pwoblèm la Implemante regilasyon enteryè apwopriye pou retire detay teknik pou devlopè yo Ajoute alèt kontwole pou anonse ekip la devlopman lè erè apar souvan Kòd echantiyon Premye 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
  });
}
 Apre 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." };
}
 Ki jan 
 
 [X] Manual nan sekirite ️ refactoring sa a chanje konpòtman an ak se san danje si ou kenbe log ak alèt aktif pou debugging. Evite retire detay ki nesesè pa ekip sipò. Riski de vire chanjman se ki ba paske ou se amelyore jesyon erè ki deja egziste anvan chanje logik biznis kle. Poukisa Kòd la se pi bon? Ou bay itilizatè a konsèy itil olye pou konfò. Ou kreye yon pi bon eksperyans itilizatè pa bay yon repons klè, aksyonab olye pou konfòme jargon teknik. itilizatè yo konprann sa ki te mal ak konnen etap pwochen yo. Ou separe pwoblèm pa kenbe detay teknik nan log pandan y ap montre mesaj biznis-zanmitay pou itilizatè yo. Ekip sipò ou jwenn pi bon debug enfòmasyon atravè estrikti logging. Ou ka proaktif rezoud pwoblèm sistèm pa kontwole alèt anvan itilizatè yo rapòte yo. Ou kenbe enfòmasyon teknik soti nan yo, men toujou anrejistre li pou yon rezolisyon pi vit nan pwoblèm. Ki jan yo amelyore bijection? ️ Ou kenbe yon matche pi byen ant mond lan reyèl ak modèl ou. Anplis de mesaj vye granmoun "Oops", sistèm ou pale nan tèm klè ki reflete evènman reyèl. mesaj erè nan gen enfòmasyon spesifik sou sa ki te mal ak ki jan yo koreksyon li. Reyèl Mondyal Yon kasyeur pa di "Oops, yon bagay te ale mal" lè kat ou se refize - yo di ou pwoblèm espesifik ak sijere solisyon. refactoring sa a aliye modèl la lojisyèl ak modèl kominikasyon erè, fè sistèm la plis intuitif ak itil pou itilizatè Bijection Limite nan ️ Ou dwe atansyon pa ekspoze enfòmasyon sensitif sistèm ki ta ka ede atakè. Yon kèk erè ka bezwen rete jenerik pou rezon sekirite (tankou erè autentifikasyon). Anplis de sa, kreye mesaj erè espesifik mande pou plis tan devlopman ak tès konplè nan senaryo erè. Refactor ak AI 
 
 Suggested Prompt: 1. Identifye tout mesaj erè jenerik nan baz la kòd ou ki sèvi ak tèm tankou "Oops", "Ki sa ki te mal", oswa "Ki yon erè te rive" 2. Replaze mesaj jenerik ak deskripsyon espesifik nan sa ki te rive 3. Ajoute yon gid aksyonable ki di itilizatè yo kèlkeswa sa yo ka fè yo rezoud pwoblèm la 4. Implemantasyon logging enteryè a apwopriye pou retire detay teknik pou devlopè yo 5. Ajoute alèt kontwole yo anonse ekip devlopè a lè erè yo ap vini souvan. Suggested Prompt: 1. Identifye tout mesaj erè jenerik nan baz la kòd ou ki sèvi ak tèm tankou "Oops", "Ki sa ki te mal", oswa "Ki yon erè te rive" 2. Replaze mesaj jenerik ak deskripsyon espesifik nan sa ki te rive 3. Ajoute yon gid aksyonable ki di itilizatè yo kèlkeswa sa yo ka fè yo rezoud pwoblèm la 4. Implemantasyon logging enteryè a apwopriye pou retire detay teknik pou devlopè yo 5. Ajoute alèt kontwole yo anonse ekip devlopè a lè erè yo ap vini souvan. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 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 Chato Chato Claude nan Claude nan Perpleksite Perpleksite Pilòt Pilòt ou ou Twin nan Twin nan DeepSeek DeepSeek Objektif nan Objektif nan Pwodwi Pwodwi Pwen Pwen Dapre ️ 
 
 Eksepsyon Nivèl 
 
 [x] Mwayen Relasyon ki gen rapò https://hackernoon.com/refactoring-014-how-to-remove-if?embedable=true Li se 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 Kredi imaj nan nan Ryan McGuire nan Pixabay nan Paj sa a se yon pati nan seri a Refactoring. 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 - Retire OOPs

About Author

KÒMANtè

KANDYE TAGS

ATIK SA A TE PREZANTE NAN

Related Stories

HackerNoon Contributor Nikita Vasilev on Programming, Python, and More

Code Smell 286 - Parent-Child Method Overlaps

Meet the Writer: Vik Bogdanov, Tech Storyteller

Code Smell 260 - Crowdstrike NULL

HackerNoon Contributor Nikita Vasilev on Programming, Python, and More

Code Smell 286 - Parent-Child Method Overlaps

Meet the Writer: Vik Bogdanov, Tech Storyteller

Code Smell 260 - Crowdstrike NULL

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps