after that discussion about making tools and making art...

1. develop tools from the bottom up and understand everything from first principles?

2. just do the thing that brings me the fastest to where I want to be, and possibly maybe work my way(down the abstraction tree) from there?

I can see pros and cons of both, and still, I usually fall into 1. for too long and almost never get to actually using my (unfinished)tools

@nff the general wisdom I've heard is to:

First: Make it work.

Then: Make it right.

Finally: Make it fast.

@paul pure fkn wisdom.
I'm probably being afraid to make it work, afraid to discover it's not really what I wanted/imagined, afraid once I get it working I won't know what to do with it...
That's why yeah, I probably really just need to make it work :))

@nff would you like to see a list of the failed things I built?

In my experience, there was never anything I tried to build that was a net negative. There was always some good insight (be it technical, artistic, or something else) that came from the process.

The "what now?" feeling that comes after building most of a tool is relatable to many I think, including myself. I'd say gently hold on to that feeling, warmly invite it to dinner, and generally let it simmer. But don't forget about it...

Follow

@nff this conversation actually inspired me to literally create a list of failures: pbat.ch/wiki/failures/

· · Web · 3 · 2 · 9

@paul hey I've been reading your failures page. Truly inspiring. Inspiring are the things you built themselves, but most of all the positive attitude you're having towards them, it does really transpire from the way you talk about them.
Thanks :)

@nff thank you! it's always nice to know there are readers out there.

more failures to come I'm sure ;)

Sign in to participate in the conversation
post.lurk.org

Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.