login::
pass::
name::
id::
node:
Paul Prudence: Patch Schematics – The
Aesthetics of Constraint / Best
Practices [Theory]
template:
4
parent:
---▲--- O ----
owner:
yerythoo
viewed by:
created:
17.04.2012 - 02:55:55
cwbe coordinatez
:
101
792011
6162869
6607002
6607010
ABSOLUT
K
YBERIA
permissions
you:
r,
system:
public
net:
yes
⠪
neurons
stats
|
by_visit
|
by_K
source
tiamat
K
|
my_K
|
given_K
last
commanders
polls
total descendants::2
total children::2
2
❤️
show[
2
|
3
]
flat
http://www.creativeapplications.net/theory/patch-schematics-%E2%80%93-the-aesthetics-of-constraint-best-practices-theory/
title/content
title
content
user
000001010079201106162869066070020660701006608495
Weaponized Cringe
17.04.2012 - 21:30:31
, level: 1,
UP
NEW
Re: Paul Prudence: Patch Schematics – The Aesthetics of Constraint / Best Practices [Theory]
vdaka!!
000001010079201106162869066070020660701006607014
StiX
17.04.2012 - 03:05:08
(modif: 17.04.2012 - 03:07:17), level: 1,
UP
NEW
!!CONTENT CHANGED!!
Re: Paul Prudence: Patch Schematics – The Aesthetics of Constraint / Best Practices [Theory]
jo! v niektorych patchocch je uz pruser ze fakt nejdem moc vertikalne ale 6 vertikalnych tokov je pospajanych dokopy horizontalne na viac krat, potom sa uz len snazim dosiahnut ako tak nejaky order, ale povedal by som ze sa snazim vzdy nejak vybalancovat co najvacsi pohlad nad data flow s nadizajnovanym poriadkom, a teda to je taka stredna najfunkcnejsia cesta, kedy interface nezabera uplne cely screen ale mozem mat viac patchov naraz otvorenych a stale je v nich toho dost prepojeneho aby boli lokalne procesy pokope, no neprestanem byt tym spojenim logiky, funkcnosti a vizuality nikdy nadseny, prirovnal by som to k premakanej architekture (co sa vlastne casto pouziva ako synonymum k programovaniu)