rndmcnlly (rndmcnlly) wrote,
rndmcnlly
rndmcnlly

Proceedings of ThinkTub 1.0

The plain-text record below was written collaboratively by Adam Smith and Jeff Lindsay during an evening session of the first instance of an event self-named, temporarily, ThinkTub. While it may be read in a linear fashion it was expanded and edited non-linearly while being projected on a wall. For the most part, outside resource were not used. Only a dictionary periodically. The bulk of this content was generated on the fly using only itself as context.



OK, WE BEGIN

Lets design SOMETHING to get practice thinking about how we would sit down and design something.

some people don't want to think?

;;;;
;;;; CURRENCY DESIGN
;;;;
"What would we want from the ideal currency system?"
Goals:
(1) Simple lives have simple finances
(2) Money can be paid for specific things
(3) Built-in easy budgeting
(4) Universal conversion
(5) Digital representation (cards)
(6) Dont carry too much crap
(7) Never run out of a certain kind of money
(8) Soft-segmentation of industries
(9) Understandable as "foreign currencies"

Idea:
- three currencies: staple, luxury, capital
- big business can only deal in capital (unless there are specific pay-through arrangements)
- salaries paid in mixed currency
- menus have three prices
- payee always gets the right types (source bank may convert on the fly)
- CONVERSION SHOULD HAVE OVERHEAD
- currency schemas or types of currencies (national standard, organizations, personal)

Paypal as the bank

;;; Related device idea: stateful payment card
- owner can set some state on the card to decide where money should come from
- can configure to only allow one transaction before manual reset
- can be disabled
- no moving parts
- programmed by wallet (or phone, if supports wallet interface)
- not personally identifiable (owner able to idenfify own card but not others)
- like a container for cash, but you get the container back

- defaults to standard assumed type

;;; Ideal wallet
- holds cards
- handles all money issues
- can be the phone?
- can do anything you can do from the bank's website (web browser, lol)
- can pay money to other people

;;; What do we really want from cell phone cameras?
- capture the moment
- capture some text
- printer

;;;;
;;;; package mngmt as service ("PMaaS")
;;;;
- central identity (email)
- several profiles (tags)
- can has base profile
- easy way to sync current installation to a profile
- easy way to sync a profile to a current installation
- initially for one package system, should support all

use case:
(1) I am setting up Yet Another Ubuntu laptop, I want my normal apps to be installed on my friends new laptop.
(2) Total reinstall.

advanced system:
- knows what computers are yours and what versions


;;;;
;;;; INTELLIGENT DESIGN LANS
;;;;
"decide upon the look and functioning of (a building, garment, or other object), typically by making a detailed drawing of it; a plan"
problem dissolving (not solving, resolving, or absolving): changing the environment of the problem so it cannot exist

"What would be (emergent/holistic) properties of the ideal social intelligent design system?"
- SYSTEMS get designed
- any kind of person can participate, no experience necessary
- minimal cost to individual (except time)
- people learn from the experience
- people are aware the system can be modified (to adapt)
- NothingForgotten
- NothingGoesUnsaid
- the system is always designing
- there is a benefit from people all participating
- some design output is visible from outside in near realtime


PEOPLE:
- hackers
- thinkers
- designers

DO YOU WANT AN AMP DRINK??
yes
thanks
word.

PARTICLES:
- whiteboards (recorded)
- projectors
- collaborative text editors
- audio/video recording
- tags

PROCESSES:

collaborative design orientation? algorithm

(1) throw out (casually propose) system to design/redesign
(2) actually throw it out if it was existing (because it was "destroyed, last night") -- what would the universe be like without it?

(3) ask "What are the (emergent) properties of the ideal system?"
(4) make a list of just too many responses

(5) invent straw man solutions that satisfy only a tiny number of these at once (or even just once) -- should be fun/silly to design
(6) criticize these straw men by showing there was a missing property
-- NOTE: these steps are here to very purposely allow people to contribute even if they can only think of problems and not think of new solutions (besides, its fun)

-- At this point you have:
- a system to design
- some properties it should have
- some initial discussion of methods for achieving somet properties and problems with these simple solution

(7) Now go design it! (--by having the people execute other design processes using whatever particles desired)

(8) RECURSE on supersystems (synthesis)
(9) RECURSE on subsystems (analysis)

properties are like Requirements (as in software design)
-but we develop them individual first (as prototypes)
* along the software design metaphor: all of us are the developers as well as clients, we play complimentary roles between all pairs of us
- I try to tell you all what I want.
- I try to design a system that does what you wanted.
(between all pairs, in parallel)

