shi-ne

Most designers today think of themselves as the designers of objects. If we follow the argument presented here, we reach a very different conclusion. To make objects with complex holistic properties, it is necessary to invent generating systems which will generate objects with the required holistic properties.

Confusion about what it means toown a book leads people to a falsereverence for paper, binding, and type—a respect for the physical thing—thecraft of the printer rather than thegenius of the author.

a typewriter with the “special key” is no more or less odious than one without; it is just a matter of the meanings we humans impart upon it.

some argue that the typewriter is just an inanimate object; a tool crafted for a specific purpose, which assumes neither the responsibility of the user nor his blame.

Take a moment to pick up the objects around you. Use them as you normally would, and sense their tactile response — their texture, pliability, temperature; their distribution of weight; their edges, curves, and ridges; how they respond in your hand as you use them.

You can edit shapes in the format panel on the right. There are several formatting options:

We can use the call() method to copy over properties from one constructor into another constructor. Let’s create a Warrior and a Healer constructor.

Mind1, which refers to the neurocognitive activity that allows you to behave in the world.

XMI describes solutions to the above issues by specifying EBNF production rules to create XML documents and Schemas that share objects consistently.

The Hibernation API allows a Durable Object that is not currently running an event handler, such as handling a WebSocket message, HTTP request, or alarm, to be removed from memory while keeping its WebSockets connected (“hibernation”).

you nailed it! A consumer should only be able to set an object's state at initialization (via the constructor). Once the object has come to life, it should be internally responsible for its own state lifecycle. Allowing consumers to affect the state adds unnecessary complexity and risk.

Making a property writable adds an order of magnitude in complexity. In the real world it's definitely not realistic for every class to be immutable, but if most of your classes are, it's remarkably easier to write bug-free code. I had that revelation once and I hope to help others have it.

I am an art theory student and started in Zettelkasten in February. I knew about Warburg moodboards of images but only now I realized that he was using zettelkasten too. Thats nice to know.

Multiplying two objects will merge them recursively: this works like addition but if both objects contain a value for the same key, and the values are objects, the two are merged with the same strategy.

Another important distinction is between data and metadata. Here, the term “data” refers to the part of a file or dataset which contains the actual representation of an object of inquiry, while the term “metadata” refers to data about that data: metadata explicitly describes selected aspects of a dataset, such as the time of its creation, or the way it was collected, or what entity external to the dataset it is supposed to represent.

While the brief explanation provides information about the social context, more information about the creator and their intention would help understand more about the background of the object and its significance personally to the creator.

inclusion of metadata such as MIME types, file sizes, and a permalink would be great for the digital age

Writing onstructuralism, Barthes (1972b) states that ‘the goal of all structuralistactivity, whether reflexive or poetic, is to reconstruct an “object” insuch a way as to manifest thereby the rules of functioning (the“functions”) of this object’

that's just the story of how we transfer knowledge and how we preserve that knowledge and move it around and even when it's taken from us and we can find it 00:53:56 we go and we sing that song and we sing that spirit out of there and so this is what's important about transmission of knowledge for for us and so that knowledge they don't belong 00:54:09 to us

Even if it's const, an object can still have properties added later returning any arbitrary type. Indexing into the object would then have to return any - and that's an implicit any.

fresh (i.e. provably do not have properties we don't know about)

Such boundary objects play a brokering role involving translation, coordination, and alignment among the perspectives of different communities coming together in a kind of meta-community [26], which is the case in our fractalized community networks.

boundary objects

I have a rule that I won't allow Capybara to be monkey-patched in Poltergeist. This gives some indication to users about whether something is non-standard. So basically all non-standard stuff must be on page.driver rather than page (or a node).

in languages (like JavaScript and Java) where external objects do have direct access to instance vars

A one-liner alternative for hash-only cases can be implemented using Enumerable#reduce: root = {} [:a, :b, :c].reduce(root){@1[@2]||={}}[:d] = 'E' # root => {:a=>{:b=>{:c=>{:d=>"E"}}}}

I think the issues/problems specified in the comments are not present with a Hash-only implementation. :) I would be supportive of re-considering this feature just for use with a Hash, where I believe 80% of the real-life use cases would (and do) exist. I have encountered this need before in the wild, but not with Arrays.

