Re:_why: "Not all code needs to be a factory, some of it can...
by judofyr on Thursday August 20, 2009 @01:27PM
(#775550)
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!"
Re:_why: "Not all code needs to be a factory, some of it can...
by nir on Thursday August 20, 2009 @02:05PM
(#775668)
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.
Re:_why: "Not all code needs to be a factory, some of it can...
by unalone on Thursday August 20, 2009 @01:40PM
(#775604)
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.
Re:_why: "Not all code needs to be a factory, some of it can...
by biohacker42 on Thursday August 20, 2009 @03:28PM
(#775918)
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.
— _why / http://rubyforge.org/pipermail/camping-list/2008-May/000673....
"Camping is magic, plus some other stuff."
(camping is an anagram of magicnp)
Origami = art
Factory = work.
Do you want to make money or art?
Not necessarily, but possibly, within the same project.
In any case, if money is your goal (absolutely legitimate) you'll have much better odds choosing finance rather than technology as your field.
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.
The latter link references a variety of particular interesting applications, from airbag design to laser waveguides.