The encrypted USB burned in my pocket like a live coal. “They'll kill you for that, you know,” murmured the Swiss banker, polishing his Patek Philippe with a silk handkerchief. Outside, the Bahnhofstrasse hummed with oblivious luxury. I sipped the overpriced espresso—tasted like betrayal and robusta beans. His smile didn't reach his glacier-blue eyes. “The 1973 oil embargo was just the prototype.” The elevator dinged. Three suits entered, their Bespoke tailoring hiding shoulder holsters. I dropped the saucer. Glass shattered. Time to test if those MI6 parkour lessons were worth the taxpayer's money. The banker sighed. “Americans. So dramatic.”

#Scratch

Today the moon and sun shone in tandem on the morning sky, seemingly disrupting the normal order of the world; indeed a storm is wreaking havoc, toppling the trees who are falling on the power lines, causing power outages, falling on the road causing blockages, falling on pedestrians, killing them.

But that’s north from here. Here in a repurposed prison cell made into a hotel room we make a stop on this little island.

Outside now only the moon shines, I see the stars on the dark sky, and some brightly coloured clouds which looks just as wrong on there — but just as beautiful — as the moon did next to the sun this morning.

Today as we took the whole family on the road we paused to go into a car wash to my child’s and my dogs’ delight.

Last time I parked diagonally in the car wash, outside of the tracks, and I’d forgotten to fold the rear view mirrors so we did that as the water was splatting into the cockpit in a dramatic manner, but this time my wife drove, and also I’ve gotten new glasses.

Last time the car had dirt stripes like a tiger after the wash, but now it’s just red

I hope you had a marvelous holiday this month, whichever one(s) you celebrate. Ours was quiet, but good.

Started on the replacement carving – this one will say “a better world is possible” – and it’s a slow process, both because my wrist can only do so much carving at once; and also, because I’ve been a bit busy.

Today, I tried something new, inspired by a random YouTube video. I can think of all sorts of things to do with these boxes. They were quick to make, and fun to paint – I look forward to improving my painting skills.

#gyushuahighschool

Hong Jisoo. Musim semi tahun ini dia akan menginjak kelas 1 SMA. Meski dirinya bertolak dari negara asalnya ke negara ini, tapi nggak apa-apa. Memang berat harus ninggalin sahabat dekatnya, Vernon, dan keluarganya yang sudah jadi keluarga beneran bagi Joshua, tapi dia yakin lebih banyak kesempatan bakal kebuka buat dia setelah ini. Sekolah yang ditujunya merupakan sekolah bergengsi dengan prestasi terbaik seantero negeri. Plus, Joshua menang beasiswa full gratis sampai ke tiket pesawat, akomodasi (karena dia dapat kamar asrama), serta uang jajan.

Maka, tanpa perlu pikir panjang, Joshua langsung mengepak barang-barangnya yang super sedikit itu dan terbang ke negara ini. Sesampainya di sekolah, dia langsung disambut oleh lelaki paruh baya yang tampan dan berambut hitam. “Salam kenal, Hong. Namaku Choi Seungcheol,” dia tersenyum ramah. “Biarpun aku kepala sekolah di sini, kita ngobrol santai aja ya. Dari berkasmu, kulihat kamu dapat beasiswa full?”

“Hehe,” Joshua meringis. Dia bangga terhadap dirinya sendiri.

“Hmm. Untuk yang lain sih oke, tapi ada masalah sama asrama kamu nih...”

Kedip-kedip mata si anak. Eh kenapa nih?

“Mohon maaf banget tapi kita sebenernya lagi nggak ada kamar kosong. Kemarin sempet ada kebakaran kecil, jadi beberapa kamar lagi direnovasi. Pun kamar yang lain lagi diperiksa dan dikuatin pertahanan akan apinya, jadi...,” Choi-sen menghela napas dan menatap Joshua dengan berat hati. “Maaf banget tapi kayaknya kamu harus tinggal di luar asrama.”

....Seriusan nih? Anjrit.

“Yah, Sen, gimana yah...,” Joshua garuk-garuk sisi keningnya. Dia juga jadi bingung banget. “Aku tuh ke sini sendirian. Nggak ada keluarga ato kenalan. Katanya dapet akomodasi di sini... Kalo mendadak disuruh tinggal di luar...” Bahasa sih nggak masalah. Yang jadi masalah itu duitnya, duit. Tinggal di luar kan butuh duit. Mau kerja sambilan juga, sewa apartemen butuh uang muka beberapa bulan. Pake duit siapa??

“Hmm...paham...,” Choi-sen mengetuk-ngetuk dagu sembari mikir. “Maaf banget, ini salah kita, ke-miss revisi detail beasiswa. Biaya sewa sih bisa kita tanggung, cuma nggak mungkin kita kasih kamu tinggal tanpa pengawasan. Gimana pun kamu masih minor.”

Choi-sen mikir, mikir, mikir...

Pas dia angkat wajah, kebetulan seseorang lagi numpang lewat. Jam pergantian kelas memang penyebab utama ruang guru ramai akan hiruk pikuk staff mempersiapkan materi selanjutnya atau sekadar berbincang sejenak melepas penat. Jadi, siapa saja bisa kebetulan numpang lewat pas kepala sekolah lagi ngobrol sama Joshua, but no, seolah takdir sudah ditulis rapi di kitabnya, seseorang itu haruslah adik tiri Choi Seungcheol sendiri.

“Oh! Mingyu!”

Yang dipanggil lantas berhenti. “Iya, Kak?” jawabnya.

“Sini dulu, sini! Anak ini bakal jadi murid di kelas kamu!”

Patuh, orang yang dipanggil Mingyu itu pun mendekat. “Ah, anak pindahan itu ya?” sapanya dengan ramah. “Salam kenal. Nama saya Kim Mingyu.”

Pas orang itu memampangkan senyuman lembutnya, Joshua harus mengerjap beberapa kali karena terpana. Ganteng banget ini orang, batinnya. Badannya tinggi, lengannya jadi. Ini mah supermodel nyasar. Lumayan juga masuk sini, jadi punya wali kelas seganteng ini. Biar nambah-nambahin semangat belajar gitu. “Salam kenal, Sen,” super manis, si anak tersenyum balik. “Aku Joshua. Hong Jisoo, tapi semua manggil aku Joshua.”

“Mingyu. Anak ini dapet beasiswa full, tapi kan asrama cowok lagi direnov,” Kim-sen mengangguk-angguk saat Choi-sen menjelaskan sambil menunjukkan berkas Joshua. “Jadi mau nggak mau dia harus tinggal di luar asrama.”

“Hoo...”

“Tapi dia nggak ada keluarga ato kenalan di sini. Nggak tau siapa-siapa.”

Serta-merta, Mingyu menjadi awas. “Bahaya dong,” kernyitan sebelah alis. “Nggak bisa dibiarin tinggal bener-bener sendirian gitu.” Apa faedahnya mereka jadi guru kalau seorang anak murid ditelantarin gitu aja di negara asing? Sekalian saja ijin mengajar mereka dicabut.

“Nah. Makanya, kamu setuju kan kalo dia tinggal sama kamu aja?” Choi-sen meringis.

Hening.

”...Maaf. Maksudnya gimana, Kak?” senyuman timpang. Jelas Kim-sen masih mencerna apa yang barusan keluar dari mulut kakaknya.

“Hah...,” otak Joshua sendiri nggak bisa menangkap secepat itu, apalagi hal yang super mendadak kayak belok kiri padahal sen kanan. “Bentar, bentar, Sen.... what??“

“Bener kan??” Choi-sen mengangkat bahu sok polos. “Aku jelas nggak bisa soalnya ada suamiku di rumah. Wonwoo juga sama. Cuma kamu yang single, tinggal sendiri deket dari sekolah dan bisa kupercaya!”

Kim-sen kehilangan kata-kata. Joshua malah jadi memandangi wajah melongo yang (tetap) ganteng itu. “Nah, nah! Semangat, Mingyu! Kalo ada kesulitan, bilang aja ya! Joshua juga! Ayo mulai kelas pagi kalian sana,” Choi-sen kemudian tertawa membahana bersamaan dengan bunyi dering bel pertama. Tepukan kencang kemudian mendatangi bahu Kim-sen seolah menyegel belitan benang merah dua orang asing yang baru pertama bertemu di hari itu, di suatu pagi ketika kelopak bunga Sakura menghujani sepanjang trotoar di depan gerbang sekolah mereka yang megah.

Menyatukan takdir Hong Jisoo dengan Kim Mingyu.

In February 2025, Andrej Karpathy, former director of AI at Tesla and a prominent figure in the machine learning community, dropped a bombshell on Twitter that would reshape how millions of developers think about code. “There's a new kind of coding I call 'vibe coding,'” he wrote, “where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.” The post ignited a firestorm. Within weeks, vibe coding became a cultural phenomenon, earning recognition on the Merriam-Webster website as a “slang & trending” term. By year's end, Collins Dictionary had named it Word of the Year for 2025.

But here's the twist: whilst tech Twitter debated whether vibe coding represented liberation or chaos, something more interesting was happening in actual development shops. Engineers weren't choosing between intuition and discipline. They were synthesising them. Welcome to vibe engineering, a practice that asks a provocative question: what if the real future of software development isn't about choosing between creative flow and rigorous practices, but about deliberately blending them into something more powerful than either approach alone?

The Vibe Revolution

To understand vibe engineering, we first need to understand what vibe coding actually is. In its purest form, vibe coding describes a chatbot-based approach where the developer describes a project to a large language model, which generates code based on the prompt. The developer doesn't review or edit the code, but solely uses execution results to evaluate it, asking the LLM for improvements in an iterative loop.

This represents a radical departure from traditional development. Unlike AI-assisted coding or pair programming, the human developer avoids examination of the code, accepts AI-suggested completions without human review, and focuses more on iterative experimentation than code correctness or structure. It's programming by outcome rather than by understanding, and it's far more widespread than you might think.

By March 2025, Y Combinator reported that 25% of startup companies in its Winter 2025 batch had codebases that were 95% AI-generated. Jared Friedman, YC's managing partner, emphasised a crucial point: “It's not like we funded a bunch of non-technical founders. Every one of these people is highly technical, completely capable of building their own products from scratch. A year ago, they would have built their product from scratch, but now 95% of it is built by an AI.”

The economic results were staggering. The Winter 2025 batch grew 10% per week in aggregate, making it the fastest-growing cohort in YC history. As CEO Garry Tan explained, “What that means for founders is that you don't need a team of 50 or 100 engineers. You don't have to raise as much. The capital goes much longer.”

Real companies were seeing real results. Red Barn Robotics developed an AI-driven weeding robot called “The Field Hand” that operates 15 times faster than human labour at a fraction of traditional costs, securing £3.9 million in letters of intent for the upcoming growing season. Deepnight utilised AI to develop military-grade night vision software, booking £3.6 million in contracts with clients including the U.S. Army and Air Force within a year of launching. Delve, a San Francisco-based startup using AI agents for compliance evidence collection, launched with a revenue run rate of several million pounds and over 100 customers, all with a modest £2.6 million in funding.

These weren't weekend projects. These were venture-backed companies building production systems that customers were actually paying for, and doing it with codebases they fundamentally didn't understand at a granular level.

The Psychology of Flow

The appeal of vibe coding isn't just about speed or efficiency. It taps into something deeper: the psychological state that makes programming feel magical in the first place. Psychologist Mihaly Csikszentmihalyi spent decades studying what he called “flow,” describing it as “the state in which people are so involved in an activity that nothing else seems to matter.” His research found that flow produces the highest levels of creativity, engagement, and satisfaction. Studies at Harvard later quantified this, finding that people who experience flow regularly report 500% more productivity and three times greater life satisfaction.

