Skip to content
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-concurrency-and-parallelism #135

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

arber-hyseni
Copy link
Collaborator

No description provided.

@tri2820 tri2820 changed the title add article a.h 2024-concurrency-and-parallelism Nov 21, 2024
@tri2820
Copy link
Collaborator

tri2820 commented Nov 21, 2024

Hi @arber-hyseni , this PR contains 4 file changes. A PR should contain only 2 file changes (the markdown article and the illustration image). Please update your branch to reflect this.

@carinaschrenk carinaschrenk added the 2024: round 2 articles of round 2 label Nov 21, 2024
@arber-hyseni arber-hyseni force-pushed the article-192-concurrency-parallelism branch 2 times, most recently from c1b55ec to 5f0f155 Compare November 28, 2024 08:51
@arber-hyseni arber-hyseni force-pushed the article-192-concurrency-parallelism branch from 5f0f155 to 973766f Compare November 28, 2024 08:52
@arber-hyseni
Copy link
Collaborator Author

Hi @arber-hyseni , this PR contains 4 file changes. A PR should contain only 2 file changes (the markdown article and the illustration image). Please update your branch to reflect this.

Fixed this


REVISED: Based on Feedback 2b

@evos96
Copy link
Collaborator

evos96 commented Nov 28, 2024

External feedback:

Part of participants that are computer science students/graduates: 47 %

Part of participants that would read the booklet if it was not for this survey: 70 %

Clarity of the article:

  • Very clear: 76 %
  • Clear: 12 %
  • Not clear: 12 %

Technical vs. Non-technical:

  • Good balance between technical depth and readability: 94 %
    The article was too technical: 6 %

Engagement:

  • I stayed engaged throughout: 76 %
  • I lost interest midway: 24 %

Structure of the article:

  • The structure is clear and easy to follow: 94 %
  • The structure was confusing: 6 %

Part of participants that understand the purpose of the article: 70 %

Part of participants that think the drawing helps to understand the meaning of the article: 59 %

Factual errors/inaccuracies or additional comments:

  • no

@carinaschrenk
Copy link
Collaborator

carinaschrenk commented Nov 28, 2024

Internal Feedback Round 2B 28.11

Thoughts

  • Not more text neeeded, good length
  • "Concurrency is like being a solo barista" -> metaphor does not fit properly

Ideas

  • Mention that concurrency is powerful but dangerous

Two general comments from today:

Just because something is listed in the feedback, does not mean you have to implement it.
This list is simply a collection of everything mentioned in the seminar and might even contain conflicting opinions.
You as the author still have the freedom to not make certain suggested changes.

Second, a general comment today was, that the articles of 2024 are quite technical and complex in comparison to 2019.
We could all strive to make our articles more simple and understandable to the general public.
Not every technical term needs to be mentioned and explained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants