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
The Evolution and Fate of Botanical Field Books
To serve as a reminder
Looking back at my notebooks now, the information seems fairly sketchy, often abbreviated, and fairly uninformative. The purpose was merely to serve as a reminder for when, that evening, I would write up my notes in a proper field book.
Sterile creatures
Now that we are in the era of personal computers, traditional field books are being replaced by computer files. By default such “field books” are sterile creatures—all the words are spelled properly, the location data are exact to a matter of a few feet, and everything is properly formatted. In the spring of 1998, I penciled my last entry into my signature field book with the bright orange cover. Thereafter I have maintained a computer-based field book.
Oh, all the right stuff is there, clear, crisp and, well, dull… I tend to be overly particular about it—the format has to be right, everything properly spelled, the descriptive sequence in the proper order, and even the observations drafted with the final publication in mind (rather than what I happen to see at the moment). The emotions of finding something new, once mentioned in my handwritten field books, are now missing, as if my mental editor says “no, that is not proper for a scientific journal.”
Further and further away
In looking over my own forty-five years of keeping a record of plant specimens, I find that I am personally moving further and further away from the words I generate, becoming more aloof and separate from the experience of the actual event of collecting, concentrating instead on the precision of where and when. It is merely record keeping for the sole purpose of giving the facts.
With the decline of letter writing and the sterilization of field books, what we are losing is the individual. Field books are like letters that are replaced by often ephemeral emails. I fear that as we move further into the computer age we will similarly lose the detailed historical record that field books once provided. Sadly, the personalities of botanists will also be lost, for such musings as might be found in a field book are often telling to those wishing to know more of the past.