Demonstrating my preferred workflow while…

• staying in APL when possible and reasonable
• using the most powerful utilities available

In a particular project (CommTools) we are going to…

• remove (minor) technical debt
• fix a bug

CommTools allows communicating with the user in the session with ⍞ and ⎕.

It comprises 5 functions and operators:

• Pause
• AskForText
• AskForNumber
• YesOrNo
• Select

CommTools is almost exclusively used in user commands.

• The CommTools can be automated (test cases!)
• Gives the user the same experience everywhere they are used
• The CommTools can be interrupted

I am using both Git and GitHub

• Git takes care of your project history
  • Access to every saved (committed) version of your code
  • Independent from a central server
  • Supports collaboration between users very well
• GitHub is an online repository hosting platform

• Git is powerful but suffers from featuritis
• GitHub offers many useful features

• The way I use Git is not a suggestion
• It works for me because I am on my own
• A team must use a different workflow
• But this talk is not about Git…

Over to APL!

• Advice: Do only simple stuff from within APL!
• Otherwise, use the Git Bash
• Sources refer to the Git Bash:
  • The documentation
  • All relevant books
  • StackOverflow etc.

Do not implement an APL function that puts together these actions:

• Switch to branch “main”
• Merge “dev” into “main”
• Push “main” to GitHub
• Delete “dev”

1. Things can go wrong!
2. Read: things will go wrong
3. Then APL appears to hang