Chapter 1: What You Say When No One Is Listening

It is late, the house is quiet, and the conversation from earlier keeps replaying in your mind. You hear the question again. You hear your own answer. At the time, the lie came out quickly, almost automatically. Now there is no one left to convince. The room is dark, your phone is face down beside you, and the truth is still awake.

Sometimes this honest Christian conversation about lying and Jesus Christ begins after everyone else has gone to sleep. There is no argument to win and no image to protect. There is only the private knowledge that what you said was not true. In that silence, the lie often feels heavier than it did when you first spoke it.

That is where this deeper reflection on bringing hidden dishonesty into the light becomes personal. A lie does not stay inside the sentence where it began. It follows you into the next conversation. It changes how you listen, how you answer, and how safe you feel around the person you misled. Even when they suspect nothing, you begin living as though discovery is always close.

Most lies are attempts to escape a feeling. We do not want to feel ashamed, exposed, weak, disappointing, or afraid. We tell ourselves that we are protecting the relationship, avoiding unnecessary conflict, or waiting for a better time. Sometimes we even call the lie kindness because the truth feels too uncomfortable to speak.

But a lie cannot create real closeness. It can only create the appearance of it.

You may sit across from someone you love while knowing they are responding to a version of events that never happened. They may comfort you, trust you, defend you, or make decisions based on what you said. That can make the guilt deeper because their kindness is landing on a story you built.

Jesus does not meet that hidden place with surprise. He already knows why you were afraid. He knows what you said, what you left out, and what you are now trying to hold together. Yet His knowledge is not cold. Jesus sees the truth completely, and He still moves toward people.

Peter discovered this after denying that he knew Jesus. He had promised loyalty, but pressure uncovered fear he did not know how to control. When the rooster crowed, Peter could no longer pretend his courage was stronger than it was. He went away and wept because the lie had shown him something painful about himself.

There are moments when our dishonesty does the same thing. A father hears himself blaming his child for a broken item he damaged. A woman tells a friend she is not hurt, then spends the evening angry because she did not say what was true. A man tells his family that money is fine while quietly moving bills from one drawer to another. The lie exposes more than a mistake. It exposes the fear beneath it.

That exposure can feel terrible, but it can also become the beginning of honesty. Peter was not restored by pretending the denial never happened. Jesus returned to him, spoke directly to the place of failure, and gave him room to answer from a humbler heart.

You may be tempted to punish yourself instead of telling the truth. Shame can feel spiritual because it keeps you focused on how bad you feel. But shame often leaves the lie untouched. You can hate yourself for what happened and still refuse to correct it.

Jesus offers something harder and kinder. He asks you to stop hiding.

Start with the sentence you have avoided saying to God. Do not polish it. Do not explain it into something smaller. Tell Him what you said, why you think you said it, and what you are afraid will happen if the truth becomes known. He already knows every part of it, but honesty changes your position. You are no longer defending the lie. You are bringing it into the presence of the One who can help you leave it behind.

The room may still be quiet. The conversation with the other person may still be ahead of you. But the moment you stop lying to God, you are no longer completely alone with what happened.

Chapter 2: The Honest Life Begins Quietly

The next afternoon, you are standing at the kitchen sink while water runs over a plate you have already washed. The person you misled is in the next room. Ordinary life is continuing as though nothing is wrong. You know you could let the moment pass. You also know the silence is becoming another form of the lie.

Telling the truth often begins in an unimpressive moment like this. There is no perfect speech, sudden confidence, or guarantee that the other person will respond gently. There is only a choice between protecting the story and protecting what is still real between you.

You may need to turn off the water, dry your hands, and say, “I need to correct something I told you.” That sentence will not erase what happened, but it will stop the lie from growing. It will place the relationship back on solid ground, even if that ground feels rough at first.

We delay honesty because we want to control the outcome. We want forgiveness before confession and restored trust before proving that we can be trusted again. Truth does not give us control. It gives us integrity.

Jesus did not allow Peter to move past his denial without facing it. He asked Peter whether he loved Him, then called him back into faithful responsibility. Peter had to live differently after that conversation. His future courage became evidence that grace had changed him.

That is how healing works for us too. The honest conversation matters, but what follows matters just as much. A promise to change becomes believable when your choices begin matching it. You tell the truth before being questioned. You admit what you do not know. You stop adding details to make yourself look better. You keep a commitment even when no one is checking.

A woman may confess that she has been hiding unopened bills in a desk drawer. The conversation may include tears, frustration, and hard questions. The next act of honesty may be sitting together, opening every envelope, and writing down the real numbers. Grace does not remove the debt, but it removes the secrecy that made the debt even more frightening.

There is peace in no longer needing to remember which version of the story you told. Your mind becomes quieter. You can look people in the eye. You stop reading suspicion into every question. The truth may bring consequences, but it also begins returning the parts of you that deception scattered.

You may wonder whether Jesus can trust you after what you have done. Peter’s life answers that question. Jesus knew exactly how Peter had failed, yet He still called him forward. Peter was not trusted because he had never been weak. He was trusted because he had been humbled, restored, and made willing to follow.

Your failure does not make dishonesty acceptable, but it does not place you beyond transformation. Jesus can use the place where you were exposed to teach you compassion, caution, and courage. The person who once lied to protect an image can become someone who values truth more than appearance.

You may need to apologize more than once. Someone may forgive you before they fully trust you, and those are not always the same thing. Let them have the time they need. Do not use faith to pressure them into moving faster. Your responsibility is to remain honest, patient, and consistent.

When the conversation is over, you may not feel immediate relief. Bring that regret to Jesus too. Let it teach you without allowing it to define you. Regret can point backward forever, or it can become wisdom that changes the next decision.

The honest life does not begin when you become fearless. It begins when truth becomes more important than hiding. It begins in a quiet kitchen, beside an open bill, during a difficult phone call, or in a prayer whispered before anyone else wakes up.

Jesus is not waiting for a cleaner version of you. He is waiting for the real one. Bring Him the lie, the fear beneath it, the damage it caused, and the future you do not know how to rebuild. Then take the next truthful step.

You do not have to keep rehearsing the lie in your head. You can begin speaking the truth with your life.

Your friend, Douglas Vandergraph

Explore the complete Douglas Vandergraph Master Index: https://douglasvandergraph.com/douglas-vandergraph-master-index/

Watch Douglas Vandergraph’s faith-based videos on YouTube: https://www.youtube.com/@douglasvandergraph

The promise was irresistible: press a key, accept a suggestion, and watch functional code materialise in seconds. By late 2025, according to the JetBrains State of Developer Ecosystem survey of nearly 25,000 developers, 85 per cent of developers regularly use AI tools for coding and development work. Stack Overflow's 2025 Developer Survey reports that 84 per cent of respondents now use or plan to use AI tools, a notable jump from 76 per cent in 2024. The adoption curve has bent sharply upward, and there appears to be no flattening in sight.

Yet beneath the productivity statistics lies a troubling counter-narrative. When METR, a non-profit research organisation focused on AI capabilities, conducted a randomised controlled trial examining how early-2025 AI tools affect the productivity of experienced open-source developers, they discovered something unexpected. Developers using AI tools took 19 per cent longer to complete tasks than those working without them. Before the study, developers predicted AI would speed them up by 24 per cent. After experiencing the slowdown firsthand, they still believed AI had improved their performance by 20 per cent. The gap between perception and reality was stark and concerning.

This disconnect reveals something fundamental about how AI coding assistance is reshaping the software industry. The tools are genuinely powerful, the adoption is genuinely rapid, and the risks are genuinely systemic. What remains unclear is whether the industry possesses the collective wisdom to establish guardrails before the consequences become irreversible.

The Illusion of Accelerated Competence

The METR study recruited 16 experienced developers from large open-source repositories averaging over 22,000 stars and more than one million lines of code. These were not novices experimenting with AI for the first time; they had an average of five years of experience working on their specific repositories, representing 59 per cent of each repository's lifetime, over which time they made approximately 1,500 commits. Each developer provided real issues that would be valuable to their repository, and these were randomly assigned to either allow or disallow AI use.

Developers accepted less than 44 per cent of AI generations. This relatively low acceptance rate resulted in wasted time, as developers often had to review, test, and modify code only to reject it in the end. Even when suggestions were accepted, developers reported spending considerable time reviewing and editing the code to meet their high standards. The study focused on mature, complex environments where AI was less effective than in simpler settings examined in other research.

What makes this finding particularly significant is the experience level of the participants. These developers possessed exactly the foundational knowledge and contextual understanding that should, in theory, allow them to leverage AI most effectively. Yet they still experienced slowdowns. The implications for less experienced developers are sobering.

METR itself now labels the result historical. The trial ran from February to June 2025 using the tools of that period, primarily Cursor Pro paired with Claude 3.5 and 3.7 Sonnet, and the organisation cautions that its findings do not necessarily reflect current tools or workflows. That caveat deserves to be taken seriously, but it does not dissolve the underlying finding: the gap between what developers believed was happening and what the stopwatch recorded is a fact about human self-assessment under automation, not about any particular model release.

