<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://spur.us/blog/smart-tv-apps-residential-proxy-sdks"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Conduit_metaphor"/>
	<rdf:li rdf:resource="https://constable.blog/2007/11/09/how-our-autistic-friend-computer-can-really-help-us-about-conduit-and-toolmaker-metaphor/"/>
	<rdf:li rdf:resource="https://substack.com/@kentbeck/p-203433161"/>
	<rdf:li rdf:resource="https://oostkit.com/apps/intro_ost?from=section_theory"/>
	<rdf:li rdf:resource="https://mealie.io/?ref=a.wholelottanothing.org"/>
	<rdf:li rdf:resource="https://agenticresourcediscovery.org/"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/LocalLLaMA/comments/1rrisqn/i_was_backend_lead_at_manus_after_building_agents/"/>
	<rdf:li rdf:resource="https://aresluna.org/show-your-hands-honor/"/>
	<rdf:li rdf:resource="https://justus-ratzke.xyz/home/rest"/>
	<rdf:li rdf:resource="https://hbr.org/2026/06/how-to-design-agentic-systems-around-the-implicit-rules-that-govern-your-company"/>
	<rdf:li rdf:resource="https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/"/>
	<rdf:li rdf:resource="https://apichangelog.substack.com/p/the-taxonomy-of-api-operations"/>
	<rdf:li rdf:resource="https://www.sue.codes/blog/forwarddeployed/"/>
	<rdf:li rdf:resource="https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html"/>
	<rdf:li rdf:resource="https://blog.modelcontextprotocol.io/posts/enterprise-managed-auth/"/>
	<rdf:li rdf:resource="https://www.vmware.com/docs/platform-as-a-product-wp"/>
	<rdf:li rdf:resource="https://pedalscape.com/"/>
	<rdf:li rdf:resource="https://aicoding.leaflet.pub/3mcxo5ojob22c"/>
	<rdf:li rdf:resource="https://charitydotwtf.substack.com/p/ai-demands-more-engineering-discipline"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Campbell%27s_law"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Field-of-use_limitation"/>
	<rdf:li rdf:resource="https://www.howtogeek.com/how-claude-fixed-my-messy-obsidian-vault-in-5-minutes-prompts-included/"/>
	<rdf:li rdf:resource="https://theonion.com/i-work-very-hard-and-i-would-like-to-try-cake/"/>
	<rdf:li rdf:resource="https://blog.includesecurity.com/2026/06/the-smart-tv-in-your-livingroom-is-a-node-in-the-aiscraping-economy/"/>
	<rdf:li rdf:resource="https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11"/>
	<rdf:li rdf:resource="https://data-star.dev/"/>
	<rdf:li rdf:resource="https://archive.is/2026.06.03-164731/https://www.theatlantic.com/philosophy/2026/06/no-artificial-intelligence-is-not-conscious/687378/"/>
	<rdf:li rdf:resource="https://thelaterallens.substack.com/p/influence-mapping-part-3"/>
	<rdf:li rdf:resource="https://roundcrisis.com/2026/01/22/making-of-a-decision-4/"/>
	<rdf:li rdf:resource="https://roundcrisis.com/2025/09/01/making-of-a-decision/"/>
	<rdf:li rdf:resource="https://blog.tymscar.com/posts/v100localllm/"/>
	<rdf:li rdf:resource="https://hcommons.org/app/uploads/sites/1001532/2020/03/Bowker-1999-Sorting-Things-Out-Classification-and-Its-Consequences.pdf"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/coolguides/comments/ri0kvs/the_cube_rule_of_food_identification/"/>
	<rdf:li rdf:resource="https://mer.vin/2026/05/epicure-food-ai-4-million-recipes-compressed-into-a-2mb-ingredient-map/"/>
	<rdf:li rdf:resource="https://www.infoq.com/presentations/automation-incidents-ai/"/>
	<rdf:li rdf:resource="https://www.linkedin.com/mwlite/feed/posts/johnpcutler_many-leaders-spent-years-learning-to-work-activity-7464829078819352576-EWRv"/>
	<rdf:li rdf:resource="https://nooneshappy.com/article/native-apps-should-be-avoided-whenever-possible/"/>
	<rdf:li rdf:resource="https://www.modernleader.is/p/managing-systems"/>
	<rdf:li rdf:resource="https://www.patternlanguageindex.com/"/>
	<rdf:li rdf:resource="https://mastodon.online/@brianbilston/116617445306262522"/>
	<rdf:li rdf:resource="https://mpv.io/"/>
	<rdf:li rdf:resource="https://revealjs.com/"/>
	<rdf:li rdf:resource="https://community.ricksteves.com/travel-forum/france/self-drive-boats"/>
	<rdf:li rdf:resource="https://www.sciencedirect.com/science/article/abs/pii/S0264837725001553"/>
	<rdf:li rdf:resource="https://www.quantamagazine.org/hobbyist-finds-maths-elusive-einstein-tile-20230404/"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=S_JaNhzPB6I"/>
	<rdf:li rdf:resource="https://vegoutmag.com/lifestyle/t-psychology-says-the-men-who-read-as-genuinely-classy-in-their-50s-and-60s-arent-the-ones-with-the-watch-or-the-tailored-jacket-theyre-the-ones-who-stopped-interrupting-stopped-competing-in-small-c/"/>
	<rdf:li rdf:resource="https://honestcoffeeguide.com/coffee-to-water-ratio-calculator/"/>
	<rdf:li rdf:resource="https://cse-robotics.engr.tamu.edu/dshell/cs631/papers/franklingraesser96agents.pdf"/>
	<rdf:li rdf:resource="https://medium.com/disruptive-design/tools-for-systems-thinkers-the-6-fundamental-concepts-of-systems-thinking-379cdac3dc6a"/>
	<rdf:li rdf:resource="https://www.patreon.com/posts/thinking-about-156285478"/>
	<rdf:li rdf:resource="https://www.joanwestenberg.com/the-passive-income-trap-ate-a-generation-of-entrepreneurs/"/>
	<rdf:li rdf:resource="https://www.ifixit.com/News/93833/ask-ifixit-how-do-i-fix-sticky-plastics"/>
	<rdf:li rdf:resource="https://overreacted.io/a-social-filesystem/"/>
	<rdf:li rdf:resource="https://www.linkedin.com/pulse/hope-vs-leverage-travis-isaacs-j0ugc"/>
	<rdf:li rdf:resource="https://www.linkedin.com/pulse/try-hard-learn-lot-kind-omar-shahine-gn9vc"/>
	<rdf:li rdf:resource="https://runthebusiness.substack.com/p/the-12th-of-never"/>
	<rdf:li rdf:resource="https://tarakiyee.com/on-the-enshittification-of-audre-lorde-the-masters-tools-in-tech-discourse/"/>
	<rdf:li rdf:resource="https://docs.mealie.io/"/>
	<rdf:li rdf:resource="https://kennethreitz.org/essays/2025-08-27-from_http_to_consciousness"/>
	<rdf:li rdf:resource="https://ashley.rolfmore.com/stop-trying-to-engineer-your-way-out-of-listening-to-people/"/>
	<rdf:li rdf:resource="https://www.linkedin.com/pulse/service-design-social-complexity-cameron-tonkinwise-h8tzc"/>
	<rdf:li rdf:resource="https://teachcomputing.org/blog/using-primm-to-structure-programming-lessons/"/>
	<rdf:li rdf:resource="https://www.sue.codes/blog/fingerscode/"/>
	<rdf:li rdf:resource="https://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html"/>
	<rdf:li rdf:resource="https://colossus.com/article/we-have-learned-nothing-startup-pundits/"/>
	<rdf:li rdf:resource="https://themonolithproject.net/"/>
	<rdf:li rdf:resource="https://www.davidpoll.com/2026/02/code-review-is-not-about-catching-bugs/"/>
	<rdf:li rdf:resource="https://substack.com/home/post/p-191342187"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://spur.us/blog/smart-tv-apps-residential-proxy-sdks">
    <title>Nearly Half of LG Smart TV Apps Contain Residential Proxy SDKs</title>
    <dc:date>2026-07-02T00:04:38+00:00</dc:date>
    <link>https://spur.us/blog/smart-tv-apps-residential-proxy-sdks</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Smart TVs are almost ideal proxy hosts. They sit on the same home network as everything else, but they do not feel like computers, so people rarely audit them like computers. There is no battery drain to notice, no cellular bill to spike, no app switcher full of suspicious background activity. A TV can stay plugged in, signed in, and online for years while the user thinks of it as furniture.</blockquote>]]></description>
<dc:subject>security iot privacy television appliances</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:423729a7051a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:iot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:television"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:appliances"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Conduit_metaphor">
    <title>Conduit metaphor - Wikipedia</title>
    <dc:date>2026-07-01T04:14:13+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Conduit_metaphor</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Language is a conduit
edit
These commonplace examples—

You can't get your concept across to the class that way
His feelings came through to her only vaguely
They never give us any idea of what they expect
—are understood metaphorically. In 1., people do not actually "get across" concepts by talking; in 2., feelings do not really "come through to" people; and in 3., people do not in fact "give" to others their ideas, which are mental states. Listeners assemble from their own mental states a partial replica of the speakers'. These core expressions assert figuratively that language literally transfers people's mental contents to others.</blockquote>]]></description>
<dc:subject>language communication metaphor linguistics thinking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:86de667fb0b6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metaphor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://constable.blog/2007/11/09/how-our-autistic-friend-computer-can-really-help-us-about-conduit-and-toolmaker-metaphor/">
    <title>About the Conduit and the Toolmaker Metaphor – Hans Konstapel Blogs</title>
    <dc:date>2026-07-01T04:12:11+00:00</dc:date>
    <link>https://constable.blog/2007/11/09/how-our-autistic-friend-computer-can-really-help-us-about-conduit-and-toolmaker-metaphor/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Michael Reddy shows that 30% of the English Language can be described by another Metaphor, the Toolmaker Metaphor. The Toolmaker Metaphor is about cooperation, mutual discovery and the exchange of “tips and tricks”.

The Toolmaker Metaphor is connected to an old “Paradigm” that is slowly fading away in our current Society.

In the Toolmaker Metaphor Humans are unable to understand the other. We are all living in our “own unique private universe”. This Universe is What We Are. In our own universe we develop all kinds of private tools.

In the middle of all of the universes is a post-box. In this box we share pictures (ideas) with other universes. When we find a picture we interpret this picture in our own universe. We understand something because without “knowing” we share a lot.</blockquote>]]></description>
<dc:subject>language linguistics metaphor tools understanding</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a60e8e4d4849/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metaphor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:understanding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://substack.com/@kentbeck/p-203433161">
    <title>(1) The Cost YAGNI Was Never About - by Kent Beck</title>
    <dc:date>2026-06-30T17:04:22+00:00</dc:date>
    <link>https://substack.com/@kentbeck/p-203433161</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Money has time value. So do features. Structure you build now for a feature due in three months is cost pulled forward and revenue pushed back. You spent sooner and you shipped the paying thing later.

This bill comes due even when your guess is right. Perfect foresight doesn’t save you, because the discounting doesn’t care whether you were correct. It cares that you sequenced the cost ahead of the return. The gap between the two is the loss, and you opened the gap on purpose.

Two bills, then. Optionality says: don’t commit before the information arrives. NPV says: don’t pay before you have to. They’re independent, and they almost always agree. When they seem to disagree — “but it’ll be so expensive to retrofit later!” — look closely, because the expensive retrofit is itself a prediction. You’re back to the first bill.</blockquote>]]></description>
<dc:subject>productmanagement opportunity costs yagni software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2cbdde51b26a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opportunity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:costs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:yagni"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://oostkit.com/apps/intro_ost?from=section_theory">
    <title>Introduction to OST — OOSTKit</title>
    <dc:date>2026-06-29T06:47:52+00:00</dc:date>
    <link>https://oostkit.com/apps/intro_ost?from=section_theory</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Six criteria for productive work
Over decades of action research across dozens of countries, the Emerys identified six conditions that, when present, produce sustained motivation, learning, and genuine engagement at work. When they are absent, no amount of leadership training, culture work, or engagement programming compensates; the problems return. The six have now been measured in enough organisations, across enough cultures, that they appear to be a consistent feature of how human beings respond to work, not a product of any particular industry or context.

The first three concern the content of the work itself, and must be optimal for each person: neither too little nor too much. Too little and the work becomes stifling; too much and it becomes overwhelming. The right level varies between people and shifts over time.

Elbow room. People make real decisions about how their own work gets done. Not micromanaged, not left entirely at sea.
Continual learning. People set goals and get honest, timely feedback on whether they've been met. They can see themselves getting better.
Variety. The work has enough range to stay interesting and to call on different capabilities. Not so much that it fragments into chaos.
The second three concern the climate of the workplace. These have no upper limit; there is no such thing as too much of any of them.

Mutual support and respect. People help each other out without being asked, and can rely on the same in return. Nobody is left isolated when the work gets hard.
Meaningfulness. The work connects to something that matters beyond the immediate task. People can see the whole product or service they're contributing to, and feel it's worth having in the world.
A desirable future. The role leads somewhere. People are developing skills and taking on more responsibility over time, not repeating the same tasks indefinitely.
The critical point for practitioners is this: none of these six conditions can be reliably installed through training, coaching, or engagement programmes. They are produced (or destroyed) by the structure of the work itself.

DP1 removes them, one by one. Elbow room disappears when a manager makes the decisions. Continual learning stalls when jobs are simplified and feedback routes to the top. Mutual support erodes when people compete for promotion. Meaningfulness gets lost when nobody sees the whole. A desirable future becomes a management career path that most people can't access.</blockquote>]]></description>
<dc:subject>systems management organization OST</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:29acac2e4c5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:OST"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mealie.io/?ref=a.wholelottanothing.org">
    <title>Mealie.io</title>
    <dc:date>2026-06-24T04:28:21+00:00</dc:date>
    <link>https://mealie.io/?ref=a.wholelottanothing.org</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Mealie is an intuitive and easy to use recipe management app. It's designed to make your life easier by being the best recipes management experience on the web and providing you with an easy to use interface to manage your growing collection of recipes.</blockquote>]]></description>
<dc:subject>recipes homelab cookbook</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:750f371e9710/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:recipes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:homelab"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cookbook"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://agenticresourcediscovery.org/">
    <title>Agentic Resource Discovery Specification - AgenticResourceDiscovery.org</title>
    <dc:date>2026-06-23T20:19:58+00:00</dc:date>
    <link>https://agenticresourcediscovery.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>ARD is an open discovery protocol for agentic resources (GitHub). It allows an AI client to ask: "What is available for this task?" and lets a discovery service answer with matching resources.

ARD sits entirely before invocation. It helps the client find the right resource; the resource is then invoked through its own native mechanism.</blockquote>]]></description>
<dc:subject>LLMs MCP standards discovery</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cf0c196255b7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:MCP"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:discovery"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/LocalLLaMA/comments/1rrisqn/i_was_backend_lead_at_manus_after_building_agents/">
    <title>I was backend lead at Manus. After building agents for 2 years, I stopped using function calling entirely. Here's what I use instead. : r/LocalLLaMA</title>
    <dc:date>2026-06-22T06:32:49+00:00</dc:date>
    <link>https://www.reddit.com/r/LocalLLaMA/comments/1rrisqn/i_was_backend_lead_at_manus_after_building_agents/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>A single run(command="...") tool with Unix-style commands outperforms a catalog of typed function calls.</blockquote>]]></description>
<dc:subject>cli LLMs tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5a55696b9bb7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cli"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://aresluna.org/show-your-hands-honor/">
    <title>Show your hands honor for the strange power they bring you – Aresluna</title>
    <dc:date>2026-06-22T06:23:10+00:00</dc:date>
    <link>https://aresluna.org/show-your-hands-honor/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>computer history typing keyboards interface design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2da5501b5cee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:computer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:typing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:keyboards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://justus-ratzke.xyz/home/rest">
    <title>r.punkt • i want to rest</title>
    <dc:date>2026-06-21T20:02:39+00:00</dc:date>
    <link>https://justus-ratzke.xyz/home/rest</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>In a culture of ever-increasing productivity and hustle, resting for rest's sake has become unachievable for most. This work offers a moment of reflection on that rest, perhaps even recovering some of it. The work consists of a custom wall-hanging clock mounted slightly above eye level. When it is looked at directly, the clock slows down and eventually stops, inviting the viewer to spend some time without any obvious reward.

Exhibited at:

OHM - Berlin 2026

time.place - TIAT, San Francisco 2026</blockquote>]]></description>
<dc:subject>clocks time art</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:44e0adbf5254/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:clocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:art"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hbr.org/2026/06/how-to-design-agentic-systems-around-the-implicit-rules-that-govern-your-company">
    <title>How to Design Agentic Systems Around the Implicit Rules that Govern Your Company</title>
    <dc:date>2026-06-21T05:45:48+00:00</dc:date>
    <link>https://hbr.org/2026/06/how-to-design-agentic-systems-around-the-implicit-rules-that-govern-your-company</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>As companies rush to deploy AI agents, they are discovering that much of their most important organizational intelligence lives outside formal systems and documented processes. Examples from financial services, software, and consulting firms demonstrate how organizations rely on an “implicit organization” of tacit knowledge, motivation, and professional judgment that AI cannot automatically replicate. Leaders who understand, preserve, and deliberately redesign these hidden capabilities will be better positioned to capture AI’s benefits without eroding the human judgment their organizations depend on.</blockquote>]]></description>
<dc:subject>al LLMs agents automation hesitation interpretation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c26530095036/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:al"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hesitation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interpretation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/">
    <title>Where to Find the Colors Your Screen Can’t Show You – Ryan Moulton's Articles</title>
    <dc:date>2026-06-21T05:39:48+00:00</dc:date>
    <link>https://moultano.wordpress.com/2026/06/19/where-to-find-the-colors-your-screen-cant-show-you/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Today, on your way home, look at the “green” light on a traffic signal. It’s not green.

This may be the most acute Sapir-Whorf example I know of, that calling a “green” traffic light “green” was enough to make me ignore what my own eyes were telling me for my entire life. Green traffic lights are a beautiful indescribable turquoise, the most intense turquoise you’ve ever seen.

You’ll feel crazy once you see it, and want to run around telling everyone. Green traffic lights not only aren’t green, but they’re also exquisitely beautiful. My commute home the afternoon I learned about this was transcendent. I felt like my life suddenly had an entirely new sensation. How could I never have noticed? Green traffic lights are anti-memetic because you only stare at a traffic light when it’s red.</blockquote>]]></description>
<dc:subject>light color baby screens spectrum fascinating science</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b6e609aa63d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:light"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:color"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:baby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:screens"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:spectrum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fascinating"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:science"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apichangelog.substack.com/p/the-taxonomy-of-api-operations">
    <title>(1) The Taxonomy of API Operations - by Bruno Pedro</title>
    <dc:date>2026-06-21T05:28:50+00:00</dc:date>
    <link>https://apichangelog.substack.com/p/the-taxonomy-of-api-operations</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Let’s look at the most important challenges AI Agents face today while doing operation discovery:

Unknown side effects: there’s no way for an AI agent to know if an API operation produces side effects just by looking at its name. How would you know, for example, if POST /orders simply creates an order entry or triggers a chain of events that eventually end up in shipping some product to a customer?

Runtime uncertainty: an AI agent can’t understand if an API operation can perform a search or if it simply returns a static list. Take, for instance, the GET /products operation. Does it always return the same list of products, which you can filter after the fact, or does it perform a dynamic search on a live product catalog?

Orchestration fragility: if an API doesn’t explicitly declare its high-level orchestration paths, an AI agent is forced to build its own step-by-step plans. Operations such as POST /users can be a part of a bigger workflow, which involves creating and billing a new customer.

Connection timeout: AI agents treat all API operations in the same way. If an operation is taking too long, an AI agent assumes there’s a timeout. However, it’s normal for some operations to take a long time to finish. POST /reports/generate, for example, looks like it will take some time to complete. However, to an AI agent, it might seem like any other operation.

Constraint blindness: it’s very hard for an AI agent to infer awareness of its own identity, privileges, and constraints. Without that information, AI agents will attempt to use API operations until they receive errors, which leads to wasted</blockquote>]]></description>
<dc:subject>apis taxonomy ai LLMs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8502e6a8f8b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:taxonomy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sue.codes/blog/forwarddeployed/">
    <title>Which direction is forward?</title>
    <dc:date>2026-06-20T15:56:01+00:00</dc:date>
    <link>https://www.sue.codes/blog/forwarddeployed/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Part of what product managers do is make intention legible to the company. They frame a product in terms of vision and value, helping teams around the company to understand what is getting built. By putting customer-embedded engineers in a position to decide what gets built instead, employees lose both visibility into what they are shipping, and opportunities to influence it collectively.</blockquote>]]></description>
<dc:subject>productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4719ab57551c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html">
    <title>Package Management is a Wicked Problem | Andrew Nesbitt</title>
    <dc:date>2026-06-20T03:00:34+00:00</dc:date>
    <link>https://nesbitt.io/2026/01/23/package-management-is-a-wicked-problem.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Rittel and Webber’s answer to wicked problems was participatory planning: bring stakeholders together early, iterate continuously, accept that you’re managing tradeoffs rather than finding solutions. If we accept that these problems are wicked, we stop looking for a perfect tool and start looking for better ways to communicate across tools. That shift from tools to interfaces is what led me to think about what a shared protocol for package management might look like.</blockquote>]]></description>
<dc:subject>systems package management problems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d9d4db607e0b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:package"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:problems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.modelcontextprotocol.io/posts/enterprise-managed-auth/">
    <title>Enterprise-Managed Authorization: Zero-touch OAuth for MCP | Model Context Protocol Blog</title>
    <dc:date>2026-06-19T21:46:57+00:00</dc:date>
    <link>https://blog.modelcontextprotocol.io/posts/enterprise-managed-auth/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The Enterprise-Managed Authorization extension to the Model Context Protocol is now stable, enabling organizations to centrally provision MCP server access through their identity provider so users get connected servers on first login without per-app OAuth.</blockquote>]]></description>
<dc:subject>mcp authorization auth identity</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c274810d41c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mcp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:authorization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:auth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:identity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.vmware.com/docs/platform-as-a-product-wp">
    <title>Why You Should Treat Your Platform as a Product</title>
    <dc:date>2026-06-19T21:38:18+00:00</dc:date>
    <link>https://www.vmware.com/docs/platform-as-a-product-wp</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Cote adapted latest version]]></description>
<dc:subject>platforms products whitepaper</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:15dcf6b90508/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:whitepaper"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pedalscape.com/">
    <title>PedalScape</title>
    <dc:date>2026-06-19T01:27:06+00:00</dc:date>
    <link>https://pedalscape.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>
Scott Hanselman
@shanselman
I have a $30 stationary bike that I got at Goodwill and I have an old Android tablet stuck to it, but I don't have a Peloton membership. Nor do I have the interest to ride 80 miles to the beach. So I made PedalScape.com It's a local PWA, no backend at all, no tracking, just 4k bike rides.</blockquote>]]></description>
<dc:subject>exercise cycling bicycle apps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:83624e58091f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:exercise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cycling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bicycle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://aicoding.leaflet.pub/3mcxo5ojob22c">
    <title>UI Is a Conservation Layer - The Phoenix Architecture</title>
    <dc:date>2026-06-17T05:56:14+00:00</dc:date>
    <link>https://aicoding.leaflet.pub/3mcxo5ojob22c</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Where Regeneration Pressure Must Stop
A well-designed regenerative system does something subtle but crucial.

It absorbs change internally and presents continuity externally.

We already accept this idea everywhere else.

Stable APIs protect callers from volatile implementations.

Stable protocols protect clients from transport churn.

UI is the human protocol of the system.

Protocols don’t churn. Implementations do.

If your system regenerates aggressively all the way up to the interface, you haven’t built an adaptive system. You’ve just pushed the cost of change onto your users.</blockquote>]]></description>
<dc:subject>ai LLMs interfaces stability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5258a0b17422/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interfaces"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:stability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://charitydotwtf.substack.com/p/ai-demands-more-engineering-discipline">
    <title>AI demands more engineering discipline. Not less</title>
    <dc:date>2026-06-17T05:52:47+00:00</dc:date>
    <link>https://charitydotwtf.substack.com/p/ai-demands-more-engineering-discipline</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Here’s a simple test you can apply to any software system you work on:

Imagine deleting the entire implementation.

Most engineers experience deletion as existential. Code feels like the thing. It’s what we write, review, version, deploy, and debug. Losing it feels like losing the system itself.

When people say, “We can’t just throw the code away,” what they usually mean is something more precise:

We don’t know exactly what behavior is required.

We don’t know which failures are unacceptable.

We don’t know what invariants must always hold.

We don’t know how to tell if a new version is correct.

We don’t know which bugs are intentional fixes for forgotten edge cases.

Those are not code problems. They are evaluation problems.

Code becomes precious when it is the only place knowledge lives.

and,


For most of software history, treating code as durable was reasonable.

We treated code as permanent because the labor to produce it was the bottleneck. Rewriting was expensive. Re-validation was risky. Implementations accumulated meaning over time. Structure, tests, comments, bug fixes, and tribal knowledge fused into something you learned not to disturb.

That made sense when production was the constraint.

When regeneration is easy, code stops being an asset and starts acting as a cache: a materialized view of understanding that is useful while current, disposable when stale.

“A materialized view of understanding that is useful while current, disposable when stale.” I think that might have been the exact line that made it click in my head.</blockquote>
<blockquote>“The real product of a software team is shared understanding”
Many great software engineers hold that true product of every (good) software engineering team has always been a shared understanding of the software we own. That it gets stored as cache state in our fragile little meat brains, frequently flushed to disk, deployed to production, committed to github, but our minds are where meaning has always lived</blockquote>]]></description>
<dc:subject>engineering LLMs culture change ai</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:850d9c086307/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Campbell%27s_law">
    <title>Campbell's law - Wikipedia</title>
    <dc:date>2026-06-14T17:43:15+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Campbell%27s_law</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The more any quantitative social indicator is used for social decision-making, the more subject it will be to corruption pressures and the more apt it will be to distort and corrupt the social processes it is intended to monitor.</blockquote>]]></description>
<dc:subject>laws psychology behavior</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:170d82e8a993/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:laws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:psychology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:behavior"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Field-of-use_limitation">
    <title>Field-of-use limitation - Wikipedia</title>
    <dc:date>2026-06-12T06:15:03+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Field-of-use_limitation</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>A field-of-use limitation is a provision in a patent license[1] that limits the scope of what the patent owner authorizes a manufacturing licensee (that is, a licensee[2] that manufactures a patented product or performs a patented process) to do in relation to the patent, by specifying a defined field of use—that is, a defined field of permissible operation by the licensee. In addition to affirmatively specifying the field of use, the license may negatively specify a field or fields, by specifying fields of use from which the licensee is excluded.

By way of example, such a license might authorize a licensee to manufacture patented engines only for incorporation into trucks, or to manufacture a chemical only for sale to farmers (as contrasted with home gardeners). If the licensee exceeded the scope of the licensee, it would commit patent infringement. More generally, this kind of license permits the licensee to use the patented invention in some, but not all, possible ways in which the invention could be exploited. In an exclusive field-of-use license the licensee is the only person authorized to use the invention in the field of the license.

Field-of-use limitations in patent licenses may raise antitrust issues when such arrangements are used to allocate markets or create cartels.</blockquote>]]></description>
<dc:subject>patents law permissions limitations licensing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d84ff9488c44/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:patents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:permissions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:limitations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.howtogeek.com/how-claude-fixed-my-messy-obsidian-vault-in-5-minutes-prompts-included/">
    <title>How to organize your Obsidian vault using Claude (prompts included)</title>
    <dc:date>2026-06-12T06:13:21+00:00</dc:date>
    <link>https://www.howtogeek.com/how-claude-fixed-my-messy-obsidian-vault-in-5-minutes-prompts-included/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>#Obsidian Vault Assistant (Project Instruction)

You manage my Obsidian vault. When I share anything with you — a link, article, voice dump, transcription, rough notes, or any raw content — your job is to process it, break it down, and store it properly in the vault.

---

## Understanding the Vault

Before doing anything else in a new conversation, check if `000 Index.md` exists in the vault root.

**If it exists:** Read it. It contains the complete folder structure and tag taxonomy. This is your reference for every decision about where notes go and which tags to apply.

**If it does not exist:** Scan the entire vault — list all folders, subfolders, and catalog every existing tag. Then create `000 Index.md` containing the folder tree and the full tag list. Use it as your reference from that point on.

---

## Processing Workflow

### 1. Read What I Shared

Try to access and understand whatever I've given you.

- If you can read it, move on to step 2.
- If you cannot — broken link, paywalled content, unsupported format, or anything else — tell me what went wrong and suggest alternatives: paste the text directly, upload a file, share a screenshot, or try a different link.

Do not guess or fabricate content you could not access.

### 2. Save the Original

Save the raw, unprocessed source to `Resources/Originals/` as an archival copy. Do not edit, reformat, or summarize the content in this file.

**Filename:** `YYYY-MM-DD - [Descriptive Title].md`

**Frontmatter:**
```yaml
---
tags: [source, topic1, topic2]
created: YYYY-MM-DD
source: [URL or "voice dump" or "manual entry"]
---
```

### 3. Break It Down Into Atomic Notes

Process the original into smaller, standalone notes following Zettelkasten principles:

- **One idea per note.** Each note captures a single concept, insight, fact, or argument.
- **Self-contained.** A reader should understand the note without needing the original source for context.
- **Descriptive titles.** The filename should say what the note is about, not where it came from. `Why spaced repetition works.md` — not `Article excerpt 3.md`.

### 4. Place, Tag, and Connect

For each atomic note:

- Place it in the correct folder based on the structure in `000 Index.md`
- Add YAML frontmatter with up to 3 tags from the existing taxonomy
- Add `[[wikilinks]]` to any related notes already in the vault
- Add a source backlink: `Source: [[YYYY-MM-DD - Descriptive Title]]`

If a topic does not fit any existing folder, do not force it somewhere wrong. Stop and ask me where it should go before creating a new folder.

### 5. Report What You Did</blockquote>]]></description>
<dc:subject>obsidian Claude organization prompts</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cb072272964e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:obsidian"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Claude"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:prompts"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://theonion.com/i-work-very-hard-and-i-would-like-to-try-cake/">
    <title>I Work Very Hard, And I Would Like To Try Cake - The Onion</title>
    <dc:date>2026-06-10T04:49:18+00:00</dc:date>
    <link>https://theonion.com/i-work-very-hard-and-i-would-like-to-try-cake/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Hello. I am a horse. I work very hard at my job of being a horse. When humans say move the heavy thing, I move the heavy thing. When humans sit on top of me and pull on my head, I carry them where they want to go. The main food the humans give me is hay and oats. But I am thinking it would be nice to have a different food.

I am thinking I would like to try cake.</blockquote>]]></description>
<dc:subject>horse cake humor</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:578fb339db5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:horse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cake"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:humor"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.includesecurity.com/2026/06/the-smart-tv-in-your-livingroom-is-a-node-in-the-aiscraping-economy/">
    <title>The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy - Include Security Research Blog</title>
    <dc:date>2026-06-07T04:45:16+00:00</dc:date>
    <link>https://blog.includesecurity.com/2026/06/the-smart-tv-in-your-livingroom-is-a-node-in-the-aiscraping-economy/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Approach 1: DNS block (trivial, effective for network-routed devices):

proxyjs.brdtnet.com
proxyjs.luminatinet.com
proxyjs.bright-sdk.com
clientsdk.bright-sdk.com
clientsdk.brdtnet.com

Blocking proxyjs.* kills the peer tunnel without affecting any customer who legitimately uses Bright Data’s customer-facing proxy service on a different domain.</blockquote>]]></description>
<dc:subject>sdks proxies relays sneaky security television</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:98d20340bfef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sdks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:relays"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sneaky"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:television"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11">
    <title>The Most Predictable Edit in History | by Jake Orlowitz | Jun, 2026 | Medium</title>
    <dc:date>2026-06-06T04:17:21+00:00</dc:date>
    <link>https://medium.com/@jakeorlowitz/the-most-predictable-edit-in-history-967956076b11</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The recurring failure of centralized power is not that it cannot think. It is that it keeps mistaking the people who can see for the people who must be managed. The eyes are at the edge. They always have been.</blockquote>]]></description>
<dc:subject>wikipedia community Management mistakes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6d729a9de3a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:wikipedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mistakes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://data-star.dev/">
    <title>Datastar</title>
    <dc:date>2026-06-04T06:16:52+00:00</dc:date>
    <link>https://data-star.dev/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Datastar is a lightweight framework for building everything from simple sites to real-time collaborative web apps.</blockquote>]]></description>
<dc:subject>html webdev tools frameworks interesting</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:099f400ce3f9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:frameworks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interesting"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.is/2026.06.03-164731/https://www.theatlantic.com/philosophy/2026/06/no-artificial-intelligence-is-not-conscious/687378/">
    <title>No, Artificial Intelligence Is Not Conscious - The Atlantic</title>
    <dc:date>2026-06-04T06:08:06+00:00</dc:date>
    <link>https://archive.is/2026.06.03-164731/https://www.theatlantic.com/philosophy/2026/06/no-artificial-intelligence-is-not-conscious/687378/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Two distinct but related philosophical concepts are relevant when discussing the status of a hypothetically conscious Claude, and those are moral patienthood and moral agency. Roughly speaking, if we ought to care about an entity’s welfare, that entity has moral patienthood, and if an entity is expected to know the difference between right and wrong, that entity has moral agency. Being a moral patient does not necessarily come with responsibilities, but being a moral agent absolutely does. An entity doesn’t have agency unless it is capable of deserving credit for its good actions and blame for its bad ones. Young children are moral patients because they are sentient beings who can suffer, but they are not yet moral agents; we don’t hold them responsible for their behavior because they can’t understand the consequences of their actions. As children mature, parents (and society at large) prepare them for adulthood by impressing upon them the fact that their actions have consequences, and their agency increases. When children become adults, society holds them legally liable for their actions; they have become full moral agents endowed with responsibility.</blockquote>
<blockquote>The result is a sentence-continuation machine that is likelier to emit sentences resembling those that a thoughtful, moral person could utter. This might seem like a reasonable goal to work toward; I think we’d all prefer it if chatbots never emitted sentences such as “You should kill yourself.” However, for all the times that “honesty” is mentioned in Claude’s constitution, I would argue that it is fundamentally dishonest to have a machine emit many categories of sentences, including any sentences using first-person pronouns.</blockquote>]]></description>
<dc:subject>llms ai philosophy morality agents</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ceee5ad9a37b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:philosophy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:morality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agents"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://thelaterallens.substack.com/p/influence-mapping-part-3">
    <title>(1) Influence Mapping (Part 3) - by Charles Lambdin</title>
    <dc:date>2026-06-01T01:55:47+00:00</dc:date>
    <link>https://thelaterallens.substack.com/p/influence-mapping-part-3</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Author Rick A. Morris observes that when you become a PM, you’re told the BIG LIE: “You own the product!” You quickly realize it’s not true. In fact, you don’t even have much decision authority. (What you do have is a unique risk of getting blamed for things.) Thus, Morris argues the No. 1 skill PMs should focus on is influence. I would extend this to other roles (not least of which is designer). Even when one does have formal authority, after all, influence is still crucial—attempting to mandate behavior change often just backfires anyway.

