<?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 Walter Pinson on Medium]]></title>
        <description><![CDATA[Stories by Walter Pinson on Medium]]></description>
        <link>https://medium.com/@walter.pinson?source=rss-6e4a7c3ec0fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OXh49AcQQlUXBrxVcCXStg.png</url>
            <title>Stories by Walter Pinson on Medium</title>
            <link>https://medium.com/@walter.pinson?source=rss-6e4a7c3ec0fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:17:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@walter.pinson/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[Why Software Craftsmanship Matters More Now, Not Less]]></title>
            <link>https://medium.com/@walter.pinson/why-software-craftsmanship-matters-more-now-not-less-1eb0801d9272?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1eb0801d9272</guid>
            <category><![CDATA[software-craftsmanship]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Mon, 25 May 2026 07:11:43 GMT</pubDate>
            <atom:updated>2026-05-25T07:11:43.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrmnnMwa0Jpc36aeztluaQ.png" /></figure><p><em>The Intent-Engineering Field Guide | Part 5 of 13</em></p><p>For about a decade, the industry has been quietly trading craftsmanship for velocity.</p><p>The trade made sense. Code was the scarce resource. The disciplines that constrained complexity were treated as preferences a strong team could afford and a fast team could skip. The fast team usually won the quarter. The craft team usually won the decade. But decades are long and quarters are short, and most organizations optimize for what they can measure this Friday.</p><p>The economic logic from the previous article in this series has not changed. What changed is which disciplines the economics now favor.</p><p>When agents produce code in seconds, the disciplines that constrain <em>what</em> they produce, in <em>what shape</em>, and to <em>what standard</em> stop being preferences. They become the constraint mechanisms that make agent output something humans can verify, maintain, and reason about. The industry deprioritized craftsmanship when humans were the executors. That was always a trade. In the agent era, it stops being a trade and starts being a liability.</p><blockquote>“If skills sold, truth be told, I’d probably be lyrically Talib Kweli.<em> <br></em>Truthfully I want to rhyme like Common Sense,<em> </em>but I did five mil. <br>I ain’t been rhyming like Common since.”</blockquote><blockquote><em>Jay-Z, </em>Moment of Clarity</blockquote><p>That is the trade. Said plainly by someone who made it and never pretended otherwise.</p><h3>How I came to believe this</h3><p>I did not arrive at craftsmanship as a theoretical position. I was formed in a crucible.</p><p>A small cohort of us from GMU’s computer science department, chaired at the time by Peter Denning, the pioneer of virtual memory whose working-set model became the reference standard for memory management, were hand-picked by the IT department to execute a mainframe-to-client-server migration. Looking back, what we pulled off was genuinely difficult work. We competed with each other in the right ways: about architectural elegance, about code quality, about getting the thing right rather than just getting it done. I had to invent composite algorithms to survive the memory squeeze going from mainframe to 32-bit. None of that work would have been possible without craftsmanship as the shared ideal.</p><p>That training is the lens through which I have read every codebase since. It is also the reason I keep noticing what is now happening at industrial scale: the disciplines that made hard things possible are the same disciplines that make agent output trustworthy. The era did not invent the need. It amplified it.</p><h3>The three disciplines, repriced</h3><p>Most of the craftsmanship stack matters more in the agent era than it did before. Three disciplines carry a disproportionate share of the weight. Each one solves a problem the agent introduces by its nature, in a way the human reviewer cannot replicate after the fact.</p><p><strong>Ubiquitous language</strong> used to be DDD’s connective tissue between domain experts and engineers. In the agent era, it becomes the connective tissue between the specification, the agent, and the code. Without it, the agent invents its own vocabulary on every generation. A <em>customer</em> becomes a <em>user</em> becomes an <em>account holder</em> becomes a <em>party</em>, and the codebase becomes a tower of synonyms that obscures what the system is actually modeling. A team that maintains a ubiquitous language gives the agent a fixed vocabulary to paint inside of. A team that does not gives the agent a thesaurus.</p><p><strong>Domain-driven design</strong> used to be the discipline that kept business complexity contained. In the agent era, it becomes the bounding mechanism that tells the agent where one concept ends and another begins. Agents are creative. Creative without boundaries produces concept sprawl. The same business idea ends up implemented three different ways across three different modules because the agent had no map of where it was allowed to operate. DDD provides the map. Bounded contexts are not architectural decoration. They are the fences that keep the agent on the property.</p><p><strong>Hexagonal, clean, and onion architectures</strong> used to be the disciplines that separated business logic from infrastructure concerns. My favorite of the family is Onion, Jeffrey Palermo’s framing of the same essential principle. In the agent era, all three serve a function their original authors did not have to articulate: they tell the human reviewer <em>where to look</em> when the agent’s output goes sideways. The metaphor I keep coming back to is paint by numbers. The painter is the agent. The numbers are the architecture. The painter can be as creative as it wants inside the lines, and a well-layered system gives the human reviewer a map of where to look when something on the canvas does not match the picture on the box. When a regression appears, the architecture narrows the search space from <em>the whole system</em> to <em>this layer, this port, this adapter</em>. That is what it means to know where the bodies are buried. A free-form agent sprawl is a system nobody can investigate quickly. A well-layered system is.</p><p>I have inherited the alternative more times than I can count. The clearest version of it was at a human capital management company that had grown by acquisition and cobbled together a stack of SaaS products through M&amp;A. The integrated codebase read like Picasso, Mondrian, and Monet had taken turns on the same canvas. Business logic lived in the application code, in inline SQL, and in stored procedures, all at once and in different proportions in different modules. Every change carried a hidden blast radius. A function modified in one place would detonate something on the other side of the system that had no logical reason to be connected to it. The code compiled. The code ran. Under load, the memory leaks and database locks surfaced, and many nights and weekends were lost to a caliber of problem that craftsmanship would have prevented entirely.</p><p>That is what the absence of these disciplines costs. The agent era does not eliminate that cost. It scales it.</p><h3>The objection worth taking seriously</h3><p>Every argument for craftsmanship in the agent era runs into the same counter-argument. It usually sounds like this:</p><p><em>“The agent can refactor anything in seconds. Why do I need clean architecture if I can just regenerate?”</em></p><p>The objection is worth taking seriously because it would be a real objection if it were true. It is not, on two separate fronts. Two failure-modes are hiding inside the same counter-argument.</p><p>The first failure-mode is directional. Regeneration without a target produces motion, not progress. The agent has no opinion about what <em>better</em> looks like. Without an architectural reference, the agent will regenerate the system forever and never converge on the version you wanted, because <em>the version you wanted</em> was never specified in a form the agent could optimize toward. Craftsmanship is what gives the regeneration a <em>toward</em>. Without it, regeneration is just expensive randomness.</p><p>The second failure-mode is economic. The objection assumes regeneration is free. It isn’t, and it is getting less free. The initial phase of the agent era was subsidized. AI companies absorbed the real cost of inference to seed adoption. That phase is ending. Token pricing is becoming more honest. Reclamation efforts are underway. Until LLMs are fully commoditized, regeneration is going to be priced as the non-trivial operation it always was. Most software development is an economic endeavor first and foremost, and TCO has always been the discipline that separated software-as-engineering from software-as-experimentation. The agent era does not exempt anyone from that math. It enforces it more strictly.</p><blockquote>The agent does not pay for the tokens. The humans who own the system do.</blockquote><p>The objection survives neither failure-mode. The team that treats regeneration as free is going to discover the price the same way the HCM company did. Under load.</p><h3>What craftsmanship is now</h3><p>It is survival.</p><p>The system without these disciplines is not slower. It is one the team will not be able to maintain when the agent reaches its limit and a human has to read the code. And the agent reaches its limit more often than the hype suggests. AI is itself software, consumed for most teams as SaaS, available some number of nines percent. That means it is unavailable some other percent, and Murphy’s Law guarantees those gaps will land on the days that matter most. The replacement of humans across planning, building, operating, and supporting software is not happening on any timeline that exempts a team from being able to read its own codebase.</p><p>When the agent is unavailable, when the bill forces discipline, when the system hits a class of problem the model cannot solve, the humans who inherit the code have to read it, reason about it, and fix it. Craftsmanship is what makes that possible.</p><p>The agent does not need craftsmanship. The humans who will inherit its output do.</p><p>The next article in this series is the receipt for what unconstrained agent output actually costs an organization. It surfaces in expanded attack surface, in maintenance debt, in cognitive load, and in the bills that arrive at the end of the month.</p><p><em>Further reading: Article 4 of this series, </em><a href="https://medium.com/@walter.pinson/code-is-cheap-trust-is-expensive-02bbc23bec78"><em>“Code Is Cheap. Trust Is Expensive”</em></a><em>, Article 2, </em><a href="https://medium.com/@walter.pinson/defining-ai-augmented-engineering-2955d4747437"><em>“Defining AI-Augmented Engineering”</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1eb0801d9272" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code is Cheap. Trust is Expensive.]]></title>
            <link>https://medium.com/@walter.pinson/code-is-cheap-trust-is-expensive-02bbc23bec78?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/02bbc23bec78</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Wed, 20 May 2026 20:12:03 GMT</pubDate>
            <atom:updated>2026-05-20T20:14:07.436Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2YHkB4cQnEPpUiM_n9FCMw.png" /></figure><p><em>The Intent-Engineering Field Guide | Part 4 of 13</em></p><h3>For thirty years, code was the scarce resource.</h3><p>The economic structure of our entire profession was built on that single assumption. Almost every argument we have had as a discipline since the 1990s has been an argument about how to produce code more efficiently, more cheaply, or with fewer humans. Whether the topic was engineering hiring, offshoring decisions, productivity tooling, IDE wars, or methodology debates, the shape of the conversation was always the same. <em>Making the code</em> was the expensive part.</p><p>That equation is now inverted.</p><p>Agents produce code in seconds. Over a weekend, a working codebase can materialize. A non-trivial feature can be delivered before lunch. The marginal cost of code is approaching the marginal cost of tokens and electricity. This is not a forecast. It is what is happening right now, on the teams that have already absorbed it.</p><p>When the cost of producing something collapses, the bottleneck always moves to whatever was next in the value chain. That is not a tech observation. That is economic physics.</p><p>So what is next in the value chain?</p><h3>The expensive thing now</h3><p><strong>Trust.</strong> Specifically, the justified confidence that what the agent produced is what you actually wanted.</p><p>The agent’s output compiles. It passes the tests the agent also wrote. Neither of those facts tells you whether the code does the thing the business asked for, under the conditions the business cares about, in a way the next engineer can maintain. That is a different question entirely, and nothing in the agent’s output answers it.</p><blockquote><strong>“Trust is a word you seldom hear from us, <br>hustlers we don’t sleep we rest one eye up.”</strong></blockquote><blockquote><em>- Jay-Z, </em>December 4th</blockquote><p>The hustler’s posture is the right posture for this moment. One eye up. Trust is scarce, and the people who treat it as scarce build differently than the people who treat it as free.</p><h3>Why trust is structurally expensive</h3><p>There are three reasons, and each of them carries weight.</p><p><strong>Trust requires a referent.</strong> You can only verify something against something else. If the specification of what you wanted lives in someone’s head, or in a Teams thread, or in an ADO backlog item written at 4 PM on a Friday, there is nothing to verify against. The agent’s output becomes the only artifact in the room, and an artifact cannot verify itself. The team reading the pull request is not reviewing the work. They are reviewing the code. Those are not the same thing, and the difference is exactly where trust goes to die.</p><p><strong>Trust requires precision.</strong> Vague specifications produce code that technically satisfies them and practically does not. I have watched this failure mode survive every methodology our profession has thrown at it. The clearest version of it came out of the globally distributed development era, and I saw it from a particular angle. I spent years being brought in as a turnaround specialist to right the ship after an offshoring engagement had gone sideways. The pattern was almost always the same. The agency had delivered, in good faith, precisely what the requirements documents said. The customer had rejected the work because it was not what they actually wanted. The agency ate the cost of correction. Sometimes they ate it twice. Sometimes the customer was lost regardless. I wrote about the broader fidelity problem in 2009 in <em>Architectural Fidelity with Globally Distributed Software Development Teams</em>, focused there on how vision and architecture get lost in the handoff to distributed teams. The deeper pattern beneath that piece is the one I keep coming back to: intent gets lost in the gap between what the human wanted and what the executor produced. That gap did not close. Agents have not closed it either. They have industrialized it.</p><p><strong>Trust requires a closing mechanism.</strong> This is the part most teams have not yet internalized. Specification alone does not close the loop. You need an artifact that <em>converts</em> the specification into something that can be evaluated against the agent’s output. Without that conversion, the specification is decoration and the verification is vibes. A PRD is not a closing mechanism. A user story is not a closing mechanism. Acceptance criteria written in narrative prose at the bottom of a ticket are not a closing mechanism. They are input to a closing mechanism that most teams have never built.</p><h3>What blockchain learned the hard way</h3><p>If you want to see what happens to a discipline when the specification is sloppy and the executor is unforgiving, look at smart contracts.</p><p>Back when I was writing Ethereum smart contracts, I had to be acutely aware of the spec. Real money was on the line. The wrong code was a gateway for the internet to rob you. Hackers, or merely industrious engineers, would read the code, remember that <em>code is law</em>, and decipher exactly how to leverage weaknesses to enrich themselves at your expense. Imprecision was not a quality problem. It was a theft vector.</p><p>The most consequential demonstration of that fact happened in 2016. An attacker exploited a recursive-call vulnerability in The DAO, a high-profile smart-contract investment vehicle on Ethereum, and drained roughly 3.6 million ETH, about $60 million at the time. The community split over what to do. The purists argued that the attacker had done nothing wrong: the contract’s own logic permitted the withdrawal, <em>code is law</em>, and the executor had executed exactly what was specified. The pragmatists argued for a hard fork to reverse the theft. The fork happened. The chain that reversed it became Ethereum. The chain that refused to alter history became Ethereum Classic.</p><p>That story is the cleanest case study our industry has of what happens when the code <em>is</em> the spec.</p><p>Some people argue that AI-augmented engineering should work that way. Let the agent produce the code, then read the code to understand the intent. The DAO is the counterargument. The code did exactly what it said. What it said was not what the humans wanted. The reason this failure mode exists, and will continue to exist, is that code is optimized for <em>machine</em> understanding and natural language is optimized for <em>human</em> understanding. The spec has to live in a medium where the humans can read it, argue about it, and agree on it before the machine ever runs.</p><p>This is where structured natural language earns its keep. But that is the argument for a later article. The point here is more narrow. The executor will execute exactly what you specified. The cost of imprecision falls on the human, not the machine. That was true on Ethereum in 2016. It is true on every team running agents in 2026.</p><h3>The trust loop</h3><p>Here is the line that the rest of this series will defend.</p><blockquote><strong><em>The loop closes when the specification of intent <br>is also the verification of output.</em></strong></blockquote><p>The loop closes when the artifact that says <em>what the agent should do</em> is the same artifact that tests <em>whether the agent did it.</em> That happens only when intent and verification are the same document.</p><p>Most teams already have half of this loop. They write user stories. They write acceptance criteria. They sometimes write them well. What almost no team does is <em>convert</em> those criteria into executable specifications before the agent ever runs. The criteria sit in the backlog. The agent writes the code. A human reviews the code. The criteria are consulted, if at all, as advisory documents. The loop never closes.</p><p>That is the gap. That is where trust gets expensive. And that is the gap a closing mechanism fills.</p><h3>What this means on Monday</h3><p>The team that figured this out a year ago is already pulling ahead. The team that figures it out this year will be fine. The team still measuring shipped features per sprint as the leading indicator of engineering productivity is going to wake up in eighteen months wondering why their codebase tripled in size while their reliability halved.</p><p>Three shifts are coming, whether the industry names them or not.</p><ol><li><strong>Shipped features per sprint will be repriced as a vanity metric.</strong> The leading indicator that matters is how much of what we shipped can we actually verify.</li><li><strong>Pull-request review will be repriced from a code-quality activity to an intent-verification activity.</strong> The question on the reviewer’s mind is no longer <em>is this code well-written.</em> It is <em>is this code what we asked for, and how do I know.</em></li><li><strong>The artifacts that close the trust loop will be repriced from QA-team concerns to load-bearing engineering deliverables.</strong> The team that owns the closing mechanism will be the team that owns the trust.</li></ol><p>The agent will give you exactly what you specified.</p><p>The cost of imprecision falls on the human, not the machine.</p><p>This article argued that trust is now the expensive thing. The next article argues why the disciplines that produce trust, the craftsmanship disciplines most of the industry has been quietly deprioritizing for a decade, are about to be repriced harder than anything else in this profession.</p><p><em>Further reading: </em><a href="https://medium.com/@walter.pinson/architectural-fidelity-with-globally-distributed-software-development-teams-5f7721fea8ce"><em>“Architectural Fidelity with Globally Distributed Software Development Teams.”</em></a><em> Walter Pinson, Medium, 2009. Article 1 of this series, </em><a href="https://medium.com/@walter.pinson/gherkin-may-be-the-most-consequential-language-of-the-ai-augmented-era-b6ce28f85a7e"><em>“Gherkin May Be the Most Consequential Language of the AI-Augmented Era.”</em></a><em> Article 3, </em><a href="https://medium.com/@walter.pinson/the-progression-nobody-finished-ebbe09bcda42"><em>“The Progression Nobody Finished.”</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02bbc23bec78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Progression Nobody Finished]]></title>
            <link>https://medium.com/@walter.pinson/the-progression-nobody-finished-ebbe09bcda42?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebbe09bcda42</guid>
            <category><![CDATA[software-engineering-job]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[intent-engineering]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Mon, 11 May 2026 19:12:58 GMT</pubDate>
            <atom:updated>2026-05-11T19:12:58.874Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9HSIde6MCJIgCqEAt5FfQ.png" /></figure><p><em>The Intent-Engineering Field Guide | Part 3 of 13</em></p><p>Three years. Four waypoints. Each one was declared the destination on arrival, and each one was quietly demoted the moment something newer showed up.</p><ol><li>Prompting</li><li>Prompt engineering</li><li>Context engineering</li><li>Intent engineering</li></ol><p>The progression is real. The story we tell about it is not.</p><p>The story we tell is that we have been getting better at talking to machines. That story is incomplete.</p><h3>What each step actually solved</h3><p>The cleanest framing I have seen comes from outside the series and is worth borrowing. Each waypoint answers a different question. <strong>Prompt:</strong> <em>what to do.</em> <strong>Context:</strong> <em>what to know.</em> <strong>Intent:</strong> <em>what to want.</em> Hold that frame in mind as the four steps walk.</p><p><strong>Prompting</strong> was the first cliff. You typed a sentence and the machine answered with a paragraph. The novelty was simply that it answered at all. GPT-3 made it real in 2020, and ChatGPT made it mainstream at the end of 2022. The discipline was that the machine answered sometimes well and sometimes badly, and the difference between the two was a black box. Prompting solved the <em>access</em> problem, meaning how you got useful output from a probabilistic system in the first place, and it left the <em>reliability</em> problem wide open.</p><p><strong>Prompt engineering</strong> was the response. Teams began treating the prompt as a designed artifact, using few-shot examples, role priming, and chain-of-thought scaffolding to coax better behavior out of the model. A small industry of tooling appeared almost immediately. Microsoft shipped PromptFlow, and the rest of the ecosystem shipped equivalents. The discipline was real and the gains were measurable.</p><p>But prompt engineering solved the prompt. It did not solve the application. A well-crafted prompt does not know what your customer’s account balance is, what the retrieval index returned, what the previous twelve turns of the conversation said, or which tools the model can call. The bottleneck moved.</p><blockquote><strong><em>The bottleneck has been moving, and the language has never caught up.</em></strong></blockquote><p><strong>Context engineering</strong> was the response to that. The work shifted from optimizing the sentence to optimizing what the model could see when the sentence arrived. Retrieval-augmented generation, tool registries, memory systems, and plugin architectures all became first-class concerns. Microsoft renamed the operating table the <em>Kernel</em> and built Semantic Kernel around it. LangChain did the same shape of work in a different idiom and arguably won the mindshare battle. By mid-2025 Andrej Karpathy was tweeting that the new skill in AI was not prompting but context engineering, and by July of that year Gartner was declaring that <em>context engineering is in, prompt engineering is out</em>. Eighteen months from practitioner observation to industry-analyst proclamation. The discipline was real and the gains were real.</p><p>But context engineering solved the input. It did not solve the outcome. A well-furnished context does not, by itself, tell the model what <em>good</em> looks like. A model with perfect retrieval and full tool access can still produce something the human did not ask for and cannot use.</p><p><strong>Intent engineering</strong> is the current waypoint. The work shifted again, this time from optimizing the input to specifying the goal. The idea is to tell the agent what you want in terms precise enough that the agent can plan its way to the outcome rather than guess at it. GitHub’s Spec-Kit is positioned around exactly this shift, and the BMAD Method has emerged alongside it as a spec-driven framework with its own following. The rest of the field is converging on the same posture from different directions.</p><p>Intent engineering is the right diagnosis. Code is no longer the bottleneck. Specification is.</p><p>But here is the part nobody is saying.</p><h3>The unfinished step</h3><p>We have named the practice. We have not named the language.</p><p>Read any serious treatment of intent engineering and watch what happens. The author defines the problem clearly. The author argues persuasively that intent is now the load-bearing artifact. The author then shows examples written in <em>English prose, in the body of a prompt.</em></p><p>That is the unfinished step.</p><p>Most of the current writing on intent engineering frames it at the altitude of governance, meaning the encoding of organizational objectives, cultural values, and policy constraints into agent architectures. That work matters and the writers doing it are not wrong. But the claim this series is making sits at a lower altitude and at finer granularity. Behavioral intent, expressed precisely enough that an agent can execute it and a human can verify it, at the level of the unit of work. That is where the trust loop closes or fails to close. Governance sits above. The unit of work is where the code gets written. The claim is not smaller. It is more consequential, because nothing in the governance layer matters if the unit of work cannot be specified and verified.</p><p>Prompting graduated to prompt engineering when prompts became artifacts a team could review and version. Prompt engineering graduated to context engineering when context became infrastructure a platform could manage. Context engineering graduated to intent engineering when the goal became more important than the input.</p><p>Intent engineering has not yet graduated, because the artifact it produces, meaning the intent itself, is still being written in unstructured prose.</p><blockquote><strong><em>The discipline has a name. The medium does not.</em></strong></blockquote><h3>The decades-long dance</h3><p>This part is worth slowing down for, because it is the move every senior engineer in the audience has already half-thought.</p><p>Humans have been expressing intent to other intelligent executors for as long as software has been built. Product managers express intent to engineers. Engineers receive that intent, enrich it, and translate it into something the machine understands. We have been doing this dance for decades, with a stack of artifacts between the human and the machine. The user story. The acceptance criteria. The design doc. The API contract. The test. The code itself.</p><p>The artifacts are not all equal. Some are negotiable English. Some are executable. The act of <em>engineering</em> is the act of moving down that stack, from the squishy to the precise, and producing something a deterministic machine can run.</p><blockquote>“Oh, you just got here? I been doin this shit for over ten years.”</blockquote><blockquote><em>- Puffy, </em>I Get Money (Forbes 1, 2, 3 Remix)</blockquote><p>AI-augmented engineering changes one variable in that equation. The executor on the other end is no longer deterministic. The agent is probabilistic. It will give you something different on Tuesday than it gave you on Monday, given the same input.</p><p>This is the fact every step in the progression has been quietly trying to solve.</p><p>That is what the four waypoints have in common. They are all attempts to wring determinism out of an inferential machine. Better prompts to make the output less variable. Better context to make the input more complete. Better intent to make the outcome more constrained.</p><p>Each step pushed determinism a little further into the system. None of them closed it.</p><p>The newest move on the field, <em>harness engineering</em>, is a confirmation of this pattern rather than an exception to it. A harness is the system around an agent, including the tools, validators, retry logic, observability, and guardrails that constrain what the agent can do and verify what it produces. A good harness is also a specification-enrichment engine. It takes the user stories and acceptance criteria a human authored, surfaces the gaps, recommends the additions needed to close them, and routes those recommendations back to a human for accept, reject, or redirect. I know this because I am building harnesses, and the harnesses I build do exactly that. They take acceptance criteria from a PRD, harden them into Gherkin, generate feature files, generate BDD tests, and surface the gaps the original criteria did not anticipate.</p><p>The human originates intent. The harness pressure-tests it. The specification, hardened by both, is what closes the trust loop.</p><h3>What closes the loop</h3><p>Here is the wager that Articles 4 through 13 will defend.</p><p>The loop closes when the specification of intent is also the verification of output. When the artifact that says <em>what the agent should do</em> is the same artifact that tests <em>whether the agent did it</em>. When intent and verification are the same document.</p><p>That is not a new idea. It is, in fact, an old one, old enough that most teams have it sitting in their backlog under the name <em>acceptance criteria</em>. They are just not using it the way the moment demands.</p><p>Article 1 planted the flag. Article 2 staked out the ground beneath it. This article traced how the industry got here and named the step nobody has finished.</p><p>The next article asks the question that makes the rest of the series urgent. <em>If agents can produce code in seconds, what is the scarce resource?</em></p><p>The answer is not code. It never was.</p><p><em>Further reading: Article 1 of this series, </em><a href="https://medium.com/@walter.pinson/gherkin-may-be-the-most-consequential-language-of-the-ai-augmented-era-b6ce28f85a7e"><em>“Gherkin May Be the Most Consequential Language of the AI-Augmented Era”</em></a><em>, and Article 2, </em><a href="https://medium.com/@walter.pinson/defining-ai-augmented-engineering-2955d4747437"><em>“Defining AI-Augmented Engineering”</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebbe09bcda42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Defining AI-Augmented Engineering]]></title>
            <link>https://medium.com/@walter.pinson/defining-ai-augmented-engineering-2955d4747437?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/2955d4747437</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-leadership]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Thu, 07 May 2026 23:29:41 GMT</pubDate>
            <atom:updated>2026-05-07T23:29:41.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HY0D1KN7xXub2JkT_WcgHw.png" /></figure><p><em>The Intent-Engineering Field Guide | Part 2 of 13</em></p><h3>Defining AI-Augmented Engineering</h3><p>The industry calls it <em>agentic engineering</em>. I don’t.</p><p>The word absolves the human. It puts the agent in the driver’s seat and quietly relocates accountability to a thing that cannot be held accountable. That isn’t a semantic preference. It’s a category error, and category errors at the start of an era compound for years.</p><p>The right phrase is <strong>AI-augmented engineering</strong>. Humans are still piloting the ship. The AI is augmenting human capability, not replacing the human who is responsible for the outcome.</p><p>Article 1 planted the flag. This article stakes out the ground beneath it.</p><h3>There is nothing new under the Sun</h3><p>When I first started groking blockchain, two recognitions made everything click.</p><p>The general ledger is just another distributed database. Smart contracts are just another form of stored procedure. The novelty wasn’t in the primitives. It was in the configuration. The trust model, the consensus mechanism, the economic incentives wrapped around well-understood building blocks.</p><p>AI-augmented engineering is the same shape of recognition.</p><p>The practice of directing other intelligent agents toward an outcome is not new. Defining the work, providing constraints, reviewing the output, redirecting when the work goes sideways. Software engineering managers have been doing exactly that for decades, with engineers as the agents. The discipline has a name. It’s called <em>management.</em></p><p>What’s new is not the discipline. What’s new is who has to exercise it, how often, and how fast.</p><h3>The definition</h3><p><strong>AI-augmented engineering</strong> is the practice of building software in which human engineers direct AI agents, through specification, constraint, and review, to produce work product the human remains accountable for.</p><p>Three things are worth calling out about that definition.</p><p><strong>Direction, not delegation.</strong> The human sets the work, the constraints, and the standard. The agent executes inside those bounds. The relationship is closer to a tech lead and a strong individual contributor than to a customer and a vendor.</p><p><strong>Specification, constraint, and review are the load-bearing activities.</strong> Each one has a discipline behind it, and each gets repriced in the agent era. Specification becomes intent engineering. Constraint becomes architecture and standards. Review becomes verification, which is the closing of the trust loop the rest of this series defends.</p><p><strong>Accountability stays with the human.</strong> The agent does not own the outcome. The agent cannot be fired, sued, audited, or held responsible. If the code ships and the system fails, a human owns that. The terminology should reflect that fact. <em>Agentic</em> does not. <em>AI-augmented</em> does.</p><p>It’s also worth being clear about what AI-augmented engineering is not.</p><p><em>Vibe coding</em> is unstructured prompting toward an unspecified outcome. It’s recreation, not engineering.</p><p><em>AI-assisted development</em> (autocomplete, in-line suggestions, the everyday tools) is one capability inside AI-augmented engineering, not the whole of it.</p><p><em>Full autonomy</em> is a destination some are pursuing and no one has reached at production scale. The accountability problem above does not get easier on the way there. It gets harder.</p><p>The practice has a practitioner. That’s the question worth answering next.</p><h3>The AI-augmented engineer</h3><p>The AI-augmented engineer is the human who exercises specification, constraint, and review at a tempo and standard the agents can execute against.</p><p>Here’s the part most of the industry isn’t saying out loud:</p><p><strong>Software engineering managers are the population best-positioned for this moment.</strong></p><p>Not because managers are better engineers. They aren’t, on average. That’s why they’re managers. But the muscle the AI-augmented engineer needs to exercise is the muscle managers have been exercising for years.</p><p>Work breakdown structure. Defining the unit of work clearly enough that someone else can execute it. Specifying acceptance criteria. Providing guardrails. Reviewing work product against the specification. Redirecting when the work drifts. Reading code you didn’t write and judging whether it’s right.</p><p>Individual contributor engineers have spent their careers exercising a different muscle: writing the code themselves. That muscle is still valuable, and Article 4 will defend why, but it’s no longer the <em>primary</em> muscle of the role. The agent writes most of the code. The human directs, constrains, and verifies.</p><p>Three advantages the experienced manager brings that survive the transition:</p><p><strong>Broad context.</strong> The ability to hold the system in your head while the agent works on a piece of it. Knowing how this module connects to that one, why this contract exists, what assumptions the data layer makes. Agents don’t have that. They have what’s in the prompt and what’s in the codebase they can see.</p><p><strong>Situational awareness.</strong> Recognizing when the work is drifting before the drift becomes damage. The half-second where you read what the agent produced and your gut says <em>something is off here</em>, even if you can’t articulate what, and you stop and look closer. That’s not a prompt. That’s a trained nervous system.</p><p><strong>Gut instincts.</strong> The accumulated residue of having watched things break before. Pattern recognition that doesn’t show up in any specification. The senior practitioner’s superpower, and the one most resistant to automation.</p><p>The honest implication for individual contributors: the translation step is real. The muscle is learnable, but it isn’t the muscle most ICs have been training. The engineers who make the translation will be the most valuable humans on the team. Article 11 takes up that question directly.</p><h3>The practitioner’s move: paint by numbers</h3><p>The agents are creative. Creative is good. Creative without constraint is a forty-eight-hour codebase sprawl that nobody wants to maintain.</p><p>The AI-augmented engineer’s move is to engineer determinism into the system before the agent ever runs.</p><p>How? With reference architectures, established patterns, and proven processes — the framework inside which the agent works.</p><p>Paint by numbers.</p><p>The painter is the agent. The numbers are the architecture. The painter can be as creative as it wants. The numbers make sure the result is recognizable. More importantly, the numbers tell the human where to look when things go sideways.</p><blockquote><em>When something breaks, I know where the bodies are buried.</em></blockquote><p>That’s the leverage. Not that surprises don’t happen. They do, even inside a well-engineered framework. The agent will surprise you inside the lines. The win is that when it does, the search space for diagnosis narrows from <em>the whole system</em> to <em>this module, this layer, this contract.</em></p><p>This is also the answer to the question that haunts every senior engineer watching agents work: <em>what happens when the agent reaches its limit and the code goes sideways?</em> The answer is that someone has to fix it, and that someone needs to know the system well enough to find the failure fast. A reference architecture you designed and a constraint set you enforced is a system you understand. A free-form agent sprawl is not.</p><p>The three load-bearing activities all benefit from determinism the engineer engineers in. The reference architecture is the constraint. The specification, and the series will argue this should be Gherkin, is the specification. The agent’s output, evaluated against both, is the review.</p><p>The whole practice is a system the engineer designs.</p><h3>What this means</h3><p>The default narrative is that AI is hardest on managers, because it automates the work they oversee. The opposite is closer to the truth.</p><p>AI is hardest on the engineer who only knew how to write code, because the code is the part the agent does fastest. The discipline that survives is the discipline of directing the work, constraining the work, and verifying the work.</p><p>That’s what managers do.</p><p>That’s what the AI-augmented engineer is.</p><p>The good news for ICs: the muscle is learnable.</p><p>The bad news: it’s not the muscle most of us trained.</p><p>The next article in the series traces the four-step progression that brought us here. Prompting, prompt engineering, context engineering, intent engineering. And the unfinished step nobody is naming.</p><p><em>Further reading: Article 1 of this series, </em><a href="https://medium.com/@walter.pinson/gherkin-may-be-the-most-consequential-language-of-the-ai-augmented-era-b6ce28f85a7e"><em>“Gherkin May Be the Most Consequential Language of the AI-Augmented Era.”</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2955d4747437" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gherkin May Be the Most Consequential Language of the AI-Augmented Era]]></title>
            <link>https://medium.com/@walter.pinson/gherkin-may-be-the-most-consequential-language-of-the-ai-augmented-era-b6ce28f85a7e?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6ce28f85a7e</guid>
            <category><![CDATA[quality-engineering]]></category>
            <category><![CDATA[gherkin]]></category>
            <category><![CDATA[ai-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[bdd]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Mon, 04 May 2026 15:23:39 GMT</pubDate>
            <atom:updated>2026-05-25T07:19:15.172Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N55U8_2gvxt8nkoc0LZbpA.png" /></figure><p><em>The Intent-Engineering Field Guide | Part 1 of 13</em></p><p>We’ve watched a four-step progression in barely three years.</p><p>Prompting. Prompt engineering. Context engineering. Intent engineering.</p><p>Each step was hailed as the destination. Each turned out to be a waypoint. And here’s the part nobody is saying out loud: we have named the <em>practice</em> of intent engineering, but we have never named the <em>language</em>.</p><p>That’s a problem. Because the practice doesn’t work without one.</p><p>I’m going to plant a flag.</p><p><strong>Gherkin may be the most consequential language of the AI-augmented engineering era.</strong></p><p>Not because it’s elegant. It isn’t. Not because it’s new. It’s been sitting on the shelf for nearly twenty years. But because it is the only widely-adopted notation that does three things at once. It expresses human intent in a form humans can read. It generates the tests that verify an agent’s output. And it survives the handoff between product, engineering, and AI agents without losing meaning.</p><h3>Why this claim, and why now</h3><p>When an agent can produce a working codebase in a weekend, the bottleneck is no longer code production. It’s two things: specifying intent precisely enough for an agent to execute it, and verifying that what came back is actually what you asked for.</p><p>Both are language problems.</p><p>Both are unsolved.</p><p>The industry’s response has been to invent better prompts, better context windows, better orchestration. All useful. None of them address the underlying issue: there is no shared, structured, executable language for expressing what we want and verifying what we got.</p><p>There is, however, a candidate. It’s structured natural language. It’s composable. It produces the tests that close the trust loop. And it’s already in your backlog under the name “acceptance criteria.” You’re just not using it the way the moment demands.</p><blockquote>“See, I couldn’t walk the walk, couldn’t really talk the talk,<em> </em>Had to get my talk to properly explain my walk,<em> </em>Cause this lack in talk had my walk looking off.”</blockquote><blockquote><em>- Lupe Fiasco, </em>Failure</blockquote><p>The walk is what your team builds. The talk is how you specify what should be built. When the talk doesn’t match the walk, the walk looks off, and in the agent era the walk looks off at industrial scale.</p><h3>Four pillars</h3><p>Four pillars hold up the claim.</p><p><strong>Code is cheap. Trust is expensive.</strong> When agents produce code in seconds, the scarce resource is justified confidence in what they produced. Gherkin closes the verification loop because the specification <em>is</em> the test. I’ve watched off-shoring outfits deliver precisely what the requirements document said and have it rejected anyway, because no one had specified what the customer actually wanted. I wrote about that failure mode in 2009. Agents have not solved it. They have industrialized it.</p><p><strong>Craftsmanship matters more, not less.</strong> When an agent can sprawl a codebase in 48 hours, the disciplines that constrain complexity (domain-driven design, ubiquitous language, hexagonal architecture) become survival tools. Gherkin is ubiquitous language made executable. It is the user-facing edge of the craftsmanship stack.</p><p><strong>Quality engineering is the new load-bearing discipline.</strong> TDD, ATDD, BDD, and the discipline of identifying edge, corner, and error cases used to live at the periphery of the team. They are now the disciplines that constrain agent output. The QE specialist is about to be repriced.</p><p><strong>The hybrid engineer is the new 10x engineer.</strong> The person who can express intent precisely <em>and</em> verify agent output against that intent is the highest-leverage human on the team. The line between PM and engineer is dissolving.</p><p>Each pillar deserves its own article. None are throwaway claims. All point at the same load-bearing conclusion: in the AI-augmented engineering era, the specification is the artifact that holds up everything else.</p><h3>What this series is, and isn’t</h3><p>I owe you the limits of the claim.</p><p>Gherkin expresses <em>behavioral</em> intent. It is not a substitute for architectural diagrams, design documents, or implementation-level constraints. That’s a real boundary, and I’m naming it now so we don’t pretend otherwise.</p><p>But the boundary is smaller than most readers assume. Non-functional requirements (performance, availability, accessibility, security) are routinely treated as a separate category from behavior. They aren’t. A well-formed NFR is a behavioral expectation with measurable thresholds:</p><pre>Given the system has 10,000 active records<br>When a user searches for a record<br>Then the results appear within 2 seconds</pre><p>That isn’t a quality goal floating in a Confluence page. It’s a passing or failing test. The NFRs that resist this treatment, like internal memory ceilings or specific implementation constraints, are real. They’re also a much smaller residue than people think.</p><p>So here’s the wager the series will defend. In the AI-augmented engineering era, behavioral intent is the load-bearing form of intent, because it is the form that closes the trust loop between a human, a specification, and an agent’s output. Architecture still matters. Pure implementation constraints still matter. But neither produces the executable verification that tells you the agent did what was asked.</p><p>That is what Gherkin does. That is why it’s the candidate.</p><h3>What’s coming</h3><p>Thirteen articles. One argument.</p><ol><li><a href="https://medium.com/@walter.pinson/gherkin-may-be-the-most-consequential-language-of-the-ai-augmented-era-b6ce28f85a7e"><strong>The Thesis</strong></a> <em>(this article)</em></li><li><a href="https://medium.com/@walter.pinson/defining-ai-augmented-engineering-2955d4747437"><strong>Defining AI-Augmented Engineering</strong></a></li><li><a href="https://medium.com/@walter.pinson/the-progression-nobody-finished-ebbe09bcda42"><strong>The Progression Nobody Finished: From Prompting to Intent Engineering</strong></a></li><li><a href="https://medium.com/@walter.pinson/code-is-cheap-trust-is-expensive-02bbc23bec78"><strong>Code Is Cheap. Trust Is Expensive.</strong></a></li><li><a href="https://medium.com/@walter.pinson/why-software-craftsmanship-matters-more-now-not-less-1eb0801d9272"><strong>Why Software Craftsmanship Matters More Now, Not Less</strong></a></li><li><strong>The Hidden Costs of AI-Generated Code Proliferation</strong></li><li><strong>Less Is More: The New Engineering Virtue</strong></li><li><strong>Platform and Language Selection in the Age of Agents</strong></li><li><strong>Quality Engineering Is the New Load-Bearing Discipline</strong></li><li><strong>Product Management as a Force Multiplier</strong></li><li><strong>The Hybrid Engineer: Why PM Skills Are the New Senior Engineering Skill</strong></li><li><strong>Stop Writing Acceptance Criteria You Don’t Convert</strong></li><li><strong>Gherkin Delivers: Closing the Loop on Intent-Engineered Software</strong></li></ol><p>If your team is already writing acceptance criteria in user stories without converting them into executable specifications before development begins, you are leaving the most important leverage point of this era on the table. Article 12 is for you. So is the capstone.</p><p>I’ve been writing code since I was twelve. Professionally since 1991. Five technology cycles: PC, client-server, web 1.0, cloud, and whatever we end up calling the era we’re in now. I have never been more convinced that the answer to the era’s hardest engineering question has been sitting in plain sight, in a notation most teams treat as “the QA team’s problem.”</p><p>The team that figures this out is going to outbuild the team that doesn’t.</p><p><em>Further reading: </em><a href="https://medium.com/@walter.pinson/architectural-fidelity-with-globally-distributed-software-development-teams-5f7721fea8ce"><em>“Architectural Fidelity with Globally Distributed Software Development Teams.”</em></a><em> Walter Pinson, 2009.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6ce28f85a7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can A Metaworld Help Stop Chicago Gun Violence?]]></title>
            <link>https://medium.com/crypt00pps/can-a-metaworld-help-stop-chicago-gun-violence-145ebf88f4ec?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/145ebf88f4ec</guid>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[metaverse]]></category>
            <category><![CDATA[rap]]></category>
            <category><![CDATA[social-justice]]></category>
            <category><![CDATA[chicago]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Thu, 28 Apr 2022 01:10:17 GMT</pubDate>
            <atom:updated>2023-06-06T10:47:47.296Z</atom:updated>
            <content:encoded><![CDATA[<h4>Drill Music NFTs</h4><h4>FōNem | CryptoOpps is a gamified NFT collection and metaworld that seeks the answer to this question.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zxkWk-v-9dJ3bzCD" /><figcaption>Photo by <a href="https://unsplash.com/@nathanncosta?utm_source=medium&amp;utm_medium=referral">Nathan Costa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Metaworlds can serve as tools that can be used to chip away at the root causes of violence in cities like Chicago. This claim raises the obvious question. What are the root causes of violence in these cities? The answer is complicated. But it most certainly involves a city’s youth and includes the trifecta of poverty and hopelessness undergirded by a poor and irrelevant (perhaps, impractical) public education system. With seemingly no other opportunities available to them, it’s not hard to understand why so many of a city’s youth gravitate to the drug trade, which is itself a source of violence around the globe.</p><p>In order to attack these root cause issues, a metaworld must provide an alternate reality with</p><ol><li>meaningful economic opportunity (goals)</li><li>meaningful example alternatives (realism)</li><li>a meaningful education (roadmap)</li></ol><p>Put another way, a metaworld must present a desirable economic goal for which the youth can strive, show that the goal is realistic and achievable, and then provide a roadmap, or clear set of instructions, for achieving the goal.</p><p>Metaworlds based on blockchain and other Web 3.0 technologies have the ability to deliver on all three dimensions. I believe in this so firmly that I have put my money where my mouth is. It is my reason for creating CryptoOpps (pronounced <em>crypto-</em><strong><em>Opps</em></strong>).</p><p>CryptoOpps, as a metaworld, is a platform for change.</p><ul><li>Changing narratives through storytelling and engagement</li><li>Changing outcomes by providing economic opportunity</li><li>Changing participation levels (in the Web 3.0 ownership economy) through meaningful and deliberate education</li></ul><h3>Goals</h3><p>In order for a metaworld to be effective in the effort to stop inner city violence, it must present a credible alternative to the status quo. Focusing on poverty as a root cause of the violence, it is easy to understand that a metaworld must provide meaningful economic opportunity.</p><p>To young people living in violence-plagued neighborhoods, the drug game, the stick-up game, and the finesse game (scamming) are well-known for the economic opportunities that they provide. So in order to capture market share from the status quo, a metaworld must demonstrate multiple avenues for people to generate personal income. Even if the income streams associated with the metaworld are less lucrative than the status quo, the metaworld can still compete by compensating with the value of <em>occupational risk reduction</em>. For instance, one is less likely to go to jail flipping NFTs than flipping coke. So after accounting for legal fees and years of life lost, the metaworld has one coming out on top.</p><p>The existing violence in these communities is often born out of disputes and rivalries associated with the drug trade. Therefore, it stands to reason that reducing drug trade participation levels must put downward pressure on the levels of associated violence.</p><h3>Realism</h3><p>Often times, community outreach efforts fall on deaf ears. This is because the target audience cannot really see themselves in the alternative scenarios on offer. To them, it’s just not real.</p><blockquote>If my mind can conceive it<br>And my heart can believe it,<br>Then I can achieve it.</blockquote><blockquote>— Muhammad Ali</blockquote><p>They’ve seen people from their neighborhood make it as “big time” drug dealers. They’ve seen people from their neighborhood make it as drill rappers. Some have even seen people from their neighborhood make it in sports. So they know that those things are, at least, achievable; despite the abysmal odds.</p><p>For a metaworld to break through, it’s not enough to just provide a dream. The target audience needs to see concrete evidence that the alternatives that they are being promoted are real and, in fact, <em>realistically possible for </em><strong><em>them</em></strong>.</p><blockquote>Now all the little soldiers wanna roll with my team<br>Cause I ain’t sold’em a dream, I just showed ’em the cream</blockquote><blockquote>—Shawn “ Jay Z” Carter, Paper Chase</blockquote><p>In effect, the metaworld must show receipts. Armed with proof that the alternative opportunities are real, people will be more inclined to pursue those opportunities than to engage in risky or violent behaviors. Give a person something to live for, they are more likely to choose life over death.</p><h3>Roadmap</h3><p>Kids often reject community outreach efforts as unreal when they are not presented with a clear path from A to Z. It’s easy for some outsider to come in and say, “Hey. Don’t sell drugs. Be a lawyer, instead.” These kids know, without anyone stating the obvious, that their schools are not preparing them to enter undergraduate college, let alone law school. Unsurprisingly, that alternative is not real to them. It’s just words.</p><p>So how can a metaworld make alternatives to the status quo real to the kids in these neighborhoods who desperately need alternatives to the status quo? A metaworld can offer step by step instructions and education that, if followed, lead directly to the outcomes on offer.</p><blockquote>I can show you better than I can tell you</blockquote><blockquote>— Ancient Street Proverb</blockquote><p>Trade schools are a great example, here. Unlike other schools that teach skills that are not necessarily directly applicable to the practical objectives, trade schools cut out the fluff. Knowledge of eighteenth century English literature is not a requirement for most trades. If a student takes some very specific training courses that are directly related to being a mechanic, then that student can be sure that they will have a good shot at earning an income as a mechanic, upon completing the training.</p><p>It’s often not enough to merely make people aware of alternatives and opportunities. Left to their own devices, many people will give up or not even try because they often do not know where to begin. A metaworld that provides clear instructions on how to take advantage of the available opportunities is much more likely to increase engagement than ones that do not.</p><p>[<em>As an aside, this is more in line with the Booker T. Washington, Tuskegee University school of thought than it is with the more cerebral W. E. B. DuBois perspective. It’s not that one is correct or the other is not. It is more that one is a platform or launching pad for the other. Think Maslow’s hierarchy.</em>]</p><p>Historically, metaworlds have been looked upon as tools of escapism. But with advances in technology, we are finding that they can, in fact, impact and improve our realities. And a metaworld can absolutely be brought to bear to make a positive impact on some of our societal ills, like inner-city violence. As long as the metaworld creates real economic opportunities for the disaffected youth, with clear guidance on how to take advantage of those opportunities, it can help stem the tide of inner-city gun violence. This assertion is not yet proven, however. It is currently just a theory. But it is a theory that is being put to the test by CRYPT00PPS.</p><h3>FōNem | CryptoOpps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lK99RDTAHK707DKzoReYtg.png" /></figure><p>CryptoOpps, as a metaworld, is a platform for change.</p><ol><li>Changing narratives through storytelling and engagement</li><li>Changing outcomes by providing economic opportunity</li><li>Changing participation levels (in the Web 3.0 ownership economy) through meaningful and deliberate education</li></ol><p>CryptoOpps has been architected from the ground up to create a virtuous cycle between the platform and the community.</p><p>Stay tuned. You won’t want to miss this!</p><p>Inspired by Chicago Drill Music, FōNem (aka The Homies) is a collection of 10,000 randomly generated but intentionally curated CryptoOpps NFTs — unique digital collectibles that live on the Ethereum blockchain. Learn more at <a href="https://www.crypt00pps.io/">https://www.crypt00pps.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=145ebf88f4ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/crypt00pps/can-a-metaworld-help-stop-chicago-gun-violence-145ebf88f4ec">Can A Metaworld Help Stop Chicago Gun Violence?</a> was originally published in <a href="https://medium.com/crypt00pps">CryptoOpps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, World!]]></title>
            <link>https://medium.com/crypt00pps/hello-world-d2f8010a8f8f?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2f8010a8f8f</guid>
            <category><![CDATA[social-justice]]></category>
            <category><![CDATA[hip-hop-culture]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[drill-music]]></category>
            <category><![CDATA[hip-hop]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Tue, 26 Apr 2022 23:17:18 GMT</pubDate>
            <atom:updated>2023-06-06T10:59:16.033Z</atom:updated>
            <content:encoded><![CDATA[<h4>Drill Music NFTs</h4><h4>Introducing the FōNem NFT collection from CryptoOpps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMUrXhN555-xkMtD0FPtvQ.png" /></figure><p>Inspired by Chicago Drill Music, FōNem (<em>aka The Homies</em>) is a collection of 10,000 randomly generated but intentionally curated CryptoOpps (<em>pronounced crypto</em><strong><em>-OPPS</em></strong>) NFTs — unique digital collectibles that live on the Ethereum blockchain.</p><p>Your <strong>FōNem NFT</strong> doubles as your <strong>Zero Block</strong> hood pass and grants you members-only (<em>gang gang</em>) benefits, the first of which is access to the Tag Wall, a collaborative graffiti board where you can write or draw anything that you like. The Tag Wall is only visible to other CryptoOpps NFT holders. Future features and perks can be unlocked by the community through <a href="https://www.crypt00pps.io/roadmap">Roadmap Activation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6r0gn0PHRG3CCrgfnxXVQ.png" /></figure><p>Not your typical NFT project, CRYPT00PS is also about doing good in the communities that inspired its creation. Be sure to follow us for more on this in future articles…</p><h3>Minting is Live</h3><p>You can, now, mint (<em>that’s crypto lingo for </em><strong><em>produce</em></strong><em> and </em><strong><em>purchase</em></strong>) your very own CryptoOpps NFTs at <a href="https://mint.crypt00pps.io/">mint.crypt00pps.io</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JCHqMexPI1_UlBzAcENfCA.png" /></figure><p>Each FōNem NFT belongs to one of four mining pools: 1) Gwei DAOs, 2) Block DAOs, 3) Vyper Logs, and 4) Ledger Keys. And you have the power to choose the mining pool that you want to mint from. Feel free to mint multiple NFTs from the same mining pool, or mix and match. You can learn more about these mining pools here: <a href="https://www.crypt00pps.io/story">https://crypt00pps.io/story</a>.</p><p>In addition to the minting website, you can also <a href="https://opensea.io/collection/crypt00pps-fonem">follow the collection on OpenSea</a>.</p><h3>Meet the Team</h3><h4>CFL Squad (CryptoOpps For Life!)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*z65crwOnfPf_-VJqdHkN5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OXh49AcQQlUXBrxVcCXStg.png" /><figcaption>Big Walt aka CFL Hug0 | Founder, Product &amp; Engineering</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kKQb9Khk3D5IB0nyLYwzjw.png" /><figcaption>CFL Ninja | Founder, Engineering</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*optWntGffFuvIL4pM0RUWA.png" /><figcaption>CFL Ace | Art &amp; Illustration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*xYpg9BZ09C9jbiwdpUjPeA.png" /><figcaption>CFL Diva | Community</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EfZnqWyGKtI7-OUgArRvhQ.png" /><figcaption>CFL Yongmun | Community</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*r8Bi4ChRsjIsEPswoqUhww.png" /><figcaption>CFL Zay | Community</figcaption></figure><p>Visit <a href="http://www.crypt00pps.io/">www.crypt00pps.io</a> for more details.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2f8010a8f8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/crypt00pps/hello-world-d2f8010a8f8f">Hello, World!</a> was originally published in <a href="https://medium.com/crypt00pps">CryptoOpps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So…, Bail-Ins Are a Thing]]></title>
            <link>https://medium.com/block-boys/so-bail-ins-are-a-thing-bb903cfd8200?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb903cfd8200</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptoeconomics]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 00:29:15 GMT</pubDate>
            <atom:updated>2022-02-09T12:46:46.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*72Rb-1p1VwFfYuES.png" /><figcaption>Image above: Cartoon of Cypriot bank teller robbing customer by Michael Ramirez.</figcaption></figure><p>“Bail-ins” are a relatively unknown risk associated with centralized banking that can be mitigated with consumer adoption of cryptocurrencies. Centralized banking is inherently risky for consumers and bail-ins are just the latest addition to its growing portfolio of risk. Cryptocurrencies, such as Bitcoin and Ether, can offer protections against bail-ins. However, replicating existing banking models by merely switching fiat currency with cryptocurrencies leaves consumers exposed to similar risks.</p><h3>What is a bail-in?</h3><p>Unless you’ve been living under a rock, you know what is a bank bail-<em>out</em>. That is when the government “loans” tax-payer money to failed banks in order to cover losses, typically incurred through high-risk speculation. What you may not be aware of is an alternative solution to that problem: the bail-in.</p><blockquote><em>…a bail-in, a term first popularised in the pages of </em><a href="http://www.economist.com/blogs/economist-explains/2013/04/economist-explains-2"><em>The Economist</em></a><em>, forces the borrower’s creditors to bear some of the burden by having part of the debt they are owed written off.</em></blockquote><p>According to <a href="http://www.investopedia.com/terms/b/bailin.asp">Investopedia</a>, a bail-in is rescuing a financial institution on the brink of failure by making its creditors and depositors take a loss on their holdings. In certain instances, this is doubly painful for consumers because they twice take a haircut. The bank ends up taking all or a portion of the money that they have deposited into their checking and savings accounts and, if their pension funds have been invested with the same bank via <em>relatively safe</em> bonds, they lose part or all of that, as well.</p><p>At this point, you may be asking yourself how this is even possible. Part of it has to do with a little-understood feature of banking. Most people believe that when they deposit money into a bank account that the bank is merely holding their money for them. This is simply not the case. As soon as a person deposits money with the bank, that person is no longer the owner of the funds. Ownership has been transferred to the bank, of which the depositor has just become an an unsecured creditor. The bank issues a promissory note to its new creditor and now it is free to do whatever its wishes with its new money.</p><p>If one believes that one’s money is safer in the bank than it is underneath one’s mattress, then the banking relationship described above appears to be a fair exchange. However, this exchange is not without risk. And that risk appears to be growing.</p><blockquote><em>The </em><a href="http://lexicon.ft.com/Term?term=bail_in"><em>US has already put in place bail-in-like powers</em></a><em> as part of the Dodd-Frank financial reform act passed last year. The law includes a resolution scheme that gives regulators the ability to impose losses on bondholders while ensuring the critical parts of the bank can keep running.</em></blockquote><blockquote><em>Employees would be paid, the lights would stay on and derivatives contracts would not have to be instantly unwound, one of the areas that caused market confusion when Lehman Brothers collapsed in September 2008.(1)</em></blockquote><p>We have already witnessed the 2013 and 2015 bail-ins involving the <a href="https://www.forbes.com/sites/nathanlewis/2013/05/03/the-cyprus-bank-bail-in-is-another-crony-bankster-scam">Bank of Cyprus</a> and several <a href="http://www.bbc.com/news/world-europe-35062239">Italian banks</a>, respectively. These were not one-offs. Evidently, bail-ins are the new, preferred bank rescue strategy in the European Union and the United States. In the US, this is possible due to a provision in the <a href="https://www.forbes.com/sites/nathanlewis/2013/05/03/the-cyprus-bank-bail-in-is-another-crony-bankster-scam">2005 bankruptcy law</a> that made derivatives liabilities more senior than depositors. This means that when a bank becomes insolvent and the line of debtors forms to collect their money, the derivative sellers get to be in the front of the line while the bank’s depositors get pushed to the back. As one might expect, the bank will have run out of money by the time it gets around to paying its depositors; which are unsecured creditors(2). In 2016, the <a href="http://www.lsta.org/news-and-resources/news/the-lsta-publishes-a-form-of-eu-bail-in-contractual-recognition-provision">EU issued similar bail-in rules</a>. A new term has entered the pop culture lexicon that captures this phenomenon. It’s called getting <a href="http://www.urbandictionary.com/define.php?term=Cyprused">Cyprused</a>.</p><h3>Cryptocurrencies To The Rescue</h3><p>Cryptocurrencies, such as Bitcoin and Ether, can offer protections against some of the risks inherent in traditional banking. Cryptocurrencies allow one to be one’s own bank. Though this is akin to storing money underneath your mattress, there are risk mitigation strategies that make self-banking a bit more practical and safe.</p><p>Bitcoin and cryptocurrencies, in general, are fundamentally peer-to-peer banking systems. They enable individuals to become their own banks. If you are your own bank, then there is no need to trust a third party. If you haven’t handed your money over to a third party then you are not at risk of losing your money due to institutional failure, either through a bail-in or bail-out. You are not at risk of being charged overdraft fees. You are also not at risk of the government taking your money without your knowledge when you store it in your private bitcoin wallet.</p><p>A bitcoin wallet is essentially a public / private cryptographic key pair within which value (BTC) can be stored on the blockchain. Bitcoin can be deposited into a wallet using the wallet’s public key. But bitcoin can only be removed from a wallet, or spent, using the wallet’s private key. Users typically store their bitcoins in a bitcoin wallet application. Bitcoin wallet applications come in one or more of three flavors: desktop, web, and mobile. In addition to wallet applications, there also exist <a href="http://www.coindesk.com/information/paper-wallet-tutorial/">paper wallets</a>; which document the wallet’s public and private key on printed paper. In order to own and spend Bitcoin, you must be in possession of both the public and private keys.</p><p>This model of banking is not risk free, however. As with keeping fiat currency under the mattress, cryptocurrency users are responsible for securing their own money. On the one hand, you have to provide for the physical security of your money. If you store your cryptocurrency on your phone, then you have to make certain that your phone is not stolen. Further, the ability to spend cryptocurrency is dependent on access to private keys. You must also protect and remember your private keys otherwise, your money can be stolen or forever lost. There are a number of methods that can be employed in order to <a href="https://www.welivesecurity.com/2015/03/03/10-tips-protecting-virtual-bitcoin-wallet/">secure a bitcoin wallet</a>, some of which include:</p><ul><li>Use 2-factor authentication</li><li>Disconnect from the internet so that hackers cannot steal private keys</li><li>Encrypt everything</li><li>Use paper wallets</li></ul><p>Nothing is 100% fool-proof but these methods can be employed to produce an acceptable level of risk with regards to protecting your cryptocurrency assets.</p><h3>Or, Maybe Not</h3><p>Simply using cryptocurrencies does not automatically protect one from classic banking risks. The risk posed by replicating existing banking models with cryptocurrencies is similar, if not greater. Leveraging third-party <a href="https://blockgeeks.com/guides/best-cryptocurrency-exchanges/">exchanges</a> to store cryptocurrencies in much the same way as we use banks to store our cash involves similar third-party risk.</p><p>Bitcoin, as envisioned by <a href="https://en.wikipedia.org/wiki/Satoshi_Nakamoto">Satoshi Nakamoto</a>, is intended to be decentralized money. It is meant to be traded from person to person as anonymously as one might place fiat currency into the cup of a homeless person. It was never intended to be controlled by one or more centralized third parties.</p><p>The nearly half a billion dollar theft from and subsequent <a href="http://www.thedailybeast.com/behind-the-biggest-bitcoin-heist-in-history-inside-the-implosion-of-mt-gox">failure of Mt. Gox</a> bears this out. A centralized repository of money on the internet represents a rich target for hackers. Further adding to the risk is that fact that there is very little regulation and oversight on these bitcoin exchanges in the US and internationally. So it is difficult to know whether the appropriate security measures matching the threat level have even been put in place. To this day, it is still unknown whether it was due to negligence or complicity. But 800,000 bitcoins were stolen from Mt Gox users. And since there is no FDIC equivalent for cryptocurrency exchanges, those users lost all of their money.</p><p>The recent situation at BitFinex was slightly different. The bitcoin exchange was hacked, much like Mt. Gox, and hackers got away with nearly 120,000 bitcoin ($60M at the time). The difference is that <a href="https://www.forbes.com/sites/francescoppola/2016/08/06/theft-and-mayhem-in-the-bitcoin-world/#15cfc953644f">Bitfinex implemented a bail-in</a>, forcing each customer to take a 36.067% haircut.</p><blockquote><em>After much thought, analysis, and consultation, we have arrived at the conclusion that losses must be generalized across all accounts and assets. This is the closest approximation to what would happen in a liquidation context. Upon logging into the platform, customers will see that they have experienced a generalized loss percentage of 36.067%. In a later announcement we will explain in full detail the methodology used to compute these losses.</em></blockquote><p>Bitfinex continues to operate, almost as if nothing ever happened.</p><h3>Conclusion</h3><p>Bail-ins can occur within any centralized financial institution where people deposit money or assets. This has started happening often enough that we call it getting “Cyprused” when a consumer loses his money in a bail-in. The bail-in, as a strategy, has been used to rescue a number of banks. And it has been used to rescue at least one cryptocurrency exchange. The only way that consumers can defend against bail-ins is to use cryptocurrency in the way that it was meant. That is by using cryptocurrency to be one’s own bank.</p><p>(1) Interestingly enough, commercial bank deposits would be completely unaffected by risky derivatives trading were <a href="http://www.investopedia.com/terms/g/glass_steagall_act.asp">Glass-Steagall</a> still in force. The law required a firewall between commercial banks that hold customer deposits and investment banks that trade high-risk derivatives.</p><p>(2) In the Cypriot bail-in, depositors were relieved of all funds they had on deposit over €100,000. In the United States, the FDIC insures bank deposits up to $250,000.</p><h3>Resources</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c243d425f013f05bd2a2cc335b6b9fa/href">https://medium.com/media/3c243d425f013f05bd2a2cc335b6b9fa/href</a></iframe><p><em>Originally published at </em><a href="http://walterpinson.com/Bail-Ins-are-a-Thing/"><em>walterpinson.com</em></a><em> on July 5, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb903cfd8200" width="1" height="1" alt=""><hr><p><a href="https://medium.com/block-boys/so-bail-ins-are-a-thing-bb903cfd8200">So…, Bail-Ins Are a Thing</a> was originally published in <a href="https://medium.com/block-boys">Block Boys</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Steem Randomness…]]></title>
            <link>https://medium.com/block-boys/steem-randomness-31ee2811f87?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/31ee2811f87</guid>
            <category><![CDATA[steemit]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 00:08:38 GMT</pubDate>
            <atom:updated>2018-10-15T00:44:34.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xrp_RyzYkyTkwQ4T" /><figcaption>“grayscale photography of man riding train” by <a href="https://unsplash.com/@lee10?utm_source=medium&amp;utm_medium=referral">Lee Hull</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, yesterday, I’m having a nice healthy conversation on Facebook with some of my more geek-minded mates (<strong><em>H/T</em></strong><em> Jamie V. for the Aussie slang rip-off</em>) about bitcoin and cryptocurrencies, in general. The whole thing started around a post about a kid who, at 18 years old, is <a href="http://www.cnbc.com/2017/06/20/bitcoin-millionaire-erik-finman-says-going-to-college-isnt-worth-it.html">now a millionaire, having invested in bitcoin</a> back when the coins were only US$12 a pop. At present, you’ll have to pay roughly US$2,300 to get your hands on a bitcoin.</p><blockquote><em>Bitcoin …a completely dumb idea, IMO. — Some Bloke</em></blockquote><p>Then general sentiment toward bitcoin was quite cold in the discussion thread. One bloke (<em>more Aussie slang, Jamie ;-)</em>) even referred to bitcoin as a “completely dumb idea”. I asserted that, though there might be challenges in the United States as it relates to bitcoin adoption, other parts of the world have shown much more interest. Asia, for instance, is a part of the world that seems very open to the idea of digital currency, in general, and cryptocurrency, more specifically. But, even this notion was challenged. So I did some quick googling to get some evidence to help make my case.</p><p>As it turns out, the future of <a href="https://www.techinasia.com/state-bitcoin-southeast-asia">bitcoin in Asia</a> didn’t look so bright back in 2014. Though the two large online Filipino merchants began accepting bitcoin payments, adoption as a payment mechanism for the rest of Southeast Asia seemed tepid. 2017 seems to mark a significant increase in Asian cryptocurrency adoption. China is currently testing a <a href="https://futurism.com/china-becomes-first-countrchina-becomes-first-country-in-the-world-to-test-a-national-cryptocurrencyy-to-test-national-cryptocurrency/">national cryptocurrency</a>. And though Japan already has roughly 4,500 merchants accepting bitcoin payments, the <a href="https://news.bitcoin.com/bitcoin-accepted-260000-stores-summer/">partnership between Coincheck and Recruit Lifestyle</a> is a game-changer. Enhancing the Recruit Lifestyle Airregi point-of-sale application to support bitcoin will enable consumers to spend their bitcoin at more than a quarter million food and retail locations throughout the country. I think the point was made. But still, Jamie is going to confirm this on his next trip. Stay tuned.</p><h3>Steemit</h3><p>Meanwhile, I decided to see how the Bic Camera bitcoin payment test, in Tokyo, was going. This led me to a <a href="https://www.reddit.com/r/Bitcoin/comments/649si6/we_tested_bic_cameras_bitcoin_payment_system_in/">reddit thread</a> on the subject. The conversation was interesting but I looked further and found myself watching video of an <a href="https://steemit.com/bitcoin/@penguinpablo/video-paying-with-bitcoin-at-bic-camera-in-tokyo-japan">actual bitcoin transaction</a> at Bic Camera. (<em>The video was also available on the reddit thread. But I was searching faster than I was reading.</em>) All of this was cool but I noticed that I was not watching the video on youtube. I was watching it on this web site called <a href="http://walterpinson.com/Steem-Randomness/steemit.com">steemit.com</a>; which I had never heard of before today. So I started to explore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w6mW0Z6YbOSAK8_1.png" /></figure><h3>What is Steemit?</h3><p>Turns out, Steemit is super cool. As far as I can gather, steemit.com is a social network built on top of the <a href="https://steem.io/">steem.io</a> platform. (<em>I could be wrong about this. It could be that steem is just the name of the rewards/currency.</em>) Its a social network that affords users the opportunity to earn cryptocurrency for their contributions. There is an algorithm that determines how much steem you get for posts, upvotes, comments, etc. The more steem you have, the more you can earn. And users have the option of converting a portion of their steem into other currencies: bitcoin, for instance.</p><blockquote><em>Steem is a blockchain-based social media platform where anyone can earn rewards.</em></blockquote><p>Naturally, there are many blockchain and cryptocurrency enthusiasts on Steemit. I immediately started consuming some great content. But, I didn’t want to just be a passive reader. I wanted to contribute to the conversations the same way that I do on GitHub or StackOverflow or even Facebook. I read one really good article <a href="https://steemit.com/eos/@trogdor/eos-vs-ethereum-for-dummies">EOS vs Ethereum for Dummies!</a>. It was such a well-written and informative piece that I wanted to give the author an up-vote. In fact, it spawned such an educational discussion that I wanted to give a few of the commenters up-votes. However, you cannot participate unless you have an account. So, of course, I kicked off the account creation process.</p><h3>Steemit is Not Anonymous</h3><p>For whatever reason, I was under the impression that I could operate under a veil of anonymity. Those hopes were quickly dashed when Steemit requested my cell phone number so that it could text me a registration code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yr-NdnEMgpbjQYUz.png" /></figure><h3>Steemit Makes You Wait</h3><p>My hopes for anonymity would not be the only ones that were dashed. So, too, were my hopes for instant gratification. It appears that I’ve been placed on some type of waiting list. At the very least, Steemit has some super-strenuous verification process. I’m not exactly sure what they are verifying, though. All they have to go on is a made-up username, a phone number, and an email address that may or may not be associated with a real identity. I hope they don’t make me wait too long. I’m ready to start contributing and earning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t1FOvs6OCEohYut0.png" /></figure><p>Since I have to wait, though, I may as well watch this educational video that explains what exactly is a blockchain-based social media platform. Perhaps, you might want to do the same.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxZmpCAqD7hs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxZmpCAqD7hs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxZmpCAqD7hs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/540c3a6f761f7c701551e212fdc6538a/href">https://medium.com/media/540c3a6f761f7c701551e212fdc6538a/href</a></iframe><h4>Resources</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/406bfb5972a4f84c890b2a932b281530/href">https://medium.com/media/406bfb5972a4f84c890b2a932b281530/href</a></iframe><p><em>Originally published at </em><a href="http://walterpinson.com/Steem-Randomness/"><em>walterpinson.com</em></a><em> June 26, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31ee2811f87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/block-boys/steem-randomness-31ee2811f87">Steem Randomness…</a> was originally published in <a href="https://medium.com/block-boys">Block Boys</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Late Payers Not Always At Fault]]></title>
            <link>https://medium.com/@walter.pinson/late-payers-not-always-at-fault-128ce1a49132?source=rss-6e4a7c3ec0fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/128ce1a49132</guid>
            <category><![CDATA[credit-report]]></category>
            <category><![CDATA[credit]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[credit-score]]></category>
            <dc:creator><![CDATA[Walter Pinson]]></dc:creator>
            <pubDate>Sun, 14 Oct 2018 23:40:06 GMT</pubDate>
            <atom:updated>2018-10-14T23:40:06.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*y8RiLkqzZvyZC6Qv" /></figure><p>The first thing that comes to mind when we learn that someone is late paying their bills is that they are irresponsible. However, when people pay their bills late in today’s economy, it is often due to circumstances beyond their control. They could be suffering the impacts of any number of macro- or microeconomic factors such as a weak economic recovery, shifts in the global economy, or an unforeseen medical emergency.</p><p>Even though the economy is in recovery, there is a great deal of underemployment and many people have been forced into low-paying jobs that don’t meet their pre-recession debt obligations. Worse yet, <a href="http://www.usnews.com/news/the-report/articles/2015/08/23/the-part-time-economic-recovery">many are still unemployed</a>. The number of part-time workers is up 84% post-recession and the number of low-wage jobs has increased by 2.4 million. Many people who were unemployed were forced to take jobs that were paying much less than what they used to earn. This can have a very negative impact on one’s ability to pay bills on time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P_0LZ3oXR2LtGTBp" /><figcaption>“photo of road between mountains” by <a href="https://unsplash.com/@sigurdarson?utm_source=medium&amp;utm_medium=referral">Gunnar Örn</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Additionally, shifts in the global economy can have an outsized impact on local geographic markets and, thus, impact entire communities’ ability to pay their bills on time. For instance, there has been a recent <a href="http://www.chron.com/business/article/More-Texans-are-late-on-credit-card-bills-car-6836280.php">substantial increase in the number of Texans who are late paying their credit cards and car loans</a>. This is due to the fact that oil is now less than $30 a barrel; which is crushing oil-dependent local economies. Louisiana, North Dakota, Oklahoma, and West Virginia are experiencing a similar impact. This is definitely beyond the control of the people affected by this.</p><p>Finally, an unforeseen medical emergency is naturally beyond anyone’s control. It can quickly sap a person’s income requiring them to make choices between paying for much-needed medical care or paying their other bills. In the wake of the Affordable Care Act, <a href="http://www.cnbc.com/id/100840148">high medical bills are still sending people into bankruptcy</a>.</p><p>So don’t be quick too judge if you learn that someone is slow to pay their bills or unable to pay, altogether. There is actually a very good chance that they could be dealing with circumstances that are completely beyond their control.</p><p><em>Originally published at </em><a href="http://walterpinson.com/Late-Payers-Not-Always-At-Fault/"><em>walterpinson.com</em></a><em> on February 26, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=128ce1a49132" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>