Stack Overflow's 2025 survey captures the ambivalence spreading through the profession. Trust in the accuracy of AI has fallen from 40 per cent in previous years to just 29 per cent in 2025. More developers actively distrust the accuracy of AI tools, with 46 per cent expressing distrust compared to 33 per cent who express trust, and only 3 per cent report highly trusting the output. Experienced developers are the most cautious, with the lowest “highly trust” rate at 2.6 per cent and the highest “highly distrust” rate at 20 per cent.

The biggest single frustration, cited by 66 per cent of developers, is dealing with AI solutions that are almost right but not quite. This often leads to the second-biggest frustration: debugging AI-generated code takes more time than expected, reported by 45 per cent of respondents. An overwhelming 75 per cent said they would still ask another person for help when they do not trust AI's answers.

Compounding Vulnerabilities in Skill Acquisition

The erosion of foundational skills presents a distinctive challenge because it compounds over time. A developer who never learns to debug effectively because AI handled early debugging tasks will struggle when AI-generated code introduces subtle errors that require deep understanding to resolve. Each gap in foundational knowledge creates dependencies on tools that cannot always be trusted.

Sonar's State of Code Developer Survey Report 2026, sampling 1,149 responses, found that junior developers expressed significant concern about the erosion of their personal coding abilities, with 50 per cent of junior developers voicing this worry. Additionally, 56 per cent of junior developers reported concern about a decline in codebase understanding. These are not abstract fears; they reflect lived experience of skills atrophying under AI dependence.

Academic research examining ChatGPT-generated code found that more than 50 per cent of generated code snippets are integrated without modifications. Studies on GitHub Copilot reveal an increase in copied and repeated code. When students use Copilot, they spend 11 per cent less time manually writing code and 12 per cent less time conducting web searches. This might sound like efficiency, but it represents a fundamental shift in how they engage in programming.

Researchers have identified two novel patterns among novice programmers using Copilot. The first, termed “shepherding”, occurs when novice programmers type code that matches Copilot's suggestions but end up not accepting those suggestions. The second, termed “straying”, occurs when they accept incorrect Copilot-generated code, leading to debugging rabbit holes that stray further from correct solutions. In exit interviews, students reported concerns about not understanding how or why Copilot suggestions work.

The pedagogical implications are significant. Simply acquiring answers and code from AI tools can be a barrier to improving learners' critical thinking and problem-solving abilities. Research emphasises that while generative AI can drastically improve the efficiency of software development, it should be viewed as a complementary tool rather than a replacement for traditional programming skills. Without instructor-led constraints, students may gravitate toward the maximum help option, undermining deliberate practice.

The Mentorship Collapse

The erosion of junior developer skills becomes catastrophic when combined with the collapse of traditional mentorship structures. According to the AI Impact Report 2025, 38 per cent of respondents agreed that AI tools have reduced the amount of direct mentoring junior engineers receive from senior engineers. The mechanisms are straightforward: if an AI can answer a junior's question, why bother a senior? If AI generates acceptable code, what is there to review and teach?

LeadDev's AI Impact Report 2025 found that 18 per cent of organisations expect fewer junior hires over the next 12 months, compared with 10 per cent anticipating fewer senior engineer hires. Over the longer term, 54 per cent felt that the adoption of AI coding tools would reduce hiring for junior developers. Marc Benioff announced that Salesforce will hire no new engineers in 2025, stating that the company has increased productivity with AI technology by more than 30 per cent. This statement reverberated through the industry as a potential harbinger of widespread contraction in entry-level opportunities.

Industry forecasts project a mid-level developer shortage emerging from 2027 to 2030 as companies compete for scarce talent, followed by a senior developer crisis from 2030 to 2035 when organisations lack oversight capacity for AI systems. The short-term savings from hiring fewer juniors could backfire dramatically. Without a steady stream of early-career developers, companies may face a shortage of mid-level talent in just a few years.

Instead of seniors guiding juniors, many companies rely on AI tools as a substitute, leaving juniors without the traditional apprenticeship that builds careers. As industry observers have warned, rather than have seniors define work for juniors, companies instead focus seniors on using AI to generate code, creating a gap where juniors would find their first jobs. Remote work has compounded the problem, eliminating countless informal learning opportunities that previous developer generations took for granted: hallway conversations, overheard code review discussions, and the ability to tap someone on the shoulder to ask questions.

The Code Quality Reckoning

GitClear's analysis of 211 million changed lines of code, authored between January 2020 and December 2024, reveals the material consequences of AI-assisted development. The percentage of code associated with refactoring sunk from 25 per cent of changed lines in 2021 to less than 10 per cent in 2024. Lines classified as copy-pasted or cloned rose from 8.3 per cent to 12.3 per cent in the same period. The number of code blocks with five or more duplicated lines increased by eight times during 2024.

For the first time in GitClear's measurement history, 2024 was the year when the number of copy-pasted lines exceeded the number of moved lines. Code churn, the proportion of new code revised within two weeks of its initial commit, grew from 3.1 per cent in 2020 to 5.7 per cent in 2024. This indicates a rise in premature or low-quality commits that require immediate correction.

The reason, according to GitClear, is that code assistants make it easy to insert new blocks of code simply by pressing the tab key. It is less likely that AI will propose reusing a similar function elsewhere in the code, partly because of limited context size. Duplicated code may run correctly, but is often a sign of poor code quality since it adds bloat, suggests lack of clear structure, and increases risk of defects when the same code is updated in one place but not in others.

Google's 2024 DORA report found that while AI adoption increased individual output by 21 per cent more tasks completed and 98 per cent more pull requests merged, organisational delivery metrics remained flat. More alarmingly, AI adoption correlated with a 7.2 per cent reduction in delivery stability. The 2025 DORA report confirms this pattern persists: AI adoption continues to have a negative relationship with software delivery stability. Speed without stability is accelerated chaos.

Security Debt at Machine Speed

The security implications of widespread AI code generation are particularly alarming. The Veracode 2025 GenAI Code Security Report found that 45 per cent of AI-generated code samples fail security tests. When LLMs generate code, they prioritise working code over secure code. Research indicates that when LLMs are given a choice between a secure and an insecure method, they choose the insecure path nearly half the time.

This creates a dangerous divergence: the functional capabilities of AI are accelerating rapidly, while its security capabilities remain stagnant. With AI adoption in software development skyrocketing, some reports indicate 97.5 per cent of companies now use AI in their engineering processes, and organisations are producing far more code, far faster. Since the proportion containing security flaws remains consistently high at around 45 per cent, the absolute volume of new vulnerabilities entering corporate codebases is exploding.

IBM's 2025 Cost of a Data Breach Report reveals that 13 per cent of organisations reported breaches of AI models or applications, with 97 per cent lacking proper AI access controls. Shadow AI breaches cost an average of $670,000 more than traditional incidents and affected one in five organisations in 2025. The global average cost of a breach actually fell 9 per cent to $4.44 million, down from $4.88 million a year earlier, yet the United States average climbed to $10.22 million. The business case for robust security controls is therefore sharpest precisely in the market generating the most AI-assisted code.

The term “vibe coding” emerged in early 2025 to describe the practice of building entire applications using natural language prompts via large language models. In this paradigm, the developer often forgets that the code even exists, shifting focus from syntax and logic to high-level intent. A systematic grey literature review found that the most common quality assurance practice among vibe coders was 36 per cent skipping QA entirely, accepting AI-generated code without validation.

The failure patterns are measurable rather than anecdotal. Veracode's testing found that Java fared worst of the languages examined, failing security tests in 72 per cent of tasks, and that AI tools failed to defend against cross-site scripting in 86 per cent of the relevant code samples. Practitioners have documented cases of insecure systems built through vibe coding, including applications that lacked authentication, authorisation, or contained hardcoded secrets.

The Environmental Footprint of Casual Generation

Beyond the immediate consequences for code quality and security, AI-assisted development carries substantial environmental costs that rarely enter productivity discussions. MIT research explains that data centres consumed an estimated 415 terawatt-hours of electricity in 2024, representing about 1.5 per cent of global electricity consumption. An April 2025 report from the International Energy Agency predicts that the global electricity demand from data centres will more than double by 2030, to around 945 terawatt-hours.

The IEA describes AI as the most important driver of this growth. AI has been responsible for around 5 to 15 per cent of data-centre power use in recent years, but this could increase to 35 to 50 per cent by 2030. The deployment of AI servers across the United States could generate additional annual carbon emissions from 24 to 44 million tonnes CO2-equivalent between 2024 and 2030, depending on the scale of expansion.

The energy consumption of individual AI queries is significant and growing. Research indicates that a single short GPT-4o query consumes 0.42 watt-hours, exceeding the footprint of a Google search by approximately 40 per cent, whilst other estimates place a standard text query on the same model nearer 0.3 watt-hours. Reasoning-heavy models consume dramatically more. Researchers estimate that GPT-5 averages around 18 watt-hours per query, with complex answers reaching 40 watt-hours, roughly sixty times the cost of a routine exchange at the average and more than a hundred times at the upper bound.