Wisdom
Understanding : Explanations : Why : Purpose (role of the system in greater system)
Knowledge : Instructions : How : Process (structure and workings within system)
Information : Descriptions : What/where/when/who

design = planning
way of problem solving by eliminating the problem, by CHANGING the environment

Purpose = Function = Why = Synthesis
Process = Operation = How = Analysis

systhink

- extract useful part of simple solutions
- identify incompatibilies/dependencies

invent new words
reinvent words

synchronous processes
asyncronous processes
** and feedback between these (to get the best of both)


ready steady go, ho

;;; ideal collaborative environment/text editor
** write what you WANT, not some features you think MIGHT enable it
- start with subethaedit
- tracks changes in output that can be replayed in sync with others at the same time
- scrub back and forth
- more dimensions of organization, not just vertical space (with headers)
- like a wiki that you can create constructs on the fly (maybe get supported by the environment)

existing partial solutions:
- subethaedit
- whiteboards
- mind maps

future buzzwords:
- mind graphs
- general tensegrity theory (and practice!!11two(lol))

TRIAL RUN ON SELF:
- emergent property is very useful ("I like that we're being so picky")
-


NothingForgotten
- microphones + audacity
- webcam
- saving text files
- subethaedit (sort of)
- encourage publishing results
- encourage involvment of old ideas

NothingGoesUnsaid
- laser pointers
- twitter?
- asyncronous collaborative text editors
- irc
- notepads
- extra whiteboard pens

RealtimeOutput
- twittering bits of
- people outside of the event should "know that something is up"

MONETIZING
monetization "m10n"
- cookbook, grab bag collections of goodness
- cover charge
- how do we monetize >>THIS<<


NAMES FOR THIS SORTA THING
- design party
- think tubs
- grassroots think tank
- intelligent design lans
- super happy design house
- DesignCamp, lol, logo? tshirt?
- a party for (SYSTEM, experience) designers and thinkers
- Design, This. (metamatic?)


;;;

SOME SYSTEMS THAT WOULD BE COOL TO DESIGN
- telephone networks
- cell phone cameras
- education
- programming
- automatic technology development - technologies emerge
- government
- taxes
- transporation
- cars
- space tourism
- deep space networks
- synthesizing experience for learning
- making political change more liquid

policy, law, convention, protocol, standard

MAKING POLICY CHANGES MORE LIQUID, LAW MAKING?
- localized policies encouraged
- policies can be removed, refactoring
- easy participation
- a tiny group of people should be make global changes
- a bigger group should be able to override this
- nobody should be unfairly opressed?
- no blocking processes
- no changes unconsiderd
- important issues automatically escalate
- small issue do not escalate
- no tangled messes of loopholes should emerge (simplicity encouraged)

process:
- if nobody has an opinion, the first person to have one sets the policy
- if desired, another person can find a friend and overrule that policy (revoke or amend)

particles:
- many kinds of votes (citizen, human, property, capital, qualified (education?), employment)


** making policies IS designing a system's mechanics (should we have separate votes for determining popular desired emergent properties??)

THE ECOSYSTEM OF ACTIVE DEVELOPMENT SOCIAL EVENTS
the social-developmental complex
"?"
- stuff gets developed
- the system is always developing
- things (in general) are better for having been involved
- the greater system of everything is redesigned interactively
- adogmatic

the usual suspects:
- BarCamp
- DevHouse
- ThinkTubs
- Inpirathon

a pipeline (a flow of good stuff)
all produce relationships, ideas

- inspiration and juices flowing at Inspirathon
consumes: videos, stories, good stuff
produces: motivation, inspiration, ideas
- problem identified at ProblemCamp? ConcernCon
consumes: ideas, life experience, pain points
produces: formulated problems
- crazy solution proposed at ThinkTub
consumes: problems, systems to redesign/design
produces: system designs
- details fleshed out at ResearchCamp
consumes: system designs, experience
produces: prototype plans
- prototype created a DevHouse
consumes: protype plans, external resources, developers
produces: prototype, experience
- prototype publically discussed at BarCamp
consumes: prototype, opinions, ideas
produces: awareness, ideas, good stuff
- relax and refresh at CampCamp
consumes: beer, lyrics, experience
produces: experience, recreation, fun, ideas

What events needs to be designed/developed:
- ProblemCamp, ConernCon, IssueIsland, MatterMaker
- ResearchCamp, LibraryHunt, LazyTown
- ThinkTub, DesignParty, SHDesignH?, DesignThis, IDLAN, DesignLan



;

Subscribe
  • Post a new comment

    Error

    default userpic

    Your IP address will be recorded 

  • 0 comments