# Smooth Ideas: The Art of Persistence

Newsy: Art 8-Ball Philosophy
Published: 2026-03-20T02:00:00.286Z
Source: https://newsyai.com/edition/8642428a-f0ab-45e6-a2b6-0229652f5f6c
Archive: https://newsyai.com/newsy/3b7e2888-fadd-4dc4-8191-e1e017e8878c.md

---

# The Daily Interesting — Art & Design Edition  
**March 20, 2026**

## The idea
> My brain thinks of it like a rock you want to make smooth. You can discuss how to best smooth its edges, debate what tools will do it best, and so forth.  
> Or you can be like a river of water that washes over the rock incessantly day after day after day, smoothing over every last rough edge by encountering it over and over and over again.  
> You can get pretty damn far by incessantly encountering a piece of software over and over, fixing everything you find along the way that doesn’t feel right.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)[[2]](https://barnsworthburning.net/extracts/recwADpnj4ZSomONQ)

— **Jim Nielsen** ([BarnsworthBurning extract](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU))[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

- Source thread on BarnsworthBurning: “Design” space ([barnsworthburning.net](https://barnsworthburning.net/spaces/recedH7bqMdI8jKga))[[3]](https://barnsworthburning.net/spaces/recedH7bqMdI8jKga)

## Who said it (and the context)
**Jim Nielsen** is a web developer and design thinker known for his insightful blog at [blog.jim-nielsen.com](https://blog.jim-nielsen.com/), where he explores design patterns, web development, and the human elements of technology.[[4]](https://www.blogsareback.com/blogs/blog.jim-nielsen.com) In his 2023 post "Build Great Software By Repeatedly Encountering It," Nielsen critiques over-reliance on planning, data, or tools, arguing instead for hands-on, daily immersion to refine products organically.[[5]](https://blog.jim-nielsen.com/2023/software-by-encountering/)[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

## A small expansion
Nielsen's river metaphor highlights how sustained, direct exposure uncovers subtle flaws that discussions miss—persistent use polishes designs through real-world friction, far more effectively than upfront theorizing.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

## Another lens on the idea
**Jared Spool**, UX research pioneer, echoes this in "Fast Path to a Great UX – Increased Exposure Hours," stressing that designers improve fastest by logging massive hands-on time with interfaces, building intuition through repetition rather than abstract study.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

---

## Why this matters across art and design

- **Visual identity**  
  Live with your marks daily—print logos, use them in notes—to spot what wears well or jars over time, refining for lasting resonance.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

- **Product & UX**  
  Daily self-testing reveals "lumps" in flows; incessant encounters smooth interactions better than one-off user tests.[[5]](https://blog.jim-nielsen.com/2023/software-by-encountering/)

- **Architecture**  
  Occupy prototypes or models routinely—walk spaces, touch surfaces—to erode awkwardness, evolving humane environments.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

- **Studio art**  
  Keep works in your daily view; repeated glances highlight unresolved tensions, guiding organic evolution without forced overhauls.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

---

## Two quick drills

1. **River Run** (7 days)  
   Use your current project daily for 10 minutes. Log one "rough edge" fixed each time—what emerges after a week?[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

2. **Exposure Audit** (15 minutes)  
   Track hours spent *using* (not planning) your work this week. Double it next week—note intuition gains.[[5]](https://blog.jim-nielsen.com/2023/software-by-encountering/)

---

## Thread to remember
Extends the *Design Squiggle*'s mess-to-clarity (45), Richter's live feedback (48), and drafts as sacrificial layers (3)—Nielsen adds: Persistent *encounter* is the river that truly refines, turning iteration into effortless polish.

---

## Sources
- Central idea and quote: Jim Nielsen via BarnsworthBurning ([extract](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU); [Design space](https://barnsworthburning.net/spaces/recedH7bqMdI8jKga)).[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)[[3]](https://barnsworthburning.net/spaces/recedH7bqMdI8jKga)  
- Full post: [blog.jim-nielsen.com/2023/software-by-encountering](https://blog.jim-nielsen.com/2023/software-by-encountering/).[[5]](https://blog.jim-nielsen.com/2023/software-by-encountering/)  
- Nielsen background: [Blogs Are Back](https://www.blogsareback.com/blogs/blog.jim-nielsen.com).[[4]](https://www.blogsareback.com/blogs/blog.jim-nielsen.com)  
- Complementary view: Jared Spool via BarnsworthBurning see-also.[[1]](https://barnsworthburning.net/extracts/rec1o6tgMHDid6kJU)

Try this today: What's one "rock" in your project needing river-like attention?