ChatGPT had reached approximately 900 million weekly active users by March 2026, and serves more than 2.5 billion queries per day. If an average query uses 0.34 watt-hours, that amounts to 850 megawatt-hours per day, enough to charge thousands of electric vehicles. This adds up to nearly one trillion queries each year. One year's energy consumption is roughly equivalent to powering 29,000 US homes for a year.

While training AI models is energy-intensive, running them through inference consumes even more power, accounting for over 80 per cent of AI's total electricity use. The gain in energy consumption will be driven mostly by AI inference rather than AI training. The Schneider Electric report estimates that all generative AI queries consumed 15 terawatt-hours in 2025 and will use 347 terawatt-hours by 2030.

The carbon footprint of AI systems alone could be between 32.6 and 79.7 million tonnes of CO2 emissions in 2025, equivalent to that of New York City, while the water footprint could reach 312.5 to 764.6 billion litres. Google's carbon emissions rose 48 per cent over the past five years and Microsoft's by 23.4 per cent since 2020, largely due to cloud computing and AI. The IEA estimates that data-centre emissions will reach 1 per cent of global CO2 emissions by 2030 in its central scenario, or 1.4 per cent in a faster-growth scenario, making this one of the few sectors where emissions are set to grow alongside road transport and aviation.

Concentration of Quality Assurance Responsibility

As AI generates ever more code, the burden of quality assurance concentrates among fewer expert reviewers. Qodo's 2026 analysis of enterprise code review tools observes that AI-assisted development now accounts for nearly 40 per cent of all committed code, and global pull request activity has surged. Leaders frequently report that review capacity, not developer output, is the limiting factor in delivery. When code can be generated faster than it can be reviewed, the natural safeguard of careful human inspection begins to fail.

The most successful engineering organisations in 2025, according to Qodo's analysis, shifted routine review load off senior engineers by automatically approving small, low-risk, well-scoped changes, whilst routing schema updates, cross-service changes, authentication logic, and contract modifications to humans. But this tiered approach requires sophisticated tooling and organisational discipline that many companies have not yet developed.

The concentration of review responsibility creates its own risks. When a small number of experts must validate ever-increasing volumes of AI-generated code, review quality inevitably suffers. Fatigue sets in, shortcuts become tempting, and the very safeguards designed to catch AI errors begin to erode. The cycle compounds: more AI code, fewer reviewers, less thorough review, more problems reaching production.

Qodo's research found that 82 per cent of developers use AI coding assistants either daily or weekly, suggesting AI has moved beyond experimentation and into the core development workflow. Among teams using AI for code review, quality improvements jump to 81 per cent. This shows that quality gains are tightly linked to how AI is implemented, not just how often it is used. Yet only a fraction of organisations have implemented the governance structures necessary to realise these gains safely.

Educational Interventions and Scaffolded Workflows

The research on educational interventions offers some grounds for optimism, though the path forward requires deliberate effort rather than passive adoption. Researchers have developed tools like CodeFlow Assistant, a generative AI tool that provides four levels of scaffolding guidance, from flowcharts to cloze coding to basic coding solutions to advanced coding solutions, supporting novice programmers in mastering skills ranging from foundational understanding to advanced application.

Scaffolding as a pedagogical approach involves providing temporary support to learners as they develop new skills. Instructors might offer sample prompts and clear examples of how to interact with AI. As students become more familiar with the AI tool, these supports can be gradually reduced, encouraging students to take more control of the learning process.

To ensure deliberate practice on comprehensive and accurate hypothesis construction, students can engage in tasks like making test suites more complete and correctly mapping explanations to bugs. LLMs can take over tasks indirectly related to core learning goals, including generating diverse bugs and fixes, freeing students from code writing, while also supporting scaffolding, generating hints, and providing immediate feedback throughout the practice.

Research emphasises that AI-generated code should be a starting point rather than a final product, and students must learn to review, test, and improve on AI output. Instructors should design assessments that evaluate students' problem-solving processes rather than just code outcomes. Students can be required to explain how AI contributed to their work or identify potential errors in AI-generated suggestions. Such strategies can foster deeper learning and critical thinking.

The adoption statistics in education are striking. Reported usage of AI among students increased sharply over recent years: in 2023, only 36.8 per cent of students reported active use, rising to 63.9 per cent by 2024, and by 2025, 91.7 per cent of respondents reported active use. The tools are already embedded in educational practice; the question is whether that embedding will develop foundational skills or undermine them.

Industry Guardrails and Governance Frameworks

The three fundamental guardrails when adopting AI-assisted coding tools are code quality, code familiarity, and code and test coverage. The good news is that the core of these guardrails can be automated. One of the simplest and most effective ways to reduce security risk from AI-generated code is to start with pull request checks. PR checks integrate directly into existing development workflows, scanning new code for vulnerabilities before it is merged into the main branch. They are easy to configure, centrally managed, and provide immediate feedback.

Organisations should focus on educating teams about the specific strengths and limitations of AI coding assistants. Engineering managers and software developers inherently know that creating software is a highly iterative process, continually improving, optimising and securing code before it moves to production. Most developers prefer working with their own code over reading, understanding and fixing the code of others, including AI-generated code.

One effective tactic is to make access to AI coding assistants contingent on the local security setup. Organisations can ask developers to submit a screenshot showing a security plugin installed and configured before granting a licence to tools like GitHub Copilot. It is a lightweight ask that sets a clear expectation: if you are using powerful code-generation tools, you are also responsible for validating that output locally.

Mandates and strict policies may succeed in the short term, but often meet resistance and reduce long-term engagement. The better approach is incentivising adoption, not enforcing it. This requires cultural change alongside technical controls.

Australia's Department of Industry, Science and Resources published guidance in October 2025 outlining six essential practices for safe and responsible AI governance. Adopting these guardrails will create a foundation for safe and responsible AI use and make it easier for organisations to comply with potential future regulatory requirements. Singapore's Infocomm Media Development Authority published the world's first formal framework for agentic AI systems on 22 January 2026 at the World Economic Forum in Davos, mandating limits on autonomy, human approvals and lifecycle monitoring to counter risks like unauthorised actions or automation bias.

The European Union became the first major jurisdiction to adopt a comprehensive framework for regulating AI with the EU Artificial Intelligence Act, which came into force in August 2024, divides AI systems into risk-based categories, and rolls out rules in phases to give organisations time to prepare. Those phases have since slipped. Negotiators reached provisional agreement on the Digital Omnibus on AI on 7 May 2026, the European Parliament formally endorsed it on 16 June 2026, and the Council gave its final green light on 29 June 2026. The package defers high-risk obligations for stand-alone systems under Annex III from 2 August 2026 to 2 December 2027, and for AI embedded in regulated products under Annex I to 2 August 2028, whilst adding a new prohibition to Article 5 covering AI-generated non-consensual intimate imagery and child sexual abuse material. AuditBoard's survey shows that only 25 per cent of companies have a fully implemented governance programme, highlighting how policy maturity still lags adoption. The direction of travel is instructive. The obligations tightened concern content that is viscerally harmful and politically legible, whilst those governing how high-risk systems are actually built, tested and documented are the ones postponed by sixteen months or more. Governance is not merely lagging adoption in the enterprise; the regulatory timetable itself has now been instructed to wait.

Preserving Critical Thinking While Leveraging Speed

The central challenge is not whether to use AI assistance but how to use it in ways that preserve the cognitive skills that make developers valuable. Finding a balance between tool usage and coding independently is crucial; failing to do so may result in eroded skills. A balanced approach is essential, where AI tools are used to complement rather than replace traditional coding practices and teaching methods.

Some developers who relied heavily on AI tools found themselves struggling with tasks that previously came naturally when working without those tools. One developer reported feeling “so stupid because things that used to be instinct became manual, sometimes even cumbersome.” Just as athletes still perform basic drills, the only way to maintain an instinct for coding is to regularly practise the grunt work.

The fix for the mentorship gap is pairing AI assistance with human mentorship. Juniors use AI to draft solutions, then review with a senior who explains what is good and what needs changing. The AI speeds up the work, the senior ensures learning happens. Organisations should make mentorship explicit rather than assuming it will happen naturally. Creating structures for regular pairing sessions, code review discussions, and architectural conversations is essential. Sharing reasoning, not just conclusions, gives junior developers exposure to thinking processes, not just outputs.

Cognitive resilience and ethics awareness will give people a creative edge through the use of critical thinking capabilities and moral reasoning when collaborating with AI. In the next decade, workforce success will be defined by the ability to integrate across disciplines and work with AI systems rather than a single skill. Emphasising continuous learning and appropriate guardrails will remain essential to ensure that the human element in software development shines through.

Preventing Irreversible Consequences

The question facing the industry is whether current trends can be reversed or whether certain consequences have already become locked in. Reliance on AI is growing among younger and heavier users. Roughly one in three Gen Z workers say they could not do their job or that it would be significantly harder without AI. Among power users, more than one in three report similar levels of dependence. When skills have atrophied and alternative approaches have been forgotten, recovery becomes exponentially more difficult.

