Jan. 9, 2020, 7:52 a.m.

blackout computer science

wonder systems

(shards of a paper I just finished editing, happy new year to you lovely)


ABSTRACT

it became part of the fabric of daily engineering
in ways which centralize design work
and in ways which distribute it, 

INTRODUCTION
loci for understanding what will be built,
while encoding (and sometimes concealing) decisions on why
design participants' perspectives clash and coalesce
its outsiders and insiders, spectators and maintainers,
and formal and informal power structures
embracing a participatory human-center

BACKGROUND
guide tradeoffs between subsystems
the agency of design models
the rhetorical arena of a design review
the notion of an iterative and progressive design specification.

S can be understood as the space of all potentially desirable answers

consider the set of potentially desirable answers
as the defining property of a mathematical program
seeking to convince other design participants

struggle to solve in hours for merely dozens
a user experience catastrophe
typos which render a constraint syntactically valid but substantively incorrect
falter because users have been abstracted away from
"shadow prices"

surprisingly large or small shadow prices are likely erroneous,
providing an opportunity for triage
a more complex
risk

METHODS
One of the best methods for gaining insight into user interactions
is to observe users as they interact

people's interactions with each other, i.e. organizational practices
are difficult to create in a more controlled environment

the scattered focus and poor outcomes that can occur in such contexts
have struggled to show any change in this effect with pairs

observing throughout continued engagement
was done to gain insight into what they wanted to express

an expressivity different from what they or the first author had expected,
interdependent, requiring the previous conceptions of each to change simultaneously.
which emerged from such spaces often felt spontaneous

RESULTS
a firm hoping to convincingly validate its existing design
in hopes of creating a horizontal culture of sharing
a great deal of organizational trust

academic contexts, where design presentations
are typically larger, longer, and less frequent
in competition or complement.

System engineers, making models for the managers
but eating lunch with the subsystem engineers, felt caught in between.

Teaching staff expressed surprise that the final build adhered so closely

government officials expressed a preference
understood without referencing the original
something which could be shown immediately
even the last holdouts came to actively appreciate it
when it saved them from typos.
later users rarely thought about such concerns.

As a bit of a joke (and to get it to stop showing up
for sufficiently small epsilon;
prioritize refinements

Solution tables are the atomic result of convex programs.
because of their rhetorical weight
made specifically for plots

define hyperplanes
the dotted parabola representing the (unknown by the algorithm)
the "client" requested a solar-powered surveillance drone
an appreciation for the synergy between convex modeling and engineering practice.

their value was not in returning

each generating
a sense of possibilities
even a singular and quantifiable goal
was thanklessly complex

(left is towards the root)
(thicker is more sensitive)

Observation E: Where Constraints "Belong"
implicitly, with "belonging" represented by the clustering

"stub models" with fixed variables and no constraints to be refined later
suggest they either repair their model or refine their expectations
by relating them to a jigsaw puzzle
without any unmatched tabs or notches.

Observation F: "An Engine With a Stick Attached"
seeing this exact diagram felt like a vindication;
the model found a curious way of flying
unexpectedly keeping the same speed
extremely comedic
a typical "multi-point"

they did not wish to specify an objective function
because they did not want to solve for a particular point.
"at what altitudes and speeds can a
helicopter be flown at all?"

DISCUSSION
our ethnographic methods were not rigorously planned
but often emerged from necessity or opportunity.
which marginalized them in the development process.
the ways in which computers are used
can be more amenable

CONCLUSION
powerful tools that can contain the hopes and concerns of many

ACKNOWLEDGEMENTS
the creative ferment
a place from which to start again.
with patient exasperation

You just read issue #392 of wonder systems. You can also browse the full archives of this newsletter.

Powered by Buttondown, the easiest way to start and grow your newsletter.