Software developers have always had an intimate relationship with flow. Many developers spend a large part of their day in this state, often half-jokingly saying they love their work so much they can't believe they're getting paid for something so fun. The flow state arises when perceived skills match the perceived challenges of the task: too easy and you get bored; too difficult and you become anxious. The “flow channel” is that sweet spot of engagement where hours disappear and elegant solutions emerge seemingly by themselves.

But flow has always been fragile. Research by Gloria Mark shows that it takes an average of 23 minutes and 15 seconds to fully regain focus after an interruption. For developers, this means a single “quick question” from a colleague can destroy nearly half an hour of productive coding time. For complex coding tasks, this recovery time extends to 45 minutes, according to research from Carnegie Mellon. Studies show productivity decreases up to 40% in environments with frequent interruptions, and interrupted work contains 25% more errors than uninterrupted work, according to research from the University of California, Irvine.

This is where vibe coding's appeal becomes clear. By offloading the mechanical aspects of code generation to an AI, developers can stay in a higher-level conceptual space, describing what they want rather than how to implement it. They can maintain flow by avoiding the context switches that come with looking up documentation, debugging syntax errors, or implementing boilerplate code. As one framework describes it, “Think of vibe coding like jazz improvisation: structured knowledge meets spontaneous execution.”

According to Stack Overflow's 2024 Developer Survey, 63% of professional developers were already using AI in their development process, with another 14% planning to start soon. The top three AI tools were ChatGPT (82%), GitHub Copilot (41%), and Google Gemini (24%). More than 97% of respondents to GitHub's AI in software development 2024 survey said they had used AI coding tools at work. By early 2025, over 15 million developers were using GitHub Copilot, representing a 400% increase in just 12 months.

The benefits were tangible. Stack Overflow's survey found that 81% of developers cited increasing productivity as the top benefit of AI tools. Those learning to code listed speeding up their learning as the primary advantage (71%). A 2024 study by GitHub found that developers using AI pair programming tools produced code with 55% fewer bugs than those working without AI assistance.

When Vibes Meet Reality

But by September 2025, the narrative was shifting. Fast Company reported that the “vibe coding hangover” was upon us, with senior software engineers citing “development hell” when working with AI-generated vibe-code. The problems weren't subtle.

A landmark Veracode study in 2025 analysed over 100 large language models across 80 coding tasks and found that 45% of AI-generated code introduces security vulnerabilities. These weren't minor bugs: many were critical flaws, including those in the OWASP Top 10. In March 2025, a vibe-coded payment gateway approved £1.6 million in fraudulent transactions due to inadequate input validation. The AI had copied insecure patterns from its training data, creating a vulnerability that human developers would have caught during code review.

The technical debt problem was even more insidious. Over 40% of junior developers admitted to deploying AI-generated code they didn't fully understand. Research showed that AI-generated code tends to include 2.4 times more abstraction layers than human developers would implement for equivalent tasks, leading to unnecessary complexity. Forrester forecast an “incoming technical debt tsunami over the next 2 years” due to advanced AI coding agents.

AI models also “hallucinate” non-existent software packages and libraries. Commercial models do this 5.2% of the time, whilst open-source models hit 21.7%. Malicious actors began exploiting this through “slopsquatting,” creating fake packages with commonly hallucinated names and hiding malware inside. Common risks included injection vulnerabilities, cross-site scripting, insecure data handling, and broken access control.

The human cost was equally concerning. Companies with high percentages of AI-generated code faced challenges around understanding and accountability. Without rigorous preplanning, architectural oversight, and experienced project management, vibe coding introduced vulnerabilities, compliance gaps, and substantial technical debt. Perhaps most worryingly, the adoption of generative AI had the potential to stunt the growth of both junior and senior developers. Senior developers became more adept at leveraging AI and spent their time training AI instead of training junior developers, potentially creating a future talent gap.

Even Karpathy himself had acknowledged the limitations, noting that vibe coding works well for “throwaway weekend projects.” The challenge for 2025 and beyond was figuring out where that line falls. Cyber insurance companies began adjusting their policies to account for AI-generated code risks, with some insurers requiring disclosure of AI tool usage, implementing higher premiums for companies with high percentages of AI-generated code, and mandating security audits specifically focused on AI-generated vulnerabilities.

The Other Side of the Equation

Whilst vibe coding captured headlines, the foundations of professional software engineering remained remarkably consistent. Code reviews continued to act as quality gates before changes were merged, complementing other practices like testing and pair programming. The objective of code review has always been to enhance the quality, maintainability, stability, and security of software through systematic analysis.

Modern code review follows clear principles. Reviews should be focused: a comprehensive Cisco study found that once developers reviewed more than 200 lines of code, their ability to identify defects waned. Most bugs are found in the first 200 lines, and reviewing more than 400 lines can have an adverse impact on bug detection. Assessing the architectural impact of code is critical: code that passes all unit tests and follows style guides can still cause long-term damage if no one evaluated its architectural impact.

Automated checks allow reviewers to focus on more important topics such as software design, architecture, and readability. Checks can include tests, test coverage, code style enforcements, commit message conventions, and static analysis. Commonly used automated code analysis and monitoring tools include SonarQube and New Relic, which inspect code for errors, track error rates and resource usage, and present metrics in clear dashboards.

Organisations with better code reviews have hard rules around no code making it to production without review, just as business logic changes don't make it to production without automated tests. These organisations have learned that the cost of cutting corners isn't worth it, and they have processes for expedited reviews for urgent cases. Code reviews are one of the best ways to improve skills, mentor others, and learn how to be a more efficient communicator.

Testing practices have evolved to become even more rigorous. During test-driven code reviews, the reviewer starts by reviewing the test code before the production code. The rationale behind this approach is to use the test cases as use cases that explain the code. One of the most overlooked yet high-impact parts of code review best practice is assessing the depth and relevance of tests: not just whether they exist, but whether they truly validate the behaviour and edge cases of the code.

Architecture considerations remain paramount. In practice, a combination of both top-down and bottom-up approaches is often used. Starting with a top-down review helps understand the system's architecture and major components, setting the stage for a more detailed, bottom-up review of specific areas. Performance and load testing tools like Apache JMeter, Gatling, and Simulink help detect design problems by simulating system behaviour.

These practices exist for a reason. They represent decades of accumulated wisdom about how to build software that doesn't just work today, but continues to work tomorrow, can be maintained by teams that didn't write it originally, and operates securely in hostile environments.

From Vibe Coding to Context Engineering

By late 2025, a significant shift was occurring in how AI was being used in software engineering. A loose, vibes-based approach was giving way to a systematic approach to managing how AI systems process context. This evolution had a name: context engineering.

As Anthropic described it, “After a few years of prompt engineering being the focus of attention in applied AI, a new term has come to prominence: context engineering. Building with language models is becoming less about finding the right words and phrases for your prompts, and more about answering the broader question of 'what configuration of context is most likely to generate our model's desired behaviour?'”

In simple terms, context engineering is the science and craft of managing everything around the AI prompt to guide intelligent outcomes. This includes managing user metadata, task instructions, data schemas, user intent, role-based behaviours, and environmental cues that influence model behaviour. It represents the natural progression of prompt engineering, referring to the set of strategies for curating and maintaining the optimal set of information during LLM inference.

The shift was driven by practical necessity. As AI agents run longer, the amount of information they need to track explodes: chat history, tool outputs, external documents, intermediate reasoning. The prevailing “solution” had been to lean on ever-larger context windows in foundation models. But simply giving agents more space to paste text couldn't be the single scaling strategy. The limiting factor was no longer the model; it was context: the structure, history, and intent surrounding the code being changed.

MIT Technology Review captured this evolution in a November 2025 article: “2025 has seen a real-time experiment playing out across the technology industry, one in which AI's software engineering capabilities have been put to the test against human technologists. And although 2025 may have started with AI looking strong, the transition from vibe coding to what's being termed context engineering shows that whilst the work of human developers is evolving, they nevertheless remain absolutely critical.”

Context engineering wasn't about rejecting AI or returning to purely manual coding. It was about treating context as an engineering surface that required as much thought and discipline as the code itself. Developer-focused tools embraced this, with platforms like CodeConductor, Windsurf, and Cursor designed to automatically extract and inject relevant code snippets, documentation, or history into the model's input.

The challenge that emerged was “agent drift,” described as the silent killer of AI-accelerated development. It's the agent that brilliantly implements a feature whilst completely ignoring the established database schema, or new code that looks perfect but causes a dozen subtle, unintended regressions. The teams seeing meaningful gains treated context as an engineering surface, determining what should be visible to the agent, when, and in what form.

Importantly, context engineering recognised that more information wasn't always better. As research showed, AI can be more effective when it's further abstracted from the underlying system because the solution space becomes much wider, allowing better leverage of the generative and creative capabilities of AI models. The goal wasn't to feed the model more tokens; it was to provide the right context at the right time.

Vibe Engineering in Practice

This is where vibe engineering emerges as a distinct practice. It's not vibe coding with a code review tacked on at the end. It's not traditional engineering that occasionally uses AI autocomplete. It's a deliberate synthesis that borrows from both approaches, creating something genuinely new.

In vibe engineering, the intuition and flow of vibe coding are preserved, but within a structured framework that maintains the essential benefits of engineering discipline. The developer still operates at a high conceptual level, describing intent and iterating rapidly. The AI still generates substantial amounts of code. But the process is fundamentally different from pure vibe coding in several crucial ways.

First, vibe engineering treats AI-generated code as untrusted by default. Just because it runs doesn't mean it's safe, correct, or maintainable. Every piece of generated code passes through the same quality gates as human-written code: automated testing, security scanning, code review, and architectural assessment. The difference is that these gates are designed to work with the reality of AI-generated code, catching the specific patterns of errors that AI systems make.

Second, vibe engineering emphasises spec-driven development. As described in research on improving AI coding quality, “Spec coding puts specifications first. It's like drafting a detailed blueprint before building, ensuring every component aligns perfectly. Here, humans define the 'what' (the functional goals of the code) and the 'how' (rules like standards, architecture, and best practices), whilst the AI handles the heavy lifting (code generation).”

This approach preserves flow by keeping the developer in a high-level conceptual space, but ensures that the generated code aligns with team standards, architectural patterns, and security requirements. According to research, 65% of developers using AI say the assistant “misses relevant context,” and nearly two out of five developers who rarely see style-aligned suggestions cite this as a major blocker. Spec-driven development addresses this by making context explicit upfront.

Third, vibe engineering recognises that different kinds of code require different approaches. As one expert put it, “Don't use AI to generate a whole app. Avoid letting it write anything critical like auth, crypto or system-level code; build those parts yourself.” Vibe engineering creates clear boundaries: AI is ideal for testing new ideas, creating proof-of-concept applications, generating boilerplate code, and implementing well-understood patterns. But authentication, cryptography, security-critical paths, and core architectural components remain human responsibilities.

Fourth, vibe engineering embeds governance and quality control throughout the development process. Sonar's AI Code Assurance, for example, measures quality by scanning for bugs, code smells, vulnerabilities, and adherence to established coding standards. It provides developers with actionable feedback and scores on various metrics, highlighting areas that need attention to meet best practice guidelines. The solution also tracks trends in code quality over time, making it possible for teams to monitor improvements or spot potential regressions.

Research shows that teams with strong code review processes experience quality improvements when using AI tools, whilst those without see a decline in quality. This amplification effect makes thoughtful implementation essential. Metrics like CodeBLEU and CodeBERTScore surpass linters by analysing structure, intent, and functionality, allowing teams to achieve scalable, repeatable, and nuanced assessment pipelines for AI-generated code.

Fifth, vibe engineering prioritises developer understanding over raw productivity. Whilst AI can generate code faster than humans can type, vibe engineering insists that developers understand the generated code before it ships to production. This doesn't mean reading every line character by character, but it does mean understanding the architectural decisions, the security implications, and the maintenance requirements. Tools and practices are designed to facilitate this understanding: clear documentation generation, architectural decision records, and pair review sessions where junior and senior developers examine AI-generated code together.