AI literacy is fast becoming a basic requirement in most jobs. Yet, nearly half of employees using AI tools at work received no training, and over one-third had only minimal guidance from their employers. Fewer than one in ten small or medium-sized enterprises offer formal AI training programmes. Adoption is happening informally and often without oversight, leaving workers and organisations exposed.

More formal governance structures remain less widespread. About three in ten workplaces report having governance policies that address approvals, disclosures or quality monitoring. The gap highlights how policy maturity still lags adoption, even as AI becomes more embedded in everyday work.

The environmental costs add urgency to the need for responsible adoption. Smart siting, faster grid decarbonisation, and operational efficiency could cut data centre impacts by approximately 73 per cent for carbon dioxide and 86 per cent for water compared with worst-case scenarios. Locating facilities in regions with lower water-stress and improving cooling efficiency could slash water demands by about 52 per cent. However, the AI server industry is unlikely to meet its net-zero aspirations by 2030 without substantial reliance on highly uncertain carbon offset and water restoration mechanisms.

Cascade failures could occur where technical debt in one system triggers failures across interconnected government and military networks. Cyber insurance companies are beginning to adjust their policies, requiring disclosure of AI tool usage, implementing higher premiums for companies with high percentages of AI-generated code, mandating security audits specifically focused on AI-generated vulnerabilities, and excluding coverage for certain types of AI-related security incidents. These market mechanisms may prove more effective than regulation in forcing behavioural change.

Building Sustainable Practices

Successful companies implement frameworks including mandatory code reviews, architectural planning before coding, comprehensive testing of AI-generated code, security validation, and ensuring human teams understand their systems. The key is using AI to enhance rather than replace human expertise.

Mandatory human-in-the-loop review is a key principle in AI governance and a primary detective control in the AI development lifecycle. Certified senior developers bring the architecture mindset that AI lacks. They validate outputs rigorously, catch shallow fixes before they pile up, and turn AI into a disciplined extension of the team rather than a loose cannon. Without them, velocity is just borrowed time.

Forrester predicts that by 2025, more than 50 per cent of technology decision-makers will face moderate to severe technical debt, with that number expected to hit 75 per cent by 2026. Small changes break unrelated systems. Reviews get waved through. Refactors stop happening. The real technical debt reveals itself not as bad code, but as unowned code no one fully understands and everyone is afraid to change.

The 2025 DORA report introduced rework rate as a fifth core metric precisely because AI shifts where development time gets spent. Teams produce initial code faster but spend more time reviewing, validating, and correcting it. Monitoring cycle time, code review patterns, and rework rates reveals the true productivity picture that perception surveys miss.

AI can become a complement to expertise, but it cannot be a replacement for it. As the technology evolves, so too must our capacity to understand it, question it and guide it toward public good. The recommendation is to pair innovation with ethics, speed with reflection and excitement with education. Guardrails and skills development, including basic AI literacy, are not opposing forces; they are the two hands that will support progress.

The tools are powerful. The adoption is accelerating. The risks are real but not yet irreversible. The industry's response over the next few years will determine whether AI coding assistance becomes a sustainable enhancement of human capability or a compounding liability that erodes the very skills it was meant to augment. The choice remains, for now, in human hands.

---

References and Sources

• JetBrains (2025). “The State of Developer Ecosystem 2025: Coding in the Age of AI.” https://blog.jetbrains.com/research/2025/10/state-of-developer-ecosystem-2025/
• Stack Overflow (2025). “2025 Stack Overflow Developer Survey: AI Section.” https://survey.stackoverflow.co/2025/ai
• METR (2025). “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity.” https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/
• GitClear (2025). “AI Copilot Code Quality: 2025 Data Suggests 4x Growth in Code Clones.” https://www.gitclear.com/ai_assistant_code_quality_2025_research
• Google DORA (2024). “DORA Report 2024.” https://dora.dev/research/2024/dora-report/
• Google DORA (2025). “State of AI-assisted Software Development 2025.” https://dora.dev/research/2025/dora-report/
• SonarSource (2025). “State of Code Developer Survey Report 2026.” https://www.sonarsource.com/state-of-code-developer-survey-report.pdf
• MIT News (2025). “Explained: Generative AI's Environmental Impact.” https://news.mit.edu/2025/explained-generative-ai-environmental-impact-0117
• MIT Technology Review (2025). “We Did the Math on AI's Energy Footprint.” https://www.technologyreview.com/2025/05/20/1116327/ai-energy-usage-climate-footprint-big-tech/
• Nature Sustainability (2025). “Environmental Impact and Net-Zero Pathways for Sustainable Artificial Intelligence Servers in the USA.” https://www.nature.com/articles/s41893-025-01681-y
• Carbon Brief (2025). “AI: Five Charts That Put Data-Centre Energy Use and Emissions Into Context.” https://www.carbonbrief.org/ai-five-charts-that-put-data-centre-energy-use-and-emissions-into-context/
• IBM (2025). “2025 Cost of a Data Breach Report.” https://www.ibm.com/reports/data-breach
• Veracode (2025). “2025 GenAI Code Security Report.” https://www.veracode.com/resources/analyst-reports/2025-genai-code-security-report/
• Qodo (2026). “AI Code Review Tools Compared: Context, Automation, and Enterprise Scale.” https://www.qodo.ai/blog/best-ai-code-review-tools-2026/
• LeadDev (2025). “Do Junior Devs Still Have a Path to Senior Roles in an AI Age?” https://leaddev.com/hiring/junior-devs-still-have-path-senior-roles
• CodeScene (2025). “AI Code Guardrails: Validate and Quality-Gate GenAI Code.” https://codescene.com/resources/use-cases/prevent-ai-generated-technical-debt
• Snyk (2025). “Build Fast, Stay Secure: Guardrails for AI Coding Assistants.” https://snyk.io/blog/build-fast-stay-secure-guardrails-for-ai-coding-assistants/
• Epoch AI (2025). “How Much Energy Does ChatGPT Use?” https://epoch.ai/gradient-updates/how-much-energy-does-chatgpt-use
• ACM ICER (2025). “The Effects of GitHub Copilot on Computing Students' Programming Effectiveness, Efficiency, and Processes in Brownfield Programming Tasks.” https://dl.acm.org/doi/10.1145/3702652.3744219
• Australia Department of Industry, Science and Resources (2025). “Guidance for AI Adoption.” https://www.industry.gov.au/publications/voluntary-ai-safety-standard
• IMDA Singapore (2026). “New Model AI Governance Framework for Agentic AI.” https://www.imda.gov.sg/resources/press-releases-factsheets-and-speeches/press-releases/2026/new-model-ai-governance-framework-for-agentic-ai
• Council of the European Union (2026). “Artificial Intelligence: Council Gives Final Green Light to Simplify and Streamline Rules.” https://www.consilium.europa.eu/en/press/press-releases/2026/06/29/artificial-intelligence-council-gives-final-green-light-to-simplify-and-streamline-rules/
• Lawfare (2025). “When the Vibes Are Off: The Security Risks of AI-Generated Code.” https://www.lawfaremedia.org/article/when-the-vibe-are-off--the-security-risks-of-ai-generated-code
• World Economic Forum (2025). “Educating a Future Workforce That Will Match AI Disruption.” https://www.weforum.org/stories/2025/10/education-disruptive-ai-workforce-opportunities/
• IT Pro (2025). “Marc Benioff Says Salesforce Might Not Hire Any Software Engineers in 2025.” https://www.itpro.com/software/development/maybe-we-arent-going-to-hire-anybody-this-year-marc-benioff-says-salesforce-might-not-hire-any-software-engineers-in-2025-as-the-firm-reaps-the-benefits-of-ai-agents

---

Tim Green UK-based Systems Theorist & Independent Technology Writer

Tim explores the intersections of artificial intelligence, decentralised cognition, and posthuman ethics. His work, published at smarterarticles.co.uk, challenges dominant narratives of technological progress while proposing interdisciplinary frameworks for collective intelligence and digital stewardship.

His writing has been featured on Ground News and shared by independent researchers across both academic and technological communities.

ORCID: 0009-0002-0156-9795 Email: tim@smarterarticles.co.uk

Listen to the free weekly SmarterArticles Podcast

“To live in hearts we leave behind is not to die.”
 — Thomas Campbell

You may recall my forlorn farewell to an old friend from a few days ago. DE lived in Dust Meridian for nearly 20 years. Before that, it was two decades in the South Pacific and another ten in Southern California. He’s a mature man in his mid-sixties, so it came as a surprise when he pulled up stakes, sold both of his homes, and headed to the other side of the country.

He says it’s for his wife’s health. The allergies here in Dust are brutal for many. On top of that, years ago, she suffered a stroke that left her speaking with what sounds like an Icelandic accent. Her heritage and native tongue are Peruvian. She went from sounding like a southern girl to something ethereal and ancient—almost elvish. Like someone installed an Old Norse filter on her voice.

