Nested Callbacks (2013)
The article reflects on a web project from 2013 that used 21 nested JavaScript callbacks to animate a series of CSS triangles. The author, then a beginner, struggled with understanding programming concepts and relied on trial and error to achieve the desired visual effect. Despite the inefficient and overly complex code, the project represented a personal milestone in learning web development.
- ▪The webpage featured 20 rows of triangles created using HTML divs and CSS styling.
- ▪The animation was achieved through deeply nested jQuery callbacks, with each row fading out sequentially.
- ▪The author copied the entire jQuery library into their JavaScript file instead of linking it externally.
- ▪The project was inspired by hand-drawn triangles from a summer road trip and an interest in creating visually appealing content for Tumblr.
- ▪The code was written in Windows Notepad and required careful indentation to manage the nested structure.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Michellebu |
| Canonical URL | https://blog.michellebu.com/2013/03/21-nested-callbacks/ |
| Publication time | Sat, 16 May 2026 06:49:30 +0000 |
| Retrieval time | 2026-05-16T07:10:17.660Z |
| Last seen | 2026-05-16T07:10:17.660Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 5HoBomJfLQ0z |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
March 27, 201321 nested callbacks About 21 months ago, before I even knew what a callback was, I built my first webpage. In honor of its 21 nested callbacks, I think it's about time I finally take a second look at it. At the time I had a perhaps cliche habit of doodling in my notebook during humanities classes and family road trips. One particular summer road trip yielded a collection of triangles that I thought looked pretty cool. I decided that a worthy mid-summer endeavour would be to reproduce it digitally. I also thought that would make me extremely cool on Tumblr. I began by asking CS major friends if they could point me in the right direction.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Michellebu.