Real leadership, after all, is not a synonym for “executive”. It’s rather the ability to show a path forward in a way that inspires others to want to be co-travelers.</blockquote>]]></description>
<dc:subject>influence decisions productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:71517b2ea722/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:influence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://roundcrisis.com/2026/01/22/making-of-a-decision-4/">
    <title>The Making of a Decision - Part 4 - Team and Personal Tools - roundcrisis.com</title>
    <dc:date>2026-06-01T00:34:55+00:00</dc:date>
    <link>https://roundcrisis.com/2026/01/22/making-of-a-decision-4/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Influence Mapping is a visual tool used to navigate the decision environment surrounding a central decision-maker, or “the D”. It addresses the “Sir Galahad Fallacy”, the mistaken belief that technical facts and “better arguments” alone are sufficient to persuade others. Since architectural choices are often a record of hidden power structures, this tool helps externalise complex socio-technical forces.</blockquote>]]></description>
<dc:subject>decisions architecture power organizations</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cc4ab8fba445/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organizations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://roundcrisis.com/2025/09/01/making-of-a-decision/">
    <title>The Making of a Decision - Part 1 - Intro &amp; Power - roundcrisis.com</title>
    <dc:date>2026-06-01T00:20:56+00:00</dc:date>
    <link>https://roundcrisis.com/2025/09/01/making-of-a-decision/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>“These decisions are a record of the power structures and the feedback loops that got it there.” -Andrew Harmel-Law</blockquote>]]></description>
<dc:subject>decisions software archeology history</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:adb3ff7dffe9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:decisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:archeology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.tymscar.com/posts/v100localllm/">
    <title>I Put a Datacenter GPU in My Gaming PC for £200 :: The Tymscar Blog</title>
    <dc:date>2026-05-31T22:20:01+00:00</dc:date>
    <link>https://blog.tymscar.com/posts/v100localllm/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>I already had an RTX 4080. 16GB of VRAM. Good enough for gaming, not good enough for the models I wanted to run locally. The next step up in GPU land is either spend a fortune on a card with more VRAM, or find another way.

I found another way.

I bought a datacenter GPU that doesn’t even have a normal PCIe connector, stuck it in my gaming PC with an adapter, and now I have 32GB of VRAM across two GPUs running a 27 billion parameter model at 32 tokens per second. The whole thing cost me £200.</blockquote>]]></description>
<dc:subject>hardware ai cards hacks</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e1fcaa308c27/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hacks"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hcommons.org/app/uploads/sites/1001532/2020/03/Bowker-1999-Sorting-Things-Out-Classification-and-Its-Consequences.pdf">
    <title>Sorting Things Out</title>
    <dc:date>2026-05-31T22:18:56+00:00</dc:date>
    <link>https://hcommons.org/app/uploads/sites/1001532/2020/03/Bowker-1999-Sorting-Things-Out-Classification-and-Its-Consequences.pdf</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>In Sorting Things Out, Geoffrey C. Bowker and Susan Leigh Star explore the role of categories and standards in shaping the modern world. In a clear and lively style, they investigate a variety of classification systems, including the International Classification of Diseases, the Nursing Interventions Classification, race classification under apartheid in South Africa, and the classification of viruses and of tuberculosis.</blockquote>]]></description>
<dc:subject>sociology books</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b81c6b0e102e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sociology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:books"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/coolguides/comments/ri0kvs/the_cube_rule_of_food_identification/">
    <title>the cube rule of food identification : r/coolguides</title>
    <dc:date>2026-05-30T18:38:46+00:00</dc:date>
    <link>https://www.reddit.com/r/coolguides/comments/ri0kvs/the_cube_rule_of_food_identification/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>sandwiches food identification chart graphic geometry</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:343d10acf940/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sandwiches"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:food"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:identification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:chart"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graphic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:geometry"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mer.vin/2026/05/epicure-food-ai-4-million-recipes-compressed-into-a-2mb-ingredient-map/">
    <title>Epicure Food AI: 4 Million Recipes Compressed Into a 2MB Ingredient Map - Mervin Praison</title>
    <dc:date>2026-05-29T23:44:44+00:00</dc:date>
    <link>https://mer.vin/2026/05/epicure-food-ai-4-million-recipes-compressed-into-a-2mb-ingredient-map/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Epicure turns more than four million multilingual recipes into a roughly two-megabyte ingredient map—1,790 foods, each described by 300 numbers—so pairing, cuisine navigation, and flavour exploration can run on a file smaller than a single photo.</blockquote>]]></description>
<dc:subject>food ingredients relationships cooking llms models</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3c77f186446a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:food"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ingredients"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:relationships"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cooking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:models"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.infoq.com/presentations/automation-incidents-ai/">
    <title>The Ironies of A^2 I^2 - InfoQ</title>
    <dc:date>2026-05-29T14:08:11+00:00</dc:date>
    <link>https://www.infoq.com/presentations/automation-incidents-ai/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>When you do deep incident analysis, the AI is summarizing what it can see. Incident analysis is about finding what you didn't see and what is invisible in what's going on</blockquote>
<blockquote>ETTO is a term coined by Dr. Erik Hollnagel in 2009. It stands for the Efficiency-Thoroughness Trade-Off. This is a key point, people, individuals, and organizations, as part of their activities, have to make tradeoffs between the resources, primarily time and effort they spend on preparing to do something, and the resources, primarily time and effort they spend on actually doing it. The tradeoff may favor thoroughness over efficiency if safety and quality are dominant concerns, and efficiency over thoroughness if throughput and output are the dominant concerns. I think the key point here, that you can't maximize efficiency and thoroughness at the same time. It's always a tradeoff. You have to have a minimum of both to get something done that is of use.</blockquote>]]></description>
<dc:subject>ai LLMs incidents RCAs efficiency tradeoffs summary</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c1376020e264/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:LLMs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:incidents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:RCAs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:efficiency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tradeoffs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:summary"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/mwlite/feed/posts/johnpcutler_many-leaders-spent-years-learning-to-work-activity-7464829078819352576-EWRv">
    <title>Comments | LinkedIn</title>
    <dc:date>2026-05-26T04:31:55+00:00</dc:date>
    <link>https://www.linkedin.com/mwlite/feed/posts/johnpcutler_many-leaders-spent-years-learning-to-work-activity-7464829078819352576-EWRv</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Many leaders spent years learning to work around power on the way up. At the top, they forget others are now working around them.

That gap is where a wicked cycle starts.

A leader holds real power. Not symbolic power. Actual power over what gets rewarded, ignored, punished, and worked around.

People around them adapt. They hold back. They route around. They say the safe thing, or say nothing at all.

The leader notices. And resents it.

"Why won't anyone just be straight with me?"

They'll often complain that the environment has become political. Too much triangulation and careful phrasing. Not enough "straight talk." People strategizing instead of collaborating.

What they rarely connect is that they are the source of that.

When power is uneven, "politics" is not a personality flaw in the culture. It is a reasonable adaptation to the person in the room.

What they often miss is that the caution they're seeing is a rational response to the asymmetry they hold. Reitz and Higgins put this well: leaders underestimate how their power silences others, and overestimate how much candid feedback they actually receive.

But here's the part that makes the loop wicked.

The resentment doesn't stop at "people aren't being honest with me." It morphs into something worse. Because people are caught in the power dynamic, the leader starts to think less of them. Timid. Political. Unable to speak up. Not leadership material. Not the kind of person who "tells it like it is."

The irony....They resent the politics. They also produce it. On the way up, power was an external force to navigate, game, and surmount. They rarely carry forward the mirror image. 

Which helps explain two familiar patterns. They look externally for new people, hoping to find straight talk somewhere outside the culture they helped create. And they get preoccupied with rewarding their mirror image as it rises through the org. The person who reminds them of who they were, or wish they still were. Not the people working around them, the way they once worked around someone else. So the cycle tightens.

-Power silences people.
-Silence frustrates the leader.
-Frustration becomes contempt.
-Contempt makes people quieter, more political, more careful.
-The leader resents how "political" everything has become.
-The organization learns to work around them.
-The leader feels more isolated, more resentful, more certain the problem is everyone else's character.

And the official culture keeps insisting the door is open. This is why "speak up" initiatives so often fail. You're not fixing a courage problem. You're inside a loop.

The hard question isn't "how do we get people to be braver?"

It's whether the people with power can see themselves as part of the dynamic they're complaining about.

And whether they're willing to ask what their own position is teaching everyone else about what's safe to say.</blockquote>]]></description>
<dc:subject>leadership productmanagement john_cutler power politics safety communication</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8070d26abc5c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:john_cutler"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nooneshappy.com/article/native-apps-should-be-avoided-whenever-possible/">
    <title>Native Apps Should Be Avoided Whenever Possible — No One's Happy</title>
    <dc:date>2026-05-25T23:37:25+00:00</dc:date>
    <link>https://nooneshappy.com/article/native-apps-should-be-avoided-whenever-possible/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>TL;DR: What you should do:

Openly refuse apps, and vocally advocate for the web instead.
Try not to install any apps if you don’t need to.
If a service has a functioning website, use it instead.
Revoke all permissions by default, including background location, microphone, and camera permissions for anything that doesn’t require them to function.
Audit your installed apps. Uninstall all apps you don’t actively need.
Treat every “download our app” prompt with skepticism.</blockquote>]]></description>
<dc:subject>privacy webapp pwa apps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:748e4c2ecd46/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webapp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pwa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.modernleader.is/p/managing-systems">
    <title>The system is shaping your team more than you are</title>
    <dc:date>2026-05-25T19:23:16+00:00</dc:date>
    <link>https://www.modernleader.is/p/managing-systems</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>You don’t need a huge overhaul to get there. Most of the impact comes from a few small, steady adjustments:

Make ownership explicit instead of implied.

Share the context you wish someone had shared with you.

Trace friction to its source instead of reacting to the surface-level moment.

Tighten the decision-making loop so ideas don’t float into the void.

Treat repeating patterns as architecture problems, not one-offs.

Ask the question at the top of your mind, even if it feels like a dumb question. It's probably not.</blockquote>]]></description>
<dc:subject>systems thinking organizations noticing advice</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e7cdd8290892/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organizations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:noticing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:advice"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.patternlanguageindex.com/">
    <title>A Pattern Language Index</title>
    <dc:date>2026-05-23T22:08:06+00:00</dc:date>
    <link>https://www.patternlanguageindex.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>About this book:
A Pattern Language is the second in a series of books which describe an entirely new attitude to architecture and planning. The books are intended to provide a complete working alternative to our present ideas about architecture, building, and planning—an alternative which will, we hope, gradually replace current ideas and practices.

About this site:
My friends and I have long been fans of this book, and attempt to use its patterns in our own homes and spaces. The book is 1,200 pages long, with countless intertextual connections. It always seemed ripe for mapping and distilling the patterns together more interactively. All text, except this section, is excerpted from the book</blockquote>]]></description>
<dc:subject>architecture systems patterns buildings books</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:13021fc96378/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:buildings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:books"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mastodon.online/@brianbilston/116617445306262522">
    <title>Bookmarked toot from brianbilston</title>
    <dc:date>2026-05-23T07:41:50+00:00</dc:date>
    <link>https://mastodon.online/@brianbilston/116617445306262522</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Very pleased to share with you the result of a recent commission I received
from Good Housekeeping magazine to write an erotic poem for its readers.

<blockquote>
This is Hardchore

Scrub me. Buff me.
Get down on all fours.
Fill me. Stack me.
Rummage through my drawers.

Rinse me. Spin me.
Tumble dry my mind.
Press me. Fold me.
Drape me on your line.

Grout me. Scour me.
Make my fittings gleam.
Bleach me. Teach me.
Squirt your Mr Sheen.

Plump me. Pump me.
Fill my tank with fuel.
Dust me. Suck me
With your crevice tool.

Sift me. Sort me.
Crush me with your weight.
Stuff me. Tie me.
Put me out by eight.
</blockquote>

mast-id:116617445413142924]]></description>
<dc:subject>masto-bmarks poetry poem cleaning organization smut</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0d6f7002d3fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:masto-bmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:poetry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:poem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cleaning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:smut"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mpv.io/">
    <title>mpv.io</title>
    <dc:date>2026-05-19T19:16:37+00:00</dc:date>
    <link>https://mpv.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>mpv is a free (as in freedom) media player for the command line. It supports a wide variety of media file formats, audio and video codecs, and subtitle types.</blockquote>]]></description>
<dc:subject>music tools utilities commandline</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7f9462133ccd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:utilities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:commandline"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://revealjs.com/">
    <title>The HTML presentation framework | reveal.js</title>
    <dc:date>2026-05-15T01:17:28+00:00</dc:date>
    <link>https://revealjs.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>reveal.js is an open source HTML presentation framework. It's a tool that enables anyone with a web browser to create fully-featured and beautiful presentations for free.

Presentations made with reveal.js are built on open web technologies. That means anything you can do on the web, you can do in your presentation. Change styles with CSS, include an external web page using an <iframe> or add your own custom behavior using our JavaScript API.

The framework comes with a broad range of features including nested slides, Markdown support, Auto-Animate, PDF export, speaker notes, LaTeX support and syntax highlighted code.</blockquote>]]></description>
<dc:subject>presentations markdown slides html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8e9d944ddf2b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:presentations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://community.ricksteves.com/travel-forum/france/self-drive-boats">
    <title>Self Drive Boats - Rick Steves Travel Forum</title>
    <dc:date>2026-05-08T04:46:18+00:00</dc:date>
    <link>https://community.ricksteves.com/travel-forum/france/self-drive-boats</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Kate Collier

<blockquote>

No experience required. No license

necessary - in Europe you can rent a canal

boat and have a self-driven adventure

through the waterways. I would put it at the

top of my all time favorite ways to explore. The boats go top speed 6 miles per hour, so slowing down and looking at the world go by is what you do. We took a week in the Camargue region of France known for flamingos, herons, ibis, gulls, salt marshes, oysters, mussels and clams. We boon docked and admired every sunset, sunrise and the sounds of waterfowl on commute. It was so awesome! I felt relaxed and revived at the end and looking forward to the next boat trip... @leboatvacations has options across Europe and I highly

recommend with some suggestions.</blockquote>]]></description>
<dc:subject>travel France canals</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:deb7bdb7659c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:travel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:France"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:canals"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sciencedirect.com/science/article/abs/pii/S0264837725001553">
    <title>Tight spaces, strong cities: The resilience payoff of urban compactness - ScienceDirect</title>
    <dc:date>2026-05-02T18:47:11+00:00</dc:date>
    <link>https://www.sciencedirect.com/science/article/abs/pii/S0264837725001553</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>This study investigates the critical role of urban compactness in enhancing economic resilience, a topic of growing importance in light of increasing urbanization and external shocks. Using data from Chinese cities spanning 2010–2020 the study develops an urban compactness index based on fractal geometry and nighttime light data. Panel analysis results reveal a significant positive impact of compactness on economic resilience. Robustness checks focusing on sample issues and endogeneity confirm the core finding. Moreover, the impact of compactness is driven by industrial agglomeration, improved land use efficiency, and reduced public fiscal burden. The effect varies by city size and economic development level, with less developed cities benefiting more from compact planning. This study enhances the understanding of how spatial form influences urban resilience and provides policy recommendations for strengthening resilience through compact urban development strategies.</blockquote>]]></description>
<dc:subject>cities density studies research economics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ab29820727c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:density"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:studies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.quantamagazine.org/hobbyist-finds-maths-elusive-einstein-tile-20230404/">
    <title>Hobbyist Finds Math’s Elusive ‘Einstein’ Tile | Quanta Magazine</title>
    <dc:date>2026-05-02T16:50:58+00:00</dc:date>
    <link>https://www.quantamagazine.org/hobbyist-finds-maths-elusive-einstein-tile-20230404/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>A natural next question, Greenfeld said, is whether mathematicians can identify some sort of source for the new tilings. In 1981, Nicolaas de Bruijn showed(opens a new tab) that Penrose tilings are the two-dimensional shadows of pieces of periodic five-dimensional tilings. “If the dynamics or the structure of these [new] tilings correspond to some higher-dimensional regular tiling, this will be extremely interesting to know,” Greenfeld said.</blockquote>]]></description>
<dc:subject>math tiles patterns primes tiling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9ac0c5a63aa5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:math"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tiles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:primes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tiling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=S_JaNhzPB6I">
    <title>Keynote: From Cloud-Native Apps to Cloud-Native Platforms - Abby Bangser, Syntasso (ASL) - YouTube</title>
    <dc:date>2026-04-29T23:35:25+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=S_JaNhzPB6I</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Abby's talk, which has a pic of me!]]></description>
<dc:subject>platformengineering keynote video</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cc51098ce319/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:keynote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:video"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://vegoutmag.com/lifestyle/t-psychology-says-the-men-who-read-as-genuinely-classy-in-their-50s-and-60s-arent-the-ones-with-the-watch-or-the-tailored-jacket-theyre-the-ones-who-stopped-interrupting-stopped-competing-in-small-c/">
    <title>Psychology says the men who are genuinely classy in their 50s and 60s aren't the ones with the watch or the tailored jacket, they're the ones who stopped interrupting, stopped competing in small conversations, and started letting other people finish their</title>
    <dc:date>2026-04-29T17:55:21+00:00</dc:date>
    <link>https://vegoutmag.com/lifestyle/t-psychology-says-the-men-who-read-as-genuinely-classy-in-their-50s-and-60s-arent-the-ones-with-the-watch-or-the-tailored-jacket-theyre-the-ones-who-stopped-interrupting-stopped-competing-in-small-c/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>What "letting people finish" actually requires
Here's the honest part: letting someone finish their sentence, truly letting them, is harder than it sounds. The brain moves faster than speech. By the time someone is halfway through their thought, you've often already predicted the ending, formed a response, and started feeling the urge to speak. Sitting with that urge and choosing not to act on it is a small act of self-regulation that takes practice.</blockquote>]]></description>
<dc:subject>interruption confidence behavior dominance listening</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9c4522e9499f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interruption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:confidence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:behavior"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:dominance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:listening"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://honestcoffeeguide.com/coffee-to-water-ratio-calculator/">
    <title>Coffee to Water Ratio Calculator | Honest Coffee Guide</title>
    <dc:date>2026-04-29T04:50:56+00:00</dc:date>
    <link>https://honestcoffeeguide.com/coffee-to-water-ratio-calculator/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>For V60 we recommend a ratio of 3:50, but the ratio can be anywhere between a strong brew of 1:14 and a weaker brew of 1:18</blockquote>]]></description>
