Skip to content

#Writing

  1. · Note

    When the room was asked who felt they had agents operating at scale, no one raised a hand. In a smaller agentic workflow breakout, only 5 of 25 said they had agents in production at all. The concerns were consistent: security everywhere, not just in the CISO office; ROI that is still hard to measure; legacy systems that must be modernized before AI can truly scale; unclear governance and ownership models; and rising questions around vendor claims, data readiness, build-vs-buy decisions, and agent lifecycle management.

    Pretty no company at all has active agents in production. And for the very same reasons that IT systems before did not get live fast.

    Ed Sim, via What’s 🔥 in Enterprise IT/VC #497

  2. · Article · 1 min read

    Laravel Agent

    I wrote an agent with Laravel. It lived in my website where I do time track and have a thin layer I set up a cronjob. It ran in the mornings and in the evenings. It worked.

    Read article →
  3. · Article · 1 min read

    Small teams of helpful generalists

    My philosophy of a tech team has been that it is a, small; b, has only generalists and c, everyone is ready to help each other. Limiting the number in a team or group keeps coordination costs low and cohesion and mutual knowledge high.

    Read article →
  4. · Note

    Capture your thoughts on Mac into one file with the Burst Notes app by the maker of the productivity app Vitamin-R. Stays out of your way, hence similar to my open source app Quick Capture. Difference: Burst Notes saves into single files while Quick Captures saves to multiple files, either daily notes or Zettelkasten notes. I've been a long-time user of Vitamin-R and it is super reliable and gets frequent updates. Burst Notes is a pay-once app, 15€.

  7. · Note

    Frontend is never right, it will always look and behave different from what you expect.
    This is already true for one person, but 2+ people using the same interface will satisfy all needs.
    Text is much more forgiving here, it's asking for a result rather than a representation.
    Text is declarative like SQL, you tell what you want.

    So text as interface is flexible as it will use the words to explain that were used to ask. Problem then is how to make result "repeatable" and "reliable".

    My idea right now is to skip frontends as often as possible and not hardwire data and presentation but to give the leanest tools possible.
    So it could mean for a personal CRM to have a database, APIs, a Bearer token in your ENV and a skill that your coding agent can use to interact with your CRM.

  8. · Article · 1 min read

    The more LLM code, the more maintenance

    Creating lots of features with LLMs will create a lot of code to maintain. Beware of overwhelm. Deliberately remove unsuccessful and unused features asap.

    Read article →
  9. · Article · 4 min read

    The Raw Stack: Powering the Post-Frontend Company

    I am convinced that LLMs will more and more replace visual frontends and middle layers and go straight to the lowest possible infrastructure and give us voice and text interfaces that will be just enough. Designing frontends is harder to test automatically, also every user needs…

    Read article →
62 posts