Preserving What Makes Development Human

Perhaps the most important aspect of vibe engineering is how it handles the human dimension of software development. Developer joy, satisfaction, and creative flow aren't nice-to-haves; they're fundamental to building great software. Research consistently shows that happiness, joy, and satisfaction all lead to better productivity. When companies chase productivity without considering joy, the result is often burnout and lower output.

Stack Overflow's research on what makes developers happy found that salary (60%), work-life balance (58%), flexibility (52%), productivity (52%), and growth opportunities (49%) were the top five factors. Crucially, feeling unproductive at work was the number one factor (45%) causing unhappiness, even above salary concerns (37%). As one developer explained, “When I code, I don't like disruptions in my flow state. Constantly stopping and starting makes me feel unproductive. We all want to feel like we're making a difference, and hitting roadblocks at work just because you're not sure where to find answers is incredibly frustrating.”

Vibe engineering addresses this by removing friction without removing challenge. The AI handles the tedious parts: boilerplate code, repetitive patterns, looking up documentation for APIs used infrequently. This allows developers to stay in flow whilst working on genuinely interesting problems: architectural decisions, user experience design, performance optimisation, security considerations. The AI becomes what one researcher described as “a third collaborator,” supporting idea generation, debugging, and documentation, whilst human-to-human collaboration remains central.

Atlassian demonstrated this approach by asking developers to allocate 10% of their time for reducing barriers to happier, more productive workdays. Engineering leadership recognised that developers are the experts on what's holding them back. Identifying and eliminating sources of friction such as flaky tests, redundant meetings, and inefficient tools helped protect developer flow and maximise productivity. The results were dramatic: Atlassian “sparked developer joy” and set productivity records.

Vibe engineering also addresses the challenge of maintaining developer growth and mentorship. The concern that senior developers will spend their time training AI instead of training junior developers is real and significant. Vibe engineering deliberately structures development practices to preserve learning opportunities: pair programming sessions that include AI as a third participant rather than a replacement for human pairing; code review processes that use AI-generated code as teaching opportunities; architectural discussions that explicitly evaluate AI suggestions against alternatives.

Research on pair programming shows that two sets of eyes catch mistakes early, with studies showing pair-programmed code has up to 15% fewer defects. A meta-analysis found pairs typically consider more design alternatives than programmers working alone, arrive at simpler, more maintainable designs, and catch design defects earlier. Vibe engineering adapts this practice: one developer interacts with the AI whilst another reviews the generated code and guides the conversation, creating a three-way collaboration that preserves the learning benefits of traditional pair programming.

Does Vibe Engineering Scale?

The economic case for vibe engineering is compelling but nuanced. Pure vibe coding promises dramatic cost reductions: fewer engineers, faster development, lower capital requirements. The Y Combinator results demonstrate this isn't just theory. But the hidden costs of technical debt, security vulnerabilities, and maintenance burden can dwarf the initial savings.

Vibe engineering accepts higher upfront costs in exchange for sustainable long-term economics. Automated security scanning, comprehensive testing infrastructure, and robust code review processes all require investment. Tools for AI code assurance, quality metrics, and context engineering aren't free. But these costs are predictable and manageable, unlike the potentially catastrophic costs of security breaches, compliance failures, or systems that become unmaintainable.

The evidence suggests this trade-off is worthwhile. Research from Carnegie Mellon shows developers juggling five projects spend just 20% of their cognitive energy on real work. Context switching costs IT companies an average of £39,000 per developer each year. By reducing friction and enabling flow, vibe engineering can recapture substantial amounts of this lost productivity without sacrificing code quality or security.

The tooling ecosystem is evolving rapidly to support vibe engineering practices. In industries with stringent regulations such as finance, automotive, or healthcare, specialised AI agents are emerging to transform software efficiently, aligning it precisely with complex regulatory standards and requirements. Code quality has evolved from informal practices into formalised standards, with clear guidelines distinguishing best practices from mandatory regulatory requirements.

AI adoption among software development professionals has surged to 90%, marking a 14% increase from the previous year. AI now generates 41% of all code, with 256 billion lines written in 2024 alone. However, a randomised controlled trial found that experienced developers take 19% longer when using AI tools without proper process and governance. This underscores the importance of vibe engineering's structured approach: the tools alone aren't enough; it's how they're integrated into development practices that matters.

The Future of High-Quality Software Development

If vibe engineering represents a synthesis of intuition and discipline, what does the future hold? Multiple signals suggest this approach isn't a temporary compromise but a genuine glimpse of how high-quality software will be built in the coming decade.

Microsoft's chief product officer for AI, Aparna Chennapragada, sees 2026 as a new era for alliances between technology and people: “If recent years were about AI answering questions and reasoning through problems, the next wave will be about true collaboration. The future isn't about replacing humans. It's about amplifying them.” GitHub's chief product officer, Mario Rodriguez, predicts 2026 will bring “repository intelligence”: AI that understands not just lines of code but the relationships and history behind them.

By 2030, all IT work is forecast to involve AI, with CIOs predicting 75% will be human-AI collaboration and 25% fully autonomous AI tasks. A survey conducted in July 2025, involving over 700 CIOs, indicates that by 2030, none of the IT workload will be performed solely by humans. Software engineering will be less about writing code and more about orchestrating intelligent systems. Engineers who adapt to these changes (embracing AI collaboration, focusing on design thinking, and staying curious about emerging technologies) will thrive.

Natural language programming will go mainstream. Engineers will describe features in plain English, and AI will generate production-ready code that other humans can easily understand and modify. According to the World Economic Forum, AI will create 170 million new jobs whilst displacing 92 million by 2030: a net creation of 78 million positions. However, the transition requires massive reskilling efforts, as workers with AI skills command a 43% wage premium.

The key insight is that the most effective developers of 2025 are still those who write great code, but they are increasingly augmenting that skill by mastering the art of providing persistent, high-quality context. This signals a change in what high-level development skills look like. The developer role is evolving from manual coder to orchestrator of AI-driven development ecosystems.

Vibe engineering positions developers for this future by treating AI as a powerful but imperfect collaborator rather than a replacement or a simple tool. It acknowledges that intuition and creative flow are essential to great software, but so are architecture, testing, and review. It recognises that AI can dramatically accelerate development, but only when embedded within practices that ensure quality, security, and maintainability.

Not Whether, But How

The question posed at the beginning (can intuition-led development coexist with rigorous practices without diminishing either?) turns out to have a clear answer: not only can they coexist, but their synthesis produces something more powerful than either approach alone.

Pure vibe coding, for all its appeal and early success stories, doesn't scale to production systems that must be secure, maintainable, and reliable. The security vulnerabilities, technical debt, and accountability gaps are too severe. Traditional engineering, whilst proven and reliable, leaves significant productivity gains on the table and risks losing developers to the tedium and friction that AI tools can eliminate.

Vibe engineering offers a third way. It preserves the flow state and rapid iteration that makes vibe coding appealing whilst maintaining the quality gates and architectural rigour that make traditional engineering reliable. It treats AI as a powerful collaborator that amplifies human capabilities rather than replacing human judgment. It acknowledges that different kinds of code require different approaches, and creates clear boundaries for where AI excels and where humans must remain in control.

The evidence from Y Combinator startups, Microsoft's AI research, Stack Overflow's developer surveys, and countless development teams suggests that this synthesis isn't just possible; it's already happening. The companies seeing the best results from AI-assisted development aren't those using it most aggressively or most conservatively. They're the ones who've figured out how to blend intuition with discipline, speed with safety, and automation with understanding.

As we project forward to 2030, when 75% of IT work will involve human-AI collaboration, vibe engineering provides a framework for making that collaboration productive rather than chaotic. It offers a path where developers can experience the joy and flow that drew many of them to programming in the first place, whilst building systems that are secure, maintainable, and architecturally sound.

The future of high-quality software development isn't about choosing between the creative chaos of vibe coding and the methodical rigour of traditional engineering. It's about deliberately synthesising them into practices that capture the best of both worlds. That synthesis, more than any specific tool or technique, may be the real innovation that defines how software is built in the coming decade.

References & Sources

• Vibe coding – Wikipedia
• From vibe coding to context engineering: 2025 in software development – MIT Technology Review
• How Vibe Coding is Changing Software Development in 2025 – Index.dev
• Vibe Coding in Practice: Motivations, Challenges, and a Future Outlook – arXiv
• What is Vibe Coding? – IBM
• Not all AI-assisted programming is vibe coding – Simon Willison
• Flow State and Programming – sap1ens.com
• Mihaly Csikszentmihalyi – Wikipedia
• Software Engineering Best Practices for Code Review – daily.dev
• Top 7 Code Review Best Practices For Developers in 2025 – Qodo
• A complete guide to code reviews – Swarmia
• 5 Vibe Coding Risks and Ways to Avoid Them in 2025 – Zencoder.ai
• Vibe coding security risks and how to mitigate them – IT Pro
• How to avoid vibe coding your way into a tsunami of tech debt – Tabnine
• When the Vibes Are Off: The Security Risks of AI-Generated Code – Lawfare
• Vibe Coding Can Create Unseen Vulnerabilities – DevOps.com
• How AI Code Reviews Ensure Compliance and Enforce Coding Standards – Qodo
• AI Code Assurance: Quality & Security in Generated Code – Sonar
• How spec-driven development improves AI coding quality – Red Hat Developer
• State of AI code quality in 2025 – Qodo
• Context-switching is the main productivity killer for developers – TechWorld with Milan
• Mitigating Context Switching in Software Development – Jellyfish
• Context Switching Is Killing Your Productivity – Software.com
• Developer Flow State Engineering – FullScale
• The Cost of Context Switching for Devs – Codezero
• Context Engineering: A Complete Guide – CodeConductor.ai
• From vibe coding to context engineering – Thoughtworks
• Effective context engineering for AI agents – Anthropic
• On Pair Programming – Martin Fowler
• Pair Programming – Coursera
• How AI Pair Programming is Transforming Development Teams in 2025 – Naveck
• A Quarter of Startups in YC's Current Cohort Have Codebases That Are Almost Entirely AI-Generated – TechCrunch
• Y Combinator startups are fastest growing in fund history because of AI – CNBC
• Developer Joy: a Better Way to Boost Developer Productivity – InfoQ
• Unlocking the Developer's Flow State – Medium
• Atlassian sparked developer joy and set productivity records – DevPath
• New data: What makes developers happy at work – Stack Overflow
• 2024 Stack Overflow Developer Survey
• AI – 2025 Stack Overflow Developer Survey
• GitHub survey finds nearly all developers using AI coding tools – InfoWorld
• Developers get by with a little help from AI – Stack Overflow
• What's next in AI: 7 trends to watch in 2026 – Microsoft
• The Future of AI in Software Development: Key 2025 Insights Revealed – Emmo
• CIOs forecast all IT work will involve AI-human collaboration by 2030 – IT Brief

---

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

U-0055 is an “antimeme”, an entity that somehow escapes people's memory. It sits in a secret facility but no one remembers how it landed there. In fact, no one can even recall it's there or what it is. Is it an object, a person or could it be just an idea? It could be a major threat but no one can come up with a plan to defeat it since no one is aware of it.

This is only a summary of the prologue of this book and it got me hooked. I was in for a ride because things only got crazier from there. The novel is described as at the crossing between scifi and cosmic horror, with a terrifying enemy that no one is even allowed to remember as just thinking about it would invite it. The story focuses on Marie, the head of the Antimemetics Division, who discovers many people in the organisation have disappeared and no one even remembers they were there, meaning something is at play. There is a “no one is safe” approach and Murphy's Law is in full swing, especially halfway through the book when the situation goes from bad to way worse. Another thing is that pretty much every detail serves a purpose in this book, everything resufaces at some point. There were some really good ideas. Special mention to the idea around the character of Adrian Gage was, even though he only appears in one chapter. It's a short but intense book, just like I like them ❤️ Definitely one of my favourites this year.

