Stay organized with collections
Save and categorize content based on your preferences.
Improve this paragraph for Jun and Arash
Jun and Arash are recent engineering school graduates who have just
joined your engineering team. In the past, new engineers on your
team have not run sufficient internal tests before releasing new
products. New engineers on your team usually don't know what the
term dogfooding means.
Revise the following paragraph for Jun and Arash:
There are several intended primary goals for dogfooding a new project.
At the current time, it is suggested by Engineering that all projects
be in dogfood for a period of no less than one month. One is to find
bugs under heavy, high-cycle usage. When disastrous bugs occurred in
153 out of 157 of the previous project releases, Engineering's analysis
of bugs in the aftermath concluded that prevention of the bugs could
have happened by more thorough testing.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-31 UTC."],[[["\u003cp\u003eJun and Arash are new engineering graduates joining the team, and new engineers have historically released products without sufficient internal testing.\u003c/p\u003e\n"],["\u003cp\u003eDogfooding, which may be unfamiliar to new engineers, is a critical testing practice where the team uses its own products internally.\u003c/p\u003e\n"],["\u003cp\u003eEngineering recommends a minimum one-month dogfooding period for all projects to find bugs under heavy usage conditions.\u003c/p\u003e\n"],["\u003cp\u003ePrevious project releases have experienced a high rate of disastrous bugs, with Engineering determining more thorough testing could have prevented them.\u003c/p\u003e\n"]]],["Okay, here's a summary of the core content, followed by a revised paragraph for Jun and Arash:\n\n**Summary of Core Content:**\n\nNew engineering team members, Jun and Arash, need to understand the importance of \"dogfooding.\" Past projects suffered from bugs due to insufficient testing. \"Dogfooding,\" or internal product testing, is now mandated for at least one month. The goal is to identify bugs under heavy use and prevent failures seen in past project releases. Thorough testing is now essential to project success.\n\n**Revised Paragraph for Jun and Arash:**\n\n\"Dogfooding\" means using our own products extensively before releasing them. Engineering now requires all projects to be \"dogfooded\" for at least one month. This allows us to find bugs under realistic, heavy usage. In the past, 153 out of 157 project releases had critical bugs. We found that these could likely have been avoided with more rigorous testing. We are now mandating internal use to ensure more reliable releases.\n"],null,["# Exercise 5\n\n\u003cbr /\u003e\n\nImprove this paragraph for Jun and Arash\n----------------------------------------\n\nJun and Arash are recent engineering school graduates who have just\njoined your engineering team. In the past, new engineers on your\nteam have not run sufficient internal tests before releasing new\nproducts. New engineers on your team usually don't know what the\nterm **dogfooding** means.\n\nRevise the following paragraph for Jun and Arash:\n\u003e There are several intended primary goals for dogfooding a new project.\n\u003e At the current time, it is suggested by Engineering that all projects\n\u003e be in dogfood for a period of no less than one month. One is to find\n\u003e bugs under heavy, high-cycle usage. When disastrous bugs occurred in\n\u003e 153 out of 157 of the previous project releases, Engineering's analysis\n\u003e of bugs in the aftermath concluded that prevention of the bugs could\n\u003e have happened by more thorough testing."]]
