-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024-reverse-engineering-unpacking-software-mysteries #109
base: master
Are you sure you want to change the base?
Conversation
External feedback: negative aspect(s) pointed out: positive aspect(s) pointed out: Did the drawing help you to understand the meaning of the article? Did you notice any factual errors or inaccuracies in the article? If Yes, which part? Additional comments? |
Internal Feedback Round 1B 14.11Thoughts
Ideas |
Article updated again with all major changes to improve clarity and explain why and how reverse engineering is performed based on feedback! 🙂 |
Review Group 5 (Arita, Ivan, Parth)The revised article successfully clarifies the purpose and process of reverse engineering using a relatable analogy and improved structure. |
Creative writing (Subahini nadarajh version):Reverse engineering is like solving a kids’ puzzle without the picture on the box. First, you study the shapes and colors of the pieces—just like analyzing a program’s structure. Then, you start guessing where they fit, identifying patterns like data and variables. Your first attempts might not work, so you shuffle things around—like debugging your approach. Eventually, the pieces click into place, and you see the full picture, much like uncovering a program’s logic. It’s all about patience, observation, and a bit of trial and error to crack the code! |
creative writing ideas and suggestions
Ali, Arbër, Ivan, Laura |
No description provided.