- Date: <DATE - when the decision was made>
- Driver: <DRIVER - list a single person driving consenus and decision making>
- Stakeholders: <STAKEHOLDERS - list all relevant stakeholders affected by this decision>
- Status: [PROPOSED | DECIDED | SUPERSEDED]
- Categories: <CATEGORIES - use a simple grouping to help organize the set of decisions (e.g. backend, payment, user management, ...)>
- Outcome: <OUTCOME - once decided, provide a short summary of the decision outcome here>
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.