GitHub Wiki appears limited but still trying. There is value in keeping the design docs with the code.

-1 for GitHub for limited index
-1 for no sub-pages or categories
-1 for no TOC

The sidebar is a workaround for limited doc features.

#BuildInPublic #GitHubWiki

My goal is to have design docs stay fresh. I believe keeping them close to the source code should push them in that direction.

Keeping design docs in #Confluence and the code in GitHub introduced a lot of friction.

#BuildInPublic

Using emacswiki.org/emacs/Projecti… to get at files quicker than only using `dired`.

Working in Emacs has made my coding more intentional.

My MVP is still a product I want to take pride in and NOT just *get it done* in any way shape of form.

#buildinpublic #emacs

I do miss the project or solution view of the traditional IDE when using Emacs.

Looking for solutions to help on this front.

#buildinpublic #emacs

I recently switched from #VisualStudioCode to #GnuEmacs for my programming tasks. It is slow and steady, and I like it.

I still use VSCode and Typora for blog stuff. Writing is a bit different and requires a different toolset.

#buildinpublic

Added github.com/benbalter/jeky… to my doc project. It had broken links!

I assumed .md -> .html links would be handled by Jekyll a.k.a. GitHub Pages.

It turns out that is not true. Thanks to @benbalter for being the top search result and providing a solution.

#buildinpublic

GitHub Pages only supports the ~/ and ~/docs locations for your site in a repository.

I found that one out the hard way after switching to a monorepo.

#buildinpublic #til

Converted 5 repos into a single repo. Looking for the following results:

• Commits to be more aligned across former repos
• Less directory jumping in IDE/editor
• More focused development (less movement)

#buildinpublic

Studying the differences between GitHub projects and Jira.

- I started using Jira b/c it was familiar (day job).
- Jira may be more than I need.
- GitHub Projects may require more work.

#jira #githubprojects #buildinpublic

Thinking of combining multiple repos into a #monorepo. As a single developer it makes sense to consolidate all things.

#buildinpublic

The goal of the project is to automate the expectations of the runbook-compiler from the command line. It should be just like having a QA tester!
#buildinpublic github.com/kenbrittain/fu…

Sometimes it is all about reading the documentation: WaitForExit(int) says "To ensure that asynchronous event handling has been completed, call the WaitForExit() overload that takes no parameter after receiving a true from this overload." #buildinpublic

Investigating why Process.WaitForExit only sends events when the timeout is -1.
#buildinpublic github.com/kenbrittain/fu…

Initial commit to the `functional-testing` framework for validating `runbook-compiler` commands and system messages. github.com/kenbrittain/fu… #buildinpublic

Today starts a new week (#2) and a new set of goals. Use #Jira to run your own sprints and track development. It's free for <10 users and you are an army of one! #buildinpublic

Shipping the beta is a milestone. You first need to build it before you can make it better. github.com/kenbrittain/ru… #buildinpublic

Releases on GitHub are a fairly simple activity. It does appear I should automate it though. #Jira issues RC-17 was just created for the next sprint. #buildinpublic

Compose a 3 part method name: Method_Scenario_Expectation

- Method is the name of the method that is being tested
- Scenario is why you are writing the unit test
- Expectation is what you are thing is going to happen

#buildinpublic

Stop overthinking about how to write your unit tests. Create an outline for your unit tests first. kenbrittain.com/posts/28-step-… #buildinpublic

Stop overthinking about how to write your unit tests and start writing them. Like everything else you need a plan. kenbrittain.com/posts/28-step-… #buildinpublic