# ia Published articles for ia. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Niche Hobby Programming Communities Reject LLM Use DevFeed: [Why Niche Hobby Programming Communities Reject LLM Use]() Original publisher: [Read original article]() Author: fogus Published: 2026-08-04T09:07:49Z Content type: opinion Language: en Sources: [Mike Fogus]() Topics: [Large Language Model](), [Programming](), [infoarena]() Tags: [ai](), [communities](), [computing](), [ia](), [llm](), [programming]() ### AI overview The essay examines why niche hobby programming communities often reject LLM use. It argues that these communities value deep understanding, domain knowledge, and the learning process itself, while presenting LLMs as most useful as a force multiplier for experts rather than a substitute for expertise. ### Source excerpt Whereby I discuss why we're seeing an increasingly aggressive rejection of LLMS by niche hobby communities... ## What van Emden's 1982 vision of conversational thought tools reveals about LLM interfaces DevFeed: [What van Emden's 1982 vision of conversational thought tools reveals about LLM interfaces]() Original publisher: [Read original article]() Author: fogus Published: 2026-04-21T10:07:49Z Content type: opinion Language: en Sources: [Mike Fogus]() Topics: [Large Language Model](), [intelligence](), [interface]() Tags: [ai](), [computing](), [ia](), [intelligence](), [interface](), [llm](), [reasoning]() ### AI overview The article revisits M.H. van Emden's 1982 vision of a conversational computer-aided thought tool and compares it with today's LLM interfaces. It highlights how natural-language ambiguity and opaque system interpretations affect interaction and structured thinking. ### Source excerpt Whereby I read a paper about Intelligence Augmentation written in 1982 and talk about how it relates to today... ## Why I migrated my blog from WordPress to Eleventy and Netlify DevFeed: [Why I migrated my blog from WordPress to Eleventy and Netlify]() Original publisher: [Read original article]() Author: Lea Verou Published: 2023-07-21T00:00:00Z Content type: article Language: en Sources: [Lea Verou's blog]() Topics: [Eleventy](), [Jamstack](), [Content Management System](), [WordPress](), [Netlify](), [Git](), [Markdown](), [Developer experience](), [GitHub Copilot]() Tags: [11ty](), [blog](), [cms](), [developer-experience](), [eleventy](), [git](), [github-copilot](), [ia](), [jamstack](), [markdown](), [meta](), [netlify](), [open-source]() ### AI overview The author explains why WordPress became less suitable for her blog and describes migrating to Eleventy, a statically generated site workflow using Git, Markdown, and Netlify. She highlights simplicity, developer experience, and reduced reliance on plugins while noting the effort required to migrate years of content, plugins, and styling. ### Source excerpt WordPress has been with me since my very first post in 2009. There is a lot to love about it: It's open source, it has a thriving ecosystem, a beautiful default theme, and a revolutionary block editor that makes my inner UX geek giddy. Plus, WP made building a website and publishing content accessible to everyone. No wonder it's the most popular CMS in the world, by a huge margin. However, for me, the bad had started to outweigh the good: Things I could do in minutes in a static site, in WP required finding a plugin or tweaking PHP code. It was slow and bloated. Getting a draft out of it and into another medium was a pain. Despite having never been hacked, I was terrified about it, given all the horror stories. I was periodically getting "Error establishing a database connection" errors, whose frequency kept increasing. It was time to move on. It's not you WP, it's me. It seemed obvious that the next step would be a statically generated blog. I had been using Eleventy for a while on a variety of sites at that point and loved it, so using that was a no-brainer. In fact, my blog was one of my last remaining non-JAMstack sites, and by far the biggest. I had built a simple 11ty blog for my husband a year ago, and was almost jealous of the convenience and simplicity. There are so many conveniences that just come for free with this workflow: git, Markdown, custom components, even GitHub Copilot as you write your prose! And if you can make the repo public, oooooh, the possibilities! People could even file PRs and issues for your blog posts! Using Netlify as a platform was also a no-brainer: I had been using it for years, for over 30 sites at this point! I love their simplicity, their focus on developer experience, and their commitment to open source. I also happen to know a bunch of folks there, and they have a great culture too. However, I was dreading the amount of work it would take to migrate 14 years of content, plugins, and styling. The stroke that broke the camel's ## Rethinking Categorization DevFeed: [Rethinking Categorization]() Original publisher: [Read original article]() Author: Lea Verou Published: 2023-07-20T00:00:00Z Content type: opinion Language: en Sources: [Lea Verou's blog]() Topics: [Information Architecture](), [11ty](), [migration](), [Netlify](), [Web Development](), [WordPress]() Tags: [11ty](), [blog](), [categories](), [folksonomies](), [ia](), [information-architecture](), [meta](), [migration](), [netlify](), [tags](), [taxonomies](), [ux](), [web](), [wordpress]() ### AI overview An account of rethinking a blog's information architecture while migrating from WordPress to 11ty. It explains separating categories from tags, handling tag aliases with global data and dynamically generated Netlify redirects, and presenting orphan tags in the tag index. ### Source excerpt This is the third spinoff post in the migration saga of this blog from WordPress to 11ty. Migrating was a good opportunity to rethink the information architecture of my site, especially around categorization. Categories vs Tags Just like most WP users, I was using both categories and tags, simply because they came for free. However the difference between them was a bit fuzzy, as evidenced by how inconsistently they are used, both here and around the Web. I was mainly using Categories for the type of article (Articles, Rants, Releases, Tips, Tutorials, News, Thoughts), however there were also categories that were more like content tags (e.g. CSS WG, Original, Speaking, Benchmarks). This was easily solved by moving the latter to actual tags. However, tags are no panacea, there are several issues with them as well. Problems with tags Tag aliases First, there were many tags that were synonyms of each other, and posts were fragmented across them, or had to include both (e.g. JS and Javascript). I addressed this by defining aliases in a global data file, and using Eleventy to dynamically build Netlify redirects for them. # Tag aliases {% for alias, tag in tag_aliases %}/tags/{{ alias }}/ /tags/{{ tag }}/ 301 {% endfor %} Turns out I'm not the first to think of building the Netlify _redirects file dynamically, some googling revealed this blog post from 2021 that does the same thing. I've also decided to expose these aliases in the tags index: "Orphan" tags Lastly, another issue is what I call "orphan tags": Tags that are only used in a single post. The primary use case for both tags and categories is to help you discover related content. Tags that are only used once clutter the list of tags, but serve no actual purpose. It is important to note that orphan tags are not (always) an authoring mistake. While some tags are definitely too specific and thus unlikely to be used again, the vast majority of orphan tags are tags that could plausibly be used again, but it simply hasn'