4 ms·
Wu wei of programming.
by ak39 7y ago
Wu wei of programming.
- kilroy_jones 7y agoHow does that work?
- mr__y 7y agoyou ignore the bugs and let them be, and if anyone questions that, you give them some vaguely related Confucius quote
- ak39 7y agoI think this sounds about right too.
- ak39 7y agoI don't know, my friend. What I'm about to type will sound a lot like Dudism ... here goes: It's impossible to explain Wu Wei in instructional format. This paradox alone is its appeal and weakness. The concept is this: never force anything. But then also: do not slack off. Be keenly aware of what is desired but don't attempt at it directly, forcefully. Rather be content that "it (whatever you are seeking to achieve) will happen when you are ready to let it happen" by you doing something quite orthogonal/oblique to the objective. It's an Eastern philosophical principle but I think there's a nugget of science that could be distilled out of this if studied for factors influencing success and failure in personal endeavours (that is, if any study were to be conducted - I know of none, btw). From a personal experience I have great moments where I don't chase deadlines or impose mental pressure to conform to explicit design objectives. In these cases I would openly admit that what I am about to do may NOT be the thing I should be doing but I'm doing it anyway to see what might come of it (always keeping in sight the original premise or objective). I've noticed too that if I force a design too literally, I soon develop neurotic anxiety about handling exceptions my forcefully created universe of abstract correctness (abstractions are gon leak!). You cannot force Wu Wei ... that will be both ironic and paradoxical.
- avindroth 7y agoI think there is also wuwei in "improving" programming. Depends on the source of wanting to optimize and improve...