NB: I read a new edition with a different cover and minor story differences but I preferred this one so I picked it for illustration.

Heute ist was cooles passiert. Oder besser: es ist nicht passiert. My girlfriend und ich waren in einem Café (eher eine Bäckerei mit Sitzmöglichkeiten und dem schlechtesten Kaffee, seit ich in der Klinik war) und auf dem Tisch war so ein Weihnachtsgesteck mit Tannengrün. Tannengrün war für mich mit einer meiner stärksten Trigger.

Heute hat mich das Zeug kalt gelassen. Die Expo hat tatsächlich etwas gebracht. Ich habe das Gesteck erst gar nicht wahrgenommen. Als ich es bemerkt habe, kam eine Erinnerung hoch. Aber sie war nur ganz schwach. Ich hatte keine Flashbacks, kein Gefühl von Hilflosigkeit. Ich war eher etwas verwundert, wie wenig mich das Tannengrün gestört hat.

Erst im Nachhinein, heute Abend, habe ich den Fortschritt realisiert. Es war keine laute Freude, eher ein stilles, warmes Sich freuen. Ein kleines Innehalten, ein freundlicher Blick auf mich selbst: Das war nicht nichts. Etwas ist leichter geworden. Und es tut gut zu spüren, dass sich all die Mühe, die Kraft und auch der Schmerz der Traumatherapie gelohnt haben 👸🏻 selbst dann, wenn der Erfolg leise bleibt.

#VeryVeri #LeiserFortschritt #SanftZuMir

As usual the subgenre I avoided because I did not think it would be for me (in this case regency/historical romance) does have something for me.

This review refers to the murder mystery, knife violence, gun violence, and 19th century homophobia that are in the book.

#SFW

Medium Used: 40% audiobook via Hoopla | 60% ebook via Kindle

Ratings out of 5

Overall Rating:
💜💜💜💜 (4/5)

Sweetness Level:
🍫🍫🍫 (3/5)

Spice Heat Level:
💧 (0/5)

Slow Burn Steamy Tension Quality: 🥵🥵🥵 (3/5)

FMC Likability:
👗👗👗👗👗(5/5)

MMC Likability:
🎩🎩🎩🎩 (4/5)

Plot Engagement:
🗡️🗡️🗡️🗡️ (4/5)

At least 1 bad dad (pass/fail):
💯 (pass)

BONUS audiobook narration:🔉🔉🔉

Spoiler Free Review

Murder at the Seven Dials is the first book in the Bow Street Duchess Mystery series. It (presumably) begins a slow burn romance between Audrey Sinclair, the Duchess of Fournier and a Bow Street Detective, Hugh Marsden. Their paths cross when Mr. Marsden finds Her Grace's husband, The Duke of Fournier covered in the blood of a murdered opera singer Ms. Lovejoy.

This is a fun read, an intriguing mystery, and cute start of a love story. I appreciated that its pace and brevity. I loved the subtlety of the paranormal fantasy that is woven into this story. Her Grace has a gift that allows her to see other's memories when she touches objects or people. A gift that she considers a curse and keeps a secret. For me, this 'light' fantasy in an otherwise grounded world was novel. I am interested to see if the paranormal aspects of the world will grow at all as the fantasy continues.

The unique circumstances surrounding the meet (not so) cute of Her Grace and Mr. Marsden and their differences in station made their growth in admiration for each other both humorous and endearing. I look forward to seeing where this series goes. Consider me hooked.
What I liked about this book
* Minor Spoiler for a reveal in the first 10% of the story >!The plutonic love between the Duke and Duchess was really interesting to me. I love the dynamic of a married woman as an FMC that loves her husband, who loves her, but only as friends.!< * I am a sucker for sass and witty banter. There is plenty in here.
* The way Audrey and Hugh have unique strengths as investigators that both compliment and conflict with each other. For example, Hugh is more careful about how he approaches things but he is also often too slow or too presumptive and misses things. Audrey can be rash but is a fast learner and her decisive action makes sure opportunities are not missed. * Audrey Sinclair is up there with Nevada Baylor and Olive Smith in heroines that just do it for me.

What I did not like about this book
* At first I was listening to this book because it was available on Hoopla and an ebook version wasn't available on Hoopla or Libby. I found it difficult to keep the various aristocrats and Nobility straight in the audiobook version. Which made it hard to follow the mystery.

Spoilers Review

Click to Reveal Spoilers

What I liked Spoilers
* Mr. Marsden's honor and kind heart is shown not told. His efforts to protect the Duke and Duchesses secrets at the end of the story and his juxtaposition to all the members of the ton only looking out for themselves is a nice change from the super tall alphahole trope in much of romance.
* The Duke being gay and how this is weaved into the mystery and Audrey's character was great. What I found fantastic though was how the danger of this reality refutes the 'glamorization' of regency London which I suspected from the genre. I see now how historical romance can use the setting in a way dystopian romances do.¹
* The Duchess thinking people are following her because Mr. Marsden has people watching her but they are actually the bad-guys watching her. Loved this dramatic irony and the pay off when Hugh and Audrey catch up to the reader.

What I didn't like Spoilers
* Maybe it was because I started with Audiobook but I found Hugh's backstory really confusing. I am fairly certain there are still questions to answer but if there isn't I cannot say I followed it completely. * Last Scene Spoilers Not a kiss or a hug in the last scene? Man you have to be kidding me.

^{1 One of the reasons I have not wanted to pick up historical romances (written in modern times, no issues reading 18th/19th century romance written at the time) is because both my parents marriage and my marriage would have been illegal (race mixing) in most of the Western World in the setting.}

This Book Reminded Me of:

• Hidden Legacy by Ilona Andrews, fast pace mystery with a strong woman lead
  
  

Who should read this book?

I think fans of slow burn romantic mysteries will enjoy this one. I described it to my wife as regency Veronica Mars vibes but with a splash of paranormal.

Get the Book

Bonus Gush Lore Olympus by Rachel Smythe Volume 1

Apparently Rachel Smythe wrote the Greek Mythology romantic comedy graphic novel I didn’t know I needed but now cannot imagine life without.

I read it in as close to 1 sitting you can have with gremlins running about on Boxing Day. The artwork is beautiful, the dialogue is witty, and the comedy lands in the way I imagine Homer’s better lines landed a few thousand years ago. So good and I cannot believe I’ve never seen this mentioned here or on any of the sister.

💜💜💜💜💜 (5/5)

Big shout out to the librarian who said it was her favorite series when I checked this out. I will be asking you for more recs next time I see you at the library.

#Books #CaraDevlin #RomanceBooks #HistoricalRomance #RegencyRomance #MysteryRomance #BowStreetDuchess

Lost and can't be Found

#nsfw #glass

The demon may be gone, but there is nothing left. The room is a mess: old candles, that mirror, stains on the floor. She knew Meredith wasn’t going anywhere. Her gaze lazily wandered to the next screen playing porn. Meredith is just mindlessly rubbing, drooling, gurgling. She looks human, but she's so much less now. With a half-whisper between moans and gasps, a tiny spark of humanity remains. Meredith whispers, “Rayeanna, porn, goddess, help,” before rubbing her pussy with no intent to stop or cum. Meredith is still fighting on the inside even if her body just wants her to goon what’s left of her life away.

“Hang in there, baby,” Rayeanna spoke with a confident and measured tone. Honestly, she didn’t know how she would fix Meredith; it’s a miracle the woman is still alive. This wasn't the time to show Meredith any doubt.

Without hesitation, Rayeanna spoke again. “First, I need to fully cleanse this space so whatever we banished will never come back.”

Rayeanna put her bra back on. She had more work to do. Meredith gurgled a faint “no, come back” as the woman walked away from the room. Meredith slow-fucking herself with a dildo, eyes glued to Rayeanna’s perfect ass as she walked away. She was just a passenger inside her body right now. The slick slurping sounds from the screens and Meredith's own ravaged body faded into the background as Rayeanna focused on what needed to be done.

Everything that was part of that ritual needed to be removed from that room: every visual remnant, every drop of wax, and most certainly that mirror. It was the most obvious threat to Meredith’s safety if she was left alone with it too long. With practiced swiftness, Rayeanna bagged what was left of the ritual, grabbed the mirror, and headed outside.

The moment she touched the mirror, she knew whatever she banished wasn't gone. The longer she held the mirror, the more she could perceive small shapes and light and shadows on the edges of her vision. When she made it to the backyard, the sounds of the night slowly faded to nothing. There was an ominous stillness. It’s a feeling she’s all too familiar with. But she was ready. She knows this sensation. She knew something powerful growing, waiting, plotting. She began to hear whispers… louder this time… coming from inside the mirror. The once reflective material had grown pitch black, almost absorbing the light of the night. Two orbs started to appear and were growing in size, as if they were coming closer to a threshold, and the mirror was just a gateway for it to cross over.

She sighed. She rolled her eyes. They always try to come back.

Her eyes glowed in response to the threat. A breeze began to swirl around her as she spoke, breaking the stillness of the night. It slowly lifted her hair and clothing, making her look bigger and dangerous.

Her voice dropped to an unnatural metallic timbre. This new voice boomed with a threat full of weight and ancient power. “Try me, and I will find all your kin and obliterate everything you ever knew. It won't be just you. Everything you know, and even every dimension you live in will be vaporized. I will not stop until everything is gone and every particle of your being is erased from existence. I will more than end you; I WILL delete you. Do… You… Understand?”

The whispers stopped. The glowing eyes blinked out of existence, and a shadowy figure turned and ran back into the inky blackness of the mirrors. The shadowy shapes in her vision faded. The light of the night started to return. Creatures of the night began to make sounds again. A gentle breeze began to blow, and the mirror was black no more. Rayeanna wasn't done yet. She knew better.

She placed the mirror and the other cursed objects that were part of it on the ground in the moonlight. With her final prayer of exorcism and release, the darkness rose up out of them and into the night. It was the final remnant left from Meredith’s foolish ritual.

The glass, unable to hold its original form, aged and faded to dust. The wooden frame soon decayed as well. Everything slowly became a fine sand-like powder. Whatever was left returned back to the earth and blew on the wind into the night. Rayeanna blessed the ground and asked for her ancient familiars to guard this place tonight. She knew she made waves in the other realm. This wasn’t her first time; this won't be her last. For now, Meredith was safe.

The glow in her eyes waned. Her clothing and hair settled. This was a form that only demons of the worst kind witness. Her grandmother is the same. This is Rayeanna’s ancient ability passed through the ages. This human ability is never written down and only spoken of at rites of passage. She was one of the true guardians of this world and took a vow to remain hidden until needed. No one is none the wiser that good won over evil once again.

With the threat finally gone, she had to make her way back to Meredith. He had to get back to that broken husk of a woman who is naked and mindlessly going. It is what she wished for. She learned the hard way there is always a price.

As Rayeanna walked back into the house, she finally knew what she had to do. If this is what Meredith truly desires, then Rayeanna will give it to her. If Rayeanna grants her wish, makes her worship, lets her experience a black woman in real life, there’s a chance Meredith can be saved.

Rayeanna texted her lifeline and contact: “Meet me here in the morning. The worst is over. I still have more work to do.” The silent watcher just responded with a “thumbs up.” A sign of life. Nothing more. Nothing less.

The door clicked shut behind Rayeanna as she stepped back into Meredith's porn shrine—a broken church of misguided need and longing. The room was dark and hazy, multiple screens flickering with explicit and pornographic scenes of black bodies writhing in ecstasy. A chorus of black voices all in ecstasy. In the center, Rayeanna spotted Meredith on the floor. A pale figure curled up and shuddering, fingers working frantically between her legs.

She wasn't even staring at her screens anymore. Her body was ravaged and overstimulated by the uncontrollable urge to masturbate. She was sweating and convulsing from every uninvited orgasm forcing her into pleasure loops nonstop.