Would it be desirable to specify the new object in a block? That would make it somewhat symmetrical to how Hash.new takes a block as a default value.

// A general key transform method. Pass it a function that accepts the old key and returns // the new key. // // @example // obj = transformKeys(obj, (key) => ( // key.replace(/\b(big)\b/g, 'little') // )) export function transformKeys(source, f) { return Object.entries(source).reduce((o, [key, value]) => { o[f(key) || key] = value return o }, {}) } // Provide an object that maps from old key to new key export function rekeyObject(source, keyMap) { transformKeys(source, key => keyMap[key]) }

function objectMap(source,keyMap) { return Object.entries(keyMap).reduce((o,[key , newKey]) => { o[newKey]=source[key] return o;},{}) }

Recursively transform object keys with a custom key transform strategy

In case you need to verify that object is instance of particular class you have to check constructor with your particular class

The MethodAccess extension allows you to quickly build method-based reading, writing, and querying into your Hash descendant.

There’s no additional logic from Trailblazer happening here. The function returns a well-defined hash which is passed as an argument to step.

patch: -> { step Destroy.method(:tidy_storage), before: :delete_model }

However, it can be a PITA if you want to customize one of those deeply nested components and add or remove a certain step, for example.

Make your functions return something meaningful, typed, and safe!

Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution

Using a terminus to indicate a certain outcome - in turn - allows for much stronger interfaces across nested activities and less guessing! For example, in the new endpoint gem, the not_found terminus is then wired to a special “404 track” that handles the case of “model not found”. The beautiful thing here is: there is no guessing by inspecting ctx[:model] or the like - the not_found end has only one meaning!

A major improvement here is the ability to maintain more than two explicit termini. In 2.0, you had the success and the failure termini (or “ends” as we used to call them). Now, additional ends such as not_found can be leveraged to communicate a non-binary outcome of your activity or operation.

Almost always form objects wrap existing model or two.

For now I've worked around this by putting all the key-value pairs into an array before passing them into the interaction, then re-building the hash inside the interaction. It works, but it requires some extra code

array :translations do hash do string :locale string :name end end array inputs can only have one input nested underneath them. This is because every element of the array must be the same type. And the inputs nested inside arrays cannot have names because they would never be used.

The outcome returned by .run can be used in forms as though it were an ActiveModel object.

You can also create a form object by calling .new on the interaction.

ActiveModel::Form happened because the "tableless model" presented in RailsCast 219 wasn't as powerful as the "real deal" from RailsCast 193.

So how are we going to create a model that doesn’t have a database table behind it? There are several potential solutions including various plugins but we’re going to use the method described in an entry on the Code Tunes blog. This shows a techinque that involves overriding a couple of methods in an ActiveRecord model and then manually defining the columns in the model file rather than in the database table. In our Recommendation model we’ll add in the two overridden methods and then use the column class method to define the columns in a similar way to how they’re defined in a migration file.

An additional usecase is where we would like to update multiple records

Why process, not save? This is entirely up to you. However, it's good to stay consistent across your team so there's no confusion. I began using save but found there are some cases for forms where you aren't saving anything, such as when you are just triggering a job or push-notification. I found using process fits more cases so that's what I use. This is also typically the only method that is public on my forms.

I've been over the use case for form objects in this post on moving away from fat models but wanted to go into more detail on how and why I use them here. I really believe in the utility of these objects; their ability to abstract and isolate logic in a simple and effective manner is unmatched, IMO.

The basic classification of a form object is a class that contains writable attributes, validations and logic to persist the attributes to ActiveRecord objects. These forms can also include other side-effects like background job triggers, emails, and push-notifications etc. The simplest way to understand the concept is to think of them as a representation of a controller action where all of the business logic that happens in that controller action is abstracted into a form object.

for (var member in myObject) delete myObject[member]; ...would seem to be pretty effective in cleaning the object in one line of code

for (var prop in obj) { if (obj.hasOwnProperty(prop)) { delete obj[prop]; } }

However, this will only walk the object shallowly. To do it deeply, you can use recursion:

Note that if you're willing to use a library like lodash/underscore.js, you can use _.pick instead. However, you will still need to use recursion to filter deeply, since neither library provides a deep filter function.

