jamietanna

6 ms·

1.
by jamietanna 7d ago
Which fonts are you seeing not looking good? It seems perfectly readable sans-serif and monospace wise, but could be system preferences on what fonts to use?
2.
by jamietanna 8d ago
And of nohello.com: https://news.ycombinator.com/from?site=nohello.com
3.
by jamietanna 9d ago
+1 on this - Jake's done the best thing with deprecating the package (which shows up locally in tooling and will also be surfaced by static analysis tooling (ie security vendors) based on that, but also archiving the repo indicates it
4.
by jamietanna 11d ago
There are many reasons: https://news.ycombinator.com/item?id=47164481
5.
Renovate: It was a packageRule all along(secustor.dev)
2 points by jamietanna 17d ago|0 comments
6.
How to Pretty-Print Your Kubernetes YAML as Kyaml and Why You'd Want To(kubernetes.io)
2 points by jamietanna 26d ago|0 comments
7.
by jamietanna 27d ago
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
8.
by jamietanna 27d ago
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"
9.
by jamietanna 27d ago
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 tak
10.
by jamietanna 27d ago
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)
11.
Issues in the Repo(nesbitt.io)
2 points by jamietanna 1mo ago|0 comments
12.
by jamietanna 1mo ago
I would love for there to be some way to review commit messages - and suggest changes - alongside reviewing the code itself
13.
by jamietanna 2mo ago
FYI the code snippets have no indentation
14.
by jamietanna 4mo ago
That was a few days ago: https://news.ycombinator.com/item?id=48313577
15.
Composer's Dependency Policies(nesbitt.io)
3 points by jamietanna 4mo ago|0 comments
16.
Chaoss Metrics in 2026(nesbitt.io)
1 points by jamietanna 4mo ago|0 comments
17.
by jamietanna 4mo ago
*11.x
18.
by jamietanna 5mo ago
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 comple
19.
by jamietanna 5mo ago
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:/
20.
by jamietanna 5mo ago
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",
21.
by jamietanna 5mo ago
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
22.
I hate the recent open-source rise(jvt.me)
16 points by jamietanna 5mo ago|27 comments
23.
by jamietanna 5mo ago
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
24.
by jamietanna 5mo ago
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 i
25.
by jamietanna 5mo ago
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 u
26.
by jamietanna 5mo ago
Was wondering why a few of my sites aren't CSSing, as they use https://classless.de
27.
by jamietanna 5mo ago
Both Renovate and Dependabot will raise PRs for a security fix, regardless of minimumReleaseAge/cooldown config
28.
by jamietanna 5mo ago
Ooh thanks!
29.
by jamietanna 5mo ago
Was wondering if there was a list of known opt outs as we are looking at a default opt out in Renovate[0] - we'll also look to set `DO_NOT_TRACK` [0]: https://github.com/renovatebot/renovate/discussions/4
30.
A GitHub for Maintainers(nesbitt.io)
2 points by jamietanna 5mo ago|0 comments

More ›