# Jamie Tanna

Recent content in articles on Jamie Tanna | Software Engineer

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Posting syntax-highlighted code snippets in your Slack messages (without 'snippets')

DevFeed: [Posting syntax-highlighted code snippets in your Slack messages (without 'snippets')](<https://devfeed.tech/articles/posting-syntax-highlighted-code-snippets-in-your-slack-messages-without-snippets-136550.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/11/16/slack-syntax-highlight/>)

Author: Jamie Tanna

Published: 2026-11-16T08:50:04Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Syntax Highlighting](<https://devfeed.tech/topics/syntax-highlighting.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>)

Tags: [block](<https://devfeed.tech/tags/block.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [code](<https://devfeed.tech/tags/code.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [messages](<https://devfeed.tech/tags/messages.md>), [slack](<https://devfeed.tech/tags/slack.md>), [syntax-highlighting](<https://devfeed.tech/tags/syntax-highlighting.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

Slack client 4.51.x can render syntax-highlighted code inline in a message without a Slack snippet or Block Kit: paste Markdown containing a fenced code block with a language label, such as ```typescript```, into the message editor. The author says typing the fenced block directly into the editor does not produce the highlighted rendering. They also note that this reduces the need for their md2slack tool for code, though they may still use it for tables. The behavior is reported as tested on Slack 4.51.x.

### Source excerpt

As I've written before, I quite like nicely rendered Slack mesages, which include full syntax highlighting of code snippets. There was a discussion on reddit last night which brought this up again, which made me think about splitting this specific knowledge into a separate post, so it's more discoverable. As I was preparing this, I found that Slack already supports posting syntax highlighted code snippets, but it's not super obvious 👀 To be clear, I'm not talking about using a "snippet", but the result of this gives you the syntax highlighted code snippet as a fully inline part of your message. For instance, we want this sort of output: I'd previously found that you needed to use the Slack Block Kit to get this rich rendering, but as I was looking at it this morning, I found that actually you don't even need that - Slack (at least as of client (4.51.x) supports it natively! To get the above text, you can take this input: Via https://learnxinyminutes.com/typescript: ```typescript // Functions can accept more than one type function f6(i: string | number): void { console.log("The value was " + i); } // Interfaces are structural, anything that has the properties is compliant with // the interface interface Person { name: string; // Optional properties, marked with a "?" age?: number; // And of course functions move(): void; } ``` And some plain code blocks: ``` This isn't syntax highlighted ``` And paste it into the message box: Now, the important thing to note is that this requires you to paste this Markdown into the editor, you can't actually write: ```typescript To get a TypeScript-highlighted code snippet. Knowing that it's possible to do this more straightforwardly means that maybe I don't need my md2slack tool as much, at least until I want to be pasting tables into Slack. I've tested this with Slack 4.51.x.

## Week Notes 26#46

DevFeed: [Week Notes 26#46](<https://devfeed.tech/articles/week-notes-26-46-134654.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/46/>)

Author: Jamie Tanna

Published: 2026-11-15T21:01:51Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [timezone](<https://devfeed.tech/topics/timezone.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apex](<https://devfeed.tech/tags/apex.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [comedy](<https://devfeed.tech/tags/comedy.md>), [driving](<https://devfeed.tech/tags/driving.md>), [family](<https://devfeed.tech/tags/family.md>), [freezer](<https://devfeed.tech/tags/freezer.md>), [github](<https://devfeed.tech/tags/github.md>), [godzilla](<https://devfeed.tech/tags/godzilla.md>), [infra](<https://devfeed.tech/tags/infra.md>), [linkedin](<https://devfeed.tech/tags/linkedin.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [storm](<https://devfeed.tech/tags/storm.md>), [tax-return](<https://devfeed.tech/tags/tax-return.md>), [ted](<https://devfeed.tech/tags/ted.md>), [timezone](<https://devfeed.tech/tags/timezone.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>), [wildcard](<https://devfeed.tech/tags/wildcard.md>)

### AI overview

A long week included comedy shows, family time, and progress on a self-assessment tax return. The author also described recent blog and infrastructure changes: improving the GitHub logo's contrast in posts, stopping SVG syndication to LinkedIn because it does not support them, fixing redirects, and making `tz` configurable instead of hard-coding timezone options. In Apex Legends, the new Godzilla mode was enjoyable, with Storm Point's scale and verticality highlighted in Wildcard. The author watched The Expanse (Season 5), Ghosts (Seasons 1 and 2), Nobody Wants This (Season 3), and In the Grey (2026).

### Source excerpt

A bit of a long week 🥱 Got the new freezer delivered - but not yet got it all set up and ready - but at least now we're able to get our Christmas Cook delivery in a couple of weeks A good week for comedy: Was a fun, chaotic night on Monday at Sam Campbell Also a fun time at Fatiha El-Ghorri on Wednesday Discovered the very funny Craig Simons - very good tribute! Wrote about my new theme, and some of the changes I've done recently, as well as this week: Improving the contrast for the GitHub logo on blog posts I post Not syndicating SVGs to LinkedIn, as they aren't supported Fixing up some redirects + improving things on my infra Made tz configurable, instead of baking timezone options into the tool Ended up missing the green bin collection, clearing out the vegetable draw 😬 Had a lovely day today seeing my sister and family It was a bit of a day of driving but worth it 🥰 Breaking Change is a perfect podcast to listen for long drives - Justin's great! Did most of my self-assessment tax return, and not happy with the numbers 😅 Playing: (No Blue Prince) Kingshot (per usual) Apex Legends The new Godzilla mode is very fun, and the scale + verticality in Storm Point is excellent in Wildcard Watched: The Expanse (Season 5) (No Ted Lasso (Season 4)) Ghosts (Season 1) Finding some of the storylines second hand stressful - wouldn't want to ?? Ghosts (Season 2) Nobody Wants This (Season 3) In the Grey (2026)

## New CSS, Who Dis? (2026 edition)

DevFeed: [New CSS, Who Dis? (2026 edition)](<https://devfeed.tech/articles/new-css-who-dis-2026-edition-124750.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/11/09/new-css-who-dis/>)

Author: Jamie Tanna

Published: 2026-11-09T18:00:01Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Hugo](<https://devfeed.tech/topics/hugo.md>), [static-site-generator](<https://devfeed.tech/topics/static-site-generator.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai](<https://devfeed.tech/tags/ai.md>), [build](<https://devfeed.tech/tags/build.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [css](<https://devfeed.tech/tags/css.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [indieweb](<https://devfeed.tech/tags/indieweb.md>), [llm](<https://devfeed.tech/tags/llm.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [neovim](<https://devfeed.tech/tags/neovim.md>), [personal-website](<https://devfeed.tech/tags/personal-website.md>), [site](<https://devfeed.tech/tags/site.md>), [static](<https://devfeed.tech/tags/static.md>), [static-site](<https://devfeed.tech/tags/static-site.md>), [want](<https://devfeed.tech/tags/want.md>), [website](<https://devfeed.tech/tags/website.md>), [www-jvt-me](<https://devfeed.tech/tags/www-jvt-me.md>)

### AI overview

The author refreshed the site's design and accessibility while deciding to keep it on Hugo: writing Markdown locally in Neovim and avoiding a dynamic site fit their preferences. Changes include social-media-style IndieWeb feeds, narrower content and larger text, improved contrast, step-count views, and a redesigned popular-posts page with an RSS feed. They removed a poorly readable, less useful post-frequency page. After rewriting the Micropub endpoint in Go and upgrading Hugo from v0.101.0 to v0.168.0, plus changing Git metadata handling, pagination, CI runners, and generated pages, reported build time fell from about four minutes to one minute and deployment time from about nine minutes total to two; deployment uploads dropped from 2,660 files (223 MB) to 12 (877 kB). Other work includes CloudFront caching and function changes, moving media storage from Netlify to S3 and CloudFront, and adding standard.site metadata support, which still requires manual post updates and does not suggest the site as a publication. Claude Code helped with code migration and implementation; the author says they will continue writing their own blog content.

### Source excerpt

In the last couple of weeks, I've been making some changes to my website (with help from Claude Code) to make some improvements to my site's look + feel, as well as some accessibility improvements. The last time I did a significant change on my site was in mid-2024, and I'd noted that: In recent years I've been deprioritising my personal website (and the many IndieWeb-y things I want to do with it), both because I have far too many other projects as well as life stuff, and far too many hours in the day. This also hasn't been helped by the fact that my site takes an age to build. Over the weekend I did a significant upgrade from an ~8 year old SSD to a new M.2 SSD, and my site still takes ~104 seconds to build. Hugo's known to be blazing fast, so if even that struggles with my site, I know I'm in trouble. [...] I've thought over the last couple of years that "I won't invest any time in my personal site, as I'll rebuild it soon", as I've wanted to migrate from a static site to a dynamic site. But that's never made it up the very long TODO list, so I thought that I should make some minor tweaks over the weekend, which are live as of this post landing. I'm, unfortunately, a long way from being able to prioritise doing a rebuild of my website - and if I'm honest, I'm not sure I will be doing it even if I had the time. I'm finding that actually I much prefer writing Markdown in my Neovim, instead of in one of the various Micropub editors I could be using, and having the ability to run my site with all my content locally is a nicer experience. Also, I don't particularly want something dynamic, which is then vulnerable to gestures wildly at the state of CVEs right now. With that in mind, I'm going to be sticking with my Hugo site for some time, so needed to make some much-needed improvements to both the user-facing site, as well as making it easier for me to maintain. Putting the Social Media in the IndieWeb# One of the things I've loved about having an IndieWeb site is tha

## Week Notes 26#45

DevFeed: [Week Notes 26#45](<https://devfeed.tech/articles/week-notes-26-45-122691.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/45/>)

Author: Jamie Tanna

Published: 2026-11-08T21:18:46Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Website](<https://devfeed.tech/topics/website.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amp](<https://devfeed.tech/tags/amp.md>), [apex](<https://devfeed.tech/tags/apex.md>), [diwali](<https://devfeed.tech/tags/diwali.md>), [featured](<https://devfeed.tech/tags/featured.md>), [halloween](<https://devfeed.tech/tags/halloween.md>), [music](<https://devfeed.tech/tags/music.md>), [notes](<https://devfeed.tech/tags/notes.md>), [posts](<https://devfeed.tech/tags/posts.md>), [prince](<https://devfeed.tech/tags/prince.md>), [products](<https://devfeed.tech/tags/products.md>), [reading](<https://devfeed.tech/tags/reading.md>), [series](<https://devfeed.tech/tags/series.md>), [ted](<https://devfeed.tech/tags/ted.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [up](<https://devfeed.tech/tags/up.md>), [us](<https://devfeed.tech/tags/us.md>), [website](<https://devfeed.tech/tags/website.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>), [writing](<https://devfeed.tech/tags/writing.md>)

### AI overview

The author made further tweaks to their website and wrote posts about setting up Pushover with Amp and `/copy` changes, though a longer post about the site updates remains unfinished. They missed the first Scrutineer community call because its email landed in spam, and noted being featured on Typescript.fm. The week also included a Diwali visit with family, time at Eden Hall, and fireworks that kept Cookie and Morph hiding in the living room. They mention receiving many emails about AI-related products after recent posts. They played Kingshot and Apex Legends, read The Sins of Our Fathers, and watched several shows and films, including The Expanse season 5, Furiosa, and The Celebrity Traitors.

### Source excerpt

Some more good tweaks to my website - feeling pretty happy with the current state of things! I've got a partly written post talking about all the changes, but haven't quite been able to get it finished this weekend as I've not had a lot of spare headspace to do it Was nice to see Mum and Dad for Diwali - we had a nice walk at Bestwood and then lunch at Mowgli 😋 It's been a pretty sucky few days with all the fireworks, but Cookie and Morph have been brave and been OK in the living room hiding from it Missed the first Scrutineer community call, unfortunately, as it landed in my spam! Was nice to be featured in Typescript.fm While doing some bits at Anna's house, Cookie started doing a bit of gremlin'ing on the grass, and then ended up having some particularly big zoomies - I wondered if she was trying to get a comfy place to sit while we were doing the ivy Had a lovely day at Eden Hall on Friday 💆🏼 which was very much needed after a busy few weeks, and it's always so lovely there I gave Morph a bit of milk from my bowl post breakfast and then he became an absolute fiend, constantly hunting for the bowls, including later that day Wrote a couple of posts this week - getting Pushover + Amp set up together and my /copy tweaks Been getting a lot of emails about AI-y products after a few of my recent posts, which hasn't been the best Playing: (No Blue Prince) Kingshot (per usual) Apex Legends Reading: The Sins of Our Fathers Watched: The Expanse (Season 5) Taskmaster (Series 22) Furiosa: A Mad Max Saga (2024) The Celebrity Traitors (Series 1) Some great music choices in that series! The Celebrity Traitors: Uncloaked (Series 1) (No Ted Lasso (Season 4)) Ghosts (US) (Season 1) The US version, on in the background while I'm writing these Ghosts (Season 1) Last One Laughing UK: Halloween (Series 1)

## Avoiding being a Meat Proxy with Claude Code Mods

DevFeed: [Avoiding being a Meat Proxy with Claude Code Mods](<https://devfeed.tech/articles/avoiding-being-a-meat-proxy-with-claude-code-mods-116425.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/11/03/honest-claude-meatproxy/>)

Author: Jamie Tanna

Published: 2026-11-03T17:25:05Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [generative-ai-tools](<https://devfeed.tech/topics/generative-ai-tools.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [llm](<https://devfeed.tech/tags/llm.md>)

### AI overview

The author automates attribution of copied LLM replies with a Claude Code Mod that intercepts `/copy`, preserving the existing command instead of requiring a new skill. The handler accepts an optional positive integer (`/copy [N]`, defaulting to the latest reply), selects the Nth nonempty assistant message from the session, and wraps its text in a Markdown block prefixed with the session's model name. It returns usage or missing-reply messages for invalid or unavailable selections, and reports copy success or the failure reason. The author says this automatically inserts the attribution and is more convenient for their repeated use.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 I'm very much not a fan of people being meat proxies and pasting AI-generated output to each other, least of all me. It's super frustrating to read it, and feels wasteful of my time, as well as anyone else in the conversation, who are having to unpack the verbose text for what is actually being communicated. That rant aside, sometimes I want to copy some text from an LLM, or sometimes you do need to reply to someone based on what an LLM has given you - sometimes it's passive aggressive, but sometimes it's actually needed - although I'd still recommend some edits + rewords. As someone who's very careful about attributing my use of LLM-derived code, as well as on this blog, I'm also very conscious of the source of the text I share in chat messages, so want to make sure I attribute the model that's come up with the words I'm parroting. This results in me writing something like: Via Claude Sonnet 5.5: ```markdown {... response from agent goes here ...} ``` I've ended up repeating this one too many time recently that I decided to look at how I could automate this. I didn't really want to introduce a new /copy-with-model skill, and require that my muscle memory changing, as I wanted to be able to continue /copying if possible. I remember hearing about Claude Code's Mods system which was recently added, and wondered if this may help out here. It turns out, yes, it's fairly straightforward to create a Mod to intercept the /copy and add extra info into it 👏🏼 import type { Register } from "claude-code"; export const register: Register = (on) => { on("command.run", { command: "copy" }, async ($, e) => { const arg = e.args.trim(); const n = arg === "" ? 1 : Number(arg); if (!Number.isInteger(n) || n < 1) { return { text: `Usage: /copy [N] where N is 1 (latest), 2, 3, ... Got: ${arg}` }; } const messages = await $.session.messages(); const replies = messages.filter((m) => m.role === "assistant" && m.text !== ""); const reply = replie

## Adding Pushover notifications to Amp

DevFeed: [Adding Pushover notifications to Amp](<https://devfeed.tech/articles/adding-pushover-notifications-to-amp-116424.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/11/03/amp-pushover/>)

Author: Jamie Tanna

Published: 2026-11-03T13:58:49Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [notifications](<https://devfeed.tech/topics/notifications.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [generative-ai-tools](<https://devfeed.tech/topics/generative-ai-tools.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amp](<https://devfeed.tech/tags/amp.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude-opus-5-5](<https://devfeed.tech/tags/claude-opus-5-5.md>), [llm](<https://devfeed.tech/tags/llm.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

The author built a small Amp TypeScript plugin to send Pushover notifications on `agent.end`, so they can tell when a session is waiting for input. Amp's plugins avoid the wrapper CLI they had considered extending from `claude-hook`, but provide less contextual information from the Thread. The excerpt ends before describing the notification's contents or setup.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 I've recently been using Amp a bit more, given you can now use your Claude subscription with it. In a similar vein to Adding Pushover notifications to Claude Code, I've been wanting to get notified when a given session is waiting for input. Although I wrote a very small CLI, claude-hook which I'd wondered about extending for Amp's usage, I found that Amp's Typescript-based plugins are much more powerful, and avoid me needing to create a wrapper CLI, even though I'd hoped to keep the codebase the same across different agent tools. (While, at the same time, not getting as much contextual information out of the Thread, which is a bit annoying) I partially wrote, and then had Amp + Claude Opus 5.5 fix up, this small Amp Plugin to notify me on agent.end. This then shows me i.e.

## Week Notes 26#44

DevFeed: [Week Notes 26#44](<https://devfeed.tech/articles/week-notes-26-44-111698.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/44/>)

Author: Jamie Tanna

Published: 2026-11-01T21:08:28Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [caching](<https://devfeed.tech/tags/caching.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [cat](<https://devfeed.tech/tags/cat.md>), [ci](<https://devfeed.tech/tags/ci.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [halloween](<https://devfeed.tech/tags/halloween.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [iac](<https://devfeed.tech/tags/iac.md>), [infra](<https://devfeed.tech/tags/infra.md>), [lambda-edge](<https://devfeed.tech/tags/lambda-edge.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [node](<https://devfeed.tech/tags/node.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [pagination](<https://devfeed.tech/tags/pagination.md>), [pizza](<https://devfeed.tech/tags/pizza.md>), [readability](<https://devfeed.tech/tags/readability.md>), [scraping](<https://devfeed.tech/tags/scraping.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

The author made a substantial site and infrastructure refresh after upgrading Hugo from 0.101.0 to 0.168.0. Changes included using `lastmod` instead of `.GitInfo`, date-based pagination, readability tweaks, a calendar view, infrastructure as code, and revised CloudFront caching that saves about 1-2 GB of transfer per day. With larger CI runners, build and deploy time fell from about nine minutes to 3.5 minutes. The post also notes a roughly one-minute outage after a Node upgrade exposed needed Lambda@Edge code changes, and delayed releases of a reporting plugin due to Maven Central publishing limits. The supplied text is an excerpt from week notes that also covers personal activities and media.

### Source excerpt

Been nice to get back to doing some things on my site again, which has been a busy week (with thanks to Claude Code for helping actually get some of this stuff done) Upgraded from Hugo 0.101.0 (2022-06-16) to Hugo 0.168.0 (2026-10-13) Made some tweaks to my site for readability - hopefully some of them are quite noticeable! After the Hugo upgrade, I then removed .GitInfo from Hugo (so each post now uses lastmod), which wasn't possible until I moved into my Micropub endpoint over to my rewrite I've finally got to date-based pagination, which is now much nicer - and saves on unnecessary changes on my site With that all done - and increasing the CI runners' sizes - I've managed to bring this down to ~3.5m/build+deploy down from ~9m! I've made some much-needed tweaks to my CloudFront caching, ending up saving ~1-2GB/day worth of transfer Added a calendar view i.e. on my Week Notes or for my main feed / for articles, which is cool Ended up IAC'ing up my site infra which has been ClickOps until now p🫣 Set up my standard.site metadata (thanks to Bridgy Fed) but given it needs a manual update to a post to link back to the at:// I did end up breaking my site for ~1 minute earlier in the week when I did a Node upgrade on my Lambda@Edge, but didn't realise my Lambda code wouldn't run (as code changes were needed) 🫣 Cookie enjoyed me moving her overnight bed into my office so she could be much comfier when she's in my office 🥰 Been trying to investigate how I've been getting notifications from Claude Code, when my work machine has had no instances running - turns out it was on my desktop, but I'd not updated the Pushover creds or the claude-hook binary 🫣 Morph is coming a real cat - wanting to go in and out and in and out 😹 It was Halloween this week, but thankfully no knocking (as we had our lights off), and not many fireworks I've had some somewhat significant scraping of my site Had a nice pizza night - and the Biscoff cheesecake was back, which is so so good 😋 Had a nice wa

## Thirteen backlogs in a trenchcoat: Analysing Renovate's many requests

DevFeed: [Thirteen backlogs in a trenchcoat: Analysing Renovate's many requests](<https://devfeed.tech/articles/thirteen-backlogs-in-a-trenchcoat-analysing-renovate-s-many-requests-109802.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/30/renovate-buckets/>)

Author: Jamie Tanna

Published: 2026-10-30T17:45:56Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [renovate](<https://devfeed.tech/topics/renovate.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [request management](<https://devfeed.tech/topics/request-management.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2019](<https://devfeed.tech/tags/2019.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [contribution](<https://devfeed.tech/tags/contribution.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [cycle-time](<https://devfeed.tech/tags/cycle-time.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [features](<https://devfeed.tech/tags/features.md>), [lead](<https://devfeed.tech/tags/lead.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mend](<https://devfeed.tech/tags/mend.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [process](<https://devfeed.tech/tags/process.md>), [product](<https://devfeed.tech/tags/product.md>), [project](<https://devfeed.tech/tags/project.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [sources](<https://devfeed.tech/tags/sources.md>), [story](<https://devfeed.tech/tags/story.md>)

### AI overview

Renovate's large workload comprises 13 distinct backlogs, so its maintainers plan to use clearer categories to prioritize incoming work. They classified requests by areas such as ecosystem support, workflow fit, bugs, security, performance, documentation, and dependency updates, alongside cross-cutting labels for rough edges, audience, and customer interest. The analysis found strong user demand for deeper ecosystem integrations and workflow fit, more community bug-fix contributions, and rising supply-chain-security requests. Community PRs have grown, with self-reported figures suggesting much of the recent increase involved substantive AI use; review response times have also slowed as the small team handles more work. Going forward, the project expects to favor reproducible bugs, rough edges, and customer requests, while acknowledging that its prioritization approach is still being refined.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 In 2019, I saw a talk called Building and Growing an Agile Team by Tom Hoyland, which has probably been one of the most impactful talks I've attended in my career. In the talk, Tom talks about how he worked with a team to build them into a high-performing team, which, among other things, involved measuring things like "cycle time", improving the way the team's deployment process worked by doing it for every story, and by discovering the sources of work coming into the team. In the latter case, by understanding the sources of work the team was being given, the team could then have full visibility into their different backlogs, which had always been present, but maybe not clearly thought of as a backlog, and make better choices going forwards. This is something that I've internalised quite deeply over the years, and have used to build teams that enjoyed working together across several companies. Most recently, this talk has come up as I've been thinking about how the Renovate project has quite a large backlog of work, in part due to increased contribution over the last ~18 months due to AI. As the Project Lead, I've been thinking about how we can approach this better in the future, and decided that one step towards this is to map out the different "backlogs" that we have as a project. This exercise will help us understand more generally what sources of work we have to help us better prioritise the existing backlog alongside new requests that come in. A brief summary of the project For those that don't know, Renovate is the excellent dependency update tool that's always been Open Source and very much open to contributions + extensions. I've been an avid user for years, and prior to joining Mend to work on Renovate last year, I'd been waxing lyrical about Why I recommend Renovate over any other dependency update tools which holds true to today - or maybe even more so, given the features we've been shipping ever since. Reno

## Creating a Typescript union, while also having runtime access to the values

DevFeed: [Creating a Typescript union, while also having runtime access to the values](<https://devfeed.tech/articles/creating-a-typescript-union-while-also-having-runtime-access-to-the-values-106007.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/28/typescript-const-array/>)

Author: Jamie Tanna

Published: 2026-10-28T12:17:12Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [union types](<https://devfeed.tech/topics/union-types.md>), [data type](<https://devfeed.tech/topics/data-type.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [example](<https://devfeed.tech/tags/example.md>), [forgejo](<https://devfeed.tech/tags/forgejo.md>), [function](<https://devfeed.tech/tags/function.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [important](<https://devfeed.tech/tags/important.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [reference](<https://devfeed.tech/tags/reference.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [union](<https://devfeed.tech/tags/union.md>), [values](<https://devfeed.tech/tags/values.md>)

### AI overview

A TypeScript string union constrains values at compile time, but does not provide a runtime list to iterate over or use when generating documentation. The excerpt shows defining the values once in an array with `as const`, then deriving the union type as `(typeof Platforms)[number]`. This makes the values available at runtime while retaining the `Platform` type for function parameters. The example uses `github`, `gitlab` and `forgejo`; the excerpt does not elaborate on other approaches.

### Source excerpt

I very regularly end up writing this pattern - primarily in Renovate's code - so thought I'd write it up as a form of blogumentation, so I can refer back to it in the future. (This example uses concepts from the Renovate codebase, but does not take any code from it) For instance, let's say that you have a known union of big Git-hosting platforms - github, gitlab and forgejo. If you wanted to make sure that a given function parameter could only include them, you'd write i.e. export type Platform = 'github' | 'gitlab' | 'forgejo'; Normally this would be sufficient for usage, and nothing else is needed. But if you then want to be able to reference the ?? - for instance, as part of generating documentation - then you need some way of accessing each of these values at runtime. This leads us to: export const Platforms = [ 'github', 'gitlab', 'forgejo', // no shade to other platforms ] as const; // `as const` is important! export type Platform = (typeof Platforms)[number]; Now, you can access Platforms at runtime (and loop through them), while also enforcing the use of Platform as a function parameter.

## Adding date-based pagination to my site

DevFeed: [Adding date-based pagination to my site](<https://devfeed.tech/articles/adding-date-based-pagination-to-my-site-106006.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/28/date-based-pagination/>)

Author: Jamie Tanna

Published: 2026-10-28T08:36:51Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Hugo](<https://devfeed.tech/topics/hugo.md>), [static-site-generator](<https://devfeed.tech/topics/static-site-generator.md>)

Tags: [adapters](<https://devfeed.tech/tags/adapters.md>), [aws](<https://devfeed.tech/tags/aws.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [claude-opus-5-5](<https://devfeed.tech/tags/claude-opus-5-5.md>), [content](<https://devfeed.tech/tags/content.md>), [hugo](<https://devfeed.tech/tags/hugo.md>), [indieweb](<https://devfeed.tech/tags/indieweb.md>), [operational](<https://devfeed.tech/tags/operational.md>), [pagination](<https://devfeed.tech/tags/pagination.md>), [s3](<https://devfeed.tech/tags/s3.md>), [www-jvt-me](<https://devfeed.tech/tags/www-jvt-me.md>)

### AI overview

Date-based pagination in Hugo makes it possible to browse posts by month, such as visiting `/posts/2026/10/` to see October entries. For a site with roughly 46,000 mixed IndieWeb posts, the author says ordinary paginated feeds can shift on each new post and trigger rebuilds of potentially about 1 GB of HTML for deployment to AWS S3. The author says Hugo Content Adapters made date-based pagination possible and also enabled a heatmap-like calendar of posting frequency, with further tweaks still planned.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 Something I've long wanted is the ability to paginate this Hugo website's pages by day. Given this is an IndieWeb website, I post a mix of content from articles, likes of others' posts and my daily step counts, totalling roughly 46000 posts. Although this may make it easier to browse, it's also an operational want - every time I post something new, each of the feeds on my site that are paginated will move forward one entry, leading to effectively all of my feed pages re-building, leading to potentially ~1GB of HTML re-building and deploying up to AWS S3, which is not ideal! Additionally, having date-based pagination allows someone to "URL hack", by i.e. taking this blog post's URL, https://www.jvt.me/posts/2026/10/28/date-based-pagination/, and browsing to /posts/2026/10/ to see what I've written in October. This is something I've wanted as early as 2020, but has been an ask since 2014 upstream, but thankfully it's now possible using Content Adapters. This also allowed me to get Claude Opus 5.5 to create a heatmap-ish calendar for how frequently posts exist i.e. from my home page: Hopefully this is useful - I've still got some tweaks to do, and feedback welcome!

## Week Notes 26#43

DevFeed: [Week Notes 26#43](<https://devfeed.tech/articles/week-notes-26-43-100138.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/43/>)

Author: Jamie Tanna

Published: 2026-10-25T21:29:00Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [ai-experiments](<https://devfeed.tech/topics/ai-experiments.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [apt](<https://devfeed.tech/tags/apt.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [cv](<https://devfeed.tech/tags/cv.md>), [cve](<https://devfeed.tech/tags/cve.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [github](<https://devfeed.tech/tags/github.md>), [hope](<https://devfeed.tech/tags/hope.md>), [museum](<https://devfeed.tech/tags/museum.md>), [sleep](<https://devfeed.tech/tags/sleep.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [utc](<https://devfeed.tech/tags/utc.md>), [vibecoding](<https://devfeed.tech/tags/vibecoding.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The author's week combined security and maintenance work with renewed site contributions and personal updates. They followed the eMudhra certificate compromise and a PHP CVE, tracked Chainguard's early embargo break, and repeatedly ran `sudo apt update && sudo apt upgrade` on a Matomo deployment. They also worked on their site and Micropub endpoint, plan to be more explicit about AI use, updated their CV, and are drafting posts about backlogs and AI productivity. The post also recounts time with family, storm debris, and current reading, games, and shows.

### Source excerpt

A busy work week with: The eMudhra certificate compromise The PHP CVE Was wild keeping on top of the situtation with Chainguard breaking the embargo early, but I'd prefer to avoid saying anything too much about it publicly Spent a lot of Wednesday afternoon re-running sudo apt update && sudo apt upgrade repeatedly on my Matomo deployment And helping a friend with a site of theirs Morph's been truffling on my big fleece - thinking it's a nice blanket - which has been very cute Seems to have been one of those weeks where I'm dreaming a lot - some mostly positive dreams Was nice to get another hour's sleep last night, and being back to easier timings with us being UTC again Been nice to do a few bits on my site (and my Micropub endpoint) now I'm a bit more able to contribute to it again Being a bit more explicit with my AI usage is something I've been meaning to do - as I mostly have the metadata already - but given the reactions on Lobsters to the vibecoding tag (and some folks vocally leaving) I thought I'd be super explicit about it Did one of my regularly scheduled "update my CV" spurts - it's something I regularly recommend y'all should do Part way through a couple of blog posts, which I hope to finish in the next couple of days: Three backlogs in a trenchcoat Am I more productive using AI? Had a nice weekend with Sarah and the niblings In particular, we had a nice mosey around Wollaton Hall yesterday (the museum is so interesting) and a 😋 roast at The Railway today Stormy this weekend, so lots of (fairly minimal) debris in roads and police cars racing around Completed the GitHub Secure Fund (🤞🏼) this week Playing: (No Blue Prince) Kingshot (per usual) Apex Legends Reading: The Sins of Our Fathers Watched: The Expanse (Season 5) (Not yet: Taskmaster (Series 22)) (No Furiosa: A Mad Max Saga (2024)) The Celebrity Traitors (Series 2) The Celebrity Traitors: Uncloaked (Series 2) Ted Lasso (Season 4) Saturday Night Live (on YouTube) Saturday Night Live UK (on YouTube)

## Lukewarm recommendations for improving AI agents' interactions with your projects

DevFeed: [Lukewarm recommendations for improving AI agents' interactions with your projects](<https://devfeed.tech/articles/lukewarm-recommendations-for-improving-ai-agents-interactions-with-your-projects-100137.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/25/renovate-agent-improvements/>)

Author: Jamie Tanna

Published: 2026-10-25T17:25:54Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [context-architecture](<https://devfeed.tech/topics/context-architecture.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [bestpractice](<https://devfeed.tech/topics/bestpractice.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude](<https://devfeed.tech/tags/claude.md>), [code](<https://devfeed.tech/tags/code.md>), [code-style](<https://devfeed.tech/tags/code-style.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [development](<https://devfeed.tech/tags/development.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [llm](<https://devfeed.tech/tags/llm.md>), [projects](<https://devfeed.tech/tags/projects.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [standard](<https://devfeed.tech/tags/standard.md>), [standards](<https://devfeed.tech/tags/standards.md>), [structure](<https://devfeed.tech/tags/structure.md>), [style](<https://devfeed.tech/tags/style.md>), [things](<https://devfeed.tech/tags/things.md>)

### AI overview

Renovate found that a predictable codebase and contributor documentation helped agents produce mostly technically correct code even before AI-specific changes. The author recommends keeping AGENTS.md or CLAUDE.md brief and directing agents to fuller development standards; providing a single `check` command for CI-like checks, including selected-file and no-test modes; and using a Claude Code `Stop` hook to require checks before an agent finishes. Common review complaints can be encoded as lint rules. Renovate uses `mise` and a Claude Code `PreToolUse` hook to steer agents toward required tools such as pnpm and Vitest; cloud agents then need less preinstalled software. The author also reports better results by having Claude Sonnet review and improve code produced by Amp's Claude Opus, at the cost of more tokens. These practices are presented as useful to human contributors as well as agents.

### Source excerpt

Over the last week I've been chatting with some folks who are looking at integrating AI more into their development work. I shared a couple of things that we've found have worked well for Renovate, as a codebase that takes a lot of human (and since mid-last year, AI) contributions. Although I've written about this a bit in my reflection on the last year, this naturally deserves its own blogumentation. Before we did anything to explicitly optimise the codebase for AI agents, we ended up finding that we'd - for the most part - receive fairly technically correct code, although it wouldn't necessarily fit in the areas that it was added for, or wouldn't completely fit our code style, but would handle a lot of file-directory architecture choices. We credit this down to the fact that we've structured our codebase in a predictable and - in my opinion, reasonable - structure, which has been optimised for the humans who are interacting with it. As well as this, we've also had documentation for new contributors to understand how best to get started, which also helps the agents! I've called this a "lukewarm" set of recommendations because for anyone who's fairly invested in doing work with AI agents, these are going to feel like so last $timePeriod. I appreciate that they're not ground breaking, but they're useful for folks who may be earlier in their AI journey than others. These recommendations build on great work that Sergei Zharinov and Sebastian Poxhofer - as well as a few other folks - have been doing. AGENTS.md / CLAUDE.md I'm largely adding this for completeness - it's a fairly standard recommendation that you'll get from most people, but the interesting angle we've got is that it doesn't need to be exhaustive. You can see that we've barely updated AGENTS.md since adding it in May, but we have made many docs edits for our "development standards" documentation. These docs were originally built for human readers, and are still our recommended area for this information to

## Being more explicit with the limited AI usage in my blog posts' content

DevFeed: [Being more explicit with the limited AI usage in my blog posts' content](<https://devfeed.tech/articles/being-more-explicit-with-the-limited-ai-usage-in-my-blog-posts-content-91206.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/20/ai/>)

Author: Jamie Tanna

Published: 2026-10-20T19:41:30Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [blog](<https://devfeed.tech/tags/blog.md>), [ethics](<https://devfeed.tech/tags/ethics.md>), [llm](<https://devfeed.tech/tags/llm.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [www-jvt-me](<https://devfeed.tech/tags/www-jvt-me.md>)

### AI overview

The author has made AI assistance in blog posts more explicit so readers can judge whether to read them. They updated post metadata to state the purpose of AI use, while acknowledging that details for some older posts may be uncertain, and plan to keep recording usage going forward. A new /ai page provides a running list and count of posts with AI involvement; the Logs as UX post is given as an example.

### Source excerpt

I don't want to read lengthy blog posts that have been spat out by a Large Language Model (LLM), because the author hasn't felt they want to write the words to share their point. I'm not going to rehash why that's (generally) a bad thing, as a lot of brilliant writers like Bryan Cantrill have written eloquently on the topic. What is important is that I don't want my readers to feel they're needing to work out what of my content is AI-assisted, and so I want to make it super explicit assisted - and when it is, in what ways - so the reader can decide if it's worth their time to read. I've previously noted that I track my LLM usage quite carefully, so I already have metadata on my blog posts to note where I am using AI model(s) to support the post, but until today, it wasn't clear what usage was for what purpose. I've updated my metadata as best as I can (especially for some of the older posts where I can't necessarily remember exactly what bits of content may have been edited) and will continue to do this with posts going forwards. You can see an example of this more in-depth metadata i.e. with the AI usage notice on my Logs as UX post. I've also created a /ai page to note this, and provide a running list (and count) of posts that have had any AI involvement in them. We'll see how that list increases over time.

## Week Notes 26#42

DevFeed: [Week Notes 26#42](<https://devfeed.tech/articles/week-notes-26-42-89759.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/42/>)

Author: Jamie Tanna

Published: 2026-10-18T20:11:52Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [claude](<https://devfeed.tech/tags/claude.md>), [go](<https://devfeed.tech/tags/go.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

The author recaps a mixed personal week, including rewriting a Micropub endpoint in Go, trying Amp with a Claude subscription, and deciding against submitting a talk proposal to KubeCon.

### Source excerpt

A busy week catching up on what I'd missed while at Open Source Summit last week Mostly wrote up the main TODOs I had last week, but still need to get a lot of them thought out more and prioritised Haven't got round to my writeup of the conference I've unfortunately come down with a cold - which has got better, and thankfully wasn't COVID - but has dampened the week Got the plumber round to fix up the pipe I'd knicked, and now we've been able to have the heating on which has been nice! Had our first Tamatanga in a while, which was nice Did the switch of my Micropub endpoint to my rewrite in Go, and so far, it's looking good Thought we'd try the local butchers for steak, and it was really nice! Reasonable price, really nice sirloin cuts, and beautifully cooked by Anna 😋 Had a nice roast today at The Railway 😋 In particular, gorgeous beef and roasties, and the whole meal all very good - sharing the STP was also very 😋 AI-y wise: Getting Pushover notifications has been handy I've started playing around with Amp, now it's possible to use a Claude subscription Decided to call notification bankruptcy on Changelog Zulip Decided not to submit to speak at Kubecon (or colocated events) as I didn't really want to try and squeeze in some talk proposals I waited until Anna was home to finish the TfL jigsaw, then we started a Wentworth one, finished it in less than 24 hours, so we're on a more complex LEGO one now Playing: (No Blue Prince) Kingshot (per usual) Apex Legends Reading: The Sins of Our Fathers Watched: (No The Expanse (Season 5)) Taskmaster (Series 22) Furiosa: A Mad Max Saga (2024) The Celebrity Traitors (Series 2) Ted Lasso (Season 4) Saturday Night Live (on YouTube) Matchbox: The Movie (2026) Not quite a Barbie but still fun

## Writing to AWS S3 from Fly.io (in Go)

DevFeed: [Writing to AWS S3 from Fly.io (in Go)](<https://devfeed.tech/articles/writing-to-aws-s3-from-fly-io-in-go-89758.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/18/fly-s3/>)

Author: Jamie Tanna

Published: 2026-10-18T16:46:39Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [fly.io](<https://devfeed.tech/topics/fly-io.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [IO](<https://devfeed.tech/topics/io.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [fly](<https://devfeed.tech/tags/fly.md>), [fly-io](<https://devfeed.tech/tags/fly-io.md>), [go](<https://devfeed.tech/tags/go.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [s3](<https://devfeed.tech/tags/s3.md>)

### AI overview

A Go tutorial shows how to obtain a short-lived OpenID Connect token from Fly.io, exchange it through AWS STS for temporary credentials, and use those credentials to write objects to S3. It also gives example IAM trust and bucket policies and notes that overly restrictive trust-policy conditions caused an access-denied error.

### Source excerpt

I'm currently in the process of moving my site's media (under media.jvt.me) from Netlify to AWS S3. The underlying infrastructure for my site that writes this media is hosted on Fly.io, so needs a way to write to S3. I really wanted to avoid long-lived AWS credentials, and fortunately Fly supports OpenID Connect which integrates with AWS' OpenID Connect Federation to allow you to use short-lived OpenID Connect tokens to authenticate as a given IAM role, and then perform any necessary AWS actions. Although Fly has an example with curl, I wanted to blogument the "how to" with Go, as it wasn't super straightforward to do so. I've written this up in a sample repo on GitLab.com. Go code The core pieces are: // via https://gist.github.com/teknoraver/5ffacb8757330715bcbcc90e6d46ac74 var unixClient = http.Client{ Transport: &http.Transport{ DialContext: func(_ context.Context, _, _ string) (net.Conn, error) { return net.Dial("unix", "/.fly/api") }, }, } func getOIDCToken(unixClient http.Client) (string, error) { s3Body := bytes.NewReader([]byte(`{"aud":"sts.amazonaws.com"}`)) // or could be `{"aud":"https://sts.amazonaws.com"}` as long as it matches your Trust Policy // get the OIDC token resp, err := unixClient.Post("http://localhost/v1/tokens/oidc", "application/json", s3Body) if err != nil { slog.Error("Failed to call Fly OIDC tokens endpoint", "err", err) return "", err } defer resp.Body.Close() body, err := io.ReadAll(resp.Body) if err != nil { slog.Error("Failed to read body", "err", err) return "", err } return string(body), nil } func newAWSClient(oidcToken string) (*s3.Client, error) { cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRegion("eu-west-1")) if err != nil { return nil, err } stsClient := sts.NewFromConfig(cfg) assumedRoleInput := &sts.AssumeRoleWithWebIdentityInput{ RoleArn: aws.String(os.Getenv("AWS_ASSUME_ROLE_ARN")), RoleSessionName: aws.String("..."), WebIdentityToken: aws.String(oidcToken), } resp, err := stsClient.AssumeRoleWithWeb

## Making an optional, required, status check with GitHub Actions

DevFeed: [Making an optional, required, status check with GitHub Actions](<https://devfeed.tech/articles/making-an-optional-required-status-check-with-github-actions-88814.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/16/github-actions-optional/>)

Author: Jamie Tanna

Published: 2026-10-16T14:47:21Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [merge](<https://devfeed.tech/tags/merge.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [pr](<https://devfeed.tech/tags/pr.md>), [tests](<https://devfeed.tech/tags/tests.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The article explains how to keep required GitHub Actions status checks passing while skipping tests that are unrelated to a change in a monorepo. It recommends checking changed files inside the workflow and marking jobs as skipped when they are not needed, and compares alternatives including a fake workflow, Buildkite's monorepo-diff plugin, and CodeCov's empty-upload action.

### Source excerpt

Something that I've hit time and time again over the years - but seemingly have never blogument'd - is that when you add a required status check on GitHub (in branch protection or a Ruleset), it needs to report back as successful before you can merge a given Pull Request. This is absolutely reasonable, and I don't think there are many complaints folks would have about this requirement. That is, until you want to consider how to handle checks that you don't necessarily want to run all the time. For instance, let's say you have a smallish monorepo where there is a mix of Java, backend Typescript and frontend React + Typescript. If you're only changing one of those parts of the codebase - or if you're fixing a typo in a Markdown file - you probably don't want to run all three suites of tests. There may be cases where the frontend needs to re-run its tests if there's a change in the backend code for instance if you've got tests that collaborate on the state of the API contract, but for the most part, the test suites only cover the changes in their part of the codebase. This results in the following set of status checks being enforced on a given PR: The ideal experience for a contributor to the codebase is that they don't want to run all these unrelated tests when they're modifying a scoped part of the codebase, but this isn't super straightforward with the way the status checks work, because if you do it wrong, you end up with a check that'll never pass: I've tried a few options over the years, and found that my preferred option is: Use your primary workflow (i.e. .github/workflows/bff.yml) Add a set of steps at the start of the workflow to determine files changed If any files you want have changed, then run the workflow If not, add a fake step to run as "successful" For instance, let's say that we have a repository like so: . ├── backend │ └── fake.Java └── ts ├── backend │ └── server.ts └── frontend └── Page.ts .github └── workflows ├── backend.yml ├── bff.yml └── fro

## Reattaching \`tmux\` to your Xorg session

DevFeed: [Reattaching \`tmux\` to your Xorg session](<https://devfeed.tech/articles/reattaching-tmux-to-your-xorg-session-88815.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/16/tmux-reattach/>)

Author: Jamie Tanna

Published: 2026-10-16T13:11:52Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Zellij](<https://devfeed.tech/topics/zellij.md>), [Text-based user interface](<https://devfeed.tech/topics/tui.md>), [LocalStorage](<https://devfeed.tech/topics/localstorage.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [terminal](<https://devfeed.tech/tags/terminal.md>), [tmux](<https://devfeed.tech/tags/tmux.md>), [xorg](<https://devfeed.tech/tags/xorg.md>)

### AI overview

When existing tmux panes lose access to a restarted Xorg/X11 session, check the current DISPLAY value in a new terminal and export it in affected panes. The post also describes tmux's update-environment behavior and setting DISPLAY for new panes.

### Source excerpt

It happens infrequently enough to not investigate too much further, but sometimes I'll end up with my Xorg/X11 session crashing, or something else happening which leads to my existing tmux sessions failing to interact with the new X session, with errors like: % gh repo view --web Opening ... in your browser. Error: cannot open display: :0 % xsel xsel: Can't open display: (null) : Connection refused In this case, the existing panes/windows may end up seeing a related error about failing to connect to the display, but any new panes/windows created will be able to interact as expected. This is a bit of an annoying one, but one way we can solve this is to nudge these panes to use the new DISPLAY. In a new pane/window/terminal session, check the DISPLAY environment variable: % echo $DISPLAY :1 That's likely different to what it shows in one of those existing panes - if so, run: % export DISPLAY=:1 After which, you can then run commands that interact with your X session. It's possible to run: % tmux set-environment DISPLAY :0 Which will update all new panes - but as mentioned, tmux likely already handled that for you, as DISPLAY is one of the environment variables it updates, as per: % tmux show-options -g update-environment update-environment[0] DISPLAY ... Instead of doing this by hand, it's also possible (Via) to script this to ??.

## Adding Pushover notifications to Claude Code

DevFeed: [Adding Pushover notifications to Claude Code](<https://devfeed.tech/articles/adding-pushover-notifications-to-claude-code-85493.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/12/claude-pushover/>)

Author: Jamie Tanna

Published: 2026-10-12T20:16:30Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [bash](<https://devfeed.tech/tags/bash.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [llm](<https://devfeed.tech/tags/llm.md>), [notifications](<https://devfeed.tech/tags/notifications.md>)

### AI overview

The post explains how to use Claude Code's Notification hook with a small Go CLI and the Pushover API to notify the author when the agent is waiting for input. It shows a settings configuration and shell wrapper, and notes that the current setup reports the message but not the session; the author also reports it works on a work Mac but not a Linux laptop.

### Source excerpt

There are times that you're away from your machine - or you've got so many terminal sessions you've not seen a notification - to say that your agent is waiting for input. Although there are ways to get first-class support for this - for instance Claude Code's Remote Control (which only works if using a Claude Code subscription, i.e. Bedrock users don't get access to it) - I wanted to write a tiny bit of Go code today, and thought I'd hand-roll some notifications. Given the Notification hook, this is actually fairly straightforward. To get a notification, you need to wire in the hook i.e. my ~/.claude/settings.json looks like: { "hooks": { "Notification": [ { "matcher": "", "hooks": [ { "type": "command", "command": "~/bin/_claude-hook" } ] } ] } } Then, my _claude-hook is a lightweight wrapper: #!/usr/bin/env bash source ~/.secrets/claude-hook claude-hook notification This is then a very small CLI which allows me to call the Pushover API given a set of inputs. In its first iteration, it echoes the message from Claude - but I'll follow-up to add some more insight into what session it's coming from. For now, I'm using a single CLI for Claude Code. If I get back to using multiple harnesses again (especially now crush has at least started to add hooks), I'll probably amend this to be i.e. -claude-hook notification +agent-hook claude notification So then I can share the same underlying codebase for the multi-agent setup - but there's no point in prematurely optimising when that's not the case! (Oddly, this works on my work Mac, but not on my Linux laptop - I need to investigate further)

## Week Notes 26#41

DevFeed: [Week Notes 26#41](<https://devfeed.tech/articles/week-notes-26-41-85016.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/41/>)

Author: Jamie Tanna

Published: 2026-10-11T20:31:38Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [enterprise certificate authority certificates](<https://devfeed.tech/topics/enterprise-certificate-authority-certificates.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [Fair Source](<https://devfeed.tech/topics/fair-source.md>)

Tags: [open-source-summit](<https://devfeed.tech/tags/open-source-summit.md>), [openssf](<https://devfeed.tech/tags/openssf.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>)

### AI overview

A personal week-notes post recounts attending Open Source Summit Europe and OpenSSF Community Day, discussing Renovate and software supply chain security, and announcing proactive upgrades for large open-source projects. It also touches on travel, work, home repairs, games, reading, and television.

### Source excerpt

A busy but very rewarding week at Open Source Summit (Europe) and the OpenSSF Community Day It was a very social week - I ended up chatting to some folks I've worked with in the Open Source ecosystem, as well as meeting a lot of other big names, which was very cool! I ended up going to all the socials I could do - which was good - and found that I enjoyed a lot of hallway track this time - I ended up bumping into a few folks who I had a number of things to talk about, and Sebastian and I had a lot of chats about different Renovate-y things (I'll do my full write-up hopefully this week - it's not an in-depth writeup!) And now I have such a long TODO list of things to plan to do off the back of the conference 🫣 But all very good things - it's been a good week talking about Renovate-y things, and more general supply chain security I was mostly good with my travelling, aside from: Losing my hoodie on the first leg of my journey, rushing out of the plane (due to a delayed arrival, and not a lot of turnaround time) Which was made worse by the fact that I'm not sure if it wasn't signposted correctly, but accidentally left the arrivals area (through to departures) when I got to BGY I forgot my second travel adapter - with one USB-C cable (and the battery on my work M4 MacBook Pro), I managed to survive with only that, but it was a bit tense! Found out that I'm in the top 4% of people found "in the weights" of AI models, which is cool (and also sad that they've trained off much of my content) Wrote a couple of cheeky posts mid-conference, and finished off a bigger post about Logs as UX On the flight on the way, I thought I'd see if Qwen could help me generate the log snippets for 👆🏼 and almost melted my legs with it During one of the talks, there was someone cutting their nails 😬🤮 Although we thought the leaky radiator was sorted, and so closed up the floorboards while I was away, it seems to have gotten worse through the week - when I was back, we took a look on Saturday, a

## Logs as UX

DevFeed: [Logs as UX](<https://devfeed.tech/articles/logs-as-ux-84301.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/09/logs-interface/>)

Author: Jamie Tanna

Published: 2026-10-09T13:12:48Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability](<https://devfeed.tech/topics/observability.md>), [session replay](<https://devfeed.tech/topics/session-replay.md>)

Tags: [debugging](<https://devfeed.tech/tags/debugging.md>), [empathy](<https://devfeed.tech/tags/empathy.md>), [it](<https://devfeed.tech/tags/it.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

The author argues that software logs are a user interface for users, operators, and support teams, and that teams should deliberately shape logs for readability, useful debugging, and user empathy. The article discusses log levels, sensitive information, aggregation and formatting problems, domain-specific viewing tools, and using AI agents with logs and code during debugging.

### Source excerpt

🤖 This post includes some LLM-derived content 🤖 A few years ago, Ryan wrote about how Bridgy, a service I use a lot, exposes log as the end user UI. This is a post that's stuck with me over the years, especially as someone whose work has generally comprised of building tools for others. I think about this post every so often with how in Renovate, our logs are the interface that users, operators, and support teams get into understanding what's going on under the hood. More generally, I think that focussing on your user-facing logs can be a key area to improve the experience for users of your software. (This make sense for a subset of applications - if you're building a SAAS platform or a mobile app, you may have different avenues to expose this information) They're there 🤷 At the laziest level, it's pretty likely that the software you're using already has logs available - often to be provided to the vendor to help support your usage. These logs are often written to disk in plain text, which means you as a human can read them without any extra tooling, making them more accessible for debugging. You may need extra configuration to increase the log level (see below) but it's often something within your control. Logs as an empathy builder As well as being the Renovate Project Lead, I am also the Community Manager for the project. One of the aspects of being the Community Manager - as well as part of my internal role at Mend including supporting Mend's Enterprise customers - is that I work through issues our other users are seeing with their Renovate setups. As part of this, I spend a chunk of time reading through debug logs, working to understand the situation they're in, and seeing how we can unblock them (in the short term) and stop it from happening (in the medium term). This puts me - and the other collaborators and maintainers on the project - in a particularly strong position to increase our empathy for our users. I could argue that Renovate's logs are "the great e

## Minifying JSON with \`jq\`

DevFeed: [Minifying JSON with \`jq\`](<https://devfeed.tech/articles/minifying-json-with-jq-76985.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/08/minify-json-jq/>)

Author: Jamie Tanna

Published: 2026-10-08T09:23:58Z

Content type: tutorial

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [jq](<https://devfeed.tech/tags/jq.md>), [json](<https://devfeed.tech/tags/json.md>)

### AI overview

The post shows how to minify JSON with jq by setting the indentation level to zero using `jq --indent 0 .`.

### Source excerpt

As an improvement to my version with Python or with Ruby, with tools like jq now being widely used, how do we minify a JSON string? Given: { "key": [ 123, 456 ], "key2": "value" } We can override the --indent: % jq --indent 0 . < a.json {"key":[123,456],"key2":"value"}

## Gotcha: GitHub Custom Properties are public

DevFeed: [Gotcha: GitHub Custom Properties are public](<https://devfeed.tech/articles/gotcha-github-custom-properties-are-public-76984.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/08/github-custom-properties-public/>)

Author: Jamie Tanna

Published: 2026-10-08T07:31:29Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [custom-properties](<https://devfeed.tech/tags/custom-properties.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [github](<https://devfeed.tech/tags/github.md>), [gotcha](<https://devfeed.tech/tags/gotcha.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The article explains that GitHub Custom Properties on public repositories are visible to anyone with read access, including property values and descriptions in the web interface. It illustrates the exposure with properties used at Elastic and an example API response, and notes that descriptions may not be available through the API to people outside the organization.

### Source excerpt

I was speaking to someone the other day - while I've been at Open Source Summit (Europe) - about the great Custom Properties that GitHub added in ~2023. However, they weren't aware that they're available to anyone with read access to the repo - which means for a public repo, that's everyone! This was something we found at Elastic while we were rolling out something that sounds pretty juicy called security_level. This was a mandatory field across all our repos, which was set to a reasonable default value. We ideally wanted to have our Custom Properties' descriptions include more context about what the security level fields meant, and a link to our internal docs for more in-depth information and how to change it. At Elastic we had a lot of Open Source (and public repos which are not-Open Source), which meant that anyone would be able to look up the descriptions of these fields. We can see this in action on i.e. github/gh-stack by using the API: [ { "property_name": "client-app", "value": "false" }, { "property_name": "CodeQL-Block", "value": "true" }, { "property_name": "dependency-review-action-enabled", "value": "true" }, { "property_name": "deployable", "value": "false" }, { "property_name": "durable-ownership-check-enabled", "value": "false" }, { "property_name": "ownership-name", "value": "@github/pull-requests" }, { "property_name": "ownership-type", "value": "Team" }, { "property_name": "repo-mirror-ci", "value": "disabled" }, { "property_name": "repo-mirror-strategy", "value": "standard" } ] You can also see this in the web UI, which can be found on each repo's homepage, following the link to "Custom Properties". Notice that in the web UI, you can see the description of the field, which isn't - as far as I can find - available through an API call if you're not part of the organisation. This does appear to be visibly documented by GitHub - but is something folks seem to not be aware of!

## Week Notes 26#40

DevFeed: [Week Notes 26#40](<https://devfeed.tech/articles/week-notes-26-40-64621.md>)

Original publisher: [Read original article](<https://www.jvt.me/week-notes/2026/40/>)

Author: Jamie Tanna

Published: 2026-10-04T20:10:03Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [superProductivity](<https://devfeed.tech/topics/superproductivity.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [CVE-2024-24806](<https://devfeed.tech/topics/cve-2024-24806.md>)

Tags: [claude](<https://devfeed.tech/tags/claude.md>), [claude-sonnet](<https://devfeed.tech/tags/claude-sonnet.md>), [claude-sonnet-5](<https://devfeed.tech/tags/claude-sonnet-5.md>), [open-source-summit](<https://devfeed.tech/tags/open-source-summit.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [security](<https://devfeed.tech/tags/security.md>), [week-notes](<https://devfeed.tech/tags/week-notes.md>), [www-jvt-me](<https://devfeed.tech/tags/www-jvt-me.md>)

### AI overview

A weekly personal roundup covers home life, games and entertainment, alongside work updates. The author describes finding an issue in Vale's LSP while using Neovim and Vale, which maintainers fixed; seeing a post advocating Renovate shared on Lobsters; and preparing for Open Source Summit while announcing security advisories.

### Source excerpt

A chilled journey back home, with a stop-off at Blakeney for a walk with the dogs We bumped into Dougie on the road home which was a nice surprise! Finally looked into a massive papercut I have with my Neovim + Vale setup, where I need to stop Vale and then clear LSP diagnostics, which Claude Sonnet 5 found as an upstream issue in Vale's LSP, which was fixed by the maintainers Was cool to see my post about why I - still - think Renovate is the best tool for the job appear on Lobsters This week I celebrated my blog's 10th anniversary - I could've spent a lot of more time reflecting but also maybe want a bit more time to think about what to say - maybe it'll even be a private post just for me Started on the TfL jigsaw, which is going well A busy week at work, announcing some big security advisories and prepping for Open Source Summit Did a bit of life admin, like finally sorting out my phone contract, upgrading to Monzo Max and getting Discord Nitro Had a good time at Phil Wang on Saturday - a few bits that were the same as his bit in last year's Christmas gig, but still good! James Trickey was a good warmup A nice time at pizza Thursday, but felt like I didn't really get a chance to talk to anyone! A busy weekend, as on Friday evening, we noticed that one of our radiators had been leaking (enough so that we found out by water dripping through the floorboards into the hallway) - I've managed to change the lockshield valve, but there's a lot of water we're drying out up there (Most likely) Morph brought in a very dead mouse one day 😅 Playing: (No Blue Prince) Kingshot (per usual) Looking forward to KvK! Apex Legends The Street Fighter mode being its own queue meant such long wait times that I ended up playing regular Wildcard Reading: The Sins of Our Fathers Watched: Neagley (Series 1) The Expanse (Season 5) Taskmaster (Series 22) (No Furiosa: A Mad Max Saga (2024)) The Celebrity Traitors (Series 2) Ted Lasso (Season 1) Between Two Ferns (on YouTube)

## A DECADE of writing on this blog

DevFeed: [A DECADE of writing on this blog](<https://devfeed.tech/articles/a-decade-of-writing-on-this-blog-63479.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/10/01/10-years/>)

Author: Jamie Tanna

Published: 2026-10-01T15:46:19Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>)

Tags: [blogging](<https://devfeed.tech/tags/blogging.md>), [career](<https://devfeed.tech/tags/career.md>), [git](<https://devfeed.tech/tags/git.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hacktoberfest](<https://devfeed.tech/tags/hacktoberfest.md>), [writing](<https://devfeed.tech/tags/writing.md>), [www-jvt-me](<https://devfeed.tech/tags/www-jvt-me.md>)

### AI overview

The author reflects on ten years of blogging, describing how writing became part of their identity and career. They recount early posts about Hacktoberfest, GitLab, and blogumentation, and note that blogging has benefited them personally and professionally.

### Source excerpt

This year I'm fortunate to be celebrating a few 10th anniversaries. One of the big ones is that this blog is officially 10 years old! This post is the 1285th post I've written on here, and I still love this part of myself. I've written about how it's helped me as someone neurodiverse, some reasons about why I think you should blog and reflecting on hitting 1000 posts (which is even more wild that was 2 years ago!! I swore it was more recent than that), and I've definitely got a number of other posts in there about the benefits. It all started 10 years ago, where I remember sitting downstairs in "the Software Studio" at Capital One, trying to desperately finish off what would be the first of many blog posts. In my memory, I felt like I was slightly taking the piss, because my lunch break was a lot longer than it should have been, which considering I was just over one month into my first job, wasn't the best look, but "I needed to get it finished". But looking back at the history, I posted it at 1050, which means I hadn't even had my lunch break and I was already trying to finish the post, which is an even worse look in retrospect 🫠 That post was celebrating the start of Hacktoberfest, which I wanted to land on the first day of Hacktoberfest, so I could share it around Hacksoc Nottingham, as I would be doing a workshop about Git + Open Source later that week. In 2016, I had basically nothing on my site - it was more of a portfolio site with some of the projects I've worked on, and this one blog post - so the traffic to my site was understandably pretty low. It wasn't until early 2017 that I started getting some real traffic, with my blog post about why you should use GitLab.com, as a big fan of the platform, which alongside using GitLab CI and Capistrano, I ended up seeing a lot more traffic. Later that year, I put some words to Blogumentation - Writing Blog Posts as a Method of Documentation, which would become a staple of my website, accounting for 557 posts (~43%)

[Next page](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md?cursor=WyIyMDI2LTEwLTAxVDE1OjQ2OjE5KzAwOjAwIiwgImJlYjkwMjk0LTY3NDQtNGEyMy1hM2YwLTkzYjM2NGRjNDNlMyJd>)