Open dynamictech-ops opened 5 years ago
How do we structure issues? Are they broad high level funnels for ideas or are they previously identified action items that need to be addressed eventually as pull requests? Just so that our issues have a structured purpose.
Topic: Psychology of the Developer: What makes us different?
Topic: Heap Search: Finding a needle in a haystack
Topic: Indexing and Partitioning: What's the difference and how do we use them together?
Topic: Sorting algorithms and Data Structures: Optimizing search in different languages
Topic: Elasticsearch, Full text search, and SQL (if these don't necessarily correlate, feel free to make them separate articles)
Topic: Non-relational Databases
Topic: The Psychology of Imposter Syndrome
Topic: The Psychology of Introverts
~Topic: Syntax and Phonology: How learning programming languages relates to learning verbal languages~
I would like to use a project board to prioritize what you think you can do quickly and what would make sense to do before tackling something else. This will also help me visualize how much time you need to develop a good article and how much time I should be equivalently spending developing other revenue streams while you're writing.
Topic: Data Structures: Tries, How and when to use them
Topic: Syntax and Phonology: How learning programming languages relates to learning verbal languages
No correlation.
There actually is a syntax within any particular natural language's phonology, usually to make speaking more efficient and less effortful. But most audiences not passionate about linguistics will be turned off by the details. Your audience is likely IT folks not quite interested in natural languages; doesn't help their work or career.
I would like to use a project board to prioritize what you think you can do quickly and what would make sense to do before tackling something else. This will also help me visualize how much time you need to develop a good article and how much time I should be equivalently spending developing other revenue streams while you're writing.
Once you decide to pick up a topic, please make a card for it on the project board. We can re-organize/prioritize this board a couple times a week.
Topic: Workflow: Multiple devs collaborating on the same issue without merge conflicts
Teaching vs Publication
Teach first, publish later.
Teach In-house First
Jon will write for in-house learning, first and foremost. That means a lot of requisite foundational knowledge will not be covered in the first draft (will be a final draft if in-house team already understands the article/lesson).
Publish Later
Writing for publication requires a fuller coverage of requisite foundational knowledge; most people (Pareto ratio, normal distribution) cannot and will not self-study said foundational knowledge. We won't be publishing to teach, actually. Mostly, we'll be publishing to entertain.