Skip to content

Commit 2cd6d09

Browse files
committed
edit
1 parent c55a732 commit 2cd6d09

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

thinking_disciplines/notes.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,3 +27,26 @@ i think one way to show the power of this thinking disciplines is to actually us
2727
in our work, we must priotitize perfecting this disciplines apparoch with the disciplines. and it will be the first proof that this works.
2828

2929
and one of the first things we shoud solve is context tracking. beacuse our thinking disciplines approach try to cover thinking space, and without proper and perminant way to list things, explore them and do this in retrackable branches without informaitno loss. Our holistic runs wont produce desired resutls.
30+
31+
but very first thing is to finsih defining disciplines, so we can use them all for self improvement.
32+
33+
34+
35+
what is feasible?
36+
will it limit us now for current other scoped items?
37+
will it limit us for future direction of what we are trying to achieve?
38+
how this can be rephrased without limiting us? maybe with port and adapters or interface approac,
39+
is it elagant?
40+
is it
41+
42+
43+
44+
45+
and if you reread all traces, and look the codebase from a bit far away to see how things are arhitectures.
46+
what would be your 3 suggestions which would make everything so easier for us, both for future deployment and development
47+
think about this from the "what causes the most cascading friction" perspective — not individual fixes, but the three structural changes that would make dozens of other things fall into place.
48+
49+
50+
51+
sensemaking + innnovation + critiq + feasible loop = sicf
52+
to iterate and unlock the solution space in roguie way. bruteforce way.

0 commit comments

Comments
 (0)