“Meredith?”she called out, approaching cautiously. Meredith's head snapped up, eyes wide and unfocused. “Rayeanna? I...I can't...” Her words dissolved into a keening moan as another wave of pleasure crashed through her.

Rayeanna felt her heart clench. In short, quick motions, the curvy golden goddess stripped fully nude in front of Meredith. Rayeanna's curvy full breasts, shapely hips, and soft curves filled Meredith's vision. She could still smell the hint of coconut that brought her back the first time at the park.

Meredith's eyes went wide with admiration and wonder. “Beautiful,” the weak woman whimpered as tears welled up in her eyes. She could die happy now if this was her last moment on this earth. She would risk her life over and over if it ended just like this every time.

Naked, Rayeanna knelt beside her, gently prying Meredith's hands away from her dripping, throbbing, and swollen sex. Her hands were puny; she had rubbed herself raw. Her hair was a mess; she was in the worst state she had ever been in in her life. Now a black goddess was naked in her room, seeing her at her worst with all of her darkest secrets revealed in one fateful swoop. She had never felt so alone, fearful, or cared for all at the same time.

Rayeanna locked eyes with her. “Shh, it's okay, baby. I got you now.”

Meredith whimpered as Rayeanna's fingers replaced hers, stroking slowly through the slick folds. It had been so long since she felt another person's sensual touch. She had never been touched by a woman this way. Men were always rough, too quick, too brutish. She felt like a thing in their grasp. She didn't feel safe. Rayeanna was different. It's like the woman could see right through her small body and into her soul.

She didn't know this kind of intimacy existed or that this was even possible. That's why she spent most of her time lost in a haze of endless pornography worship and masturbation. She would rather chase the high that only came from pornography and the admiration of black bodies on her screen.

But now Rayeanna was here. Her soft yet strong guiding hands touched Meredith's trembling body as she worked magic with her fingers. She was pressing and circling in all the right ways, coaxing out gasps and cries of pleasure. Every inch of her body got attention.

As Rayeanna touched her body, Meredith felt sensations on her nipples, neck, ears—wet kisses, whispers, and intimate affirmations no man had ever given her. Rayeanna maintained deep eye contact as if she was looking for something to return. “Such pretty eyes,” Rayeanna would say, coaxing what was left of the lost woman back to reality.

Meredith thought she saw a faint glow from her eyes, but she didn't question it. Whatever happens to her now, she accepts it. “That's it,” Rayeanna purred, leaning down to capture Meredith's lips in a deep, sensual kiss. “Let go for me, baby. Let me take care of you.”

Meredith melted into the kiss, hands coming up to tangle in Rayeanna's thick curls. She could taste herself on Rayeanna's tongue as they plundered each other's mouths, all wet heat and sliding tongues.

When Rayeanna finally pulled back, Meredith was panting harshly, hips undulating against her friend's touch. “Please,” she whined, eyes dark with lust and desperation. “I need...”

“I know what you need.” Rayeanna's voice was husky as she guided Meredith onto her back. She settled between her legs, spreading them wide open to the heated gaze of multiple screens.

Meredith watched through half-lidded eyes as Rayeanna lowered her head and dragged her tongue through the weeping slit. She cried out, fingers fisting in Rayeanna's hair as that wicked mouth set to work on her aching pussy.

Lips and teeth and tongue all worshiping Meredith's sex with single-minded focus. Lapping up the sweet nectar, suckling on her swollen clit until she was bucking mindlessly into Rayeanna's face. The obscene sounds of suckling and slurping filled the room, mingling with the pornographic cries echoing from the screens.

Meredith could feel her orgasm building fast, coiling tighter and tighter in her core. Her thighs began to tremble around Rayeanna's head as she teetered on the edge of oblivion.

“Rayeanna!” she keened, voice breaking on a sob. “I'm...I'm gonna...”

Two thick fingers pushed deep inside just as Rayeanna sealed her lips around Meredith's clit and sucked hard. The dual stimulation sent Meredith careening over the edge with a scream of ecstasy. Her pussy clenched rhythmically on Rayeanna's fingers as wave after wave of mind-numbing pleasure crashed through her.

Through it all, Rayeanna never let up. She lapped and suckled through every spasm, extending Meredith's high until she was a boneless puddle on the floor. Only then did she release Meredith's sex with one final kiss to her sensitive flesh.

Meredith lay there gasping for breath as Rayeanna crawled up her body. She could feel the heat of Rayeanna's breasts pressing against hers, the delicious weight of her body blanketing her own as they lay there on the floor.

“That was...incredible,” Meredith managed to get out between panting breaths. “I haven't come like that in so long.”

“Shh, rest now, baby.” Rayeanna pressed a tender kiss to Meredith's forehead before settling beside her on the floor. She gathered Meredith close, cradling her against her full breasts.

Meredith nuzzled into Rayeanna's warmth, feeling safe and sated in a way she hadn't since before the exorcism. Her fingers trailed lazily over the smooth skin of Rayeanna's back as she listened to the steady thrum of her heartbeat.

Slowly, Meredith felt the fog of lust begin to lift from her mind. The constant background hum of arousal that had plagued her for so long was fading away, replaced by a sense of peace and clarity. She could feel herself coming back to herself in Rayeanna's embrace.

“Thank you,” she whispered, pressing a soft kiss to Rayeanna's neck. “For everything. I don't know what I would have done if you hadn't been there for me.”

Rayeanna hummed, carding her fingers through Meredith's tangled hair in a soothing rhythm. “I'll always be here for you, baby. You never have to face this alone again.”

They lay like that for a long time, wrapped up in each other as the pornographic scenes played out around them. Rayeanna looked around the room now that it was free of darkness. The carefully placed screens, curated clips, even the fact that not one white body was to be found. It was something to marvel at. “I'm really impressed, Meredith. You have built something great. You understand us even though you have never met us until today.”

Meredith's eyes welled up with tears and she sobbed. All she wanted was to be validated and seen. Not feared. All she wanted were real friends, not platonic connections. Her life outside of porn had just been a shell. A performance. A means to an end. Tonight was a real connection. Rayeanna could feel the pain and hurt well up from Meredith. She just patted her head and held her close. Meredith's sobs subsided and she slowly drifted off to sleep.

Rayeanna had broken through the fog of obsession and spiritual possession. She brought Meredith back from the brink of sudden death. Rayeanna watched porn as Meredith drifted off to sleep. She acknowledged her own wetness and arousal, but her guardian instinct was still on point.

After a few hours of watching all the screens, Rayeanna was convinced there was no danger and texted her silent witness, “The deed is done. All is well.” She gently woke Meredith and said, “Hey, let's take a shower and go to bed.”

Meredith blinked slowly as she came back to awareness, Rayeanna's gentle voice and the soft feel of her hand on her arm grounding her in reality once more. The last thing she remembered was being consumed by ecstasy as Rayeanna worshipped between her legs with lips and tongue and fingers. Now here they were again, naked bodies entwined amidst the detritus of Meredith's porn shrine.

She looked up at Rayeanna through heavy-lidded eyes, still hazy from pleasure but feeling more lucid than she had in weeks. The golden goddess smiled down at her with tenderness and warmth, eyes shining with affection that made Meredith's heart flutter in her chest.

“Shower?” she echoed softly, voice hoarse from crying and screaming and moaning. “That...that sounds perfect.”

Rayeanna helped her to her feet, supporting her weight as she stumbled slightly on weak legs. Meredith leaned into the taller woman's embrace, marveling at the softness of her skin against hers. She felt safe in Rayeanna's arms, cherished and protected in a way she hadn't since before everything went wrong.

Hand in hand, they made their way to the bathroom, Meredith admiring the sway of Rayeanna's full breasts and round hips as she walked ahead of her. The scent of coconut still clung to her skin, making Meredith's mouth water with memories of how it tasted on her tongue.

In the shower stall, they stood close together beneath the warm spray, bodies slick with steam and sweat and residual arousal. Rayeanna reached for the soap, lathering up between Meredith's breasts as she kissed along the column of her throat.

“Let me take care of you,” she purred against Meredith's skin, voice low and rough with desire. “I want to make you feel good, baby, in every way.”

Meredith shivered at Rayeanna's touch and words, a needy whimper escaping her lips as she arched into the taller woman's embrace. Her hands roamed over Rayeanna's curves reverently, mapping out the shape of her, committing every dip and swell to memory.

“Please,” she breathed, turning in Rayeanna's arms to press back against her chest. “I need you so bad...”

Rayeanna groaned at the feeling of Meredith's slick heat pressing back against her, hands sliding down to grip her hips possessively. She rocked forward, grinding her pelvis against Meredith's ass as she nipped and sucked along the elegant line of her neck.

“Fuck, baby, you feel so good,” she growled, one hand dipping between Meredith's thighs to cup her sex. “I could just bend you over right here...”

Meredith cried out at Rayeanna's touch, hips bucking back desperately as needy fingers teased through slick folds. She braced herself against the shower wall, head tipped back against Rayeanna's shoulder as she worked her into a mindless haze of pleasure once more.

It didn't take long before Meredith was shaking and trembling in Rayeanna's arms, clinging to her like a lifeline as orgasm crashed through her. She came with a ragged scream that echoed off the tile walls, hips jerking spasmodically as wave after wave of ecstasy consumed her.

Rayeanna held her close through it all, fingers working her through the aftershocks until she collapsed bonelessly against her. They stayed like that for a long moment, bodies tangled together under the shower spray as they caught their breath.

Finally, Rayeanna turned Meredith in her arms, cupping her face and tilting it up to meet her gaze. Her eyes were dark with lust and tenderness, full of promises she didn't have to speak out loud.

The two naked women dried their bodies and Meredith led Rayeanna to the bed. Smiling and safe and clean, Meredith drifted off to sleep holding Rayeanna's hand.

Shortly after, the gifted sage drifted off to sleep, another soul saved from the darkness once again. As if on cue, her secret monitor and silent sentry pinged her phone. “I'll bring breakfast. Sweet dreams.”

I have no discernible reason for it, but I have always loved Saint John the Evangelist. Since childhood he has been my favorite apostle, and his gospel among my favorite books of the Bible (Revelation, sometimes purported to be written by him, is my absolute favorite, if you must know). I used to have these thoughts that maybe I was related to him in some way (I was in second grade and a very strange child). I think it’s because he was spoken of as Jesus’ closest friend and I wanted to be that too.

Saint John, according to both the Bible and the tradition that helps us understand it, was one of two brothers who were fisherman, working for their dad, Zebedee. His brother James and he were part of Jesus’ inner circle, which also included Saint Peter. If memory serves, they were among the first five disciples called by Jesus (Andrew and Nathaniel being the others). Among the famous stories involving John is one where he wants to call thunder and lightning down on Jesus’ opponents—which Jesus dismisses—and granting him and James the nickname “the Sons of Thunder.”

If you subscribe to the view that the gospel of John was written by this Saint John (and given that our feast day is called “the Feast of Saint John the Evangelist,” Episcopal tradition does hold to this view, despite the long-standing controversy around that gospel’s authorship), then you’ll know that John was the one entrusted to care for Mary, Jesus’ mother, after the crucifixion and that he was privy to some elements of Jesus’ life that other evangelists were not (further, since we don’t actually know where the quotes in John 3 end, John may have been the one to pen the words of the most famous verse of the Bible—John 3:16—despite most “red letter” Bibles treating them as Jesus’ words).

John’s gospel has long stood out among the other four canonical gospels.

The other three gospels are called the “Synoptics” and contain a lot of overlapping material, whereas John has a lot of unique material as well as stories told in different orders (Jesus cleanses the temple in Jerusalem at the very beginning of His ministry, rather than near His arrest, for instance; John also includes the foot-washing but not the institution of the Eucharist at the last supper). Why is this? Well, scholars have their ideas (of course), but the longer tradition of the Church has held that John penned his gospel while he was in exile.