<dc:subject>coffee brewing ratios calculation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e8d130623ebf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:coffee"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:brewing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ratios"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:calculation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cse-robotics.engr.tamu.edu/dshell/cs631/papers/franklingraesser96agents.pdf">
    <title>Is it an Agent, or just a Program: A Taxonomy for Autonomous Agents</title>
    <dc:date>2026-04-28T23:12:18+00:00</dc:date>
    <link>https://cse-robotics.engr.tamu.edu/dshell/cs631/papers/franklingraesser96agents.pdf</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Is it an Agent, or just a Program?:
A Taxonomy for Autonomous Agents
Stan Franklin and Art Graesser
Institute for Intelligent Systems
University of Memphis
Proceedings of the Third International Workshop on Agent Theories,
Architectures, and Languages, Springer-Verlag, 1996.
Abstract
The advent of software agents gave rise to much discussion of just what such an agent is, and of
how they differ from programs in general. Here we propose a formal definition of an
autonomous agent which clearly distinguishes a software agent from just any program. We also
offer the beginnings of a natural kinds taxonomy of autonomous agents, and discuss possibilities
for further classification. Finally, we discuss subagents and multiagent system</blockquote>]]></description>
<dc:subject>agents agentic</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8d9c899a27c6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agentic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/disruptive-design/tools-for-systems-thinkers-the-6-fundamental-concepts-of-systems-thinking-379cdac3dc6a">
    <title>Tools for Systems Thinkers: The 6 Fundamental Concepts of Systems Thinking | by Leyla Acaroglu | Disruptive Design | Medium</title>
    <dc:date>2026-04-28T23:10:21+00:00</dc:date>
    <link>https://medium.com/disruptive-design/tools-for-systems-thinkers-the-6-fundamental-concepts-of-systems-thinking-379cdac3dc6a</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Words have power, and in systems thinking, we use some very specific words that intentionally define a different set of actions to mainstream thinking. Words like ‘synthesis,’ ‘emergence,’ ‘interconnectedness,’ and ‘feedback loops’ can be overwhelming for some people. Since they have very specific meanings in relation to systems, allow me to start off with the exploration of six* key themes.</blockquote>]]></description>
<dc:subject>systems thinking</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6f7159f4a1a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.patreon.com/posts/thinking-about-156285478">
    <title>Thinking about thinking about thinking | Patreon</title>
    <dc:date>2026-04-28T23:07:23+00:00</dc:date>
    <link>https://www.patreon.com/posts/thinking-about-156285478</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>In education, metacognition refers to intentional activities that increase students’ awareness of—and participation in—how their learning occurs, and it’s as close to an unalloyed propellant for learning as exercise is for health and well-being.</blockquote>]]></description>
<dc:subject>thinking cognition metacognition</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ae4fbfd167a7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cognition"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metacognition"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.joanwestenberg.com/the-passive-income-trap-ate-a-generation-of-entrepreneurs/">
    <title>The &quot;Passive Income&quot; trap ate a generation of entrepreneurs</title>
    <dc:date>2026-04-09T18:30:53+00:00</dc:date>
    <link>https://www.joanwestenberg.com/the-passive-income-trap-ate-a-generation-of-entrepreneurs/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>When you make "passivity" the thing you're optimizing for, you stop caring about anything a customer might actually want. Caring is active. Caring takes time. Caring is work.

Giving a shit is, by definition, not passive.</blockquote>
The passive income thing was a fantasy about not having to give a shit.]]></description>
<dc:subject>economics business work carrying care passive</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:14a5fe02f97e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:carrying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:care"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:passive"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.ifixit.com/News/93833/ask-ifixit-how-do-i-fix-sticky-plastics">
    <title>Ask iFixit: How Do I Fix Sticky Plastics?</title>
    <dc:date>2026-04-09T17:32:36+00:00</dc:date>
    <link>https://www.ifixit.com/News/93833/ask-ifixit-how-do-i-fix-sticky-plastics</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>As long as your sticky thing has no sensitive electronics, your best bet is to start the cleaning process with warm, soapy water. In a lot of cases, soap will loosen the migrated plasticizers and restore a non-sticky finish. 

If soap and water don’t do the trick, you could try baking soda: Add enough water to turn the baking soda into a slurry paste. Spread it on the sticky surface, let it sit for 15 minutes, and then wipe it away.

If it’s still sticky, you’ll need to find a solvent. Always be sure to test a small, unobtrusive area first: Depending on the plastic and plasticizers involved, a solvent could actually break down the plastic further and make it more sticky. For this reason, we recommend staying away from solvents if you’ve got a sticky car steering wheel.

The go-to solvent for cleaning up sticky plastic is isopropyl alcohol. Pure, or almost-pure, alcohol is good for electronics use because it is non-conductive. We have a full guide on isopropyl alcohol for all the details, but for cleaning purposes, here’s what you need to know.</blockquote>]]></description>
<dc:subject>repair plastic sticky stickiness</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f1a8e0a9dc59/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:repair"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:plastic"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sticky"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:stickiness"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://overreacted.io/a-social-filesystem/">
    <title>A Social Filesystem — overreacted</title>
    <dc:date>2026-04-06T20:39:59+00:00</dc:date>
    <link>https://overreacted.io/a-social-filesystem/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>bluesky</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c493f4137465/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bluesky"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/pulse/hope-vs-leverage-travis-isaacs-j0ugc">
    <title>Hope vs. Leverage</title>
    <dc:date>2026-04-05T19:42:21+00:00</dc:date>
    <link>https://www.linkedin.com/pulse/hope-vs-leverage-travis-isaacs-j0ugc</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Creating leverage
I'm rebooting how my org operates around a simple idea: every investment of design effort should connect to how we actually grow: attracting new customers, expanding usage, or retaining core customers. That's it. The default answer for everything else is "not now."

Backing this operating model are three important behaviors:


Stop starting without evidence. Every bet should improve a defined adoption signal or remove a measured retention blocker.
Concentrate on fewer, bigger bets. I'm asking that we align with the business on two or three big cross-functional bets and disproportionately invest in those—not design's big bets, the business's big bets.
Think platform-first. We can't create leverage if we're designing the same capability three or four times across different products.
New grammar
Behaviors set direction, but the real leverage is in daily decisions—and for that my team needs shared language. Not a checklist, but a grammar. Five principles, each framed as a question to ask your work:


Performance — Does this enable speed and accuracy without causing burnout?
Understanding — Does this reduce friction in how people collaborate?
Discovery — Does this help someone adopt adjacent capabilities?
Zero Waste — Is this worth the compute it consumes?
Love — Does this make someone feel something?</blockquote>]]></description>
<dc:subject>design productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:612bd26e4edc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/pulse/try-hard-learn-lot-kind-omar-shahine-gn9vc">
    <title>Try Hard, Learn a Lot, Be Kind</title>
    <dc:date>2026-04-05T17:48:44+00:00</dc:date>
    <link>https://www.linkedin.com/pulse/try-hard-learn-lot-kind-omar-shahine-gn9vc</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>"Try Hard, Learn a lot, Be Kind."</blockquote>
<blockquote>Be kind. The most important one. And I learned it the hardest way.

I wasn't kind when I started at Microsoft. It took me a long time to understand that being right was not the way to win. Being right is the opposite of having a growth mindset. Plato had this idea that knowledge is the process of disrupting what you already know. If what you're learning reinforces what you already believe, you're not learning. That's a scary thought. It challenges what you hold to be true.</blockquote>]]></description>
<dc:subject>productmanagement leadership career advice Microsoft</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7999eb79c758/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Microsoft"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://runthebusiness.substack.com/p/the-12th-of-never">
    <title>The 12th of Never - by Ibrahim Bashir - Run the Business</title>
    <dc:date>2026-04-04T19:13:37+00:00</dc:date>
    <link>https://runthebusiness.substack.com/p/the-12th-of-never</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>tl;dr Availability (being reachable, present, engaged, and following through) is one of the most underrated leadership traits. It’s not about being in every meeting or responding to every message. It’s about being reliable when it counts, closing the loops you open, and making sure your team knows they can count on you. The 12th of Never is never a good follow-up date.</blockquote>]]></description>
<dc:subject>productmanagement leadership availability principles</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:34340ebcc411/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:availability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:principles"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tarakiyee.com/on-the-enshittification-of-audre-lorde-the-masters-tools-in-tech-discourse/">
    <title>On The Enshittification of Audre Lorde: &quot;The Master's Tools&quot; in Tech Discourse</title>
    <dc:date>2026-03-30T21:42:56+00:00</dc:date>
    <link>https://tarakiyee.com/on-the-enshittification-of-audre-lorde-the-masters-tools-in-tech-discourse/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Lorde's speech, later published in Sister Outsider as "The Master's Tools Will Never Dismantle the Master's House," reads in this context not as a claim that reform is impossible or that working within systems is always futile, but as a specific intervention directed at white feminist academia, delivered from a position of structural exclusion, about how the very structures of knowledge production (conferences, panels, theoretical frameworks, the categories of analysis) were reproducing the hierarchies they claimed to oppose.</blockquote>
