<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Alek&#x27;s Blog - claude-code</title>
    <subtitle>Production notes on Kubernetes, OpenShift, and OVHcloud: observability, log archiving, service mesh, LLM inference, and digital sovereignty.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://blog.none.at/tags/claude-code/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://blog.none.at"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-07-09T00:00:00+00:00</updated>
    <id>https://blog.none.at/tags/claude-code/atom.xml</id>
    <entry xml:lang="en">
        <title>Who Has Access? Humans, Accounts, AI Agents</title>
        <published>2026-07-09T00:00:00+00:00</published>
        <updated>2026-07-09T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              aleks
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.none.at/blog/2026/2026-07-09-sovereignty-access-model/"/>
        <id>https://blog.none.at/blog/2026/2026-07-09-sovereignty-access-model/</id>
        
        <summary type="html">&lt;p&gt;&lt;a href=&quot;https:&#x2F;&#x2F;blog.none.at&#x2F;blog&#x2F;2026&#x2F;2026-07-09-sovereign-cloud-washing&#x2F;&quot;&gt;Part 1&lt;&#x2F;a&gt; split the technology-supply-chain
question into two halves: what the platform is built on, and who — or what — actually has access to
it. &lt;a href=&quot;https:&#x2F;&#x2F;blog.none.at&#x2F;blog&#x2F;2026&#x2F;2026-07-09-sovereignty-technology-stack&#x2F;&quot;&gt;Part 2&lt;&#x2F;a&gt; answered the first half. This
post answers the second, using systems already built and operated for this blog rather than new
research — human access, service-account access, and (increasingly relevant) AI-agent access, all
checked against the same bar: is it documented, is it audited, and is it technically enforced or
just expected to be followed.&lt;&#x2F;p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>How I work with Claude Code</title>
        <published>2026-06-10T00:00:00+00:00</published>
        <updated>2026-06-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              aleks
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.none.at/blog/2026/2026-06-10-how-i-work-with-claude/"/>
        <id>https://blog.none.at/blog/2026/2026-06-10-how-i-work-with-claude/</id>
        
        <summary type="html">&lt;p&gt;Since 2025, I have been using AI tools as part of my daily work. Not as a replacement for
thinking — as a productivity aid. An AI coding agent has become a regular part of how I work on infrastructure, blog posts,
and software projects. Most of what follows likely applies to other agents as well —
Cursor, Copilot, or whatever comes next. I happen to use Claude.&lt;&#x2F;p&gt;
&lt;p&gt;This post is not a tutorial and not a pitch. It is a reflection on what actually works — for me, on my projects —
across months of real use, across 40+ projects, and across months of agent use.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