See, John was the only apostle to not be martyred. This was not for lack of trying. My church growing up had this weird poster in the library that showed how all the apostles were martyred. I used to look at John’s story all the time: he was stoned to death, but survived; he was thrown in boiling oil, but came out unscathed; since the dude could not be killed, the authorities exiled him to an island called Patmos, where he managed to keep on living and grew old; the authorities eventually just gave up on the old man and let him back into Asia Minor where he lived until his 90s and then died of old age.

The tradition holds that it was during those years of exile that he wrote. He wrote three letters, and a gospel, and then recorded the holy visions he had and mailed them to the churches he’d overseen (the visions collected into a volume the author himself called the Revelation of Jesus Christ—or, “Apocalypse” in his own language). This view helps explain why John is so different from the Synoptics. He had the other gospels and wanted to fill in blanks, or shift events around to help the Church see things from a different perspective (remember, ancient histories were not as concerned with what today think of as “accuracy”). Further, he had a lifetime of prayer and reflection under his belt and so wrote the most extensive theology about Jesus being God that had been written by that point (found in the first chapter of his gospel).

As I mentioned in yesterday’s post about Saint Stephen, a key theme of the days between Christmas and the feast of the Holy Name is suffering. Stephensmas and Johnsmas (I have no idea if that’s an accurate term) provide a degree of juxtaposition: we have one of the shortest saint’s lives held alongside one of the longest. Both are equally dedicated in their faith, articulate in their view of who Jesus is.

John also teaches us a way to see turmoil as a blessing. Patmos was supposed to be a place of agony and slow death. Instead, John saw it as a chance to reflect, pray, and record. He was likely the last living person who’d actually seen Jesus with his own eyes. He wanted to give the world a deeper view of Jesus—the Jesus he knew, the Jesus he loved.

Saint John spent a lifetime seeing the horrors of humanity. He stood at the foot of Jesus’ cross, after having witnessed Him being scourged. He lived through the violent deaths of his closest friends, all monstrously killed because of their faith in Jesus, His forgiveness of sins, and His promise of resurrection. He also saw that things were going to get worse. He saw the writing on the wall, as it were (to employ language from another apocalyptic figure). But on the other side of that, he saw that God’s love stands victorious. A day is coming, he writes, where “mourning, crying, and pain are no more.” A day where all things have been made as though they are new.

John reminds us that the Incarnation never ended. That God has made His home with us and that, in the end, the day will come where we will see that fact plainly:

Then the angel showed me the river of life-giving water, shining like crystal, flowing from the throne of God and the Lamb through the middle of the city’s main street. On each side of the river is the tree of life, which produces twelve crops of fruit, bearing its fruit each month. The tree’s leaves are for the healing of the nations. There will no longer be any curse. The throne of God and the Lamb will be in it, and his servants will worship him. They will see his face, and his name will be on their foreheads. Night will be no more. They won’t need the light of a lamp or the light of the sun, for the Lord God will shine on them, and they will rule forever and always.

Then he said to me, “These words are trustworthy and true. The Lord, the God of the spirits of the prophets, sent his angel to show his servants what must soon take place. (Revelation 22:1-7 CEB)

***

The Rev. Charles Browning II is the rector of Saint Mary’s Episcopal Church in Honolulu, Hawai’i. He is a husband, father, surfer, and frequent over-thinker. Follow him on Mastodon and Pixelfed.

Mélusath est le troisième roman appartenant au cycle romanesque Le Rêve du Démiurge de Francis Berthelot.

Si les deux premiers romans appartenaient à la littérature blanche et pouvaient sembler indépendants l'un de l'autre, celui-ci introduit une touche plus fantastique et commence à relier les romans les uns aux autres. Ainsi, on retrouve dans Mélusath des personnages déjà présents dans Le jongleur interrompu et surtout dans L'ombre d'un soldat. La fresque commence doucement à prendre forme.

Le récit se déroule dans le milieu du théâtre parisien, en 1970. Le Théâtre du Dragon est en difficulté, accumulant les échecs critiques et publics. La prochaine pièce, inspirée du mythe grec des Atrides, pourrait être la dernière.

On suit plus particulièrement trois personnages : Wilfried, le directeur allemand du théâtre et metteur en scène allemand ; Katri, l'actrice principale dont l'âge l'oblige à un tournant dans sa carrière ; Gus, un peintre et décorateur qui a perdu la mémoire.

Francis Berthelot offre à nouveau un très joli roman, tragique et puissant. Si tout le cycle est au niveau des trois premiers romans, cela promet de grandes choses !

Le jongleur interrompu est le deuxième roman appartenant au cycle romanesque Le Rêve du Démiurge de Francis Berthelot.

Le récit se déroule dans un port de pêche du Finistère, au milieu des années 1960. Un cirque arrive et s'installe quelques jours, mené par un jongleur malade qui rêve de voir une île mythique située au large de ce village côtier avant de mourir. Il se lie avec un adolescent épileptique qui vit isolé, détesté par son grand-père et traité comme l'idiot du village.

Francis Berthelot a décidément une très jolie plume, capable en quelques pages de décrire un décor et des personnages comme le ferait un peintre. Si j'ai peut-être été légèrement moins sensible à ce récit qu'à celui de L'ombre d'un soldat, j'ai malgré tout trouvé très bon ce roman envoutant.

Le Rêve du Démiurge est un cycle romanesque de Francis Berthelot, composé de neuf romans publiés en l'espace d'une vingtaine d'années, entre le milieu des années 1990 et celui des années 2010. Il a pour particularité de commencer en littérature blanche avant de basculer clairement dans le fantastique.

L'ombre d'un soldat est le premier roman de ce cycle. Il nous plonge dans l'enfance et l'adolescence d'Olivier, dans une petite ville de la France des années 1950. La ville est tiraillée par des secrets et des rancoeurs, l'ombre de la guerre est encore très présente.

Cette ambiance est parfaitement rendue par Francis Berthelot, qui nous permet de suivre les pas d'Olivier, un héros tourmenté par le silence et les non-dits. Son père était prisonnier de guerre en Autriche, et sa mère a été tondue à la libération après avoir eu une relation avec un soldat allemand. Tout cela, Olivier l'ignore d'abord mais le devine.

Le roman est court mais je l'ai trouvé absolument sublime. Son héros n'est pas parfait mais parfaitement humain, aussi tourmenté que la France d'après-guerre.

There are chapters in Scripture that feel like grand mountain peaks, where doctrines rise high and sweeping visions stretch as far as the eye can see. And then there are chapters like Colossians 4, which feel more like the walk home after the sermon has ended, when the music has faded, the sanctuary lights have dimmed, and you are left alone with the question that matters most: how do I actually live this out tomorrow? This chapter does not shout. It leans in close. It does not announce a new theological universe. It hands you a set of keys and says, “Now go unlock the ordinary.”

Colossians 4 is where belief becomes behavior, where cosmic Christology meets kitchen-table Christianity, where eternal truth is pressed into the shape of daily speech, relationships, pressure, opposition, and fatigue. If Colossians has taught us who Christ is, this final chapter teaches us how a Christ-shaped life sounds, looks, and moves in the real world. It is the chapter for people who already believe but are trying to endure. It is the chapter for those who know the gospel is true but are still learning how to carry it without dropping it in the mess of everyday life.

The danger with Colossians 4 is that we read it too quickly. It feels like closing instructions. A few exhortations. A few greetings. A polite goodbye. But that is precisely where we miss its power. This chapter is not an appendix. It is an audit. It asks whether the truth you say you believe has reached your mouth, your time, your tone, your relationships, and your resilience. It asks whether Christ reigns only in your theology or also in your conversations, your patience, your prayers, and your posture toward people who do not believe what you believe.

Paul begins this final movement not with grand statements about heaven but with something far more revealing: prayer. Not flashy prayer. Not impressive prayer. Persistent prayer. He does not say, “Pray occasionally when you feel inspired.” He says, “Continue steadfastly in prayer, being watchful in it with thanksgiving.” That word steadfastly carries weight. It implies effort. It implies resistance. It implies that prayer is something that will be challenged, crowded, interrupted, and resisted by life itself. Paul assumes that prayer will be difficult, not because God is distant, but because the world is loud.

To continue in prayer is not to live in constant religious language. It is to refuse to let urgency replace dependence. It is to resist the temptation to believe that productivity can substitute for presence. Paul knows that the Colossian believers, like us, will be tempted to move faster than their faith can carry. So he anchors them in something slower, deeper, and more durable. Prayer is not presented as a spiritual luxury. It is presented as a survival practice.

But notice how Paul qualifies this prayer. He pairs watchfulness with thanksgiving. That combination matters. Watchfulness without gratitude turns into anxiety. Gratitude without watchfulness turns into complacency. Paul is teaching them how to remain spiritually awake without becoming spiritually brittle. Watchfulness means awareness, discernment, attentiveness to what is happening in and around you. Thanksgiving means grounding that awareness in trust rather than fear. Together, they form a posture that can endure uncertainty without losing peace.

This matters because Colossians 4 is written to people living in tension. They are not insulated believers. They are a minority community surrounded by competing worldviews, social pressure, and spiritual confusion. Paul knows that their greatest threat is not persecution alone, but distraction. Not heresy alone, but exhaustion. Not opposition alone, but silence. And silence is where faith quietly erodes.

Then Paul does something striking. He asks for prayer for himself. This is not false humility. This is leadership realism. He asks them to pray that God would open a door for the word, to declare the mystery of Christ clearly, as he ought to speak. This is Paul, the apostle, the theologian, the missionary, asking for prayer not for safety, comfort, or relief, but for clarity. He knows that the hardest thing in ministry is not finding opportunities, but stewarding them well. Not having words, but speaking the right ones in the right way at the right time.

There is something deeply grounding here for anyone who feels pressure to perform spiritually. Paul does not present himself as spiritually self-sufficient. He presents himself as dependent, vulnerable, and aware of his limits. He understands that clarity is not automatic, even for those called by God. It is cultivated through prayer, community, and humility.

Then the chapter turns outward, toward those outside the faith. “Walk in wisdom toward outsiders, making the best use of the time.” This is not a call to isolation or aggression. It is a call to attentiveness. Paul is telling believers that how they move through the world matters. Their timing matters. Their awareness matters. Their conduct is not neutral. It is communicative.

This is where many Christians struggle. We want to be bold, but we forget to be wise. We want to be truthful, but we neglect to be thoughtful. Paul does not separate conviction from consideration. He binds them together. Wisdom toward outsiders means understanding that people are watching not just what you believe, but how you believe it. They are listening not only to your arguments, but to your tone. They are reading not only your words, but your patience, restraint, and respect.

Paul then narrows the focus even further, landing on something we often underestimate: speech. “Let your speech always be gracious, seasoned with salt, so that you may know how you ought to answer each person.” This is not about being nice. It is about being intentional. Grace in speech does not mean avoiding truth. It means delivering truth in a way that can be received. Salt does not overpower a meal. It enhances it. It draws out what is already there. Paul is teaching believers to speak in ways that preserve, clarify, and invite rather than corrode, confuse, or repel.

This is one of the most demanding commands in the chapter because speech is where pressure leaks out. We can manage our actions for a while, but our words reveal our inner state quickly. Fatigue shows up in sarcasm. Fear shows up in defensiveness. Pride shows up in harshness. Paul knows this. That is why he does not tell believers to be clever in speech, but to be gracious. Cleverness impresses. Grace connects.

Notice also that Paul says you should know how to answer each person. This means there is no single script. No universal response. No copy-and-paste gospel conversation. People are not problems to solve; they are stories to enter. Wisdom requires listening before speaking, understanding before answering, presence before proclamation. Paul’s vision of evangelism is not loud. It is attentive.

After laying out these foundational practices of prayer, conduct, and speech, Paul shifts into what many readers treat as throwaway material: names. Greetings. Personal updates. But this section may be the most revealing of all. Paul does not end Colossians with abstract theology. He ends it with people. Because the gospel does not move through ideas alone. It moves through relationships.