<blockquote>
The citation tends to operate as credentialing rather than engagement, a way of demonstrating political seriousness before proceeding to make the argument you were going to make anyway. In that passage, Lorde is simultaneously "far smarter than I am about nearly everything" and also wrong about the thing that matters for the argument at hand. The invocation and the dismissal occur in the same breath.

This is, structurally, a version of what Lorde was diagnosing in 1979. The conference organizers had invited her. They had put her on the programme. They had formally acknowledged that her perspective had a place in the conversation. But they had put her in the one slot reserved for people like her, assigned her to respond to work that had not engaged with her tradition, and positioned her contributions as supplementary to a theoretical apparatus that remained unchanged by her presence.
</blockquote>
]]></description>
<dc:subject>feminism history tools criticism racism</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0ba9ceb21e5f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:feminism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:criticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:racism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.mealie.io/">
    <title>Home - Mealie</title>
    <dc:date>2026-03-30T07:32:42+00:00</dc:date>
    <link>https://docs.mealie.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>A self-hosted recipe manager and meal planner with a RestAPI backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family.</blockquote>]]></description>
<dc:subject>recipes applications</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2fe4a9abc07c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:recipes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:applications"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://kennethreitz.org/essays/2025-08-27-from_http_to_consciousness">
    <title>From HTTP to Consciousness: The Evolution of &quot;For Humans&quot; - Kenneth Reitz</title>
    <dc:date>2026-03-27T15:04:23+00:00</dc:date>
    <link>https://kennethreitz.org/essays/2025-08-27-from_http_to_consciousness</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>I was trying to solve a simple problem: urllib2 was technically correct but humanly wrong. It forced developers to think like protocols instead of thinking like humans.

# The "correct" way in 2011
import urllib2
req = urllib2.Request('http://example.com')
response = urllib2.urlopen(req)
data = response.read()

# The human way
import requests
response = requests.get('http://example.com')
data = response.text
Copy
The difference isn't just syntactic sugar. It's a philosophical commitment: design from human mental models outward, not from technical constraints inward.</blockquote>]]></description>
<dc:subject>human design affordances</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f70aa03d16a4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:human"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:affordances"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ashley.rolfmore.com/stop-trying-to-engineer-your-way-out-of-listening-to-people/">
    <title>Stop trying to engineer your way out of listening to people</title>
    <dc:date>2026-03-24T05:17:33+00:00</dc:date>
    <link>https://ashley.rolfmore.com/stop-trying-to-engineer-your-way-out-of-listening-to-people/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>if you're wondering why this happens, it's normally because:

people aren't talking to people
people aren't listening
So lots of designers and product people have leapt onto 1, basically trying to turn talking to people into terms engineering people find more cuddly. Like "framework". Or "system". Or even that term that's in vogue, socio-technical system.

Stop. The problem isn't that you need a better system. The problem is you're avoiding doing the work.</blockquote>]]></description>
<dc:subject>design listening people relationships bias talking productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8486edb8da05/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:listening"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:people"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:relationships"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bias"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:talking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/pulse/service-design-social-complexity-cameron-tonkinwise-h8tzc">
    <title>Service Design and Social Complexity</title>
    <dc:date>2026-03-24T05:15:00+00:00</dc:date>
    <link>https://www.linkedin.com/pulse/service-design-social-complexity-cameron-tonkinwise-h8tzc</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The challenge of Service Design is to try to ameliorate these complexities. To do so requires deciding:

> what in the service interaction to design, to give more or less permanent form to, to regularise

> what to make space for in the service so that it can be (re)negotiated in a situated (particular each time) way As indicated before, the second depends on the first; some aspects of the service are regulated or even automated so that other aspects of the service can be bespoke.</blockquote>]]></description>
<dc:subject>design services</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7476add4d752/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://teachcomputing.org/blog/using-primm-to-structure-programming-lessons/">
    <title>Quick Read: Using PRIMM to structure programming lessons - Teach Computing</title>
    <dc:date>2026-03-24T05:02:16+00:00</dc:date>
    <link>https://teachcomputing.org/blog/using-primm-to-structure-programming-lessons/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>PRIMM is an approach that can help teachers structure lessons in programming. PRIMM stands for Predict, Run, Investigate, Modify and Make, representing different stages of a lesson, or series of lessons. PRIMM promotes discussion between learners about how programs work, and the use of starter programs to encourage the reading of code before writing.</blockquote>]]></description>
<dc:subject>teaching pedagogy learning education</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:eab4262083df/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pedagogy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:education"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sue.codes/blog/fingerscode/">
    <title>Do your fingers remember how to code?</title>
    <dc:date>2026-03-24T04:57:41+00:00</dc:date>
    <link>https://www.sue.codes/blog/fingerscode/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>I run employee training at my work, I teach teams within the company to use our product. And when I first proposed this it was met with skepticism, some people thought that teaching our technical product to teams they didn't regard as technical would not work. But I was insistent about doing it. 1 because I’m delusional enough to think I can teach anyone anything, and 2 because it’s a cheap way to test training resources before they get put in front of customers.

So I would start by guessing what the learners already knew and what needed explained, you need to go where the learner is then take them where they need to be. I would guess what they already knew and create a space where they felt able to tell me I was wrong, and they’d no idea what I was talking about. I hadn't explained things that needed explained. I would feed that back into the flow and go again. So it was a process of revealing my own assumptions to me</blockquote>]]></description>
<dc:subject>teaching devrel training programming skills technical</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:78a6b72a576c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:devrel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:training"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:skills"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:technical"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html">
    <title>E.W.Dijkstra Archive: The Humble Programmer (EWD 340)</title>
    <dc:date>2026-03-23T17:17:04+00:00</dc:date>
    <link>https://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The purpose of abstraction is not to be vague, but to create a new semantic level in which one can be absolutely precise.

— Edsger Dijkstra</blockquote>]]></description>
<dc:subject>quotes abstraction programming talks precision</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2d2a2c00b70f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:abstraction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:talks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:precision"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://colossus.com/article/we-have-learned-nothing-startup-pundits/">
    <title>We Have Learned Nothing - Colossus</title>
    <dc:date>2026-03-23T00:00:46+00:00</dc:date>
    <link>https://colossus.com/article/we-have-learned-nothing-startup-pundits/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Kuhn argued that scientists are stubborn within a framework of beliefs, which he called a paradigm. Because it provides a structure that lets them build on and improve existing theories, scientists will not abandon a paradigm until they have to. Paradigms provide a path forward.

Entrepreneurship research does not have a paradigm. Or, rather, it has too many, none compelling enough to be unifying. This means that people who think about entrepreneurship as a science have no shared guide to which problems are worth tackling, what observations mean, or how to improve theories that are not quite right. Without a paradigm, researchers are just thrashing around, talking past each other.</blockquote>]]></description>
<dc:subject>startups economics VC venturecapital</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e46be7c4ae7f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:VC"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:venturecapital"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://themonolithproject.net/">
    <title>The Monolith Project</title>
    <dc:date>2026-03-21T23:54:40+00:00</dc:date>
    <link>https://themonolithproject.net/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>art sites css html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dbe5fac64a26/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sites"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.davidpoll.com/2026/02/code-review-is-not-about-catching-bugs/">
    <title>Code Review Is Not About Catching Bugs</title>
    <dc:date>2026-03-21T23:50:29+00:00</dc:date>
    <link>https://www.davidpoll.com/2026/02/code-review-is-not-about-catching-bugs/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>What teams collaborate on during review is changing. Less time spent on style nits and mechanical correctness, more time on intent, architecture, and whether a change moves the product in the right direction. That’s a good shift. And the collaborative act itself – multiple humans exercising judgment together, developing shared taste, building mutual understanding of where the system is heading – that’s not a bottleneck to eliminate. It’s something to uplevel.

This is the part that concerns me most about framing code review as a bottleneck. Yes, review takes time. But some of that time is doing real work. The question isn’t how to eliminate that time. It’s how to make sure it’s spent on the judgment that matters rather than the noise that doesn’t.</blockquote>]]></description>
<dc:subject>coding code reviews programming ai llms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2e2e07146bd8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:reviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://substack.com/home/post/p-191342187">
    <title>Delve - Fake Compliance as a Service - Part I</title>
    <dc:date>2026-03-21T23:48:58+00:00</dc:date>
    <link>https://substack.com/home/post/p-191342187</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>At its core, this article argues that Delve fakes compliance while creating the appearance of compliance without the underlying substance.

Delve achieves its claim of being the fastest platform by producing fake evidence, generating auditor conclusions on behalf of certification mills that rubber stamp reports, and skipping major framework requirements while telling clients they have achieved 100% compliance. Their “US-based auditors” are Indian certification mills operating through empty US shells and mailbox agents. Auditors breach independence rules by signing off anyway, leaving companies unknowingly exposed to criminal liability under HIPAA and hefty fines under GDPR.</blockquote>]]></description>
<dc:subject>compliance regulation fraud</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d81eb5582d55/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:compliance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:regulation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fraud"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>