summaryrefslogtreecommitdiff
path: root/.trash/1 projects/openstack-golang-impl/control-plane-feedback.md
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-01-08 10:48:09 +0100
committerJasper Ras <jras@hostnet.nl>2025-01-08 10:48:09 +0100
commited0753ad224f0c65133bd7a63180257eecd9f5e3 (patch)
treecc662868574fe17db58be9e0faadd452c84dc59c /.trash/1 projects/openstack-golang-impl/control-plane-feedback.md
parent493be30dc981eaf762a95a1218f96893b1976727 (diff)
vault backup: 2025-01-08 10:48:09
Diffstat (limited to '.trash/1 projects/openstack-golang-impl/control-plane-feedback.md')
-rw-r--r--.trash/1 projects/openstack-golang-impl/control-plane-feedback.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/.trash/1 projects/openstack-golang-impl/control-plane-feedback.md b/.trash/1 projects/openstack-golang-impl/control-plane-feedback.md
new file mode 100644
index 0000000..7d62574
--- /dev/null
+++ b/.trash/1 projects/openstack-golang-impl/control-plane-feedback.md
@@ -0,0 +1,11 @@
+Garden hose vs arrows: garden hose easy to aim bc continuous feedback, arrow difficult to aim only feedback once. ^ UX designer analogy.
+
+Control plane should hose us down with information about our actions. It would be even cooler if it can simulate our actions and tell us exactly what would happen before submitting it finally.
+
+Not just feedback from the initial "submit" but also any background tasks that spawn off of it.
+
+Good feedback includes:
+- examples of what's about to happen
+
+---
+https://www.youtube.com/watch?v=_RKFDTNxFJE \ No newline at end of file