fast capitalism versus slow, you know, organic mutualism.

If Zettelkasten is the solution, what was the underlying problem?

I enjoyed this podcast but got the feeling they see PKM as a kind of grueling Fordist production line. The process in your book seems a lot less like a grind and a lot more like fun!

there's a huge disparity between state of law application of tech and what's 00:15:42 actually happening

Probably not. But it would do us good to remember that machines are supposed to make our lives better, not faster. Perhaps we should unplug just a little before we become undone. Such decompression is why we think so many Levenger customers savor the pensive pause of the fountain pen (which David McCullough also uses).

As of right now the full build takes over an hour to run, and this makes cycling for PRs and quick iterative development very difficult.

Kommt ein Teil der Angst nicht auch aus der Furcht vor Fehlern? Oft funktioniert die Software eben doch nicht so gut wie die Bremsen meines Autos. Der Computer beruht auf den gleichen einfachen Prinzipien wie vor sechzig Jahren. Aber die Leistungsfähigkeit hat sich millionenfach gesteigert. Der Effekt dieser Leistungssteigerung auf die Programmierung ist allerdings sehr negativ – vor allem auf die Disziplin der Programmierung. Früher waren die Ressourcen extrem begrenzt, heute dagegen ist alles in Unmengen vorhanden: Speicher, Rechenleistung, Übertragungskapazitäten, einfach alles. Niemand muss mehr sparen. Programmieren heißt aber, Disziplin zu bewahren und jeden Moment darauf zu achten, dass man unnötige Komplexität vermeidet. Dieses Denken verschwindet mehr und mehr. Denn eine solche Optimierung erfordert Zeit. Sie wäre viel teurer, als einfach noch ein bisschen Hardware dazuzukaufen. Deswegen wird es nicht gemacht. Anzeige Warum ist das schlimm? Diese schnell erstellten Programme sind nicht nur weniger ökonomisch. Sie enthalten auch mehr Fehler.

called thinking fast and slow by daniel

In their article, Scientist Spotlight Homework Assignments Shift Students’ Stereotypes of Scientists and Enhance Science Identity in a Diverse Introductory Science Class,” Jeffrey Schinske, Heather Perkins, Amanda Snyder, and Mary Wyer created a “scientist spotlight” weekly homework assignment to introduce counter stereotypical examples of scientists and provide a diverse representation of contributions to science. Each week, students reviewed a resource regarding these scientists’ research and personal history in lieu of other textbook readings. Through their analysis, the scholars were able to study and detect shifts in both scientist stereotypes and the students’ ability to see their possible selves in science.

“If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and five minutes thinking about solutions.” -- Albert Einstein

Make the case that the status quo is inequitable

if cultural evolution is sufficiently rapid, it may act to pre-empt and slow genetic evolution. That is, in solving adaptive challenges before genetic evolution takes place, cultural inheritance may reduce the opportunity for natural selection on genes and weaken the adaptive value of information stored in genetic inheritance in the long term. This process is the opposite of genetic assimilation, in which a plastic trait becomes genetically encoded. We call this mode of GCC cultural pre-emption.

the human brain is an energy hog like and you can learn a lot about a lot of our uh biases and problems from the kinds of shortcuts that the brain takes 00:06:41 in the name of energy conservation well it looks like estimating group consensus is one of those shortcuts right because all it's equal your brain tends to assume that the loudest voices repeated 00:06:53 the most are the majority and and i think about that i think wow that doesn't seem like a good a good shortcut at all but i guess if you go back and f through evolution and when most of our time was spent and like 00:07:05 seeing like the dumbar number kind of you know groups it probably it obviously had to work well enough right to just be here with us but now when you think about with social media 00:07:18 and these massive imaginary communities like nations where you're never going to meet more than a tiny tiny percentage of the people in your group that shortcut becomes problematic um and 00:07:31 we can talk about it like i mean social media in particular makes it very very easy to distort perceived group consensus

you can’t force insight into a preconceiveddirection

But it is kind of verbose, and it’s also a lot slower, so I can understand why the model test might be preferred.