I thought she was faking it at first, but it’s a real thing. Foreign Accent Syndrome. Rare, but real. The result of a traumatic brain injury that causes someone to suddenly start speaking with an accent from a region they’ve never even visited.

In her case, it even shows up in her writing. She spells things phonetically now, based on how she hears herself speak. It’s charming, honestly. But also a constant reminder of how fragile the brain is. That same stroke could’ve left her unable to communicate at all. That would’ve been a terror.

My own sister suffered a hypoxic brain injury—lost her short-term memory, and now struggles even with simple tasks. She’s aware of her limitations, which might be the cruelest part. It occasionally lends itself to moments of levity, but mostly, it’s just tragic.

As for DE, I don’t doubt his reasons—physical or mental. His wife or his own. From experience, I believe the lifestyle and mentality here in Dust Meridian takes a tole on anyone with sufficiently curious or robust intellect.

That sounds harsh. Like dummies thrive here. Apologies—I calls ’em like I sees ’em. There are many fine minds here, many dear souls. But there are also plenty of fantastically difficult situations. My own family not excluded.

So no, I don’t blame DE for the move. It’s exciting. I’m a little jealous, if I’m honest. Not that I’d pack up three trucks and drive 1,500 miles to West Potato—but the idea of a fresh start, a new landscape, is tempting. Then again, he’s lived in three other vastly different places. Why not make it four? He’s tapped all four compass points while he still can.

---

My brother-in-law, RLW, volunteered to be part of the cross-country convoy, hauling DE’s belongings to his new home. That’s significant because RLW is the same man who buried his wife—my wife’s sister—just sixty-nine days ago. A partner of 45 years, gone in an instant. Snuffed out like a candle in the rain.

When talk of the trip started, RLW had big plans. He’d trailer his motorcycle behind one of DE’s work trucks, help with the move, then spend a few days exploring West Potato. From there, he’d kit out the bike and ride west—through the Northwest, down to the Pacific. He talked of revisiting places he and his wife had seen, and discovering new ones. He didn’t say it aloud, but I suspect he meant to scatter some ashes along the way.

But as time wore on, the plans shrank. Late spring snow made the northern routes dicey. Then he nixed the coast. West Potato lies just beyond the Continental Divide, and soon enough, he cut out any idea of leaving the mountains at all. By the time he left two days ago, the month-long journey had been trimmed to a week.

A few hours ago, he texted that he’ll be back in Dust Meridian tomorrow night. Yep. Thirty days of freedom and healing, whittled down to just four.

There and back. Turn and burn.

---

His son, SLBY—the boy (a man in his thirties, forgive an aging Wolf)—tells me he thinks his dad just misses home. The quiet of the road was heavier than expected. That makes sense. My nephew wants his dad to get out and see new places, to build memories without her. A critical step in healing.

When I speak to RLW, he says it’s his son and grandson who are nudging him to come back. He can 'hear it in his voice' that if he was back, they would all be happier. Home is big and lonely and his son misses his family. Doesn't like being without his core. His people. His comfort zone.

Essentially, they are both arguing the other wants to be together again. They tell me what the other wants. But really, they're telling me what they themselves long for.

SLBY the boy has told me more than once this last few weeks that he can’t stand being alone. He’d grown used to the bustle—his wife, his son, his parents, all under one roof. They live in a mobile home, so sharing space really means sharing.

Constantly.

With his mom gone, dad out of town, wife at the chiropractor, and the boy at school, SLBY finds himself alone on a rock hurtling through space at sixty-seven thousand miles per hour. Working from home means his only company is the blinking cursor on a plastic display.

He’s admitted, with surprising emotional honesty, that he cries often. This from a man who, just a few years ago, was all whiskey, beer, and bravado. Guns and guts. Today, the bottles are dusty and the guns live in a safe—a large one, granted—but they’re just objects now.

SLBY has become the kind of man who can acknowledge his pain and grow through it. A shock, honestly. But a welcome one.

His father, RLW, has also cracked open in ways I didn’t expect. Always the quiet, stoic one—he now speaks freely about how much his wife meant to him. That she was his light. His purpose.

And being retired is salt on the wound. 10 years ago, he would at least have a job he had to contend with, coworkers and daily business to get back to. But now? His only obligations are those which he chooses. A full plate with his spiritual family, but that can be shelved much longer than it should be. Leaving him in self-inflicted isolation.

Since her passing, he sleeps maybe four hours a night. He cries often. I imagine these moments are private—the kind where your ears roar, your eyes burn, and you fight to contain the flood so others don’t have to feel it too.

Every time we’ve spoken since he hit the road, he’s mentioned that he can’t stop crying. Triggers are everywhere. A song. A vista in silence where she would have commented or asked to pull off and take a picture. The absence of agitation at his driving (the way he jerks the wheel in little increments). No one stuffing the door panel with trash.

But mostly—silence.

An imagination haunted by 16,425 sunrises and sunsets together... and all that is in between—the subtle golden rhythms of a life shared. Every small moment now echoing in absence.

My God, how do you move on from that?

Patience.

Patience and tears. And prayer that God will intervene and part that ocean like he did for Moses.

I told him as much. “It’s good you’re blind with tears. You probably need to really cut loose—and that’s hard to do with a seven-year-old always around, or your son who’s dealing with his own grief. I hope this trip gives you some catharsis. That it helps you begin to heal in earnest.”

Grief is the price we pay for love. The greater the love, the higher the cost.

Three thousand miles in four days. And tears, door to door.

---

---

Luke 22:1-6 Now the Festival of the Unleavened Bread, which is called Passover, was getting near. And the chief priests and the scribes were looking for an effective way to get rid of him, because they were afraid of the people. Then Satan entered into Judas, the one called Is·carʹi·ot, who was numbered among the Twelve, and he went off and talked with the chief priests and temple captains about how to betray him to them. They were delighted at this and agreed to give him silver money. So he consented and began looking for a good opportunity to betray him to them without a crowd around.

Mark 14:1,2 Now the Passover and the Festival of Unleavened Bread was two days later. And the chief priests and the scribes were looking for a way to seize him by cunning and kill him; for they were saying: “Not at the festival; perhaps there might be an uproar of the people.”

Mark 14:10,11 And Judas Is·carʹi·ot, one of the Twelve, went off to the chief priests in order to betray him to them. When they heard it, they were delighted and promised to give him silver money. So he began seeking an opportunity to betray him.

---

#essay #travel #memoir #loss #death #biblereading #100DaysToOffload #Writing

---

2025-04-11 09:35:00

'Dad's heart stopped after I said amen to a prayer'

---

At 11:44am Sunday November 9, 2025, the Conductor took his last breath. My friend, a minister of the Bible, watched his father pass away even as he said a benediction for him. It is heartbreaking and beautiful.

It was a 3 month long journey that resulted in the Conductor laying in a hospital bed for more than 30 days all told over the course of the illness.

I read recently that none of us truly become men until our fathers die. Dubious logic, but absolutely beautiful poetry. And in the generations of today, losing our fathers may be the thing that is needed to trigger the metamorphosis of maturity.

It is a hard passage if it's true. I think I'd prefer to be Peter Pan if it is.

The Conductor and his family have been in and around my life since childhood. His widow, the Queen of Swords, is among my closest friends. He was a vaguer component for decades but in the last 10 years has emerged as a clear cheerleader for this wolf, often telling me how much he appreciated everything I've done for and with his family.

He was a weird guy. One of our friends describes meeting him 30 years ago in a suit with no socks or shoes. Probably about the best and most succinct way of understanding this complex creature.

He was gone a lot from his family. Conductors have to conduct (trains as well as symphonies) and his route kept him on the road for days at a time. It provided a good living for his family, but the absence took it's toll emotionally.

I don't' think it was the job so much as it was the baggage of his life, but he struggled with addiction for decades before finally kicking the heavy stuff. Though he was hooked on tobacco until things got serious for him about 3 months ago.

He had a sister who struggled emotionally too. She passed away a few years ago from heart failure. The same thing that killed her brother. His sons are now rightly worried about their own life-pumps.

As I have watched him over my life, I have seen the Conductor through the eyes of his sons and wife, all close friends. They always hoped better for him and honored him as best they could in their own flawed ways. But he could never measure up to the standard the Bible holds out to those who hope for the approval of Jesus and His father.

And so I did, as righteous men often do, judge him. Inferior, broken, needing to change. But, in all the years I knew him, he remained absolutely confident that he would have a place in God's kingdom. As a man myself who feels unworthy of that role, I always found it eyebrow raising.

He would need to change this and that in order to yadda yadda. It's a life-long mantra of the Bible-thumper. In recent years, I've started to change my understanding and softened a lot. On others as well as myself—well somedays I'm less soft on myself, but trying. And I've started to see that there are good-hearted humans who just cannot meet that standard. Something in them is broken beyond repair and they are doing the best they can.

We all have demons. Some of us are better at cowing them than others.

