2024-art-of-knowing-when-to-stop-optimization

[subahini]

…zation)'

[liuchengray]

External feedback:

negative aspect(s):
• It was not clear 2/12
• The article was too technical 1/12
• I lost interest midway 0/12
• The structure was confusing 1/12
• I didn't understand the purpose 1/12
positive aspect(s):
• The information was easy to understand 5/12
• Good balance between technical depth and readability 2/12
• I stayed engaged throughout 1/12
• The structure is clear and easy to follow 3/12
• I understood the purpose 1/12
did the drawing help to understand the meaning of the article?: 57,1 % Yes
factual errors or inaccuracies in the article:
“It is not entirely clear if the article is about code optimization or problem optimization. These are two different approaches. We can rewrite a piece of code "n" times and run it each time to see if the solution gets better. Or, a piece of code can be run once where it iteratively improves a solution "n" times and finally stop when no improvements happens. From the article, I understood that the example of baker corresponds to the first approach.”
additional comments:
“The image was bit confusing. From the text, I assume that the over-optimized image should be worse that optimized image. However, it was difficult to know which image is better than another one.”
“The heading should also mention about "smart improvements" and not just "when to stop".”

[carinaschrenk]

Internal Feedback Round 1A 07.11

Thoughts:

• Good metaphor, text is good
• Does not have to be about optimizing code but could actually be about optimizing
  data and models
• There should not be any text in the graphic
• It is misleading towards optimization in AI
• Is over-optimized really the same as having something that is too complex?

Ideas:

• The graphic should reflect the bakery metaphor

[erdemkoca]

Review Group 2

Feedback:

• The baking metaphor is engaging and effectively explains the concept of optimization.
• The text is concise and easier to follow compared to the previous version.
• Adding a brief example specific to data or model optimization could make the connection to technical concepts clearer.
• The balance between metaphor and technical explanation is well-maintained, though the conclusion could more explicitly tie back to practical applications.
• Overall, the article is a solid improvement and does a great job simplifying a complex concept.

[Ajorian]

The mesh-up practice feedback on 12.12.2024:

You can always improve your software; if you imagine different versions of software, you can see that developers consistently make progress. This means they can postpone releasing the current working version to achieve even more advancements. As this is a never-ending process, if they choose to follow this path, they might never release any version!

Detecting when to stop developing and release a version is not an objective fact; rather, it is an art. There are various factors to consider, including time, money, complexity, and more. Thus, computer science is not always purely scientific; sometimes, it requires a touch of artistry.

[subahini]

Thank you for your feedback. will try to update

[cloudflare-workers-and-pages]

Deploying tilics with    Cloudflare Pages

Latest commit:	ed653e9
Status:	🚫  Build failed.

View logs