Skip to content

finished general concepts#105

Open
williamldennis wants to merge 1 commit intofractal-nyc:mainfrom
williamldennis:will-dennis/general-concepts
Open

finished general concepts#105
williamldennis wants to merge 1 commit intofractal-nyc:mainfrom
williamldennis:will-dennis/general-concepts

Conversation

@williamldennis
Copy link
Copy Markdown

@williamldennis williamldennis commented May 31, 2025

finished general concepts


Important

Adds willdennis.md with explanations on key computer science concepts and language choice considerations.

  • New Content:
    • Adds willdennis.md under computer-science/general-concepts/answers/ with explanations on synchronous vs asynchronous processing, recursion, parallel vs concurrent processing, and anonymous functions.
    • Discusses language choice with a comparison between JavaScript (Node.js) and Go for building a real-time chat app.
  • Concepts Explained:
    • Synchronous vs asynchronous processing, including how different languages handle async operations.
    • Recursion and its use cases.
    • Parallel vs concurrent processing.
    • Anonymous functions and their use cases.
    • Language choice considerations based on project needs.

This description was created by Ellipsis for 2384114. You can customize this summary. It will automatically update as commits are pushed.

Copy link
Copy Markdown
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Changes requested ❌

Reviewed everything up to 2384114 in 1 minute and 26 seconds. Click for details.
  • Reviewed 75 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 3 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .DS_Store:1
  • Draft comment:
    Avoid committing OS‐specific files like .DS_Store. Add it to your .gitignore to prevent clutter.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
2. computer-science/general-concepts/answers/willdennis.md:64
  • Draft comment:
    Add a newline at the end of the file for consistency with POSIX standards.
  • Reason this comment was not posted:
    Confidence changes required: 33% <= threshold 50% None
3. computer-science/general-concepts/answers/willdennis.md:2
  • Draft comment:
    Suggestion: In the question on line 2, consider capitalizing the names of the programming languages – change "go, python, etc" to "Go, Python, etc" for consistency.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While technically correct that language names are conventionally capitalized, this is a very minor stylistic issue in what appears to be a markdown file with Q&A content. The meaning is perfectly clear without the capitalization. This feels like nitpicking that doesn't materially improve the code or documentation quality. The capitalization convention for language names is a real thing, and some might argue it shows attention to detail and professionalism. However, this is a minor stylistic issue in an informal Q&A document, and our rules specifically say not to make comments that are obvious or unimportant. This comment should be deleted as it's too minor and doesn't materially improve the content.

Workflow ID: wflow_PgoG09ABIUbdCCKt

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.


Why would you choose one language over another? Can you give an example scenario and trade off two languages?
- You choose one programming language over another based on the project's needs, including factors like performance, developer experience, ecosystem, scalability, and community support.
-
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate bullet found in the language choice answer. Remove the repeated entry.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant