Code & Development
Open Transclude
The Website Obesity Crisis
A Talk by Maciej CegłowskiWeb Design - The First 100 Years
A Talk by Maciej CegłowskiVisualizing Algorithms
An Article by Mike BostockAias
A Profile by Nick TrombleyThe Future of Programming
A Talk by Bret VictorWhat Makes Software Good?
An Article by Mike BostockAn incoherent rant about design systems
An Article by Robin RendleNo matter how fancy your Figma file is or how beautiful and lovingly well organized that Storybook documentation is; the front-end is always your source of truth. You can hate it as much as you like—all those weird buttons, variables, inaccessible form inputs—but that right there is your design system.
...being honest about this is the first step to fixing it.
Right-Angle Doodling Machine
A Game by Clive Thompson- You draw one single line. It can be as long as you like.
- To start the line, you put your pen down.
- You can make right-angle turns only, either 90 degrees or -90 degrees.
- You cannot back up. You must always move forward.
- You don’t lift your pen until you’re ready to stop. When you lift the pen, the doodle is done.
What do I need to read to be great at CSS?
An Article by Baldur BjarnasonA rule of thumb is that the importance of a blog in your feed reader is inversely proportional to their posting cadence. Prioritise the blogs that post only once a month or every couple of weeks over those that post every day or multiple times a day...Building up a large library of sporadically updated blogs is much more useful and much easier to keep up with than trying to keep up with a handful of aggregation sites every day.
Designing with code
An Article by Matthew StrömRecently I’ve had a few opportunities to use code to create design. In two of my bigger projects at The Wall Street Journal, writing code has led to new ideas. Problems that typically plague early designs — e.g. “how does this look with real content?” — are easy to solve. By exploring visual ideas directly in code, I’ve started to see the amazing potential of code as a design tool.
Picking better names for variables, functions, and projects
An Article by Tom MacWright- Avoid weasel words
- Follow patterns religiously
- Don’t cheap out on characters
- Call things the same thing
- Don’t name internal projects
- When things change, change their names
this vs. that
A Website by Phuoc Nguyentixy.land
A Websitesin(t * x) * cos(t * y)
Creative code golfing.
Front-of-the-front-end and back-of-the-front-end web development
An Article by Brad FrostA succinct way I’ve framed the split is that a front-of-the-front-end developer determines the look and feel of a
button
, while a back-of-the-front-end developer determines what happens when thatbutton
is clicked.The Great Divide
An Article by Chris CoyierOn one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
Painting With the Web
An Article by Matthias OttSo much about [Gerhard Richter's painting process] reminds me of designing and building for the Web: The unpredictability, the peculiarities of the material, the improvisation, the bugs, the happy accidents. There is one crucial difference, though. By using static wireframes and static layouts, by separating design and development, we are often limiting our ability to have that creative dialogue with the Web and its materials. We are limiting our potential for playful exploration and for creating surprising and novel solutions. And, most importantly, we are limiting our ability to make conscious, well-informed decisions going forward. By adding more and more layers of abstraction, we are breaking the feedback loop of the creative process.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
bees & bombs
A Blog
Cubed
A dry, husky business
Despite the furor over their aggressive unmanliness, clerks, and with them the office, crept silently into the world of nineteenth-century America. Moral philosophers were mostly preoccupied with the clang of industrialization and its satanic mills, and most regarded as negligible the barely audible scratch of pens across ledgers and receipts that characterized the new world of clerical work. It was only a “dry, husky business,” as the narrator of Bartleby had it.
A segment of the enormous file
As office buildings grew taller, and flammability became a problem, steel file cabinets replaced wooden ones – the tall cabinets mimicking the shape of the skyscraper, such that the “file” seemed to be a metaphorical stand-in for the office itself. “Each office within the skyscraper,” C. Wright Mills would argue some years later, “is a segment of the enormous file, a part of the symbolic factory that produces the billion slips of paper that gear modern society into its daily shape.” Aldous Huxley, in his dystopian novel Brave New World, could imagine no more powerful symbol of a totally bureaucratized world than the idea of each person having his or her name on a file.
Taylorism
“In the past the man has been first. In the future the system must be first.” — Fred W. Taylor
Taylorism was a way of thinking that came at the expense of the workers’ own knowledge of their system. Taylor summed up his philosophy thus:
“It is only through enforced standardization of methods, enforced adoption of the best implements and working conditions, and enforced cooperation that this faster work can be assured. And the duty of enforcing the adoption of standard and enforcing this cooperation rests with the management alone.”
The unscripted practices of the old offices would remain, but as a kind of subterfuge: in the future, a leisurely pace wouldn’t be the norm; time would not be given, but stolen.
Divided against itself
By separating knowledge from the basic work process (“the separation of conception from execution,” as Harry Braverman once put it), in the factory as well as the office, the ideology of Taylorism all but ensured a workplace divided against itself, both in space and in practice, with a group of managers controlling how work was done and their workers merely performing that work.
Somewhat more dangerously, this division put into serious doubt the notion that office workers were, as a whole, on the way up. It became increasingly clear from the shape of the offices themselves, and from the distance between the top and the bottom rungs of the “ladder”, that some workers were never going to join the upper layers of management. For some, work was always, frankly, going to suck.
Form follows finance
The formula that Sullivan coined to explain this individualist-conformist principle has become a commonplace of architectural history: “Form follows function.” The envelope of the building was to reflect no particular style, no empty ideal, but rather, with as pure a transparency as possible, the shape and feel of the interior. It was the office that determined the skyscraper – a fact that might have had a beneficial effect on the form of the office itself.
But the result was the opposite: few conceptions of the office have had a more deleterious effect on the human work environment. The title of an influential work by the architectural historian Carol Willis gives us a better, if less palatable, explanation: Form follows Finance. For by and large, making an office “functional” had less to do with making it serve the needs of a particular corporation and much more with serving any corporation. The point was not to make an office building per specification of a given company, but rather to build for an economy in which an organization could move in and out of a space without any difficulty. The space had to be eminently rentable.
Serendipity
This was not meant to be like Bell Labs; there were no expectations that the clerical workers would run into their managers in a “serendipitous encounter” and produce a new innovation. The ideas was rather to create a workplace in which status barriers seemed to dissolve, in which participation and friendliness all around made the work environment look less like the white-collar factory it was.
Office survival
“The caveman was undoubtedly very pleased to find a good cave but he also undoubtedly positioned himself at the entrance looking out. Protect your back but know what is going on outside is a very good rule for survival. It is also a good survival rule for life in offices.” — Robert Propst, The Office: A Facility Based on Chicago
The office landscape
An organic, almost forest-like office layout.
There is an affinity with certain planned “landscapes” of the natural world – namely, the classic Italian Baroque garden. In the sample plans the Schnelle brothers devised, the arrangement of desks seems utterly chaotic, totally unplanned – a mess, like a forest of refrigerator magnets. But, as with the seemingly “wild” overgrowth of a “natural” garden, the office landscape is more thoroughly planned than any symmetrical and orderly arrangement of desks. Imaginary lines wend their way around every cluster, delineating common pools of activity; between and through the undergrowth of clusters are invisible, sinuous paths of work flow.
Open-plan the world
In the end, noise would always be a problem, when quiet was not placed at a premium. Interaction and communication were conceived of as norms in the landscaped office; introspection and concentration were sidelines. In the rush to open-plan the world, some crucial values for the performance of work were lost.
The cubicle
The cubicle had the effect of putting people close enough to each other to create serious social annoyances, but dividing them so that they didn’t actually feel that they were working together. It had all the hazards of privacy and sociability but the benefits of neither. It got so bad that nobody wanted them taken away; even those three walls offered some kind of psychological home, a place one could call one’s own. All these factors could deepen the frenzied solitude of an office worker.
Chilled-out anxiety
Working in the typical dot-com office was an admixture of frenetic pace and a relaxed overall atmosphere, exemplifying that chilled-out anxiety which was the general mood of the 1990’s.
A resource
The office, Chiat argued, had become the site of a turf war, not a place to do work. Changing the office “means focusing on doing great work instead of focusing on agency politics,” he argued. “You come to work because the office is a resource.”