Blog
All posts including articles and notes. (2602 total)
-
-
Permalink
I have not gotten any spam (yet) but I’m concerned about this too… for webmentions I built a backend moderation tooling so that I can block future webmention spam if that happens one day I can also delete webmentions (even if they keep existing at the source obviously) but for comments and other forms input I’m not sure how I’m going to proceed yet
-
Building Enterprise AI: Hard-Won Lessons from 1200+ Hours of RAG Development
https://bytevagabond.com/post/how-to-build-enterprise-ai-rag/PermalinkI’m going to have to distill this great blog posts into bullet points summary of things to pay attention or to avoid when building our RAG documentation at work.
-
This blog post (sadly on substack) is truly fascinating :
Two years after the campaign started, in August 2021, China’s Supreme People’s Court, along with the Ministry of Human Resources and Social Security, officially ruled “996” illegal. It was, as far as I know, the first time that a grassroots, developer-led campaign used open source organizing mechanisms to enforce not just intellectual property norms, but labor rights norms, and ultimately ended in a legal victory.
-
Chinese Open Source: A Definitive History
https://interconnect.substack.com/p/chinese-open-source-a-definitivePermalinkThe first major chapter of the Chinese open source story did not begin with some grand government proclamation or a visionary founder. It started, as most open source stories do, with engineers trying to solve hard problems for their company. This company was Alibaba.
-
Permalink
I went and added AI usage metadata to my JSON-LD also added a AI usage page https://rmendes.net/ai/ and every posts on my blog have a easy to read/interpret AI usage transparency card;
I went this direction because I think, AI on blogs is not a blanket, its not ALL or nothing, it should be granular, per posts.
And just because one co-draft a tutorial or long form with an AI does not mean or equal AI generated.
I posit that this approach will be implemented in different ways but will ultimately be common in just a few months/years
-
Funny how building an ActivityPub plugin for #indiekit fully based on Fedify, migrating my Mastodon account to my own server @rick@rmendes.net and building my own UI to consume AP content from the #Fediverse made me use even more than before.
This post is simultaneously a blog post, an #ActivityPub object in the inbox of my followers and a syndicated post to Bluesky.
Next in line? getting inspired by #Wafrn and turn this indiekit/AP instance into my own #Bluesky Pds.
-
https://www.lowyinstitute.org/the-interpreter/un-s-commission-status-women-empty-chairs-are-storyPermalink
more than half of humanity is not represented at various levels of governance, be it supra national or national representative democracy.
what could go wrong?
-
Bookmark : A eulogy for cyberspace
https://newdesigncongress.org/en/pub/who-will-remember-us-when-the-servers-go-dark/PermalinkThis is a eulogy for a world we were promised but never lived in.
This is a long read, keeping it here to read later !
-
-
Permalink
I’m reading your posts about your experimentation with Claude Code and I have a few suggestions :
- how do people use it with large project ? by setting it up properly, claude.md at the user level and repo level is bare minimum (these are two very different claude.md with different purpose)
- Use Obra Superpower to plan/execute dev tasks (literraly change the way claude behave)
- Do not “chat” with it, investigate code base, plan, execute and carefully augment the claude.md of the repo with carefully chosen information you want it to load in its context each time you launch claude in that repo
- your repo claude.md is not for humans or for documentation, its for claude; do not let it grow indefinitely, you’ll poison your context window
- If you really need to give specific documentation know-how to claude, build a separate repo only for documentation, generate documentation from code base and then launch agents to fact check it, configure your claude with a hook to update documentation or claude.md when necessary after each dev phases
- If you have to repeat more than 2 times an information of context about a code repo to claude, this information should be stored in claude.md
There is so much more to say but…perhaps I should write this down on a blog post :)
fosstodon.org
manton.org
feedgrab.net
interconnect.substack.com
mastodon.social
shellsharks.com
newdesigncongress.org
kittygiraudel.com
daveverse.org
