Hacker News: jamietanna

How to Pretty-Print Your Kubernetes YAML as Kyaml and Why You'd Want To

jamietanna — Mon, 31 Aug 2026 07:13:40 +0000

Article URL: https://kubernetes.io/blog/2026/08/11/how-to-pretty-print-kubernetes-yaml-as-kyaml/

Comments URL: https://news.ycombinator.com/item?id=49506588

Points: 1

# Comments: 0

New comment by jamietanna in "Sort branches by last commit date"

jamietanna — Sun, 30 Aug 2026 20:50:07 +0000

At any time I'm working across 5-30 branches (some when I'm reviewing other folks' code) so it's handy to see my latest branches

New comment by jamietanna in "Claude Session URL appended to commit messages and PR descriptions by default"

jamietanna — Sun, 30 Aug 2026 18:55:38 +0000

Very much agree, and per https://www.jvt.me/posts/2026/02/25/llm-attribute/ there are a number of other benefits to attributing correctly - you know what parts of the code may be "tainted" by AI-generated code, and allow yourself to clarify to the reader what parts are AI and what are not

New comment by jamietanna in "Just the rumour of a bug is enough to find an exploit these days"

jamietanna — Sun, 30 Aug 2026 08:27:35 +0000

If it helps, in the Renovate project we don't usually request a full CVE ID, but use the GitHub Security Advisory (GHSA) ID

You can use those numbers in changelogs as soon as they're published

There is some human review, which takes time, before the GHSA is "GitHub-reviewed" which then allows security scanners to pick it up

Then, the CVE ID can be assigned to it after-the-fact if need be, but the GHSA should be a sufficient starting point

New comment by jamietanna in "Just the rumour of a bug is enough to find an exploit these days"

jamietanna — Sun, 30 Aug 2026 08:25:43 +0000

https://github.blog/security/supply-chain-security/inside-th... goes into it more

As mentioned by another commenter, they intentionally have a human reviewer in the process before a GitHub Security Advisory (GHSA) becomes "official" post-publish

(this is separate to getting CVE ID assigned, if wanted)

Issues in the Repo

jamietanna — Thu, 20 Aug 2026 10:55:42 +0000

Article URL: https://nesbitt.io/2026/08/20/issues-in-the-repo.html

Comments URL: https://news.ycombinator.com/item?id=49372925

Points: 2

# Comments: 0

New comment by jamietanna in "Why I still hand write my commit messages"

jamietanna — Mon, 17 Aug 2026 22:11:00 +0000

I would love for there to be some way to review commit messages - and suggest changes - alongside reviewing the code itself

New comment by jamietanna in "Instrumenting my espresso machine with OpenTelemetry"

jamietanna — Sun, 02 Aug 2026 12:16:29 +0000

FYI the code snippets have no indentation

New comment by jamietanna in "Malicious npm packages detected across Red Hat Cloud Services"

jamietanna — Mon, 01 Jun 2026 20:11:31 +0000

That was a few days ago: https://news.ycombinator.com/item?id=48313577

Composer's Dependency Policies

jamietanna — Fri, 29 May 2026 10:59:24 +0000

Article URL: https://nesbitt.io/2026/05/29/composer-dependency-policies.html

Comments URL: https://news.ycombinator.com/item?id=48321542

Points: 3

# Comments: 0

Chaoss Metrics in 2026

jamietanna — Wed, 27 May 2026 13:04:16 +0000

Article URL: https://nesbitt.io/2026/05/27/chaoss-metrics-in-2026.html

Comments URL: https://news.ycombinator.com/item?id=48293671

Points: 1

# Comments: 0

New comment by jamietanna in "Staged publishing and new install-time controls for npm"

jamietanna — Sat, 23 May 2026 09:13:42 +0000

*11.x

New comment by jamietanna in "I hate the recent open-source rise"

jamietanna — Tue, 12 May 2026 17:03:13 +0000

I personally prefer Free Software (FSF-approved) or Open Source (OSI-approved) licenses, but I also agree that there is a place for other licenses. It's better that there's space for kinda-open, rather than it being open vs completely closed repositories.

I've previously worked at a company using an "open source" license (Elastic, with the ELv2) and have enjoyed having to explain the difference to folks between what it meant to be "open source" vs "Open Source", and the fact that a lot of folks generally don't understand the difference and some of the nuance. Mentioning the BuSL was because it's something a lot more folks may be aware of, i.e. given Hashicorp's recent relicense (as with other companies in recent years)

Sustainability is hard, and having different ways to describe this is good! But it's a lot harder when people don't understand why something calling itself "open source" when it's "but you can't run it if you're a company" is bad

New comment by jamietanna in "I hate the recent open-source rise"

jamietanna — Tue, 12 May 2026 16:20:48 +0000

I must say, I'm honoured this commenter is so angry about this post, they've read through many of my blog posts, and gone through microsites like my Manual of Me[0], to pull this quote to attempt to criticise me

[0]: https://manual.jvt.me/

New comment by jamietanna in "I hate the recent open-source rise"

jamietanna — Tue, 12 May 2026 13:29:55 +0000

Hah, yes very true!

If you've not read up on the background between the two - I'd very much recommend it (and sorry if I'm re-explaining something you understand)

With Free Software, it's "free as in freedom", not "free as in gratis". Free Software is generally a bit more strongly biased towards the users of a piece of software, but as businesses started to use it they were a bit unhappy with that, so Open Source came to reduce that a little bit, making it easier for companies to use it, without as many strong protections for a user

New comment by jamietanna in "I hate the recent open-source rise"

jamietanna — Tue, 12 May 2026 13:11:19 +0000

I think using `open source`, and clarifying that it includes non-OSI-approved licenses could work.

Alternatively, "source available" is a term that's been used to imply the source is there, but it's not "open source" (which led to the Fair Source folks working on their own naming for it, so as some folks have negative views of "source available")

I hate the recent open-source rise

jamietanna — Tue, 12 May 2026 12:58:13 +0000

Article URL: https://www.jvt.me/posts/2026/05/12/open-source/

Comments URL: https://news.ycombinator.com/item?id=48107615

Points: 16

# Comments: 27

New comment by jamietanna in "Update on "Co-authored-by: Copilot" in commit messages"

jamietanna — Wed, 06 May 2026 13:33:28 +0000

Nice! I've been doing similar, but prefer using Co-authored-by, especially as it allows for cases where there may be multiple models in play

New comment by jamietanna in "Update on "Co-authored-by: Copilot" in commit messages"

jamietanna — Wed, 06 May 2026 07:08:10 +0000

As I've written elsewhere in the thread, having worked at a large Enterprise in collaboration with Legal, if there isn't tracking of what AI contributions you have, it's harder to be protected legally by ie Microsoft's indemnity clause if you're sued

New comment by jamietanna in "Update on "Co-authored-by: Copilot" in commit messages"

jamietanna — Wed, 06 May 2026 07:06:07 +0000

Agreed they could be clearer on this

IMO (and I am biased because I have written about this before in https://news.ycombinator.com/item?id=47164481) but I believe it's to make sure they're legally covering their users, and making sure users of AI tools do at least have some attribution for AI-derived contributions