We need these super cook markdown templates that need DRY instructions.
Solution
Add a section that covers how to use the Markdown Software Engineering, Markdown Game Design, and Markdown Cookbook templates. We need to make the chapter generalizable to other industries so we need to re-add the Markdown Hardware Engineering templates ASAP.
It messes you up to do a HoSe when you have to watch videos to learn. You need to do things quickly in the HoSe.
Solution
Just skip the HoSe if you have to watch videos or if you're not set up the night before. It's better to pause the videos and just be an active learner. It sucks to have to stop making progress to deal with the logs.
The session tickets will start to become noise with thousands of developers.
Solution
The Workspace repo shares the same name as the GitHub account or organization, for example, the a-startup Workspace Repo is located at<github.com/a-startup/a-startup>. The link format for the Hierarchy IDD Tickets is:
I'm going to use this one as the copy and paste and ensure it's the most up to date because I can use AStartupCookbook for DRY documentation for contributors.
A
Fixed license in the root directory I forgot to update.
The repo link in the License is broken. Issue-driven development is a very technical subject worthy of its own chapter but it's part of Development. We also need a DRY instruction on how to make a Cookbook.
Solution
Development is not a Part that contains a Chapter on IDD. Fix the broken link.
There is confusion about (R) vs (TM), and this caused me to lose a grant once because someone on the panel called me out for using a (TM) when that was the appropriate usage.
Solution
(TM) is for a common law trademark and there are requirements to publicize your copyright in specific contexts. (R) is a legally registered trademark, which is not required.
We need a Don't Repeat Yourself (DRY) contributors Guide for all of the a-startup, oregon-cooler, kabuki-starship, future, and third-party organizations.
I've been just pushing the project onto the stack because the initial overview of the prior day sounded exactly the same.
Solution
Start the Secondary Log with a brief progress report. Example: Yesterday I worked on WikiSpy and I made good progress. This way I can work on my startup and not for my startup.
I'm utterly shocked there is nothing in the Mission Ticket section.
Solution
Currently only one of my repos links here on the contributing section but this is linked to now in every project I do so the instructions need to be top-notch.