# blogging Published articles for blogging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## JulyReply - Re: Stuck in draft DevFeed: [JulyReply - Re: Stuck in draft]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2026-07-09T18:52:00Z Content type: opinion Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Learning](), [Parser](), [REST API](), [Containers](), [Git](), [Cloudflare](), [Compose](), [LLMs](), [Command-line interface]() Tags: [blog](), [blog-posts](), [blogging](), [cli](), [cloudflare](), [compose](), [containers](), [git](), [julyreply](), [llms](), [rest-api](), [technical-writing]() ### AI overview The author reflects on managing unfinished blog drafts, explaining that feedback, public interest, curiosity, and motivation sometimes lead to completion while many drafts are abandoned. They invite readers to vote on several proposed technical topics, including Retrofit, an HTML parser, Git, Docker containers in NixOS, Cloudflare, Compose UI, and LLM-assisted development. ### Source excerpt On drafts and being okay with them ## Building My Dream Developer Blog with Astro, Cloudflare, and AI DevFeed: [Building My Dream Developer Blog with Astro, Cloudflare, and AI]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-04-20T00:00:00Z Content type: article Language: en Sources: [Shreyas Patil's Blog]() Topics: [Astro](), [Cloudflare](), [AI Agent](), [Google]() Tags: [ai-agent](), [antigravity](), [astro](), [blogging](), [cloudflare](), [developer](), [engineering](), [gemini](), [git](), [google](), [markdown]() ### AI overview The author describes migrating more than 60 technical blogs from Hashnode to a custom Astro site hosted on Cloudflare Pages. The site uses Markdown files in Git, and the author used Google Antigravity as a pair-programming AI agent while building it. ### Source excerpt How I migrated my 60+ engineering blogs from Hashnode to a custom Astro setup on Cloudflare with the help of Google Antigravity AI. ## How I Made $360 by Serving Markdown to A.I. agents from My Jekyll Blog DevFeed: [How I Made $360 by Serving Markdown to A.I. agents from My Jekyll Blog]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-04-11T00:00:00Z Content type: opinion Language: en Sources: [Daniel Doubrovkine]() Topics: [Jekyll](), [Markdown]() Tags: [ai](), [blogging](), [jekyll](), [markdown](), [tech]() ### AI overview The author describes adding clean Markdown versions of Jekyll blog posts so AI agents can fetch them instead of parsing HTML. Thirty days later, a linked Monarch referral produced 18 signups, 12 paid conversions, and $360 in referral earnings, with no change in SEO traffic. ### Source excerpt In April 2025 I wrote Apologizing for My Obsessiveness Over Punctuation, a post about my various organizational compulsions. Near the end, almost as an aside, I mentioned that I obsessively categorize expenses in Monarch, a personal finance app, linking it with my referral code. That post earned me exactly one referral in the nine months that followed. Then, on January 15th, 2026, I wrote Serving Markdown for AI Agents. The idea is simple: for every post on this blog, there's now a .md version at the same URL. AI agents can discover and fetch clean markdown instead of parsing HTML. I didn't think much of it. Exactly thirty days later - the length of Monarch's free trial -- I started getting a stream of referral conversion notifications without any change in SEO traffic. Eighteen signups. Twelve converted to paid. At $30/referral, that's $360. We live in the future. How I Made $360 by Serving Markdown to A.I. agents from My Jekyll Blog was originally published by Daniel Doubrovkine at code.dblock.org | tech blog on April 11, 2026. ## 2025年总结 DevFeed: [2025年总结]() Original publisher: [Read original article]() Published: 2025-12-31T08:00:00Z Content type: article Language: zh Sources: [MaskRay]() Topics: [toolchain](), [LLVM](), [patches](), [Linux]() Tags: [assembler](), [blogging](), [bugs](), [https-maskray-me-blog-tags-assembler](), [linux](), [llvm](), [patches](), [summary]() ### AI overview A 2025 personal summary covering reduced open-source involvement, 18 blog posts, work on LLVM's integrated assembler and ELF specifications, Linux kernel contributions, ccls, binutils reports, and travel. ### Source excerpt TODO 一如既往，主要在工具链领域耕耘。但由于工作忙碌在open source社区投入的时间减少了。 Blogging 不包括这篇总结，一共写了18篇文章。 ## Ways in which GenAI has changed my (tech) life so far DevFeed: [Ways in which GenAI has changed my (tech) life so far]() Original publisher: [Read original article]() Author: Julien Published: 2025-12-07T11:35:32Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [genai](), [Artificial Intelligence](), [Large Language Model]() Tags: [ai](), [blogging](), [communities](), [devrel](), [genai](), [llms](), [tech]() ### AI overview The author reflects on how generative AI has affected their technology work and online information habits. They argue that AI-generated content has made quality technical material harder to find, increased low-quality and inaccurate social media content, and encouraged people to rely more on specialized communities and documentation. ### Source excerpt GenAI changed everything: harder to find quality content, social media flooded with bots, lost communities. But maybe it's making us more human again? #GenAI #TechCommunity ## 11ty Hacks for Fun and Performance DevFeed: [11ty Hacks for Fun and Performance]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-10-04T00:00:00Z Content type: tutorial Language: en Sources: [Alex Russell]() Topics: [Script](), [Nunjucks](), [Markdown](), [Web Development](), [Code]() Tags: [11ty](), [async](), [blog](), [blogging](), [build](), [code](), [fun](), [hacks](), [how-to](), [js](), [module](), [performance](), [script](), [web](), [webdev]() ### AI overview A developer shares techniques for improving performance in an 11ty site, including selectively loading shortcode resources through the 11ty Bundle plugin, avoiding duplicate scripts, and handling Nunjucks and Markdown preprocessing. ### Source excerpt This blog really isn't just for beating up on Apple for the way it harms users, the web, standards, and society to maintain power and profits. So here's some fun stuff I've been doing in my 11ty setup to improve page performance. Contents Page-Specific Resources via Shortcodes and the 11ty Bundler Mo Pagination, Mo Problems Build Time Impact Scroll-Position Based Delayed Code Loading Faster CSS Selectors for 11ty Syntax Highlighting Lean Rada's CSS-only Low-Quality Image Previews Bonus Hack: Global Acronyms for Better Abbreviations Does It Work? Page-Specific Resources via Shortcodes and the 11ty Bundler You know how it gets once you've got a mature 11ty setup: shortcodes proliferate, and some generate output that might depend on JS or CSS. If your setup is anything like mine, you might also feel conflicted about including some of those resources globally. It's important to have them available for the posts that need them, but it's not great to bring a charting library, e.g., into every page when only 1 in 20 will need it. This blog has grown many such shortcodes that generate expansions for features like: Web Components for YouTube and Vimeo embeds WebPageTest.org test embeds plot.js based charts Here, for instance, is how a Vimeo embed looks in the markdown of a page, using Nunjucks for Markdown pre-processing: {% vimeo "VIDEOID", "TITLE" %} This expands to: TITLE But this also requires script; e.g.: And the list keeps growing. To avoid having the weight of these components clogging up every page, a system for selectively pulling in their code would be helpful. It'd also be grand if we could make sure scripts appear just once, even if shortcodes are invoked multiple times per page. Included code should preferably also be located towards the top of the document. The 11ty Bundle plugin ## Twelve years of blogging DevFeed: [Twelve years of blogging]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-09-30T11:35:44Z Content type: opinion Language: en Sources: [Vlad Mihalcea]() Topics: [Development](), [Java](), [Spring Framework](), [Spring Boot](), [Jakarta EE](), [WordPress]() Tags: [anniversary](), [article](), [blog](), [blogging](), [jakarta-ee](), [java](), [software-developer](), [spring](), [spring-boot](), [wordpress](), [writing]() ### AI overview A personal reflection marking twelve years of blogging. The author describes starting the blog while working as a software architect, developing writing experience over time, and finding inspiration in wide-ranging reading. The article also promotes Hypersistence Optimizer for detecting performance issues in JPA and Hibernate data access layers across several Java frameworks. ### Source excerpt Twelve years later! Twelve years ago today, I decided to create this blog on WordPress.com to share whatever I was finding interesting while working as a software architect. Prior to starting this blog, I didn't have any writing experience, which you can clearly see in the first article I've ever published. However, practice makes perfect, and in time, I managed to learn how to express myself in writing, whether it was an article, a social media post, an answer on StackOverflow, or a book. Follow Your Bliss I've always loved to read.... Read More The post Twelve years of blogging appeared first on Vlad Mihalcea. ## #51 - My developer blogging journey so far DevFeed: [#51 - My developer blogging journey so far]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2025-02-18T14:10:44Z Content type: opinion Language: en Sources: [Shreyas Patil's Blog]() Topics: [Learning](), [Android](), [Firebase UI](), [Open Source](), [GitHub](), [Realtime Database](), [SDKs]() Tags: [android](), [androiddev](), [blog](), [blogging](), [code](), [community](), [content-creation](), [developer](), [development](), [firebase-database](), [firebase-ui](), [flutter](), [github](), [journey](), [kotlin](), [open-source](), [technical-documentation](), [technical-writing-1](), [writing]() ### AI overview A personal account of the author's blogging journey, beginning with an Android project in 2019 and a contribution to FirebaseUI-Android that led to a first published technical article. The author describes how writing supported learning, career development, and sharing with the developer community. ### Source excerpt A personal account of my journey as a tech blogger, from my first post in 2019 to becoming a GDE. Insights on English barriers, criticism, and why sharing matters. ## Website refresh DevFeed: [Website refresh]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2024-09-20T00:00:00Z Content type: opinion Language: en Sources: [Jeroen Mols]() Topics: [Website](), [Hugo](), [Jekyll](), [Web Development](), [modern web development](), [Netlify](), [Vercel]() Tags: [blogging](), [blogs](), [development](), [hugo](), [jekyll](), [migrate](), [netlify](), [platform](), [redesign](), [static-site-generator](), [vercel](), [web-development](), [website](), [website-refresh]() ### AI overview A personal account of migrating a seven-year-old Jekyll website to Hugo. It explains the old site's deployment setup and limitations, the motivations for the redesign, and the author's evaluation of static-site generators and hosting options. ### Source excerpt After 7 years, it was time to migrate my old Jekyll website to a new more modern platform. Read on to learn why, how, and what the main challenges were in this process. ## How to Build a Profitable Lifestyle Business without Chasing VC Funding DevFeed: [How to Build a Profitable Lifestyle Business without Chasing VC Funding]() Original publisher: [Read original article]() Author: TheAnkurTyagi Published: 2024-04-19T10:27:39Z Content type: article Language: en Sources: [ByteSizedBets]() Topics: [Search engine optimization (SEO)](), [WordPress](), [Software Engineering]() Tags: [blogging](), [business](), [developer](), [indie-hackers](), [lifestyle](), [seo]() ### AI overview An interview with developer and entrepreneur Sai about building a lifestyle business around Superblog.ai. The article presents an alternative to venture-funded growth and explains how Sai used his blogging and SEO experience to create a blogging platform that handles design, speed, optimization, scale, readability, and related publishing needs. ### Source excerpt Learn How to Dominate B2B SaaS with SEO and the Power of "Build in Public" Strategies. ## Trying Substack as a Simpler Blogging Platform DevFeed: [Trying Substack as a Simpler Blogging Platform]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2023-07-06T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Publishing](), [configuration]() Tags: [blog-post](), [blogging](), [simplicity](), [subscriptions]() ### AI overview Bruce Eckel explains why the ceremony of creating blog posts can discourage him from writing and describes trying Substack as a simpler publishing platform. He likes its clean writing workflow, live preview, email delivery, and subscription-based business model, while noting that he is still adjusting to some limitations. ### Source excerpt TLDR: BruceEckel.substack.com I've noticed that I haven't been writing here that much lately, and I began to suspect it is because of the necessary ceremony of creating a blog post. Which, really, isn't that much but I've started to see that even the smallest amount can be an impediment. When I began trying to paint, I discovered these impediments, and they're different for each person. In my case, the stretched canvas was "too important" and I resisted putting paint on it (both parents grew up in the depression, so I am overly careful about wasting things, which makes experimentation hard). ## The Dark Side of Blogging DevFeed: [The Dark Side of Blogging]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:27.078000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Development](), [Tutorial]() Tags: [advice](), [blog-post](), [blogging]() ### AI overview An opinion article about the downsides of blogging for developers, drawing on the author's experiences and offering advice. It highlights the time required to create, test, edit, and publish quality content, especially when personal circumstances affect writing speed. ### Source excerpt Lately, I've seen multiple excellent posts about why developers should blog. They list very good reasons, and I wholeheartedly agree with them. Blogging is good for many things, it's fun, and you learn a lot during the process. However, there are downsides to blogging as well, especially if you write about controversial topics. This blog post will discuss some of these downsides, tell my own experiences, and share tips on conquering those not-so-great things. I'm writing the tips for myself as advice I would have needed to hear, so they might not all apply to you, but I hope you'll get at least something out of this post! Some Background I started actively blogging about a year ago. My motivator was, at first, to write blog posts 16 weeks in a row to get the 16-weeks badge from Dev.to. I earned the badge, and if you're interested, I wrote a blog post about what I learned from that journey. Blogging is something I like a lot. It has given me a way to construct my thoughts through writing and learn in the process. I already have a good archive of articles I've written. It hasn't been once or twice that I've had the opportunity to refer to one of my blog posts in a conversation. However, as much I like this, there have been downsides as well. And during the past year, I've been struggling with stuff - as I would imagine most of us have because of Covid and all the isolation it causes. I'm also recovering from a brain injury, which makes me prone to fatigue. So these things have significantly slowed my speed of writing, especially in 2021. So, let's have a look at the downsides and some advice! Writing Quality Content Takes Time If you want to write some quality content, it takes time. Suppose you're creating a tutorial of some sort, building the end result, testing it, and writing the blog post. It can take a long time from the start to publishing it. In Dev, I've come across multiple posts that are basically just (short) lists of links. There is time and place for tho ## SoloCoder Podcast: About Coding and Martial Arts DevFeed: [SoloCoder Podcast: About Coding and Martial Arts]() Original publisher: [Read original article]() Published: 2021-03-30T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [coding](), [Programming](), [Learning]() Tags: [blogging](), [coding](), [podcast](), [programming]() ### AI overview A personal account of appearing on the SoloCoder podcast to discuss programming, career development, learning in public, blogging, and connections between coding and martial arts. ### Source excerpt Lorem ipsum dolor sit amet ## An Open Letter to Bob Frankston DevFeed: [An Open Letter to Bob Frankston]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-07T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [RSS Feed](), [RSS]() Tags: [blogging](), [rss]() ### AI overview An open letter urges Bob Frankston to configure his blogging tool to publish full-content RSS feeds instead of summaries. The author argues that requiring readers to click through from aggregators can cause them to miss the full post and notes that full-content feeds are no harder to produce. ### Source excerpt (Photo Credit - Lisa Meece; Thank You) Hi Bob, I strongly doubt you remember but I met you years ago as part of the Boston Blogging group that Dave Winer used to organize. About the same time I also met Dan Bricklin. I wanted to make a suggestion to you. I've been subscribed to you in my aggregator for a long time but due to the design of aggregators, it isn't clear if a post in the aggregator is full content or summary. Here's all I saw of your current (wonderful) CES post: CES is a time to see new products and services. Alas, my expectations might be too high. And here is how this appears in an aggregator: I thought this was just a lament but I happened to click through and lo and below, a wonderful bit of writing. So my suggestion to you is to change your blogging tool to output the full content of each post you write. I'm pretty certain you wrote your own blogging tool and, thus, I know this is possible; you obviously have the skills (and if that isn't the greatest understatement I've made blogging, I don't know what is). My suspicion is that for yourself it is more important that you get your ideas out into the universe than that you drive people to your site. This is the single best reason for a full content feed. Every time you have to rely on someone clicking thru from their aggregator to your site, there is a solid chance (1 in 2; 1 in 3; 1 in 5; 1 in 10 ???) that they just won't). Often times they don't ever know that there is more content out there; I certainly didn't and I've been in the RSS world now for almost 20 years and I have pretty solid credentials in the RSS world - I was the creator of the Feedster RSS and Blog search engine. Note: My own blog and my recipes are all done with full content feeds so I'm not askign you to do anything that I'm not doing. Also full content feeds aren't really any harder than a summary feed - just put out the full content. Feel free to use my feed as an example. Even better - use Dave's. Btw I loved this point: "I mo ## Year in review 2016 DevFeed: [Year in review 2016]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-01-09T00:00:00Z Content type: opinion Language: en Sources: [Jeroen Mols]() Topics: [Android](), [GitHub](), [Google](), [Library](), [Stack Overflow](), [IO](), [Mastodon](), [X (Twitter)]() Tags: [android](), [blogging](), [blogs](), [conference](), [github](), [google](), [io](), [mastodon](), [personal](), [projects](), [retrospective](), [review](), [side-projects](), [speaking](), [stackoverflow](), [year-in-review]() ### AI overview A personal retrospective of 2016 covering family life and the author's technical activities, including blogging, Android conference speaking, open-source work, social-media growth, Google I/O attendance, and side projects. ### Source excerpt It's that time of the year again to do a little personal retrospective. 2016 passed by so quickly! I had a fantastic time playing around with (and taking care of) my wife and daughter. ## Why I moved my blog from WordPress.com to Pelican and GitHub Pages DevFeed: [Why I moved my blog from WordPress.com to Pelican and GitHub Pages]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2015-08-02T18:55:00Z Content type: opinion Language: en Sources: [Andrea Corbellini]() Topics: [migration](), [WordPress](), [Content Management System](), [Vim](), [GitHub]() Tags: [blog](), [blogging](), [github-pages](), [migration](), [pelican](), [static-site](), [static-site-generator](), [version-control](), [vim](), [wordpress]() ### AI overview The author explains moving a blog from WordPress.com to Pelican and GitHub Pages after encountering customization, editor, and workflow limitations. They describe using Vim, MathJax, theme customization, version control, and scripts with the static-site setup, while noting that feed URLs changed and that Pelican lacked a preferred theme. ### Source excerpt Today I switched from WordPress.com to Pelican and GitHub Pages. First off, let me say: almost all URLs that were previously working should still work. Only the feed URLs are broken, and this is not something I can fix. If you were following my blog via a feed reader, you should update to the new feed. Sorry for the inconvenience. Having said that ... ## Using Github Pages for Blogging DevFeed: [Using Github Pages for Blogging]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2014-11-19T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [GitHub Pages](), [Jekyll](), [static-site-generator](), [GitHub](), [Ruby](), [Rails](), [WordPress]() Tags: [blogging](), [github](), [github-pages](), [jekyll](), [rails](), [ruby](), [static-site-generator]() ### AI overview The author discusses moving a programming blog from Artima and evaluates blogging platforms and static-site generators. The article presents Jekyll and GitHub Pages as promising options, while noting personal preferences and trade-offs involving WordPress, Blogger, Ruby, and Python. ### Source excerpt I've wanted to move this programming blog away from Artima for what seems like several years now (Here's an earlier update on the process). My buddy Bill hasn't found developing the blogging platform to be of much interest anymore, and in particular he realizes there are many better alternatives at this point. The conversion took a surprising amount of research, partly because I've been away from blogging technology for quite awhile. ## Discourse as my blogging platform DevFeed: [Discourse as my blogging platform]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2013-10-10T10:44:37Z Content type: article Language: en Sources: [Sam Saffron]() Topics: [Rails](), [Code](), [Digital Ocean](), [Sidekiq](), [GitHub]() Tags: [blogging](), [code](), [digital-ocean](), [email](), [github](), [integration](), [plugin](), [rails](), [sidekiq]() ### AI overview The author describes moving a blog into Discourse by building a Discourse plugin with Rails engines. The post also discusses hosting on DigitalOcean and experimenting with Rails, Unicorn, Rack Hijack, Sidekiq, and email integration. ### Source excerpt This Blog has gone through several incarnations. When I started blogging I used subtext. Then I decided it was time to reinvent wheels and rolled my own, hodge-podge, blogging solution. It worked ok, but I found I had extreme difficulty engaging with the community. People would leave replies and I had no idea if they ever got my response. Further more creating content was becoming a huge pain. I ended up using the Discourse editor for some posts and then pasting the body of the post here. Crazytown. So I had this idea, what if I could have Discourse turtles all the way down. I took some time to extend our plugin story and using the magic of Rails engines managed to host my blog inside Discourse. You can see the full source code of this blog as a Discourse plugin at: GitHub - SamSaffron/blog: samsaffron.com blog plugin for Discourse I am hosted on Digital Ocean (a 2GB instance). I am also experimenting with some less traditional Discourse configs: I am running Rails 4 I am running unicorn, with Rack Hijack to handle long polling I am running no bluepill, I tricked unicorn into daemonizing sidekiq and use an upstart job. Let's see how it goes. All of this and more deserves a much more detailed blog post. Before any of this, let me address the elephant in the room. Commenting on this blog just became way more complicated. I plan to address that, in a future update, this is a temporary state. I want to bring back the traditional commenting box. That said, I have email integration set up, so now when I respond to you, you will get an email you can respond to. You will not even need to visit this site to spam my blog Overall, I am super excited about this. It pushes the limits of what can be done with Discourse and leaves breadcrumbs for others to follow. More to come, now that blogging became so much easier. ## Finishing my Blog Relocation DevFeed: [Finishing my Blog Relocation]() Original publisher: [Read original article]() Published: 2012-09-26T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [Jekyll](), [GitHub](), [Development](), [RSS Feed]() Tags: [blog](), [blogging](), [github](), [jekyll](), [rss]() ### AI overview The author announces the relocation of a six-year-old blog from blog.js-development.com to juristr.com. The blog was migrated from Blogger to GitHub-hosted Jekyll to provide more flexibility, licensing control, and source-controlled static files. ### Source excerpt Lorem ipsum dolor sit amet ## Web browser, frontend and standards feeds to follow DevFeed: [Web browser, frontend and standards feeds to follow]() Original publisher: [Read original article]() Author: Paul Irish Published: 2011-11-22T03:57:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [Front end](), [frontend development](), [browser](), [Web](), [JavaScript](), [GitHub]() Tags: [blog](), [blogging](), [browser](), [development](), [frontend](), [frontend-development](), [github](), [javascript](), [news-reader](), [standards](), [web]() ### AI overview A curated collection of frontend development, web standards, browser news, and large web application feeds, organized into downloadable OPML bundles for import into a news reader. The article also encourages durable blogging and recommends several weekly newsletters. ### Source excerpt While a lot of conversation has moved to twitter and G+, hugely useful information is still published regularly to blogs. I've shared collections of frontend development feeds twice before. Now I'm back, but with three choices: Download this: frontend-feeds.opml 2013.07.26: Poor Reader. :'( Here are the three below bundles grouped up into an OPML file. Your new news reader can import them in one go. Also, do not forget the most important site that has no feed: webplatformdaily.org. It's the best thing. (2013.09.12: It has a feed now! Added) 2013.09.12: The OPML is now on Github Frontend development exploration, techniques, tips. Lots of JavaScript. 275 feeds. Standards development and browser dev news. 56 feeds. Blogs focusing on building large webapps (new!) 22 feeds. Also, a short commentary on blogging vs tweeting.. while a lot of people have changed to twitter+jsfiddle only, tweets are not available via search after 30 days, so if you expect anything you share to last, blog it for real. :) 2011.12.02: Adding newsletters! 2012.08.09: Refreshed all the bundles. Added the frontend-webapps feed. Also please subscribe to these guys which do a great job of highlighting the top stories of the week: JavaScript Weekly Web Design Weekly HTML5 Weekly 2013.07: Added opml. ## Emacs Muse powered blog DevFeed: [Emacs Muse powered blog]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2008-12-04T23:00:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [Software]() Tags: [blog](), [blogging](), [emacs](), [muse](), [software]() ### AI overview A brief note about a blog powered by Emacs Muse and blogging software for geeks. ### Source excerpt So finaly a blogging software for geeks exists? The problem with communication is that you think it happened.