17 Matching Annotations
  1. Feb 2026
    1. It's as though many people in the tech industry have no real desires at all beyond the desires that they're told to have by their wider social circles.

      Software devs desires as the current highest probability desires of their environment. (Vgl [[Groep som der delen of container 20201207194431]]

    2. When LLM coding agents are the new hot thing, everything that the engineering community previously said about engineering standards, testing and robustness suddenly goes out the window,

      Techno-optimists wrt LLM throwing established practices to safeguard quality out the window. (And I noticed if you point it out it gets them mad, e.g. wrt web search by LLM)

    3. The pattern in the tech world seems to be a distorted mirror of this, where some entity pushes a propaganda narrative and, like clockwork, the core influencers of general tech opinion shift their desires to match

      Observes a quick uptake of narrative du jour, where in other groups existing opinions, wishes and aims are to be navigated around

    4. Whether it's talking about race science and eugenics, the blockchain and NFTs or our current LLM situation, the core voices in the tech community (which is to say the people who have a disproportionate influence on general opinion within tech) are consistently willing to pick it up and go along with it, regardless of how obviously the narrative has been deliberately engineered and almost as though they have no real desires or internal motivation of their own.

      Mentions example topics where author observes this pattern

    5. I drew the conclusion that software developers are almost uniquely vulnerable among educated and professional people to being taken in by propaganda.

      Author observes that software devs are more swayed by propaganda that other professional classes, like stats and engineering.

    1. Peter Naur reminded us some decades ago that a program is more than its source code. Rather a program is a theory that lives in the minds of the developer(s) capturing what the program does, how developer intentions are implemented, and how the program can be changed over time. Usually this theory is not just in the minds of one developer but fragments of this theory are distributed across the minds of many, if not thousands, of other developers.

      Peter Naur, Programming as Theory Building 1985 https://doi.org/10.1016/0165-6074(85)90032-8

      Programming as theory building 1985 in Zotero

    2. Technical debt nicely captures that “human understanding” also matters, but the words “technical debt” conjure up the notion that the accrued debt is a property of the code and effort needs to be spent on removing that debt from code.

      While techdebt is about the accumulation of human decisions, and the resulting erosion of human understanding, the term itself suggests it is a property of the code itself, and that one could remove it from code.

  2. Jan 2026
    1. Generally, doing less is faster and easier! Depending on the task, you may be able to soften the requirements.

      try and reduce reqs. For my personal tools this is often achieved by not having to deal with edge cases and my own behaviour being predictable, or that I can prescribe myself a specific way of working.

    2. Some tips on how to build software quickly. Via Alper, who says it seemd obvious to him, but then said he also recognised it bears repeating. It seems useful to use as cheat sheet even of tiny personal tools I make, and for home vibe coding projects too, wrt how to initiate interaction w LLMs

      • [ ] return om n:: software dev v t maken
    1. The thing is, software is not an asset, it's a liability. The capabilities that running software delivers – automation, production, analysis and administration – those are assets. But the software itself? That's a liability. Brittle, fragile, forever breaking down as the software upstream of it, downstream of it, and adjacent to it is updated or swapped out, revealing defects and deficiencies in systems that may have performed well for years.

      software is a liability. Dutch equiv of this phrase? The assets are its impact : automation, production, analysis, admin

  3. Nov 2025
    1. Kommer den artificiella intelligensen att bli bättre på att tänka än den mänskliga? Kognitionsvetaren Peter Gärdenfors förklarar varför så inte är fallet.  Den mänskliga intelligensen består av en rad olika färdigheter och specialiteter som har förfinats under tusentals år. Mycket återstår innan den artificiella intelligensen kan mäta sig med det tänkande som inte bara människor utan även djur har. När vi förstår att vår intelligens är en bred palett av många olika förmågor ter sig tanken på att AI-tekniken trumfar oss i schack och kan skriva avancerade texter inte lika skrämmande. Utifrån ett brett forskningsunderlag förklarar Gärdenfors varför AI-tekniken inte kan och inte kommer att kunna tänka på samma sätt som människor och djur gör. »Peter Gärdenfors tilldelas Natur & Kulturs debattbokspris 2025 för att han fördjupar AI-debattens centrala begrepp och utmanar dess utgångspunkter. Med lätt språk och stabil lärdom blottlägger han tänkandets evolutionärt slipade mekanismer, och skärper bilden av vad intelligens är och vilken plats tekniken intar i vår digitala värld.« – Juryns motivering

      [[Kan AI tänka by Peter Gärdenfors]] via Sven Dahlstrand, dahlstrand.net Publ okt 2024 Seeks to define what thinking actually is, and how that plays out in other animals and humans. The 2nd part goes into sofrware systems and AI and how they work in comparison.

  4. Sep 2024