Some of us have to hide under the bed, or behind a haze of chemical stupor in order to function. It isn't fair to say 'you aren't good enough' if you're doing the best you can. I think the Conductor was. I think I am.

Sometimes all you can do is limp through life.

In the end, he was a kind man, a good man—if flawed. In truth, I've known many 'better' men from a righteousness point of view who didn't have half the kindness or thoughtfulness. Maybe that's why we discuss Jesus we focus not on his righteousness, which no man could match, but rather, his goodness.

He was a guidepost. A point of consistency on the landscape of my existence that's gone now. It will be far worse for his wife and his sons, but the loss of that waypoint will effect us all.

It's terrible and sad. Another loss in a long line that will just continue until the Wolf breathes his last breath. And that's not the scary part; the last breath. The scary part is all the unknown between today and that moment.

Death is only a problem for the living.

Good night, Conductor. I'll keep waiting faithfully for my own line. I'll wait as best I can. Broken, tired and unworthy. Thank you for showing me that it's less about what others think of you and more about being honest with yourself. It's a weight I am still learning to carry.

Just like all of us.

#death #memorial #essay #writing #100daystooffset

---

originally published: 2025-11-10 15:00:00

---

Long poems are easy to write, hard to read.

Short poems are easy to read, hard to write.

Which is better Depends on which you are.

Writer, or Reader.

Lover, or Loved.

---

#poetry #storytelling #write #100daystooffload

---

Orig Pub: 2025-04-27 12:26:52

In Summary: * Listening now to the Nationals vs Phillies MLB game, currently in the 3rd inning. The game should be over by 20:00 CDT or so, at which time I'll finish what night prayers remain unsaid, and send myself to bed, hopefully to find a restful sleep.

Prayers, etc.: * I have a daily prayer regimen I try to follow throughout the day from early morning, as soon as I roll out of bed, until head hits pillow at night.

Health Metrics: * bw= 229,83 lbs. * bp= 127/78 (76)

Exercise: * morning stretches, balance exercises, kegel pelvic floor exercises, half squats, calf raises, wall push-ups, BP breathing exercises, pilates

Diet: * 05:40 – bread and butter * 12:15 – 1 banana * 15:45 – home mmade beef and vegetable soup. * 16:50 – small piece of cheese cake

Activities, Chores, etc.: * 03:20 – listen to local news talk radio * 04:10 – bank accounts activity monitored. * 04:55 – read, write, pray, follow news reports from various sources, surf the socials, nap * 12:10 – service guy just arrived to check my a/c unit. Sure hope he can fix it quick; it's hot in here! * 15:15 to 15:45 – watch old game shows and eat a quick lunch at home with the wife. * 16:10 – listening to general sports talk on WJFK The Fan 106.7 FM ahead of tonight's MLB game between the Nationals and the Phillies

Chess: * 10:30 – moved in all pending CC games

Well. Shit. Valdez is not happening. That's all the bandwidth I have at the moment.

When I woke this morning ~03:00 the temperature in this house was 80 degrees and rising. The a/c unit was blowing air through the vents, but it wasn't cold air.

Called the landlord at 09:00, he called an a/c company and a tech guy was here shortly after Noon. The very old compressor in the central unit is dead and is so very old it's unlikely a replacement unit can be found.

There are several old window units in some of the rooms here, and we got two of them working: one in the wife's room, and one in a spare room we use for storage. That storage room may become my room temporarily.

Sitting here in my room now, with the ceiling running as fast as it can, my desk thermometer shows 92.8 degrees F. I may be dealing with this situation for awhile.

Our Father Who art in Heaven Hallowed be Thy name Thy Kingdom come Thy will be done on Earth as it is in Heaven Give us this day our daily Bread And forgive us our trespasses As we forgive those who trespass against us And lead us not into temptation But deliver us from evil

Amen

Jesus is Lord! Come Lord Jesus! Come Lord Jesus! Christ is Lord!

The apiary be Scottish run to mute Late December this hugger And seeing simply rise What time in Hearst for Will Enough of oak And seeming simpler For five octet and lane And pasture by the law Economy forever- and nines to the Moon Giving ray to God And night shall let us be- the end of war.

Boss Under The Radar (A Time Appeal)

And so it rained The sympathy of curious men First in flash Lights under for the camera of Win’ This is what year again For the peaceful day Russians knew and capitulated We were all with God under the Sun And in Victory Day And seeing this warmth A golden kite- flew in his memory And apocalypse then- hit our pay

For peace to begin at near Rights to be able And sending this day A successful and special computer Life is art And capitulation And Ukraine will last- a Lifetime.

🇺🇦 💛💜🩷

Personal log: Experimental

I LOVE pebble ice! I've been experimenting. So far, my favorite way to crunch and munch on them is with a sprinkle of electrolytes. Not just any electrolytes. Oh, no, no, no, no. Hibiscus electrolytes with a tiny dash of ground freeze-dried rosehips. The latter isn't necessary. It's just additional happy yum.

The air pockets in the ice end up wicking the liquified powder up into the ice via capillary action, so every morsel of crunch is an explosion of flavor! There's so much crunch! So much cold! I'm getting quite the dopamine hit, and my oral fixation tendency is pretty happy right now.

On the plus side, having zirconia teeth means I can crunch my happy little heart out.

On the negative side, canines go ouch when I bite wrong. Also, I should probably slow down on the crunching because my tongue is numb enough that I sound ridiculous trying to speak.

I am in a very happy place, sensory-wise. It only takes a tiny sprinkle because the cold amplifies the tart sweetness. My trigeminal nerve is all brrrrrrr. Which is admittedly a wee bit euphoric. And I am shivering with delight though it is currently 101°F outside.

I have always been a sucker for this type of tea. Preferably iced. Having it sucked into the ice with the addition of electrolytes... holy moly! I can only think of one thing that would make this better right now. Alas, it's not something that is going to happen. One day, I shall ensure that it will. I'm not sure I'd be capable of handling such bliss, but I'm definitely up for the challenge!

Okay. Enough of that. I do recommend an insulated tumbler so that the glass doesn't sweat. My preference is my 12 ounce Simply Modern Voyager Series Lunar Iced Coffee cup. I don't know if they're still available. Black stainless steel with embossed crescent moons and stars. I normally rarely use it because I don't like coffee and it's rarely cool enough for hot cacao. I shall now use it every single day!

This...This is euphoria!

I should probably research if there's a safety limit on ice crunching. It is sooooo good. It's like sour punch straws whisked into frozen, liquidy, hydrating, goosebumps producing ambrosia. I'm so happy.😹

My intoxicated mouth and I now return you to my normally darker scribbles. Maybe. Or maybe not. It could be, dear journal, that my writing is heading down a much more zany lane until I get accustomed to this sensory high. I think all living quarters should come with this delicious concoction. Wars would surely end.

Did I mention it turns the ice a gorgeous pomegranate color? No? It does. My senses don't know what's beguiled them, but they are a most willing and amorous supplicant.

Written August 6, 2026. © 2026 AnOublietteofThought.

El Instituto Latinoamericano de Terraformación fue invitado a participar en una audiencia pública en la Comisión de Ciencia, Tecnología, Innovación e Informática del Senado Federal de Brasil para discutir el Proyecto de Ley n.º 3018, de 2024, por el que se regula la actividad de los centros de datos de inteligencia artificial.

En la ocasión, partimos repasando un panorama general de los diversos, crecientes y aún desconocidos impactos socioambientales de los centros de datos. Por tanto, mostramos que el principio precautorio -como una regla de protección ambiental y de salud pública- parece ser el indicado como política pública para enfrentar los crecientes y aún desconocidos impactos de estas infraestructuras.

Luego, hicimos un panorama de América Latina que nos permitió afirmar que:

• Los gobiernos del continente tienen una deuda sobre la sostenibilidad de la IA.
• La autoregulación no funciona para la sustentabilidad de los centros de datos.
• El desafío requiere marcos regulatarios específicos con una serie de condiciones.

Asimismo, revisando el caso chileno, transmitimos al Senado que debido a la falta de salvaguardas legales y claras que regulen los impactos socioambientales de estas infraestructuras, los proyectos de centros de datos en Chile muchas veces terminan judicializados, lo que implica un amplio costo de capital y de incertudumbre para las empresas y las comunidades impactadas.

Lo anterior puede ser útil en Brasil para aprender que la falta de marcos legales y políticas públicas adecuadas y participativas ha hecho que se retrasen los planes de desarrollo de centros de datos, y que, consecuentemente, no puede haber desarrollo de estas infraestructuras sin que las comunidades estén involucradas en todo el proceso de evaluación ambiental.

Entre nuestras sugerencias para Proyecto de Ley 3018/2024, están:

1. Planificación socioambiental estratégica y participativa como rol de Estado: Sobre todo para evitar lo que pasa en Estados Unidos, donde los Estados compiten agresivamente por atraer centros de datos de hiperescala y las decisiones se trasladan desde espacios públicos hacia acuerdos privados y decretos ejecutivos. Este modelo privatiza beneficios y control, mientras socializa riesgos económicos y daños ambientales. También debilita la rendición de cuentas democrática y la resiliencia frente a los límites ecológicos (Kollar, J.. 2026).