Paul names coworkers, messengers, companions, and supporters. He highlights faithfulness, perseverance, and presence. He acknowledges those who have stayed, those who have struggled, those who have been restored, and those who continue quietly serving behind the scenes. This is not filler. This is formation. Paul is showing the Colossians what a gospel-shaped community actually looks like.

There is no celebrity culture here. No spiritual hierarchy. No competition for prominence. Paul speaks of people not as brands, but as brothers. Not as tools, but as partners. He honors their labor without inflating their ego. He acknowledges their humanity without diminishing their calling. This is leadership without domination, authority without arrogance.

This section also quietly dismantles the myth of solitary faithfulness. Paul is in prison, but he is not alone. The gospel has bound people together across geography, ethnicity, background, and failure. Even those who once abandoned him are mentioned without bitterness. The gospel has done something deeper than create agreement. It has created endurance.

As Colossians 4 unfolds, you begin to see the shape of mature faith. It is not dramatic. It is durable. It does not draw attention to itself. It directs attention outward. It prays persistently, speaks thoughtfully, walks wisely, and values people deeply. It understands that faithfulness is not proven in moments of intensity, but in patterns of consistency.

This chapter is especially relevant for those who feel spiritually tired. It does not ask you to do more. It asks you to do what you are already doing, but with greater awareness of Christ’s presence in it. It does not demand perfection. It calls for intention. It does not promise ease. It offers endurance.

Colossians 4 reminds us that the Christian life is not lived in dramatic leaps, but in faithful steps. It is not sustained by constant inspiration, but by steady practices. It is not measured by how loudly we speak, but by how faithfully we live. And perhaps most importantly, it teaches us that the final proof of belief is not found in what we claim to know, but in how we relate, respond, and remain.

This is not the ending of a letter. It is the beginning of a way of life.

One of the quiet strengths of Colossians 4 is that it refuses to let faith remain abstract. It insists that belief must descend into habit, and habit into posture. By the time Paul reaches the end of this letter, he is no longer explaining who Christ is; he is revealing what Christ produces in ordinary people who take Him seriously. The chapter reads less like a conclusion and more like a mirror, reflecting back to the reader the kind of life that naturally grows where Christ is genuinely central.

It is important to notice that Paul never separates spiritual maturity from emotional maturity. This is one of the great correctives of Colossians 4. Many believers grow theologically sharper while becoming relationally dull. They know more, argue better, quote faster, but listen less. Paul refuses to let that imbalance stand. He repeatedly ties faith to restraint, insight, patience, and discernment. Wisdom, in this chapter, is not measured by volume or certainty, but by timing, tone, and care.

The phrase “making the best use of the time” deserves deeper reflection. Paul is not speaking about efficiency in the modern sense. He is speaking about stewardship. Time is not merely something to manage; it is something to honor. Every interaction is an opportunity that will not repeat itself in the same way again. Every conversation carries weight, even if it feels casual. Paul understands that people rarely remember everything we say, but they remember how we made them feel when we said it. Wise use of time means recognizing that moments are sacred because people are.

This perspective reshapes how we think about everyday encounters. The grocery store line, the email exchange, the strained family conversation, the unexpected interruption—none of these are neutral. They are not obstacles to spiritual life; they are the context in which spiritual life proves itself. Colossians 4 quietly insists that faith is not primarily demonstrated in worship gatherings, but in unplanned moments where patience is tested and character is revealed.

Paul’s emphasis on speech being “seasoned with salt” also pushes against extremes. Some believers become sharp without becoming helpful. Others become agreeable without becoming truthful. Salt, in the ancient world, preserved food from decay. It did not rot what it touched; it protected it. Speech shaped by Christ should slow decay, not accelerate it. It should prevent conversations from spoiling into hostility, cynicism, or despair. This does not mean avoiding hard truths. It means delivering them with care for the person receiving them, not just satisfaction in saying them.

Paul’s insistence that believers “know how to answer each person” subtly dismantles one-size-fits-all spirituality. Faithfulness requires attentiveness. It requires noticing who is in front of you, what season they are in, and what they are actually asking beneath their words. Wisdom is not about having answers ready; it is about being present enough to discern which answer, if any, is needed at all.

This has profound implications for how Christians engage a fractured, polarized world. Colossians 4 does not call believers to withdraw, nor does it call them to dominate. It calls them to inhabit the world with awareness, humility, and intention. The goal is not to win arguments, but to bear witness. Not to control outcomes, but to remain faithful. Paul’s vision of Christian influence is relational before it is rhetorical.

As the chapter moves into personal greetings, something else becomes clear: the gospel produces loyalty. Not blind loyalty to a leader, but deep loyalty to one another. Paul names people who have labored, suffered, failed, returned, and continued. The absence of bitterness in these acknowledgments is striking. There is no scorekeeping here. No public shaming. No subtle distancing from those who once disappointed him. Paul’s confidence is not in human consistency, but in God’s ability to restore usefulness.

This matters deeply for believers who feel ashamed of past missteps. Colossians 4 reminds us that failure is not the end of faithfulness. Restoration is possible. Contribution can resume. The gospel does not erase consequences, but it does redeem stories. Paul models a community that does not discard people at the first sign of weakness. That alone is a radical witness in a culture that often cancels rather than redeems.

Another often-overlooked feature of this chapter is its emphasis on unseen labor. Many of the people Paul names are not famous, not central, not celebrated. They carry messages. They encourage churches. They pray quietly. They remain present. Their work is not dramatic, but it is indispensable. Paul honors them without embellishment. This is a subtle rebuke to a culture obsessed with visibility. Faithfulness, in Colossians 4, is not measured by platform, but by perseverance.

This chapter also exposes a misconception about spiritual growth: that it is always upward and outward. Colossians 4 suggests that growth is often inward and stabilizing. It is learning to speak less impulsively, pray more persistently, listen more carefully, and endure more quietly. It is learning when to act and when to wait. When to speak and when to remain silent. When to push forward and when to remain steady.

Paul’s closing instruction to have the letter read publicly, and to exchange letters with other churches, reinforces the communal nature of faith. Christianity is not a private possession. It is a shared inheritance. Insight deepens when it is circulated. Faith strengthens when it is practiced together. Isolation, even when spiritually motivated, weakens discernment. Paul wants the Colossians to hear truth together, wrestle with it together, and live it together.

The final line of the letter—Paul’s personal signature and reminder of his imprisonment—grounds everything that came before it. These are not theoretical teachings. They are forged in chains. Paul does not speak as an observer, but as a participant. His call to endurance is credible because he is enduring. His call to prayer is authentic because he is dependent. His call to wisdom is grounded because he has learned it through suffering.

Colossians 4 leaves us with a quiet but demanding question: does the way we live make the gospel believable? Not impressive. Believable. Does our prayer reflect trust or panic? Does our speech invite understanding or provoke resistance? Does our conduct signal wisdom or reactivity? Does our community reflect grace or performance?

This chapter does not allow faith to hide behind doctrine alone. It brings belief into the light of daily life and asks whether Christ has reached the places where we are most ourselves—our habits, our words, our relationships, our responses under pressure. And it does so not with condemnation, but with clarity.

Colossians 4 is not a call to do extraordinary things. It is a call to do ordinary things faithfully, attentively, and with Christ at the center. It reminds us that the gospel advances not only through bold proclamations, but through steady lives. Through prayer that continues when answers delay. Through speech that remains gracious when patience wears thin. Through presence that endures when recognition never comes.

In a world that rewards speed, noise, and certainty, Colossians 4 calls us back to depth, wisdom, and faithfulness. It teaches us that the final chapter is not about closure, but about continuation. The letter ends, but the life it describes begins again tomorrow—in our conversations, our decisions, our endurance, and our quiet obedience.

And perhaps that is its greatest gift. It does not leave us inspired and unsure what to do next. It leaves us grounded, steady, and clear about what faith looks like when the page turns and real life resumes.

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

Support the ministry by buying Douglas a coffee https://www.buymeacoffee.com/douglasvandergraph

Your friend, Douglas Vandergraph

#Colossians #FaithInAction #ChristianLiving #BiblicalWisdom #SpiritualGrowth #ChristianReflection #EnduringFaith #ChristianEncouragement

There are chapters in Scripture that don’t just ask to be read, but ask to be lived slowly, quietly, and honestly. Colossians 3 is one of those chapters. It does not shout. It does not argue. It does not try to win debates or impress crowds. Instead, it speaks directly into the unseen spaces of a person’s life—the places where habits form, where motivations are born, where character is either strengthened or quietly compromised. This chapter is not concerned with how faith looks on the outside as much as it is with what faith does on the inside when no one else is watching.

Colossians 3 opens with a statement that sounds simple but is anything but: “If then you have been raised with Christ, seek the things that are above.” Paul is not offering a suggestion here. He is stating a reality and then drawing a conclusion from it. If you have been raised with Christ, then your orientation in life has changed. Not theoretically. Not symbolically. But fundamentally. Something about how you aim your thoughts, your desires, and your daily choices is now different because your life is anchored somewhere else.

This is where many modern believers struggle, often without realizing it. We tend to treat salvation as a destination rather than a transformation. We think of it as something that secures our future while leaving our present mostly untouched. Colossians 3 refuses to allow that separation. Paul insists that resurrection life is not only about where you go after death, but about how you live before it. If your life is “hidden with Christ in God,” then your priorities, your reactions, and your internal compass must begin to reflect that hidden reality.

The phrase “hidden with Christ” is deeply important. Hidden does not mean absent. It does not mean invisible in the sense of being irrelevant. It means that the truest version of who you are is not fully on display yet. In a culture obsessed with visibility, exposure, and self-promotion, this idea runs directly against the grain. We are trained to believe that what matters most must be seen, validated, and affirmed publicly. Paul suggests the opposite. He says the real work of faith is happening beneath the surface, where applause cannot reach.

When Paul tells believers to “set your minds on things above, not on things that are on earth,” he is not encouraging escapism. He is not telling people to disengage from responsibilities, relationships, or the realities of daily life. He is teaching alignment. Your mind determines what you interpret as valuable, threatening, or worth pursuing. When your mind is anchored to temporary things, your emotional life becomes reactive and unstable. When your mind is anchored to eternal things, your inner life gains a steadiness that circumstances cannot easily shake.

This is why Colossians 3 moves so quickly from identity to behavior. Paul does not say, “Behave better so you can become someone new.” He says, “You have become someone new, so stop living like someone you no longer are.” This distinction matters more than many realize. Moral effort without identity leads to exhaustion and hypocrisy. Identity without transformation leads to complacency and self-deception. Paul insists on both: a new identity that produces a new way of life.

The language he uses is intentionally strong. “Put to death therefore what is earthly in you.” That is not gentle phrasing. Paul is not asking believers to negotiate with sin or manage it more effectively. He is calling for decisive separation. The list that follows—sexual immorality, impurity, passion, evil desire, and covetousness—addresses impulses that often feel deeply personal and private. These are not just actions; they are desires. Paul understands that transformation does not begin with external behavior alone. It begins with what we allow to take root in our inner life.

Covetousness is especially revealing, because Paul calls it idolatry. That connection often surprises people. Covetousness feels normal in a consumer-driven society. We are constantly encouraged to want more, be more, and compare ourselves to others. But Paul exposes covetousness as a spiritual issue, not a cultural one. When desire becomes unrestrained by gratitude and contentment, it quietly replaces God as the center of trust and satisfaction. Idolatry does not always look like worshiping statues. Sometimes it looks like constantly believing that fulfillment is just one more thing away.

Paul then turns to relational sins—anger, wrath, malice, slander, and obscene talk. These are not abstract concepts. They show up in conversations, reactions, and online interactions every single day. What is striking is how Paul treats speech as a spiritual issue. Words are not neutral. They either align with the new life in Christ or they betray allegiance to the old self. When Paul says, “Do not lie to one another,” he roots honesty in identity. Lying is incompatible with a life that has “put off the old self with its practices.”

