Re:How to Do Philosophy
by DanielBMarkham on Thursday December 25, 2008 @07:06PM
(#409847)
To me philosophy is a way to make life easier. Philosophy is also a way to make technology solutions easier.
I see no conflict between using the same tool for both types of work. However I would not go so far as to say both types of work are identical. As a deep pragmatist, I pick and choose philosophies of living and idea development concentrating on what works and ditching what doesn't. It doesn't matter to me that on different projects, or on different days, different philosophies which might be mutually contradictory are required. Philosophy is always a work in progress. I have a small enough moral sense that stealing what works isn't a problem and a small enough ego that I don't worry with trying to come up with the ultimate philosophy of everything.
I'm afraid of such detached situations, and so I'm trying to get highest possible abstraction of source code taking into account current programming environment / developers mental world. Each small abtraction step, which I'm achieving is one step forward - I can identify of what was done correctly and what was done wrong and take into consideration on making the next step. Unfortunately the further I go - more resistance I feel is hitting me back.
For example programming language compilers are made by whole teams, and architecture and design - even if they exists require enormous effort to develop similar compiler.
I however still think there is a way to simplify things, but it's very hard to find a better way / solution, as it is probably with philosophy. I'm inspired by language like Toki Pona, and that what drives me forward.