_why: "Not all code needs to be a factory, some of it can just be origami."(rubyforge.org)
rubyforge.org
_why: "Not all code needs to be a factory, some of it can just be origami."
http://rubyforge.org/pipermail/camping-list/2008-May/000719.html
18 comments
FYI, I'm cleaning up the documentation right now, so we can finally release this thing. It's taken way too long time when you don't have a guy who says "okay, release it!"
Indeed, but beware:
Origami = art
Factory = work.
Do you want to make money or art?
Origami = art
Factory = work.
Do you want to make money or art?
I would rather make art than money. Money is wasted away on details. But art, oh art, is beautiful. Art can do things that money never can.
Just like money can do things art never will ... boring, ugly, world-changing things ... which can be very beautiful.
Both.
Not necessarily, but possibly, within the same project.
Not necessarily, but possibly, within the same project.
Making money depends on a lot of variables beyond your control. Making art is completely within your control. Every 5 year old does art, very few people make real money.
In any case, if money is your goal (absolutely legitimate) you'll have much better odds choosing finance rather than technology as your field.
In any case, if money is your goal (absolutely legitimate) you'll have much better odds choosing finance rather than technology as your field.
No reason it can't be both, but given a choice between making something that makes me happier and making something that makes me money, I'll go for happiness.
does it have to be a choice? why not create value with art, and exchange that value for money.
Doing both would be great, but often doing both is impossible. Code is one of those things.
Don't ever code as smart as you can because debugging is twice as hard as coding. If you write the smartest code you can, you will not be able to debug it.
I imagine origami code as this kind of brilliant and amazing puzzle solution that brings a smile to your face when you grok it. And that's exactly the kind of thing I would not want to maintain for a living. Write it, sure. But not maintain/extend/debug it etc.
Don't ever code as smart as you can because debugging is twice as hard as coding. If you write the smartest code you can, you will not be able to debug it.
I imagine origami code as this kind of brilliant and amazing puzzle solution that brings a smile to your face when you grok it. And that's exactly the kind of thing I would not want to maintain for a living. Write it, sure. But not maintain/extend/debug it etc.
What if smart code is readable code is debuggable code?
Then I wouldn't label it origami.
Sometimes the two meet: http://www.industrialorigami.com/technology/how.cfm
http://www.langorigami.com/science/science.php4
The latter link references a variety of particular interesting applications, from airbag design to laser waveguides.
The latter link references a variety of particular interesting applications, from airbag design to laser waveguides.
[deleted]
— _why / http://rubyforge.org/pipermail/camping-list/2008-May/000673....