Developing this argument, Bauman (2000) talks of the super-rich as the 'new cosmopolitans', suggesting that the fundamental consumption cleavage in contemporary society is between these 'fast subjects' who dwell in transnational space and those 'slow subjects' whose lives remain localised and parochial. The fast world is one consisting of airports, top level business districts, top of the line hotels and restaurants, chic boutiques, art galleries and exclusive gyms - in brief, a sort of glamour zone that is fundamentally disconnected from the life worlds of the vast majority of the world's population. Bauman thus equates power with mobility, echoing Massey's notion of unequal 'power-geometries'

Normally use guix can be frustratingly slow to use.

Happy Third Birthday #24728!

Why does test suite performance matter? First of all, testing is a part of a developer's feedback loop (see @searls talk) and, secondly, it is a part of a deployment cycle.

“Monetising what we see as sacred knowledge, our way of being – driving, walking – is sacred knowledge and the only people who should have any purview over that is our community. … What if we look at what the data could do for our community and how to achieve that? … We are gathering our data because we love our people, we want a better future for the next generations. What if all data was gathered for those reasons? What would it look like?”

At the Philadelphia Museum of Art, educators train medical students in slow looking to hone their observational skills, but as West notes, it’s not just about noticing small physical details that might inform a diagnosis.

At Slow Art Day events, museums generally ask visitors to look at five objects for 10 minutes each — enough time, often, to keep them looking a little longer. But the practice varies. Jennifer Roberts, an art history professor at Harvard University and a proponent of slow art, has her students look at an individual artwork for three hours. “Approach it as if you were a visitor from another planet with no prior knowledge of the configuration or content of earthly art,” she tells them.

This year’s Slow Art Day — April 10 — comes at a time when museums find themselves in vastly different circumstances.

Studies suggest that the average museumgoer looks at an artwork for less than 30 seconds. And with crowds that seem to push you from one piece to the next, overwhelmingly large exhibitions, and a dismal lack of seating options, museum spaces sometimes seem to encourage this “more is more” ethos. But on “Slow Art Day” every April, museums around the world offer programming that guides visitors in looking more patiently.

Silence Here’s another, more subtle, point about the grace of email and newsletters: Creation and consumption don’t happen in the same space. When I go to send a missive in Campaign Monitor the world of my laptop screen is as silent as a midnight Tokyo suburb.9 I think we’ve inured ourselves to the (false) truth that in order to post something, in order to contribute something to the stream, we must look at the stream itself, “Bird Box”-esque, and woe be the person in a productive creative jag, wanting to publish, who can resist those hot political tweets.

Sorry you’re surprised. Issues are filed at about a rate of 1 per day against GLib. Merge requests at a rate of about 1 per 2 days. Each issue or merge request takes a minimum of about 30 minutes (across at least 2 people) to analyse, put together a fix, test it, review it, fix it, review it and merge it. I’d estimate the average is closer to 3 hours than 30 minutes. Even at the fastest rate, it would take 3 working months to clear the backlog of ~1000 issues. I get a small proportion of my working time to spend on GLib (not full time).

Age of a ticket is completely irrelevant as anyone can request anything but the number of developers is limited. If you'd like to see something implemented, please consider providing a patch. Thanks!

Sorry if I sounded rude. I am using Gnome on a daily basis and am highly appreciating all the work anyone has put into it. I was just surprised when I found an AskUbuntu post from 2010 linking to this bug.

Wow 14 years. I still keep stumbling over this issue...

Progress is slow though. I want to change how assets are loaded, the current implementation of "pipelines" is challenging to work with.

Still broken, @cannikin. Nobody's on board to investigate, much less fix it. Please do dig in

release 0.0.1 after around 5 years.

It almost feels unreal finishing up this release post. It’s been so long!

After around 3 years of silence, Trailblazer is back with its 2.1 release.

To tell you the truth, the new tracing feature was the original reason why I decided to write 2.1 and make you sit and wait in agony for years. Nevertheless, tracing is simply blowing my mind. I can’t count how many hours and angering rushs of adrenaline I’ve saved since the introduction of the wtf? method and its helpful higher-level stack trace.

