This assumes a mature XP process is underway (this is almost 20 years old, so should not be a surprise to anyone).

If you are actively developing software there are only a limited category of bugs:

• The critical – stop development and fix
• The important – to be picked up as the next highest priority item
• Prioritised alongside other upcoming work items.
• Do not fix – record as unimportant

These days there should be no reason to keep an extensive bug backlog.

A bug is effectively a missing test (unit, integration or end-to-end).

With a sufficient test suit the QA should be getting bored. Hopefully they are spending the time working on acceptance criteria and acceptance tests for upcoming work.

This is a site that tries to spread the load on open source projects.

The idea is that you volunteer to help out triage the issues on projects allowing the maintainers to focus on adding new cool features.

https://www.codetriage.com/

Here is a useful reference for bash shortcuts:

https://www.skorks.com/2009/09/bash-shortcuts-for-maximum-productivity/

The following is the means of finding the directory size of a folder and its contents on a mac:

du -s

This came in handy when I was trying to speed up a website deploy.

It turns out that over 98% of the content of the site was in one folder. Spliting this off an changing the copy policy saves between 50% and 75% of the deploy time.

Look for the quick wins!

I have recently moved jobs. This comes with the inevitable machine setup issue.

This is a list of things that I have been installing on my machine so that I won’t have to build myself another list:

• Chrome
• homebrew
• neo4j
• java8
• elixir
• exercism
• vscode
  • Enable autosave (on the file menu)
  • GitLens
  • IntelliJ IDEA Keybindings
  • JS Refactor
• Gradle
• git ssh setup

After every mac os upgrade:

xcode-select –install

I have just left one company for a new role. These are a few notes that I would like to bring forward to future companies:

• Empower the devs add cloud resources within a limit say $100 per month without having to ask. The meetings to request this will cost more than the benefits. Dev teams will spend less time waiting.
• Have a bell that can be used to trigger team timeouts. Hold the discussions as soon as they are needed. Decisions should be made by the team. Go one better than us and actually write up the decision including why’s and assumptions.
• When adding a new piece of technology always consider how to replace it. Cloud services do stop with anything between 1 and 6 months notice.
• Actively monitor the cloud infrastructure bills, both current and projected. Warn the team daily if a threshold is breached.
• Never let the build stay broken. You can only ignore tests for a fixed period of days. This is only to be used for infrastructure failures.
• Deploy frequently. Weekly at a minimum. Code not deployed will rot. Use feature switches if possible (but ruthlessly remove them after a feature is live). This does allow deploy from master.

https://watabou.itch.io/medieval-fantasy-city-generator

This is a great article on regex.

This looks like a useful library: https://bramp.github.io/js-sequence-diagrams/

The hand drawn styling looks like  a demo only styling that I have been looking for.

Or on a mac/linux

grep -v @tag *_test.exs > test.exs && elixir test.exs