There are other features you *could* actually polyfill, such as Array.of, Number.isNaN or Object.assign, because those don’t introduce syntax changes to the language – except that you shouldn’t.

Polyfills are naughty as they patch native APIs, while ponyfills are pure and don't affect the environment.

How are ponyfills better than polyfills? A polyfill is code that adds missing functionality by monkey patching an API. Unfortunately, it usually globally patches built-ins, which affects all code running in the environment. This is especially problematic when a polyfill is not fully spec compliant (which in some cases is impossible), as it could cause very hard to debug bugs and inconsistencies. Or when the spec for a new feature changes and your code depends on behavior that a module somewhere else in the dependency tree polyfills differently. In general, you should not modify API's you don't own.

I forgot to mention in the original issue way back that I have a lot of data. Like 1 to 3 MB that is being passed around via export let foo.

Object.keys(obj).forEach could work, but it only includes own properties; for…in includes enumerable properties anywhere on the prototype chain.

Why we attribute a continued existence to objects, even when they are not present to the senses; and why we suppose them to have an existence DISTINCT from the mind and perception.

Matter and Geographical Objects

Object.filter = (obj, predicate) => Object.fromEntries(Object.entries(obj).filter(predicate))

Using reduce and Object.keys As (1), in combination with Object.assign Using map and spread syntax instead of reduce Using Object.entries and Object.fromEntries

hus, we believe challenges occur in all three indica-tors of the level of development of a TMS—expertisespecialization, credibility, and expertise coordination—requiring a need to consider extending theorizing abouteach indicator for emergent response groups.

third response to manage tensions is to promoteknowledge collaboration by enacting dynamic bound-aries. In social sciences, although boundaries divide anddisintegrate collectives, they also coordinate and inte-grate social action (Bowker and Star 1999, Lamont andMolnár 2002). Fluidity brings the need for flexible andpermeable boundaries, but it is not only the propertiesof the boundaries but also their dynamicity that helpmanage tensions.

Based on our collective research on to date, we haveidentified that as tensions ebb and flow, OCs use (or,more precisely, participants engage in) any of the fourtypes of responses that seem to help the OC be gen-erative. The first generative response is labeledEngen-dering Roles in the Moment. In this response, membersenact specific roles that help turn the potentially negativeconsequences of a tension into positive consequences.The second generative response is labeledChannelingParticipation. In this response, members create a nar-rative that helps keep fluid participants informed ofthe state of the knowledge, with this narrative havinga necessary duality between a front narrative for gen-eral public consumption and a back narrative to airthe differences and emotions created by the tensions.The third generative response is labeledDynamicallyChanging Boundaries. In this response, OCs changetheir boundaries in ways that discourage or encouragecertain resources into and out of the communities at cer-tain times, depending on the nature of the tension. Thefourth generative response is labeledEvolving Technol-ogy Affordances. In this response, OCs iteratively evolvetheir technologies in use in ways that are embedded by,and become embedded into, iteratively enhanced socialnorms. These iterations help the OC to socially and tech-nically automate responses to tensions so that the com-munity does not unravel.

Fluidity recognizes the highly flexible or permeableboundaries of OCs, where it is hard to figure out whois in the community and who is outside (Preece et al.2004) at any point in time, let alone over time. Theyare adaptive in that they change as the attention, actions,and interests of the collective of participants change overtime. Many individuals in an OC are at various stagesof exit and entry that change fluidly over time.

Recently, Brown and Duguid (2001, p. 208) sug-gested that coordination of organizational knowledgeis likely to be more challenging than coordination ofroutine work, principally because the “elements to becoordinated are not just individuals but communitiesand the practices they foster.” As we found in ourinvestigation of coordination at the boundary, signif-icant epistemic differences exist and must be recog-nized. As the dialogic practices enacted in responseto problematic trajectories show, the epistemic dif-ferences reflect different perspectives or prioritiesand cannot be bridged through better knowledge

Boundarywork requires the ability to see perspectives devel-oped by people immersed in a different commu-nity of knowing (Boland and Tenkasi 1995, Star andGriesemer 1989). Often, particular disciplinary focilead to differences in opinion regarding what stepsto take next in treating the patient.

The termdialogic—as opposed to monologic—recognizes dif-ferences and emphasizes the existence of epistemicboundaries, different understandings of events, andthe existence of boundary objects (e.g., the diagnosisor the treatment plan). A dialogic approach to coordi-nation is the recognition that action, communication,and cognition are essentially relational and highlysituated. We use the concept of trajectory (Bourdieu1990, Strauss 1993) to recognize that treatment pro-gressions are not always linear or positive.

In knowledge work, several related factors sug-gest the need to reconceptualize coordination.

signifies a new epistemology insofar as it portraysevents as discrete and isolated; knowledges as mod-ifiable, categorizable, and abstractable; and locally-situated knowledges as best understood by thoseworking remotely

. Previously, scholars have generally ignored any notion of time. Now, we need to make explicit our use of time in understanding disaster. Such an application, I believe, will give us a much deeper understanding on defining disaster, how and why such events unfold, and how various social entities attempt to return to normal after the event. Finally, the use of social time in disaster can provide sociologists a deeper look into understanding key theoretical issues related to social order, social change and social emergence, along with voluntaristic versus deterministic patterns of behavior among various units of analysis.

the field. Such a fresh approach possibly improves a wide range of conceptual issues in disasters and hazards. In addition, such an approach would give us insights on how disaster managers, emergency responders, and disaster victims (recognizing that these “roles” may overlap in some cases) see, use and experience time. This, in turn, could assist with a number of applied issues (e.g., warning, effective “response,” priorities in “recovery”) throughout the process of disaster.

The next logical step to aid analysis would be to cross-tabulate the temporal periods of "before, during, and after" with functional activities. This type of analysis and consideration could be further extended by including both the unit of analysis and various social categories such as social class or ethnicity. This type of three-dimensional approach would also strongly highlight the idea that disaster phases are multilayered. Overall, not only do different groups and units of analysis experience the phases at different times, but that multiple aspects of time (i.e., objective and subjective; before, during, after a disaster) intermesh with specific activities.

We must differentiate whether the use of any phrase refers to temporal or functional aspects of disaster. They should not have multiple meanings

Second, the manner the field handles the issue of disaster phases actually reflects a larger problem in the field. Specifically, how do we define disaster? Kreps (1984, p. 324) comes closest to recognizing the relationship among disaster phases, the theoretical components of disaster (i.e., social order and social action), and the definition of disaster (primarily in a heading in his paper). Unfortunately, he does not elaborate upon the connection of defining disaster and disaster phases. Thus, recognizing and recasting our notion of disaster phases may actually help the field more precisely understand or define "disaster."

Mileti, Drabek, and Haas developed their six categories of: 1) preparedness/adjust­ment; 2) warning; 3) pre-impact, early actions; 4) post-impact, short-term actions; 5) relief or restoration, and 6) reconstruction. They justify these categories by noting that "Numerous researchers have documented how activities and nonnative definitions appear to vary across time and vary greatly among events" (Mileti, Drabek, Haas 1975, p. 9). The six phases serve as a central component of the authors' codification effort (it organizes the book chapters). Yet, the authors do not provide a more specific defini­tion for each category. Other theoretical underpinnings in the book receive much more detailed justification (e.g., collective stress, social nature of disaster).

It is boundaries that help us separate one entity from another: "To classify things is to arrange them in groups ... separated by clearly determined lines of demarcation .... At the bottom of our conception of class there is the idea of a circumscription with fixed and definite outlines. "7 Indeed, the word define derives from the Latin word for boundary, which is finis. To define something is to mark its boundaries, 8 to surround it with a mental fence that sepa­rates it from everything else. As evidenced by our failure to notice objects that are not clearly differentiated from their surroundings, it is their boundaries that allow us to perceive "things" at all.

es an entity with a distinctive meaning5 as well as with a distinctive identity that sets it apart from everything else. The way we cut up the world clearly affects the way we organ

Nonetheless, without some lumping, it would be impossible ever to experience any collectivity, or mental entity for that matter. The ability to ignore the uniqueness of items and regard them as typical members of categories is a prerequisite for classifying any group of phenomena. Such ability to "typify"106 our experience is therefore one of the cornerstones of social reality

A mental field is basically a cluster of items that are more similar to one another than to any other item. Generating such fields, therefore, usually involves some lumping.

A frame is characterized not by its contents but rather by the distinctive way in which it transforms the contents' meaning.

Temporal differentiation helps substantiate elusive mental dis­tinctions. Like their spatial counterparts, temporal boundaries often represent mental partitions and thus serve to divide more than just time.

In order to endow the things we perceive with meaning, we normally ignore their uniqueness and regard them as typical mem­bers of a particular class of objects (a relative, a present), acts (an apology, a crime), or events (a game, a conference).2 After all, "If each of the many things in the world were taken as distinct, unique, a thing in itself unrelated to any other thing, perception of the world would disintegrate into complete meaninglessness. "3 Indeed, things become meaningful only when placed in some category.

The perception of supposedly insular chunks of space is probably the most fundamental manifestation of how we divide reality into islands of meaning. Examining how we partition space, therefore, is an ideal way to start exploring how we partition our social world

These protocols, formal structures, plans, procedures, and schemes can be con-ceived of asmechanismsin the sense that they (1) are objectified in some way(explicitly stated, represented in material form), and (2) are deterministic or at leastgive reasonably predictable results if applied properly. And they aremechanisms ofinteractionin the sense that they reduce the complexity of articulating cooperativework.

In this section of the paper we broach two aspects of this articulation issue, onefocusing on the management of workflow, the other on the construction and manage-ment of what we term a ‘common information space’. The former concept has beenthe subject of discussion for some time, in the guise of such terms as office automa-tion and more recently, workflow automation. The latter concept has, in our view,been somewhat neglected, despite its critical importance for the accomplishmentof many distributed work activities

Resistance Realily is 'that which resists,' according to Latour's (1987) Pragmatist­inspired definition. The resistances thal designers and users encounter will change lhc ubiquitous networks of classifications and standards. Although convergence may appear at times to create an inescapable cycle of feedback and verification, the very multiplicity of people, things and processes involved mean lhat they are never locked in for all time.

Infrastructure and Method: Convergence These ubiquitous, textured dai;sifications and standards help frame our representation of the past and the sequencing of event� in the present. They (:an best be understood as doing the ever local, ever partial work of making it appear that science describes nature (and nature alone) and that politics is about social power (and social power alone).

Practical Politics �1 ·he fourch major theme is uncovering the practical politics of classifying awl standardizing. 'fhi<; is the de.sign end of the spectrum of investigat­ing categories and standards as technologies. There are two processes associated with these politics: arriving at categories and standards, and, along the way, deciding what will be visible or invisible within the system.

The Indeterminacy of the Past: Multiple Times, Multiple Voices The third methodological theme concerns ihe f1asl as indetc,rr,1inate. 10 We are constantly revising our knowledge of the past in light of new developments in the present.

Materiality and Texture The second methodological departure point is that. classifications and standards are material, as well as symbolic.

This categorical saturation furthermore forms a complex web. Al­though it is possible to pull out a single dassilication scheme or stan­dard for reference purposes, in reality none of them stand alone. So a subproperty of ubiquity is interdependence, ,md frequently, integration. A systems approach might see the proliferation of both standards and classilications as purely a matter of integration-almost like a gigantic web of interoperability. Yet the sheer density of these phenom­ena go beyond questions of interoperability. They are layered, tangled, textured; they interact lo form an ecology as well as a flat set of compatibilities.

Ubiquity The first major theme is the ubiquity of classifying and standardizing. Classification schemes and standards literally saturate our environ­ment.

A definition of infrastructure

This chapter offers four themes, methodological points of departure for the analysis of these complex relationships. Each theme operates as a gestalt switch-it comes in the form of an i11fras/:ruclural inversion (Bowker 1994). This inversion is a struggle against the tendency of infrastructure to disappear (except when breaking down). Tt means learning to look closely at technologies and arrangements that, by design and hy habit, tend to fade into the woodwork (sometimes literally!). Infrastructural inversion means recognizing the depths of interde­pendence of technical networks and standards, on the one hand, and the real work of politics and knowledge production8 on the other.

Standards Classifications and standards are closely related, but not identical. \-Vhile this book focuses on classificalion, standards are crucial compo­nents of the larger argument. The systems we discuss often do become standardized; in addition, a standard is in part a way of classifying the world. What then are standards? The term as we use it in the book has several dimensions:

Infrastructures are never transparent for everyone, ancl lheir '\\•ork­abilit y as they scale up becomes increasingly complex. Through due methodological attention to the architecture and use of these syslems, we can achieve a deeper understanding of how it is that individuals and communities meet infrastructure. ·we know that this means, at Lhe leasl, an understanding of infraslructure that includes these points:

The sheer density of the collisions of classification schemes in our lives calls for a new kind of science, a new set of metaphors, linking tradi­tional social science and computer and information science. We need a tqpography of things such as the distribution of ambiguity; the fluid dynamics of how classification systems meet up-a plate tectonics rather than a static geology. This nevi science will draw on the best empirical studies of work-arounds, information use, and mundane tools such as desktop folders and file cabinets (perhaps peering back­wards out frorn the Web and into the practices). It will also use the best of object-oriented programming and other areas of computer science to describe this territory. It will build on years of valuable research on classification in library and information s<:ience.

Information infrastrucLUre is a tricky thing to analyze_l; Good, usable systems disappear almost by deiinition. The easier they arc lo use, the harder they are to see.

A� we know from studies of work of all sorts, people do not do the ideal joh, but the doable job. \Vhen faced with too many alternatives and too much information, they satisfice (Mard1 and Simon 1958).

Forms like Lhe death certificate, ·when ag6TTcgated, form a case of what Kirk and Kutd1ins (1992) call "the substitution of precision for validity" (see also Star 1989b). That is, when a seemingly neutral data collection mechanism is substituted for ethkal conflict about the con­tents of the forms, the moral debate is partially erased. One may get ever more prn:ise knowledge, without having resolved deeper ques­tions, and indeed, by burying those questions.

we ·define boundary o4_jects as those o�jects that both inhabit several communities of practice and satisfy the informational requirements of each of them. In working practice, tJ1ey are objects that are able both to travel across borders and maintain some sort of constant identity. They can be tailored to meet rhe needs of any one community (they arc plastic.: in this sense, or customizable). At the same time, they have common identities across settings. 'Ibis is achieved by aJlowing the objects to be weakly struc­tured in wmmon use, imposing stronger structures in the individual­site cailored use. They a.re thus both ambiguous and constant; they may be abstract or concrete.

Classifications may or may not become standardized. If they do not, they are ad hoc, limited to an individual or a local community, and/or of Limited duration. At the same time, every successful standard imposes a classification system, al the very least between good and bad ways of organizing acLions or things. And the work-arounds involved in the practical use of standards frequently entail the use of ad hoc nonstandard categories.

Nomenclature and dassifi<:at..ion are frequently confused, howevc1; since attempts are often made to model nomencla­ture on a 1>ingle, stable system of classification principles, as for exam­ple with bot.any (Bowke1; in press) or anatomy.

Clas.�ification A classification is a spatial, temporal, or sjH1ti11-lemporal segmm,tation rif lhe world. ,\ "classification system" is a set of boxes (rnelaphorical or literal) inlo which things can be pul to then do some kind of work-bureau­cratic or knowledge production. In an abstract, .ideal sense, a classifica­tion system exhibits the frillowing properties:

vVe have a moral and ethical agenda in our querying of these systems. Each standard and each category valorizcs some point of view and silences another. This is not inherently a bad thing-indeed it is inescapable.

Table 1.1 A definition of infrastructure

This categorical saturation furthermore forms a complex web. Al­though it is possible to pull out a single classification scheme or stan­dard for reference purposes, in reality none of them stand alone. So a_ subproperty of ubiquity is interdependence, and frequently, integra­t10n. A systems approach might see the proliferation of both standards and classifications as purely a matter of integration-almost like a gigantic web of interoperability. Yet the sheer density of these phenom­ena go beyond questions of interoperability. They are layered, tangled, textured; they interact to form an ecology as well as a flat set of compatibilities.

Ubiquity __ The first major theme is the ubiquity of classifying and standardmng. Classification schemes and standards literally saturate our environ­ment.

This chapter offers four themes, methodological points of departure for the analysis of these complex relationships. Each theme operates as a gestalt switch-it comes in the form of an infrastructural inversion (Bowker 1994). This inversion is a struggle against the tendency of infrastructure to disappear (except when breaking down). It means learning to look closely at technologies and arrangements that, by design and by habit, tend to fade into the woodwork (sometimes literally!). Infrastructural inversion means recognizing the depths of interde­pendence of technical networks and standards, on the one hand, and the real work of politics and knowledge production8 on the other.

Infrastructures are never transparent for everyone, and their work­ability as they scale up becomes increasingly complex. Through due methodological attention to the architecture and use of these systems, we can achieve a deeper understanding of how it is that individuals and communities meet infrastructure. We know that this means, at the least, an understanding of infrastructure that includes these points:

Information infrastructure is a tricky thing to analyze.6 Good, usable systems disappear almost by definition. The easier they are to use, the harder they are to see. As well, most of the time, the bigger they are, the harder they are to see.

The sheer density of the collisions of classification scheme� in_ our liv�s calls for a new kind of science, a new set of metaphors, hnkmg tradi­tional social science and computer and information scien�e. We ne�d a topography of things such as the distribution of ambiguity; the flu_,d dynamics of how classification systems �eet u�-a plate tectomcs rather than a static geology. This new science will draw on the best empirical studies of work-arounds, info�mation use, and �undan_e tools such as desktop folders and file cabmets (perhaps peering back­wards out from the Web and into the practices). It will also use th<: best of object-oriented programming and other areas of compute, science to describe this territory. It will build on years of valuablt research on classification in library and information science.

s we know from studies of work of all sorts, people do not do the ideal job, but the doable job. When faced with too many alternatives and too much information, they satisfice (March and Simon 1958).

Forms like the death certificate, when aggregated, form a case of what Kirk and Kutch ins ( 1992) call "the substitution of precision for validity" (see also Star 1989b). That is, when a seemingly neutral data collection mechanism is substituted for ethical conflict about the con­tents of the forms, the moral debate is partially erased. One may get ever more precise knowledge, without having resolved deeper ques­tions, and indeed, by burying those questions.

we define boundary objects as those objects that both inhabit several communities of practice and satis� the informational requirements of each of them. In working practice, they are objects that are able both to travel across borders and maintain some sort of constant identity. They can be tailored to meet the needs of any one community (they are plastic in this sense, or customizable). At the same time, they have common identities across settin�s. This is achieved by allowing the objects to be weakly struc­tured m common use, imposing stronger structures in the individual­site tailored use. They are thus both ambiguous and constant; they may be abstract or concrete.

Classifications may or may not become standardized. If they do not, they are ad hoc, limited to an individual or a local community, and/or of limited duration. At the same time, every successful standard imposes a classification system, at the very least between good and bad ways of organizing actions or things. And the work-arounds involved in the practical use of standards frequently entail the use of ad hoc nonstandard categories.

Standards Classifications and standards are closely related, but not identical. While this book focuses on classification, standards are crucial compo­nents of the larger argument. The systems we discuss often do become standardized; in addition, a standard is in part a way of classifying the world.

Nomenclature and classification are frequently confused, however, since attempts are often made to model nomencla­ture on a single, stable system of classification principles,

Classification A classification is a spatial, temporal, or spatio-temporal segmentation of the world. A "classification system" is a set of boxes (metaphorical or literal) into which things can be put to then do some kind of work-bureau­cratic 9r knowledge production.

We have a moral and ethical agenda in our querying of these systems. Each standard and each category valorizes some point of view and silences another.

Members of organizations sometimes have differing (and multiple)goals, and conflict may be as important as cooperation in obtaining is-sue resolutions (Kling, 1991). Groups and organizations may not haveshared goals, knowledge, meanings, and histories (Heath & Luff,1996; Star & Ruhleder, 1994).

Knoll workstation fabric panel, 3'6" by 2', with crepe Knoll workstation fabric panel, 3'6" by 2'6", with crepe Knoll workstation fabric panel, 3'6" by 3'6", with crepe BPI workstation 1/2 plexiglass panel, 5'6" by 2'6"

Choose an object to consider.All objects signify; some signify more expressively than others.

What is decisive in collecting is that the object is detached from all its original functions in order to enter into the closest conceivable relation to things of the same kind. The relation is the diametric opposite of any utility, and falls into the peculiar category of completeness

His method is lo treat man as the measure of all things, but in doing so he again proceeds from the error of believing that he has these things [which he intends to measure] im~ "'" o.+ llP> mediately before him as mere objects

She would have to listen to the members of this college community, watch what they did, and participate in their activities to learn such meanings.