Take 3, Previously attempted in 2012 (#8189) and 2015 (#19709). This new version uses ActiveModel Attributes API.

Another recent attempt: #35246

The downside is the installation files are bigger than the traditional Debian package manager (DEB) files. They also use more hard drive real estate. With snaps, every application that needs a particular resource installs its own copy. This isn’t the most efficient use of hard drive space. Although hard drives are getting bigger and cheaper, traditionalists still balk at the extravagance of each application running in its own mini-container. Launching applications is slower, too.

How can you work when an application take a long time to open? even a calculator. On the first opening of writer, i do not have ssd, i have time to drink a coffee when with a deb i can work. Use snap only when it will be as effective as a deb.

Andrew Bosworth, one of Facebook’s longtime executives, has compared Facebook to sugar—in that it is “delicious” but best enjoyed in moderation. In a memo originally posted to Facebook’s internal network last year, he argued for a philosophy of personal responsibility. “My grandfather took such a stance towards bacon and I admired him for it,” Bosworth wrote. “And social media is likely much less fatal than bacon.”

One of the criticisms I’ve heard since I realised that better datastructures were possible is that I was “working secretely”. I certainly understand this feeling, but this is based on a misunderstanding of how research works. When I first had the idea that I’m explaining in this post, I realised that a complete rewrite would be needed. But for a very long time, almost nothing other than unusable, unreadable prototypes happened.

We advocate for a Slow Web Movement. We are what we eat, and we are also what we consume online. Data-driven advertising, BlackBox algorithms, and the competition between Big Tech to keep us “engaged“ has created an addiction to low-value content. It is time to reset our digital consumption and create healthier habits. Since the last decade, with a set of guidelines, the Slow Web Movement is changing Software to make it care about us again. Think of it as the equivalent of "Organic" for Technology.

But maybe this PR should still be merged until he finds time for that?

Sorry this sat for so long!

Unfortunately, many third party libraries, even though they are written in ESM, are published to npm as CJS modules, so we still need to concatenate them.

Anil Dash said it well: In general, a healthy mix of time spent online should be like healthy sourcing of food — it’s fine to have fast food from factories, but you want to make sure to also have fresh, local apps and sites and content, created by people you know and love, sourced within your community.

The date, time and place are scheduled according to when/where we can reserve Matz's time.

Problem is, everyone's busy, so it can be days or even weeks before even a small PR is merged. So I'm stashing my stuff here as I write it. I'll still try to keep the PRs in motion, to gradually get some of this merged.

It is not customary in Rails to run the full test suite before pushing changes. The railties test suite in particular takes a long time, and takes an especially long time if the source code is mounted in /vagrant as happens in the recommended workflow with the rails-dev-box.As a compromise, test what your code obviously affects, and if the change is not in railties, run the whole test suite of the affected component. If all tests are passing, that's enough to propose your contribution.

People say I'm prolific and proficient, I think that's because I like slow.

In 2010, the Chronicle of Higher Education asked two dozen scholars “What will be the defining idea of the coming decade, and why?” I wrote that Facebook would end up having more users than the population of China, and that giant social networks, with their madding crowds, would provoke a reaction: Just as the global expansion of fast food begat the slow-food movement, the next decade will see a “slow information” counterrevolution focused on restoring individual thought and creativity. And here we are a decade later, and we’re still hoping for the same thing. Maybe next decade?

In Reader, Come Home: The Reading Brain in a Digital World, Maryanne Wolf talks about how technology has led to more skimming rather than reading slowly and carefully. She talks about the benefits of “cognitive patience.” And she reminds us that reading quickly isn’t what makes someone a good reader.

„Wir brauchen weniger Eile und mehr Sorgfalt, sowohl beim Denken als auch beim Fühlen.“

The use of social time may also give us a unique view on understanding slow moving disasters (e.g., environmental events, famines and droughts) when compared to sudden impact events. Social time and social disruption provides tools to define disaster without making assessments (i.e., good/bad) of the event.

He adds that this phase could be important with sudden impacts, but not as important with slow-moving impacts.

Slow Design (Strauss & Fuad-Luke, 2009) celebrates slowness as an answer to critical issues in design, such as an often-perceived support to consumerism, a restrictive focus on functionalism, the diminishment of users’ engagement with materials, a lack of attention to local idiosyncrasies, and the need to think in the long-term.

cance. Waiting, for example (which, given the modern utilitarian approach to time [Zerubavel 1981, pp. 54-59], is generally regarded as an ordeal), is normally associated with worthlessness, and making others wait is often regarded as a symbolic display of deg

The slow technology design agenda, first presented by Hallnäs and Redström [15], builds on the idea that as tech-nologies become more ubiquitous they must do more than prioritise the efficiency and productivity associated with task-completion. In contrast to fast technologies that savetime, the aim with slow technologies is to produce time, by serving as an incitement for reflection.

The association of alternative approaches to time with a rejection of technology reinforces dichotomies that do not reflect the way people relate to artefacts and systems (Wajcman 2015). As a result, these proposals not only risk being interpreted as nostalgic or backward looking, but also leave little space for integrating more complex accounts of time (particularly those arising in the social sciences) or for discussing more nuanced rhythms, as well as more complex forces and consequences related to temporal decisions. As a result, instead of challenging dominant accounts of time, these proposals arguably reinforce the overarching narrative of universalised acceler

gs done. Accepting an invitation for reflection inherent in the design means on the other hand that time willappear, i.e. we open up for time presence” (Hallnas & Redstrom 2001). A slow technology would not disappear, but would make its

In Slow Technology, Hallnas & Redstrom (2001) advance the need for a form of design that emphasises reflection, the amplification of environments, and the use of technologies that a) amplify the presence of time; b) stretch time and extend processes; and c) reveal an expression of presenttime as slow-paced. Important here is the concept of “time presence”: “when we use a thing as an efficient tool, time disappears, i.e. we get things done. Accepting an invitation for reflection inherent in the design means on the other hand that time willappear, i.e. we open up for time presence” (Hallnas & Redstrom 2001). A slow technology would not disappear, but would make its