2. Obligación de someterse a procedimientos de licenciamiento ambiental participativo y especifico en los territorios.

3. Exigencias de métricas y mecanismos de rendición de los impactos socioambientales.

4. Asegurar mecanismos de justicia energética.

5. No perder de vista temas de fondo para la política pública, como son el poco valor social que tiene la IA en poblaciones como la estadounidense, el bajo impacto laboral de los centros de datos, y los riesgos de una burbuja económica y fananciera de la IA, que dejan la pregunta abierta de cómo Brasil debiera legislar para responder a estos peligros y blindar a su economía y población.

Puedes leer nuestra intervención completa en este link.

#Spanish

---

I had a dream today. a nice one, actually, but only for about five minutes. we got married, not somewhere ordinary either. a castle, a pretty one. a place rich people rent because normal buildings isn’t dramatic enough. it was really beautiful ill admit that. stone everywhere, high ceilings, light coming through the window. i remember walking towards her, angel. she looked. i dont know, there arent enough words for that part, or too many words i cant put together. i just remember stopping for a second because she didnt even look real. like someone had accidentally put an angel in the wrong room, she just looked. majestic. she smiled. i reached for her face. i remember crying before i even spoke. which is embarrassing considering i was unconscious and still somehow managed to lose composure. and suddently. out of nowhere, my hands, they werent hands anymore. they started falling apart into maggots. no blood in between, no cuts. just worms, hundreds of them. then my arms, then the rest of me, everything. like my whole body had already died and nobody had bothered telling me. it wasnt strange that i was falling apart. angel was strange. she didnt scream, she didnt panic either, she just looked at me, disgust. ive seen that dream before, worms. In different ways, usually the people i love become the dead ones. they rot, they become the maggots. this time, it was me. and she stayed exactly the same, she didnt even try to help, as if i was nobody, she just looked at me like i had become something filthy. the warmth disappeared from her eyes so quickly i remember that more clearly than the maggots themselves. then i woke up, sweating as always, breathing like I’d forgotten how. same routine as always, i went to work. bad day, nothing special happend, i just couldnt stop thinking about the dream. every quiet moment my head decided to replay it. then replay it again, then ask me twenty questions it already knew i couldnt answer. if this, if that, what if. why, just pointless thoughts. angel texted me today, she was happy. i dont know how to explain it without sounding ridiculous, but she seemed brighter. happy in a way that makes you forget whatever you were about to complain about. i almost told her about the dream. then i thought maybe she deserved to stay happy for one afternoon, one evening. she needed to sleep anyway, so thats fine. ill keep the dream, ill keep the bad day, ill kep the jealousy from something i wish i hadn’t noticed. ill keep my thoughts, thats what i thought i was good at, im clearly not, otherwise i wouldnt be writing about it. but anyway, hopefully tomorrow gives me something less dramatic to complain about.

Or maybe my wrist restraints have started controlling my dreams now. at this point i wouldnt even argue with the diagnosis. they already keep me from scratching myself awake, might as well start directing the nightly entertainment too.

Sincerely, Perhaps i should stop sleeping.

Institutional Capacity and the Clocks of the Republic

Republics do not fail for lack of formal power alone. They also fail when rule-bound institutions cannot convert lawful authority into competent performance—or correct failure before distrust hardens into constitutional disloyalty.

Writing in The Washington Post on July 13, as Iraq’s prime minister prepared to visit Washington, David Petraeus offered a line that reads like a diagnosis of something much larger than Baghdad’s troubles:

“Institutions ultimately derive legitimacy not merely from legal authority, but from performance. Courts must administer justice fairly. Ministries must provide reliable public services.”

Governments, as Petraeus put it, earn confidence through competence—not through the mere fact of having been elected, established by law, or endowed with formal powers. 

For a growing number of liberal republics, that confidence is no longer merely eroding. In some places it has already collapsed.

Viktor Orbán spent sixteen years reshaping Hungary’s courts, media, constitutional structures, and electoral machinery before voters removed Fidesz from power in April 2026. The new government’s difficulty is not simply to replace one political leadership with another, but to recover institutions whose personnel, rules, and informal loyalties were altered over many years. Germany’s Alternative for Germany (AfD) reached a record 28 percent in an April INSA voting-intention poll. In France, Marine Le Pen again leads presidential polling after an appeals court upheld her conviction for misuse of European Parliament funds but shortened her electoral ban enough to allow her to run in 2027. The V-Dem Institute’s 2026 Democracy Report identified the United States, the United Kingdom, and Italy among ten new autocratizing countries and described the speed of democratic deterioration in the United States as unprecedented in its modern data. 

This is not a problem confined to unstable states or the democratic periphery. It has reached countries long treated as anchors of the postwar liberal order.

The standard explanations reach for ideology, polarization, disinformation, corruption, economic insecurity, or cultural conflict. Each explains something important. Nor should democratic decay be reduced to administrative malfunction. Some institutions are not merely weak; they are deliberately captured. Some delays are not accidental; they are useful to people who profit from institutional paralysis. Some political movements do not wish to make constitutional government perform better; they wish to use its failures as grounds for replacing constitutional restraint with personal authority.

Yet grievance and ideology explain the fuel better than the ignition. They do not fully explain why distrust has become so politically potent, or why constitutional governments so often appear unable to correct failures that almost everyone can see.

For that, one has to look at the machinery underneath—at what might provisionally be called institutional capacity.

Institutional capacity is the durable ability of a rule-bound governing system to recognize collective problems, establish lawful priorities, mobilize and coordinate resources, perform public purposes reliably and fairly, absorb credible feedback, defend its rules against strategic abuse, and revise or retire failing arrangements in time.

The last words matter: in time.

An institution that eventually identifies a failure but cannot correct it before the harm becomes entrenched is not fully capable. An institution that produces a commission, an audit, or a lessons-learned report but leaves the underlying practice untouched has collected information without learning. An institution that can create programs, regulations, and offices but cannot terminate any of them has growth without metabolism. And an institution that preserves every existing procedure while losing the ability to accomplish the purpose for which those procedures were created may remain formally intact while becoming practically hollow.

The Framers understood that republican government required both restraint and energy. They did not simply fear concentrated power more than incompetent administration. Madison described energy, stability, liberty, and dependence on the people as principles that had to be combined in difficult proportions. Hamilton called energy in the executive a leading characteristic of good government and warned that feeble execution amounted to bad government in practice. 

They nevertheless designed legislation to be difficult. Bicameralism, presentment, the veto, federalism, staggered elections, divided powers, and judicial review introduced friction because coercive public decisions should not be made as quickly or unilaterally as private ones. Legislative delay can permit scrutiny, amendment, compromise, minority protection, and the cooling of temporary passions. In that sense, slowness was not a design error.

But the constitutional order they established now governs an administrative state of a scale, technical complexity, and social reach they could not have anticipated. Congress delegates broad objectives to permanent agencies, which develop the rules and procedures through which much public policy is actually experienced. Yet the legislature has become increasingly unable to maintain, review, reconcile, or retire the accumulated machinery it has authorized.

Fiscal year 1997 remains the last year in which all regular federal appropriations were enacted by the October 1 deadline. Since then, continuing resolutions, consolidated packages, delayed appropriations, and occasional full-year stopgaps have become normal instruments of government finance. The machine continues to operate, but increasingly on inherited instructions, temporary extensions, and emergency deadlines rather than sustained legislative supervision. 

At the same time, a digital information environment broadcasts every failure immediately and nationally. Institutional performance still unfolds through investigation, budgeting, rulemaking, litigation, implementation, and appeal; public judgment now forms at the speed of a phone notification. The constitutional order and its political environment operate on radically different clocks.

That temporal mismatch is not the sole cause of democratic decay. It is, however, an underexamined condition that makes decay easier to exploit.

It also compounds corruption rather than standing apart from it. Legislators, officials, regulated interests, and beneficiaries who profit from an obsolete program, loophole, subsidy, jurisdiction, or procedural obstacle have little incentive to spend political capital removing it. Inertia is not always the unintended product of a cumbersome design. Sometimes it is a preference, quietly held by precisely those actors best positioned to correct it.

None of this means that the answer is simply to move faster.

The DOGE initiative in Washington offers the cautionary counterexample. It treated rapid personnel reduction as though subtraction were itself evidence of reform. But a serious capacity review would first have asked which missions were failing, which processes were duplicative, which skills were essential, which functions could be automated or consolidated, and what capacities would have to be preserved or rebuilt after reorganization.

By May 2026, the federal civilian workforce had declined by more than 272,000 employees from its January 2025 level. At the Office of Personnel Management, staffing fell by 35 percent between December 2024 and March 2026; ten offices disappeared, and 57 percent of those leaving had more than eleven years of service. The Government Accountability Office described the result as a significant loss of institutional knowledge, while OPM’s inspector general identified immediate operational-capacity gaps. GAO also found that the Defense Department had reduced its civilian workforce by more than 78,000 employees without consistently analyzing the effects on workload, cost, or mission performance and without a plan for assessing lessons learned. 