This idea of “putting off” and “putting on” is one of the most practical metaphors in all of Scripture. Clothing is something we interact with daily. We choose what we wear based on where we are going and who we understand ourselves to be. Paul uses this everyday action to illustrate spiritual transformation. You are not asked to become someone else through sheer effort. You are asked to live consistently with who you already are in Christ.

The “new self,” Paul says, “is being renewed in knowledge after the image of its creator.” Notice that renewal is ongoing. This is not a one-time event. Growth in Christ is not instant perfection; it is steady formation. Knowledge here is not merely information. It is relational understanding—learning to see reality the way God sees it. As that understanding deepens, the believer becomes more aligned with the image of Christ, not by force, but by familiarity.

One of the most radical statements in Colossians 3 comes next: “Here there is not Greek and Jew, circumcised and uncircumcised, barbarian, Scythian, slave, free; but Christ is all, and in all.” Paul is not denying human differences. He is declaring that none of them determine value, access, or belonging in the kingdom of God. In a world that constantly categorizes, ranks, and divides people, this statement remains profoundly disruptive.

Identity in Christ reorders social boundaries. It does not erase individuality, but it redefines worth. Paul is reminding believers that their primary allegiance is no longer to cultural labels or social hierarchies. Christ is the defining center. This truth challenges every attempt to build superiority, resentment, or exclusion within the body of Christ. It also challenges the believer to examine where they have allowed secondary identities to overshadow their primary one.

From here, Paul shifts into a description of what the new self looks like when fully expressed. Compassion, kindness, humility, meekness, and patience are not abstract virtues. They are relational practices. They show up in how people treat one another under pressure. Bearing with one another and forgiving one another are not signs of weakness. They are evidence of spiritual maturity. Forgiveness, Paul reminds them, is not optional. It is patterned after Christ’s forgiveness of them.

Then Paul makes a statement that deserves far more attention than it often receives: “And above all these put on love, which binds everything together in perfect harmony.” Love is not merely one virtue among many. It is the integrating force that gives coherence to all the others. Without love, patience becomes endurance without warmth. Humility becomes self-erasure. Kindness becomes performative. Love holds them together and directs them outward.

Paul then introduces peace as a ruling presence. “Let the peace of Christ rule in your hearts.” The word “rule” here carries the sense of an umpire or arbiter. Peace is not just a feeling; it is a governing force that determines what is allowed to dominate the inner life. When peace rules, anxiety does not get the final word. When peace rules, reactions are measured rather than impulsive. Gratitude naturally follows, because peace reminds the believer that they are already held, already known, already secure.

The chapter continues by emphasizing the role of the word of Christ dwelling richly among believers. This is not about isolated spirituality. It is communal. Teaching, admonishing, singing psalms, hymns, and spiritual songs are all expressions of a shared life shaped by truth and gratitude. Worship is not presented as an event but as a posture that spills into every aspect of life.

Paul then offers one of the most comprehensive summaries of Christian living: “Whatever you do, in word or deed, do everything in the name of the Lord Jesus.” This statement leaves no category untouched. Faith is not confined to religious moments. It permeates work, relationships, decisions, and speech. Doing something “in the name of the Lord Jesus” means acting in alignment with His character, authority, and purposes. It is an invitation to integrity rather than compartmentalization.

As Colossians 3 moves into household relationships—wives and husbands, children and parents, servants and masters—it continues the same theme. Christ-centered identity reshapes power dynamics. Authority is not for domination but for care. Obedience is not blind submission but relational trust within godly order. Every role is reoriented by accountability to Christ. No one operates outside His lordship.

Paul’s instruction to servants to work “as for the Lord and not for men” has particular relevance in a world where work is often reduced to productivity and recognition. Paul reframes work as worship. Effort becomes meaningful not because it is noticed by others, but because it is offered to God. This perspective liberates the believer from needing constant validation while also calling them to excellence and integrity.

The chapter closes with a reminder that God shows no partiality. This is both comforting and sobering. Comforting because no one is overlooked or marginalized in His sight. Sobering because no one is exempt from accountability. Identity in Christ brings dignity, but it also brings responsibility. Grace does not excuse injustice or negligence; it transforms motivation.

Colossians 3 does not offer a checklist. It offers a vision of a life reordered around Christ. It speaks to a generation overwhelmed by noise, comparison, and performance. It calls believers back to something quieter, deeper, and far more demanding: a hidden life that steadily reshapes everything visible.

This chapter reminds us that the most powerful testimony is not always the loudest one. It is the person whose inner life is so anchored in Christ that their outward life begins to reflect a different rhythm, a different posture, a different hope. In a world chasing visibility, Colossians 3 invites us to embrace faithfulness. In a culture obsessed with image, it calls us back to substance. In an age of constant reaction, it teaches us how to live from resurrection rather than from anxiety.

This is not an easy chapter to live. But it is a necessary one. Because when heaven touches the ordinary, everything changes—not all at once, but steadily, faithfully, and for good.

Colossians 3 does something that modern spirituality often avoids: it refuses to separate faith from emotional health, daily work, and ordinary relationships. It does not treat belief as a private mental agreement or a weekly ritual. It treats belief as a re-centering of the entire self. That is why this chapter continues to feel unsettling when read slowly. It presses into areas where we are often most defensive—how we react, how we speak, how we work, and how we handle power, disappointment, and desire.

One of the most overlooked dimensions of Colossians 3 is its quiet impact on emotional life. Paul never uses modern psychological language, yet he addresses emotional regulation with remarkable clarity. When he speaks about anger, wrath, malice, and slander, he is not simply condemning behavior. He is identifying emotional patterns that corrode both the individual and the community. These emotions are not sinful merely because they feel intense. They become destructive when they rule unchecked, when they define identity, and when they shape how others are treated.

Paul’s solution is not emotional suppression. He does not say, “Stop feeling.” He says, in effect, “Stop letting old emotions govern a new life.” When the peace of Christ is allowed to rule the heart, emotions are no longer dictators. They become signals rather than masters. This is profoundly relevant in a world where emotional authenticity is often confused with emotional authority. Colossians 3 offers a different path—one where emotions are acknowledged but submitted to a deeper truth.

This reordering of the inner life is what gives believers resilience. When identity is hidden with Christ, it is not as vulnerable to public approval or rejection. Praise does not inflate the ego as easily, and criticism does not crush the soul as completely. The believer begins to operate from security rather than striving. This does not eliminate pain, disappointment, or grief, but it changes how those experiences are processed. They are no longer interpreted as threats to worth but as moments that must be navigated with Christ at the center.

Colossians 3 also reshapes how believers understand success. In a performance-driven culture, worth is often measured by visibility, productivity, and achievement. Paul quietly dismantles this framework by grounding value in being “chosen, holy, and beloved.” Notice that these descriptors come before any instruction about behavior. They are not rewards for obedience; they are the foundation of obedience. When people know they are already loved, they no longer need to prove themselves through endless comparison or overwork.

This has direct implications for how work is approached. When Paul tells believers to work heartily “as for the Lord,” he is not sanctifying exploitation or unhealthy work environments. He is reframing motivation. Work becomes an offering rather than a performance. Excellence becomes an act of worship rather than a strategy for validation. This perspective does something subtle but powerful: it frees the believer from being controlled by outcomes while still calling them to diligence and integrity.

In practical terms, this means a person can work faithfully without being consumed by ambition, and they can endure unnoticed seasons without bitterness. Their identity is not tied to titles, recognition, or external success. It is anchored elsewhere. This does not make work meaningless; it makes it honest. The believer can show up fully without believing that their soul depends on the results.

Relationships are another area where Colossians 3 brings both comfort and challenge. Paul’s emphasis on forgiveness is not sentimental. Forgiveness, in this chapter, is not about excusing harm or pretending wounds do not exist. It is about refusing to let resentment become a permanent resident in the heart. Paul roots forgiveness in imitation of Christ. “As the Lord has forgiven you, so you also must forgive.” That statement carries weight precisely because Christ’s forgiveness was costly, deliberate, and undeserved.

Forgiveness, as described here, is not a denial of justice. It is a decision about who controls the future of the relationship—resentment or grace. This does not mean all relationships must be restored to their previous form. Colossians 3 does not demand proximity at the expense of wisdom. It demands freedom at the expense of vengeance. That distinction matters deeply for those navigating fractured families, church wounds, or long-standing conflicts.

The emphasis on love as the binding force is particularly relevant in an era of polarization. Paul does not suggest that unity is achieved by ignoring differences. He suggests that love holds people together despite differences. Love, in this sense, is not agreement; it is commitment. It is the refusal to reduce others to their worst moments or most irritating traits. It is the willingness to bear with one another in a way that reflects patience rather than superiority.

Colossians 3 also offers a counter-narrative to the modern obsession with self-expression. Paul’s language of “putting off” and “putting on” implies discernment. Not every impulse deserves expression. Not every desire defines identity. Freedom in Christ is not the absence of restraint; it is the presence of purpose. The believer learns to ask not only, “Can I?” but “Does this align with who I am becoming?”

This is especially significant when considering how Paul addresses speech. Words are treated as moral acts, not neutral tools. Slander, lying, and obscene talk are not merely social missteps; they are remnants of the old self. Speech reveals allegiance. What we say under pressure often exposes what we truly believe about others, ourselves, and God. Colossians 3 invites believers to let their speech be shaped by the same renewal that shapes their thoughts.

The communal dimension of the chapter is equally important. Paul does not envision spiritual growth as a solo endeavor. Teaching, admonishing, and worship are shared practices. Gratitude is expressed together. The word of Christ dwells richly “among you,” not merely within isolated individuals. This challenges the hyper-individualism of modern spirituality. Faith is personal, but it is not private. It is formed and sustained in community.

When Paul addresses household relationships, his instructions reflect a radical reorientation of power. In a first-century context where hierarchy was rigid and often abusive, Paul introduces mutual accountability under Christ. Husbands are commanded to love rather than dominate. Fathers are warned against provoking their children. Authority is restrained by responsibility. Obedience is framed within care. While these passages have often been misused, Colossians 3 itself pushes against misuse by placing every role under the lordship of Christ.

This emphasis on accountability culminates in the reminder that God shows no partiality. No one is exempt from His gaze. No role grants moral immunity. This truth levels the field. It affirms dignity while enforcing responsibility. Grace does not erase consequences; it transforms motivation. The believer is called to live with integrity not because they fear rejection, but because they belong.

Perhaps the most enduring gift of Colossians 3 is its insistence that the Christian life is not lived from anxiety but from resurrection. “You have died, and your life is hidden with Christ in God.” That sentence reframes everything. Death to the old self means freedom from its constant demands. Resurrection life means access to a new source of strength. The believer is not endlessly trying to become acceptable. They are learning how to live from what has already been given.

This chapter speaks quietly but persistently into a culture marked by exhaustion. It reminds us that transformation does not come from trying harder but from seeing more clearly. When Christ is the center, everything else finds its place. When Christ is all, and in all, life becomes coherent again—not perfect, not easy, but grounded.

Colossians 3 does not promise a life free of struggle. It promises a life no longer defined by it. It invites believers to step out of reactive living and into intentional faithfulness. It calls for daily decisions that align with an eternal reality. And it assures us that what is hidden now will one day be revealed. The quiet work of becoming will not remain unseen forever.

Until that day, Colossians 3 teaches us how to live between resurrection and revelation—with humility, patience, love, and a peace that rules rather than merely visits. It teaches us how to let heaven touch the ordinary, one faithful choice at a time.

Your friend, Douglas Vandergraph

Watch Douglas Vandergraph’s inspiring faith-based videos on YouTube

Support the ministry by buying Douglas a coffee

#faith #christianliving #biblestudy #colossians #spiritualgrowth #christianencouragement #christianwriter #hope #discipleship