As in Slow Food—with its unhygienic soil, disorderly farmers’ markets, and inconvenient seasons—the annoyances of Slow Computing have become pleasures. With community-made software, there’s no one to blame but us, the community. We’re not perfect, but we’re working on it.

civic hackers often act as the “slow food movement” of digital political action, embracing local sourcing, ethical consumption, and pleasure of community work. Civic hackers are hardly responding to a new narrative of technological change.

infrastructure (the Internet is slower in Egypt)

Artificially Slow UI 2016-07-06 The UX Secret That Will Ruin Apps For You Facebook actually slows down its interface to make users feel safe, a Facebook spokesperson confirmed in an email.... various services on the web including travel sites, mortgage engines, and security checks are all making a conscious effort to slow down their omnipotent minds because our puny human brains expect things to take longer.... companies introduce what Kowitz calls an "artificial waiting" pattern into their interfaces. These are status bars, maybe a few update messages, to construct a facade of slow, hard, thoughtful work, even though the computer is done calculating your query. Another good reason to use your own tools (if it's faster than expected, you feel accomplished, not distrusting), or at least re-use indieweb software etc. that others are selfdogfooding because you know they won't be (or there's at least less chance of them) deliberately slowing it down.

slow readers down

you can never slow down too much. It’s impossible todisconnect. Right now I’ve got a ferry to catch from Swartz Bay to the GulfIslands, and Tony has a plane to catch at the airport. The idea of islandtime is all about trying, this is the keyword,trying, to slow down.

Delays that are too short cause overreaction, “chasing your tail,” oscillations amplified by the jumpiness of the response. Delays that are too long cause damped, sustained, or exploding oscillations, depending on how much too long. At the extreme they cause chaos. Overlong delays in a system with a threshold, a danger point, a range past which irreversible damage can occur, cause overshoot and collapse.