The point is not that every abolished position was indispensable. It is that head count is an input, not a measure of capacity. Removing people and offices without a demonstrated redesign of how the public mission will be performed is speed without diagnosis. It is not agility but demolition.

Agility does not mean velocity. It means temporal competence: the ability to move at the speed appropriate to the task and to change tempo without sacrificing legality, quality, rights, or accountability.

Different public functions properly operate on different clocks.

A police response to an emergency call should be measured in minutes. Disaster response may require decisions within hours. Benefits and permits should move within declared service periods. Major infrastructure planning may require months of technical and environmental review. Ordinary legislation should remain deliberative because legislative friction protects interests that administrative efficiency alone cannot protect.

Not every delay is incapacity, and not every institutional friction is a defect. Delay becomes failure when it no longer serves deliberation, evidence, legality, or minority protection, but instead prevents correction of demonstrated harm—or permits organized actors to exploit the lag indefinitely.

A capable republic therefore needs more than one institutional clock. It needs a disciplined and narrowly bounded pathway for recurring cases of demonstrated failure: a statutory loophole repeatedly identified by courts, a program discredited by years of evidence, contradictory regulations that prevent implementation, an administrative process producing persistent unlawful disparities, or a formerly informal norm that bad-faith actors have learned to violate with impunity.

Such a pathway should not permit automatic enactment or emergency government by decree. A documented finding by a court, the Government Accountability Office, an inspector general, or a genuinely bipartisan oversight body could instead trigger mandatory expedited consideration. The legislature would retain authority over the response, but it could no longer bury the problem indefinitely.

The safeguards would have to be stringent. The triggering finding should establish a recurring pattern rather than one politically disputed incident. The proposed correction should be publicly explained, prospective rather than punitive, narrowly tailored to the identified failure, and applicable generally rather than to named persons or disfavored groups. Ordinary judicial review should remain available. Temporary measures should expire automatically unless reenacted after evaluation under ordinary procedures.

This is not a proposal to eliminate constitutional friction. It is a proposal to distinguish friction that protects republican government from delay that disables it.

Petraeus’s account of strategic leadership offers a useful organizational analogy. His command operated through a disciplined “battle rhythm”: daily operational assessments, weekly specialized reviews, continuous field observation, and periodic strategic reassessment. Different questions were addressed on different clocks, but the clocks were connected. Information moved from operations into evaluation and from evaluation back into strategy. A lesson was not considered learned merely because it had been documented; it had to produce a change in doctrine, training, organization, or practice. 

Civilian republican institutions cannot be commanded like a military theater. They contain divided authority, lawful opposition, federal relationships, independent courts, competing constituencies, and rights that cannot be suspended for administrative convenience. But the underlying principle remains transferable: evaluation must feed correction, and correction must occur on a clock appropriate to the harm.

Performance itself must also be measured more carefully than DOGE-style personnel totals or political claims of success. A public institution should be assessed against declared standards of effectiveness, reliability, legality, fairness, accessibility, timeliness, resilience, and responsiveness. Agency self-reporting should be tested through independent audit, front-line evidence, professional evaluation, and authenticated citizen experience. Faster processing accompanied by more errors is not improved capacity. Lower cost achieved by excluding eligible citizens is not efficiency. High aggregate performance that conceals regional or demographic failure is not reliable public service.

Institutional capacity also includes the ability to stop.

A capable state must be able to retire obsolete mandates, merge duplicative bodies, reconcile contradictory statutes, simplify accumulated procedures, and remove requirements whose administrative cost has overtaken their public value. New regulation should therefore be accompanied not by a crude one-rule-in, one-rule-out formula, but by a published regulatory-burden assessment and a requirement to identify existing provisions that should be consolidated, amended, or repealed. Major programs and rules should undergo retrospective review on a fixed schedule rather than persist indefinitely because no political coalition can be assembled to revisit them.

The relationship between capacity and legitimacy then runs in a loop:

Authority → capacity → performance → evaluation → correction → confidence → renewed legitimacy

Run backward, it becomes the mechanism now visible across multiple republics:

Authority → weakening capacity → poor performance → distrust → evasion and noncooperation → further capacity loss → delegitimization

When repeated failures remain uncorrected, declining public confidence weakens voluntary compliance and constitutional loyalty, creating a self-reinforcing cycle in which populist and authoritarian movements can present themselves as more effective alternatives to rule-bound republican government.

They are not the only beneficiaries. Technocrats may claim that democratic deliberation is too cumbersome. Oligarchs and patronage networks profit from complexity ordinary citizens cannot navigate. Executive leaders can argue that only personal command can cut through institutional paralysis. Each offers a different escape from incapacity; all diminish the citizen’s role in constitutional self-government.

Political theory has immense literatures on legitimacy, republicanism, constitutional structure, and democratic backsliding. Public administration and organization theory contain powerful but dispersed accounts of Weberian professionalism, bureaucratic autonomy, policy capacity, institutional integration, organizational learning, dynamic capabilities, resilience, and high-reliability systems.

What remains underdeveloped is their integration into a republican theory connecting lawful authority, differentiated institutional time, measurable performance, correction, integrity, organizational renewal, and renewed legitimacy.

Such a theory would have to explain not merely how an agency performs its assigned tasks, but how a constitutional order recognizes that its institutions are failing; how it distinguishes necessary restraint from disabling inertia; how it accelerates correction without inviting arbitrary power; how it learns without becoming captive to transient opinion; how it preserves professional autonomy while enforcing accountability; and how it removes obsolete machinery without destroying capacities that may be difficult or impossible to recover.

This essay is not that theory. It is the claim that the question deserves one.

The unfinished business of republican government in the twenty-first century is not simply to demand that citizens trust institutions that have disappointed them. Nor is it to demolish those institutions in the name of speed. It is to construct the lawful mechanisms through which institutions can perceive failure, correct it in time, and repeatedly demonstrate that constitutional government remains capable of governing.

I am often asked, directly or indirectly, why my essays stop where they do.

Why, after exploring a question from multiple directions, do I resist the final step? Why not advocate more clearly? Why not propose a solution? Why not tell the reader what ought to be done?

The answer is neither uncertainty nor reluctance. It is a matter of sequence. We live in an age that prizes opinions. We are encouraged to take positions rapidly, often before a question has been fully understood. Public debate is increasingly organised around answers.

Yet many of our deepest disagreements are not disagreements about answers at all. They are disagreements about the questions to which those answers are addressed. When two people argue over immigration, education, taxation, climate change, religion, or identity, they often assume they are debating solutions. More frequently, they are operating from different understandings of the problem itself. Their disagreement lies upstream from the conclusion.

In such circumstances, further advocacy rarely helps. It merely adds another answer to a conversation that lacks a shared question.

My own instinct as an essayist has therefore been to proceed differently.

The essay, at least as I practise it, is not a vehicle for resolution. It is a means of attention. It begins with a tension, a puzzle, an ambiguity, or an apparent contradiction. The task is not immediately to dissolve that tension but to inhabit it. To examine it from multiple perspectives. To remain with it long enough for underlying relationships to become visible.

This approach owes much to an early lesson I learned in education. Like many students, I entered discussions believing that achievement consisted in arriving at the correct answer. What I gradually discovered was that the most transformative moments often occurred before the answer. They occurred when an unexpected question revealed that the problem itself was not what I had assumed.

Once the question changes, everything changes.

A solution that appears obvious from one perspective can seem inadequate from another. A conflict that appeared irreconcilable may reveal previously unnoticed common ground. What looked like competing truths may turn out to be partial descriptions of a larger reality.

Understanding begins not with agreement but with perception.

This has important consequences for democracy. Agreement, consensus, and genuine democratic outcomes require more than the aggregation of opinions. They require some degree of shared understanding. Before citizens can move forward together, they must first know what it is they are moving forward from. They must possess, however imperfectly, a common view of the question before them. Without that shared understanding, calls for action become little more than competing assertions. The result is not deliberation but collision.

The essay can play a modest but important role here. Not by deciding matters in advance, but by helping to clarify the terrain on which decisions will eventually be made. Not by instructing readers what to think, but by helping them see more fully what is at stake.

This is why my essays so often stop where they do.

I do not withhold advocacy because I believe conclusions are impossible. Nor do I imagine that every question can remain permanently open. Decisions must ultimately be made. Judgements must eventually be formed. Action is unavoidable.

But action that precedes understanding is often premature.

The task I set myself is therefore a limited one. It is to contribute, where I can, to a richer perception of the question. To bring hidden relationships into view. To make visible some dimension of reality that may previously have gone unnoticed. Only then, I believe, can meaningful disagreement occur. Only then can genuine agreement emerge.

The essay ends where collective judgement begins. It is not the final stage of public reasoning. It is the stage before that. Its purpose is not to tell us where to go, but to help us see where we are.

And perhaps, for now, that is enough.

David Marshall Dublin