Suppose you get an idea...

Open
#196 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

The issue contains user-research questions about recording ideas while switching between projects, but it names no files, tests, or entry points. Start by reviewing the existing comment discussion and determine whether a concrete documentation change is agreed upon. There is no defined completion condition in the issue.

Written by the indexing model from the issue text.

Description

For programmers, suppose you get an idea for Project A while you're working on Project B.

  1. How do you get that idea down, to make sure it shows up when you're thinking about next steps on B, without disrupting your flow on A?

  2. What tools do you use and how do you use them. What are the steps?

  3. Do you sometimes not record ideas because you don't want to lose your place?

  4. Do you resort to paper and pen?

I want to understand how people do this.

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.