<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tim Consolazio on Medium]]></title>
        <description><![CDATA[Stories by Tim Consolazio on Medium]]></description>
        <link>https://medium.com/@tconso?source=rss-ab6bd56865df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9pPP5BGQi-gpUp2cqYNTkQ.png</url>
            <title>Stories by Tim Consolazio on Medium</title>
            <link>https://medium.com/@tconso?source=rss-ab6bd56865df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:33:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tconso/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Medium Is No Longer Safe For Me]]></title>
            <link>https://medium.com/@tconso/medium-is-no-longer-safe-for-me-b290df7f00ff?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/b290df7f00ff</guid>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 13:26:47 GMT</pubDate>
            <atom:updated>2026-07-23T14:29:39.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eO9UEDdx6vuoK_nBm5mjgw.png" /></figure><h4>Asymmetric policies have gone too far</h4><p>You can say anything you want about the demographic I belong to — I’m talking really, really miserable things. And you can manufacture quotes and tell outright lies about people without consequence.</p><p>Naturally, saying the same things about any other group — I mean literally replacing the words that identify the group — gets your stories suspended, with the related threats of outright banning.</p><p>“All men are burdens who want nothing but coddling and should be abandoned. They are useless.”</p><p>That is actual. In fact, that author publishes such stories regularly, to massive accolades. She makes an ongoing point of completely gutting the integrity of men.</p><p>Had I written those words about any other group, my account would be banned. They wave it away as “the author’s opinion.”</p><p>It’s everywhere on Medium. Recently, one author told numerous lies and manufactured quotes attributed to JK Rowling.</p><p>I pointed out the intentional misinformation and published what she actually said. The story was suspended, and I was also threatened with outright banning — because it doesn’t align with the identities they prefer. They threw an identity-specific policy in my face while making it clear that no such protection exists for my demographic.</p><p>In fact, I fully expect this story to be suspended, and possibly my account, which would likely prevent me from porting my content.</p><p>What a disappointment. I’ve really put a lot of effort into my material on this platform.</p><p>But, clearly, Medium — by design of their policy — is no longer safe for me.</p><p>I resisted it for a long time, really wanting to believe that it wasn’t true. But it is. The proof is everywhere.</p><p>What a disappointment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b290df7f00ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Epistemic Surface In Action]]></title>
            <link>https://medium.com/@tconso/epistemic-surface-in-action-ae461b5dac6e?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae461b5dac6e</guid>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Fri, 17 Jul 2026 14:08:49 GMT</pubDate>
            <atom:updated>2026-07-17T14:08:49.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCxY-5E4ft-Pd8Q6q4zBNQ.jpeg" /><figcaption>Generated by Sol5.6</figcaption></figure><h4>A Multi-Session Development Cycle with CodeLoop</h4><p>Another “field notes” article:</p><p>(CodeLoop is a framework I authored that implements the concept of an “epistemic surface” in a given project. A link to the related articles are at the bottom in the sources section.)</p><blockquote>At this point, I no longer consider a stewarded epistemic surface — a governed, project-local record of verified facts, decisions, claims, and open work — optional in production projects that use AI-augmented coding. — Me</blockquote><p>I just finished a fairly involved development cycle implementing a new medical transactions compliance report for my platform’s compliance stack.</p><p>The report exists so that tax-free and medical (non-recreational) sales can be audited quickly and accurately by clients and by the regulatory body. In our Vermont operating environment, existing systems do not otherwise provide a coherent view of this compliance state.</p><p>There are human-involvement invariants in this kind of work: sandboxing, testing, validation, and verification. But allowing the model to record that evolving knowledge in the project’s corpus on the feature branch, to use as a shared working context, proved enormously valuable.</p><h3>Partway through the implementation, I had to stop for the day.</h3><p>Rather than leaving the implementation plan trapped in a particular chat history, I had the model record the intended mutation in the branch’s project-local corpus.</p><p>This morning, I pulled the feature branch on a different computer, told the model to read the mutation and the relevant corpus context, and it reoriented itself in ~10 seconds using a couple of local CodeLoop CLI calls.</p><p>I reviewed the reconstructed proposal, approved it, and the model implemented, tested, verified, and summarized the intended mutation. I approved the summary and authorized the PR.</p><p>After verification and authorization, the PR is automatically reviewed and, if it passes, merged. A targeted sync then updates the source-of-truth corpus from the merged code rather than from the ephemeral branch’s state. Previous state records are retired, new verified facts are recorded, outstanding claims remain visible, and newly discovered mutations become open work items.</p><p>The CodeLoop viewer now reflects the project’s current verified state, including the new report, its supporting mechanisms, verified facts, open claims, and follow-on mutations. Filtered on “medical”, the implementation is transparent, current, and immediately inspectable.</p><h4>The practical effect:</h4><p>• Cognitive load drops dramatically.<br>• The verified state of the project is instantly reportable.<br>• Documentation, executive summaries, and architectural overviews can be generated directly from the corpus instead of being reconstructed from memory.<br>• Every completed mutation increases the project’s verified coverage.</p><h3>Most importantly, the usual, ever-increasing drift between completed work and recorded project state was eliminated from this development cycle.</h3><p>The value was not that the model remembered more. The project retained what mattered, and each model could recover it from governed local state. CodeLoop lets temporary AI-assisted work become durable project knowledge without allowing provisional branch assertions to masquerade as verified truth.</p><pre>Sources:<br>- [AI, Fact Convergence, and the Age of Verified State] (https://x.com/tcoz_tweet/status/2058269184229097801_)<br>- [Who Owns the Epistemic Surface?] (https://x.com/tcoz_tweet/status/2061524889450737815)<br></pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae461b5dac6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mind Your Harness: Field Notes on Harness -> MCP -> Model -> Project]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@tconso/mind-your-harness-field-notes-on-harness-mcp-model-project-a12e3c2270f6?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1774/1*4ZdDCX4P2crzCDkSIVk7GQ.png" width="1774"></a></p><p class="medium-feed-snippet">Your &#x201C;Agentic Stack&#x201D; can generate extreme costs</p><p class="medium-feed-link"><a href="https://medium.com/@tconso/mind-your-harness-field-notes-on-harness-mcp-model-project-a12e3c2270f6?source=rss-ab6bd56865df------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@tconso/mind-your-harness-field-notes-on-harness-mcp-model-project-a12e3c2270f6?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/a12e3c2270f6</guid>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 21:48:34 GMT</pubDate>
            <atom:updated>2026-07-14T11:54:14.090Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[CodeLoop and Odysseus]]></title>
            <link>https://medium.com/@tconso/codeloop-and-odysseus-3ce46873fcd6?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ce46873fcd6</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai-development]]></category>
            <category><![CDATA[ai-augmented-development]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 17:02:37 GMT</pubDate>
            <atom:updated>2026-07-07T18:12:47.475Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aloUlhcgVFjQiEqXxMdEhA.jpeg" /><figcaption>Generated by ChatGPT</figcaption></figure><h4>Bootstrapping an epistemic surface with GLM 5.2</h4><p>There seems to be interest in my AI tinkering and something I call “stewarding a project’s epistemic surface,” so I’ll write about it here for those curious.</p><p>CodeLoop is a framework I wrote to implement an “epistemic interface” for a given project. The idea is generally applicable, but it’s highly relevant to code and technology systems; ergo, this implementation as an npm package with a .vsix viewer.</p><p>You install the framework, initialize it, tell it to load and follow the directives, and it breaks a project down into facts, claims, decisions, observations, project state, and mutations. All that info is written to a lightweight corpus that travels with the project and serves as a persistent context for the model and a queryable resource for the user. The model owns the corpus; the human doesn’t write to it. It gets modified and updated based on changes to the source, not as a matter of oft-gratuitous human archeology and anxious info packratting. Provenance is primarily captured in the model-authored git commit/PR messages, which, if written by a well-directed model, provide more than enough rationale, history, and context when needed. The human engages with the project via the framework and works with the epistemic surface to understand it and direct the model’s efforts, ever converging toward a fully verified project state.</p><p>(How the corpus reconciles forward-moving PRs and team-based development of mutations is a little more in the weeds than I want to get now; this article is about how the bootstrapping of Odysseus went, what CodeLoop structured as its corpus, and what was immediately actionable as a result.)</p><p><em>What follows is a narrative of my current live working session, which is to bootstrap CodeLoop for a framework called “Odysseus”.</em></p><p><strong>First, after population of the corpus was complete:</strong></p><p>Here’s what the CodeLoop webview displayed, and the chat shows a response to the prompt, “Tell me what this project does. Only use the CodeLoop corpus to derive your response.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLYF3LA2tGor9wjLBKLu4Q.png" /><figcaption>CodeLoop Webview and Odysseus Project Summary</figcaption></figure><p>Now you know what Odysseus is: a “self-hosted personal AI assistant. It lets you chat with AI models from many providers…email/calendar/contacts/notes…”</p><p>(Other than cloning it, I don’t have any involvement with Odysseus and know nothing about how it works. I was interested in the project and decided to give it a going over; that’s it.)</p><p><strong>How that visibility happens:</strong></p><p>One of the first things CodeLoop does after initialization is determine if the corpus is new. If so (just created by the init process), it knows it needs to bootstrap it, which means evaluating the project. It did so here and recommended five passes across three scopes to avoid overloading the context and achieve a high-fidelity projection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*Y-ty-mDV5lihXg9DurvSyw.png" /><figcaption>GLM 5.2’s recommendation for scopes for CodeLoop corpus population</figcaption></figure><p>I asked a couple of questions, was satisfied with the proposal, and released it. The result (some time later) was what you saw in the first picture (the webview and report description).</p><p>As a developer looking to understand this project, I might want to know the major technologies involved, which I would expect to be found in the facts. Some quick filtering in the webview shows me that Docker and Python are major players, but I wanted more detail, so I asked the model to define the stack using the information in the corpus.</p><p>Suffice to say, insofar as stack, I now know exactly what I’m looking at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VePTeeo7UQaQ_4tr2TSfTQ.png" /><figcaption>Odysseus stack analysis derived from CodeLoop’s corpus</figcaption></figure><p>My next question, which I have never seen answered quickly and plainly in almost 40 years of software work: “Based on the application’s verifiable state, how stable is it?”</p><p>(Model uses MCP layer to query the facts, mutations, observations, claims, and decisions from the corpus — it’s not reading code files or stale human docs, the latter of which is defined by the directives as high-risk insofar as being authoritative).</p><p>Here’s what I got back:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*q7LUr7jk7Y45cvV-vDZ77g.png" /><figcaption>CodeLoop’s stability and verified state analysis of Odysseus</figcaption></figure><p>Pretty good news all around, but some items to look at and some deeper “really in the weeds” sources I haven’t had to look at yet. Database.py seems high on the “look at this now” list, though.</p><p>I’d expect to find that as a mutation, and sure enough, there it is (in the corpus webview), along with some others, I posted a trivial one here as example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*Oo4MULxxgVcOhAtvMHaAjA.png" /><figcaption>CodeLoop Webview open mutations</figcaption></figure><p>The version mismatch is a tweak (easy but important), but the one in database.py is pretty involved. That’s a huge “big brain” style file that seems in need of a huge refactor.</p><p>So, I clicked the mutation ID in the webview to copy it, then asked the model to “succinctly explain the mutation with this ID.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*2NPnWhl6g5w1ZsKxha9kdA.png" /><figcaption>GPM 5.2 analyzes a mutation from the CodeLoop corpus</figcaption></figure><p>The webview also shows that a filter on “core/database.py” brings up a number of items across facts, observations, project state, and mutations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4TEYN-tH7F3EDiCf3B_yA.png" /><figcaption>Corpus Webview filtered on core/database.py</figcaption></figure><p><strong>Now I’ve got a real idea of the current state, the issue, and the best use of my time, insofar as driving the verified state of this application.</strong></p><p>(I quickly checked the code, and the corpus info is correct.)</p><p>So, I want to start thinking about the change in the context of CodeLoop’s “loop” protocol, which is a structured dev cycle. You move through Plan, Proposal, and Release. The “Release” is a hard gate; unless you REALLY try to prompt around it, the model won’t release the proposal until you say “Y(es)” in response to its request to begin authoring (principle of human verification, etc.).</p><p>The model already made it clear that a single loop wouldn’t suffice (the mutation requires multiple dependent changes). Multiple loops and different constructs would be required if I wanted the entire change completed, such as parallel and stack. Subagents could be applied to given loops, and/or I could steward the whole thing myself.</p><p>So, first question: What comes first, and then what?</p><p>Again, the corpus analysis makes it clear. From this alone, I could write extremely high-quality tickets, along with the mutation ID from the corpus, to track them against the epistemic surface — though since the mutations travel with the corpus, anybody pulling the branch will already see it, so the ticket becomes an assignment to a mutation in the corpus — very tidy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*nLrm7JA8sXj92E5DJF3L3g.png" /><figcaption>GPM 5.2’s recommended CodeLoop loop sequence 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*s_SYXuWPCELmmtXE86bLWA.png" /><figcaption>GPM 5.2’s recommended CodeLoop loop sequence 2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*H6Fbtpf24FRftSisGfQs2A.png" /><figcaption>GPM 5.2’s recommended CodeLoop loop sequence 3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*8AqoHIK1wttctK4bk0wT9g.png" /><figcaption>GPM 5.2’s recommended CodeLoop loop sequence rationale</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*ojebBp75GlgMn-zaMPjjEA.png" /><figcaption>GPM 5.2’s recommended CodeLoop loop summary with block gates</figcaption></figure><p>At this point, this work — which is complex and order-dependent — is simple to assign to a team. I know exactly what needs to be done and how to reconcile the mutations against the source of truth to ensure the state remains verified and the related observations/mutations are retired.</p><p>The analysis makes it clear this is no “write a ticket” task. Multiple developers and agents will be involved in this, and they’ll need to own different areas, but with some coordination on the indicated blocking gates. Fortunately, since the issue is already well defined in the corpus, you won’t need the high-end frontier models for any of this. A developer could just point to a locally run Qwen coder model or a less expensive cloud model like Sonnet 4.1 and be off to the races. As long as the model/harness can use MCP tools, it’ll have the corpus available for context and analysis.</p><p><strong>The real ringer for all of this: Cost.</strong></p><p>Using GLM on Ollama’s cloud, using the $20/month allowance, I used ~20% of my weekly usage. Plenty of headroom for more work, other bootstraps, corpus syncs, and so forth.</p><p>That’s a couple of bucks, and it includes all the bootstrap work, which is one-time. Because the model doesn’t have to constantly read and interpret files, but instead pulls records stored in an AI-friendly manner through a tool-level interface, the token cost of reading and analyzing project state drops dramatically. The rest of the team works more inexpensively, too.</p><p>I don’t have hard numbers on that yet, but I can say this: the latest version of the framework is costing so little to use that three $20/month accounts- OpenAI, Anthropic, and Ollama are now giving me what I need to get the job done. Previously, I was spending roughly $100 a month on Anthropic and another $60 on OpenAI…minimum.</p><p>Anyways, that’s a typical bootstrap and start of a working session using CodeLoop. Maybe the Odysseus authors can look forward to a PR from me. After all, I do know what needs looking at.</p><p>Links:</p><p><a href="https://x.com/tcoz_tweet/status/2058269184229097801"><strong>AI, Fact Convergence, and the Age of Verified State</strong></a></p><p><a href="https://x.com/tcoz_tweet/status/2061524889450737815"><strong>Who Owns the Epistemic Surface?</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ce46873fcd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There Is No “Manosphere”]]></title>
            <link>https://medium.com/@tconso/there-is-no-manosphere-caa1037fdca8?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/caa1037fdca8</guid>
            <category><![CDATA[manosphere]]></category>
            <category><![CDATA[men]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[feminist]]></category>
            <category><![CDATA[mens-mental-health]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 14:38:40 GMT</pubDate>
            <atom:updated>2026-06-04T14:46:27.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73Hci4ckNWkKoZyNtR6W2g.png" /><figcaption>Generated by ChatGPT</figcaption></figure><h4>It’s a reductionist, lazy, social media concoction. Nothing more.</h4><p>This is a quick-but-important one. To me, anyway.</p><p>I’m a man, and have spoken to other men about that neologism. I can tell you this for a fact:</p><p><strong>Men didn’t create it, don’t acknowledge it as much more than a feminist-coded pejorative term, and reject external assignment to it. Any man who acknowledges it is just some wanker maxing social media reach. “I’m a proud member, I slam bourbon while driving my Ferrari across a frozen lake, envy me, hate me!!! (click follow).”</strong></p><p>In short, it fails the most basic legitimacy test: almost nobody described by it would recognize it as a meaningful boundary, much less claim membership in it.</p><p>That matters because it means the term isn’t really a community name. It’s an external label imposed on a loose collection of male spaces, behaviors, grievances, anxieties, markets, influencers, jokes, failures, and legitimate unmet needs.</p><p>Like any group’s spaces, some criticisms are valid. But summing it all up under a single label does more than identify those things. It draws a boundary around them, then treats the boundary itself as if it explains what’s inside. It’s an accepted tautology — by definition, logically incoherent.</p><p><strong>Fact:</strong> the term is almost always deployed as a pejorative containment label. It means, more or less, men are doing this to themselves. Obviously, there are larger conditions involved. But by slapping some catchy label on it, those conditions end up on the cutting floor of those who have a vested interest — i.e., social media reach — in producing it.</p><p>How it’s almost always represented:</p><ul><li>A depressed man locked to a screen.</li><li>A depressed man sitting alone at home.</li><li>A cartoonish, flannel-cutoff, caveman-coded man tying rockets to bicycles and lifting weights while drinking beer.</li></ul><p>That’s not neutral. It all frames male distress as pathology, regression, absurdity, or self-inflicted grievance before the argument even begins.</p><p>I defy you to show me:</p><ul><li>One widely circulated representation of “the manosphere” that uses the term primarily to address the negligence men experience around wellness, isolation, emotional need, social value, or the narrow terms under which men are still allowed to be considered useful.</li><li>One where the main frame is not “look what men have become,” but “look what we have allowed to happen to men.”</li></ul><p>When that broader neglect appears at all, it’s a grudging footnote. “Yeah, well, sure…some stuff…but we’re not talking about that right now! Get back to the problem, which is the thing-o-sphere!”</p><p>That’s a real problem: The term is presented as analysis, but it’s actually knowledge and compassion-washing. It gathers loneliness, resentment, misandry, self-improvement, sexual insecurity, economic precarity, fatherlessness, humor, grift, and genuine male suffering into a single enclosure, then invites the reader to judge it from a predefined suggestion.</p><p>The result: everything is conflated into a single idea predefined for the consumer. The term and its typical representation are the focus of the discussion. “Oh, everybody knows what that is.”</p><p>Precision evaporates, and the term used in discourse perpetuates the problem rather than moving toward a solution.</p><p>This story was written in response to a story with the title, <a href="https://medium.com/the-manosphere/asmongold-has-everything-the-manosphere-promised-hes-still-alone-f7229b495785">“Asmongold Has Everything the Manosphere Promised. He’s Still Alone.”</a></p><p>That’s not just a description of a man encountering a harmful ideology. It’s a frame in which male distress is treated as something men wandered into, bought into, or deserved to learn the hard way. The social conditions that helped produce the distress may be acknowledged somewhere, but they’re not what’s governing the interpretation.</p><p><strong>I therefore do, and will continue to, object to the term — strongly.</strong></p><p>The label itself is doing argumentative work while pretending to be a taxonomy, and that’s the worst kind of intellectual laziness. It drives the neglect of something that should be examined thoroughly and compassionately.</p><p>As a side note, consider: if social media tried to drive “femisphere” the same way, what would the result be?</p><p>We already know. The blowback would be extreme, the term would be buried under female objections of misogyny and perceived as offensive and hurtful.</p><p>But hey, we’re talking about men here.</p><p>Stop being a baby.</p><p>As always, thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caa1037fdca8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No, I’m Not Ashamed Of My Tesla]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@tconso/no-im-not-ashamed-of-my-tesla-d32e73b64210?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1024/1*fUUPqP3K6VGjCHaGn4t8KA.png" width="1024"></a></p><p class="medium-feed-snippet">It&#x2019;s Not the Car That Changed&#x200A;&#x2014;&#x200A;and No, Elon is Not a Nazi.</p><p class="medium-feed-link"><a href="https://medium.com/@tconso/no-im-not-ashamed-of-my-tesla-d32e73b64210?source=rss-ab6bd56865df------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@tconso/no-im-not-ashamed-of-my-tesla-d32e73b64210?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/d32e73b64210</guid>
            <category><![CDATA[tesla]]></category>
            <category><![CDATA[elon-musk]]></category>
            <category><![CDATA[society-and-culture]]></category>
            <category><![CDATA[political]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Fri, 25 Apr 2025 11:34:38 GMT</pubDate>
            <atom:updated>2025-05-15T13:59:54.523Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Didn’t Support Trump, But…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/thought-thinkers/i-didnt-support-trump-but-9a4d1bcfdd0f?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1024/1*5py4FYqHiABG93drt9fi0A.jpeg" width="1024"></a></p><p class="medium-feed-snippet">People Are Speaking Again</p><p class="medium-feed-link"><a href="https://medium.com/thought-thinkers/i-didnt-support-trump-but-9a4d1bcfdd0f?source=rss-ab6bd56865df------2">Continue reading on Thought Thinkers »</a></p></div>]]></description>
            <link>https://medium.com/thought-thinkers/i-didnt-support-trump-but-9a4d1bcfdd0f?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a4d1bcfdd0f</guid>
            <category><![CDATA[censorship]]></category>
            <category><![CDATA[freedom-of-speech]]></category>
            <category><![CDATA[political-discussion]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[society-and-culture]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 22:49:40 GMT</pubDate>
            <atom:updated>2025-02-18T13:36:25.555Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[You’re All Winners!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@tconso/youre-all-winners-f7c6e76f3cc1?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1024/1*O6zsbn7_t1DkoM5B4fDguA.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Participation trophies&#x200A;&#x2014;&#x200A;what do they teach, who are they really for?</p><p class="medium-feed-link"><a href="https://medium.com/@tconso/youre-all-winners-f7c6e76f3cc1?source=rss-ab6bd56865df------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@tconso/youre-all-winners-f7c6e76f3cc1?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7c6e76f3cc1</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[children]]></category>
            <category><![CDATA[character-development]]></category>
            <category><![CDATA[dealingwithfailure]]></category>
            <category><![CDATA[child-psychology]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Sat, 18 Jan 2025 19:00:47 GMT</pubDate>
            <atom:updated>2025-01-27T22:27:25.370Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Break the Adult Alcohol Norm]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/crows-feet/break-the-adult-alcohol-norm-e27950e82dba?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1792/1*KLSKKUdB0QUPTyEHtZ1T_Q.png" width="1792"></a></p><p class="medium-feed-snippet">You&#x2019;re not obliged to drink&#x200A;&#x2014;&#x200A;ever, for any reason</p><p class="medium-feed-link"><a href="https://medium.com/crows-feet/break-the-adult-alcohol-norm-e27950e82dba?source=rss-ab6bd56865df------2">Continue reading on Crow’s Feet: Life As We Age »</a></p></div>]]></description>
            <link>https://medium.com/crows-feet/break-the-adult-alcohol-norm-e27950e82dba?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/e27950e82dba</guid>
            <category><![CDATA[societal-pressures]]></category>
            <category><![CDATA[alcohol-and-health]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[alcohol]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Wed, 15 Jan 2025 16:39:23 GMT</pubDate>
            <atom:updated>2025-02-15T16:39:53.835Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Tinnitus Update]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@tconso/tinnitus-update-1a1b32e639d9?source=rss-ab6bd56865df------2"><img src="https://cdn-images-1.medium.com/max/1024/1*EowK-AW_r6DGVOy1XqRJmQ.jpeg" width="1024"></a></p><p class="medium-feed-snippet">A new study may shed some light on the cause</p><p class="medium-feed-link"><a href="https://medium.com/@tconso/tinnitus-update-1a1b32e639d9?source=rss-ab6bd56865df------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@tconso/tinnitus-update-1a1b32e639d9?source=rss-ab6bd56865df------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a1b32e639d9</guid>
            <category><![CDATA[hearing-loss]]></category>
            <category><![CDATA[tinnitus-treatment]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[tinnitus]]></category>
            <category><![CDATA[hearing-aids]]></category>
            <dc:creator><![CDATA[Tim Consolazio]]></dc:creator>
            <pubDate>Thu, 21 Nov 2024 16:58:23 GMT</pubDate>
            <atom:updated>2024-11-21T17:06:01.850Z</atom:updated>
        </item>
    </channel>
</rss>