There are rare, powerful moments in life when you feel something shift—not just in your circumstances, but in your soul. The wind that once pushed against you begins to propel you forward. The doors that seemed bolted shut creak open. The people who once doubted you now want to collaborate. The silence turns into applause. It’s not always loud or dramatic. But you feel it: the world is turning towards you.

And it’s not magic. It’s momentum.

---

🌍 The Turning Point Is Often Earned

What feels like a sudden turn is often the result of quiet consistency. Those early mornings, those late nights, those times you kept going when no one was watching—they compound. The world doesn’t just “turn toward” people randomly. It turns toward people who have been turning toward it all along—with curiosity, commitment, and care.

When your values, your vision, and your velocity begin to align, things around you begin to align too. That’s when you see synchronicity instead of resistance. Invitations instead of rejections. Allies instead of obstacles.

---

🧭 It’s Not Just the World—It’s Your Orientation

Sometimes it’s not that the world has shifted—it’s that you have. You’ve grown into someone who can receive what’s been there all along. You’ve done the inner work. You’re no longer shrinking to fit in. You’re taking up space. You’re leading, not chasing. That shift in energy ripples outward. The world responds differently when you show up differently.

---

🚪 What to Do When the World Turns Toward You

1. Say yes—but wisely. Not every open door is the right one. Choose what aligns, not just what’s available.
2. Stay humble. This isn’t the time to coast. Keep learning, keep listening, keep contributing.
3. Lift others. If the light has found you, reflect it onto others. Share the mic. Create room at the table.
4. Build sustainably. Don’t just ride the wave—shape the current. Think long-term.

---

⚖️ Don’t Wait for It—Create It

If you’re still in the season where it feels like the world is turning away from you—keep going. These shifts often arrive disguised as failure, fatigue, or frustration. Keep showing up. Keep getting better. Keep turning toward yourself.

The world has a funny way of catching up to people who do that.

And when it does, when you feel it shift—breathe it in. You’ve earned it.

---

🌀 You’re not lucky the world turned toward you. You’re ready.

I was one of the panelists at SPGI-FINOS Community Networking Panel: Agentic AI – and like all other FINOS events, I really enjoyed presenting about the topic of Agentic AI.

Me representing both a bank and FINOS gave me a rare and powerful dual lens here – to balance the practical enterprise adoption concerns (due to security, scaling, etc) with the open collaboration and interoperability advocacy.

My major core message was, that Agentic AI is not just about autonomous capabilities, it’s about trustworthy delegation in a regulated context. MCP, being the HTTP of AI, gives us a framework for this delegation to be standardized, secure and interoperable, across teams, tools and institutions.

Representing us, a bank, I shared:

• Risk & accountability – Agentic AI has to be traceable, auditable, explainable; cannot be a black box
• Delegation with oversight – Agentic AI always should operate under role based constraints, compliance layers, escalation protocols, just like any junior team member would be
• MCP is the Rosetta Stone for AI behaviors – with it, banks gain the uniform way to describe what agents can do, how they are governed, how they interop, across depts and firms

When I represented FINOS (and I put up a FINOS Ambassador hoodie – I would not go for the neighbor for some theatrics), I spoke about the other angle:

• Avoiding vendor lock in – future of agents cannot be tied to single vendor – FINOS pushing for the open governance, interchangeable agent skills, cross platform compatibility
• MCP enabling financial grade AI agents – just like FDC3 from FINOS standardized inter app comms, MCP standardizes agent governance and orchestration if we do so – opening the door for agent market place, p&p, composable trust and more
• Collaborative dev & shared protocols – banks do not need to reinvent governance wheels in silos, as FINOS do offer sandboxing, and hopefully soon sandbox for shared MCP schemas, safety patterns, audit templates and more: helping the industry move faster together, safer.

I touched some practical example, like:

• Agent skills via manifest saying “this agent can only draft emails, not send them”
• Versioned agent behavior, to track it like we do track code changes
• Cross firm collaboration for example for a KYC agent

I closed it with explaining how Agentic AI is not a product, it’s a new (junior) teammate. MCP helps us ensure that this teammate plays by the rules, explains its decisions, works well with others. Through FINOS, and their https://air-governance-framework.finos.org/ platform, we make sure those rules aren’t just good for one bank, they are good for the whole industry.

I would like to thank Olivier Poupeney for thinking about me and moderating us, Adam Dikker for organizing, Sudeep Kesh for bearing with me on the stage, Ryan Morris for his presentation and demos about S&P Global ‘s AIxtra platform, and Frank Tarsillo ‘s opening remarks.

Ah, the age-old debate: should developers code in the sweltering embrace of summer or the frosty grip of winter? It’s a question as divisive as tabs vs. spaces, dark mode vs. light mode, or whether pineapple belongs on pizza (spoiler: it does, but not on your laptop).

Let’s break it down scientifically.

---

🔥 Hot Weather Devs: The Sweat-Driven Coders

Pros:

• Your fingers move faster because they’re slipping across the keyboard.
• You don’t need a heater — just your CPU at 99% compiling a React build.
• Sunlight might remind you that there’s life beyond GitHub issues.

Cons:

• You can’t tell if your laptop is overheating or if it’s just in empathy mode.
• Your water-cooled PC is now a sauna.
• Coffee turns to iced coffee. Without ice. By itself.

Developer profile: They wear tank tops and shorts year-round. They prefer typing on keyboards with fans underneath. They’re powered by iced lattes and vibes. Their motto? “If I’m not sweating, I’m not shipping.”

Laptop’s response: 💻 “Please, I beg you, not another render loop test… I’m already at 92°C and hallucinating Blender objects.”

---

❄️ Cold Weather Devs: The Frostbitten Builders

Pros:

• You can layer up. Hoodies. Two hoodies. Blanket hoodies. Cat.
• CPUs stay frosty and happy. Fans? What fans? They’re on vacation.
• Every keystroke is a warm rebellion against frostbite.

Cons:

• Fingers cramp after 20 minutes of coding and look like spaghetti left in the freezer.
• You type so slowly, GitHub Copilot finishes your thoughts before you think them.
• You mistake coffee steam for a production server on fire.

Developer profile: Lives in thermal socks. Has a keyboard warmer (it’s just a cat). Believes productivity is directly proportional to the number of cups of hot tea consumed. Their motto? “Cold hands, clean builds.”

Laptop’s response: 💻 “Thank you for this igloo. I’ve never compiled so coolly. I might even update your drivers without crashing today.”

---

🌡️ So… What Do the Laptops Actually Prefer?

Let’s not kid ourselves — your MacBook or ThinkPad doesn’t want to be anywhere near a heatwave. That aluminum chassis? It’s not a heat sink. It’s a cry for help.

Laptops thrive in the cold. The only downside? Developers might stop typing midway through a function call to microwave their fingers.

---

🧣 Final Verdict:

• Hot weather makes developers cranky, sweaty, and creative with bug excuses.
• Cold weather slows down human execution time but keeps machines happier than a clean git log.
• Ideal compromise? A perfectly climate-controlled cave, hoodie optional, GPU ventilated, and a steady stream of caffeinated beverages.

If your laptop could vote, it’d choose winter. If your fingers could vote, they’d just ask for heated keys. And if your code could vote? Well, it’d vote to work… in the cloud.

---

#TeamCold or #TeamHot? Choose wisely. Just remember: your productivity may be frozen, but your bugs are eternal.

Quantum computing is no longer a distant promise—it’s becoming a strategic business priority and a scientific reality. Two timely developments—one from the boardroom and one from the laboratory—are accelerating the arrival of a quantum-powered future.

💼 Business Leaders Bet Big on Quantum

A recent survey, highlighted by Yahoo Finance, reveals that more than one in four business leaders already consider quantum computing a vital force shaping their operations. This isn’t speculative hype. These decision-makers are actively integrating quantum strategy into areas like optimization, risk modeling, and encryption.

From financial institutions managing portfolios to logistics giants optimizing supply chains, executives are recognizing that quantum advantage could unlock efficiencies traditional computers simply can’t reach. The buzz has moved beyond R&D departments—quantum computing is now a C-suite conversation.

🧪 Teleportation at Telecom Wavelengths: A Quantum Internet Milestone

Meanwhile, in a groundbreaking experiment reported by Phys.org, researchers at Nanjing University have teleported a photonic qubit, encoded in telecom wavelengths, into a solid-state quantum memory built on erbium ions. What makes this especially remarkable is the real-world relevance: these wavelengths are compatible with existing fiber-optic infrastructure.

This is a key step toward a quantum internet—a network that could one day enable ultra-secure communications, entangled cloud computing, and real-time distributed quantum systems. The setup combined entangled photon sources, Bell-state measurements, and solid-state memory tuned to telecom frequency—marking the first successful teleportation from light to a scalable memory system suitable for long-distance communication.

🧭 Where Business Meets Breakthrough

Why do these two developments matter together?

• Businesses are ready—they’re allocating budgets and aligning strategies.
• Scientists are delivering—turning quantum concepts into deployable technologies.

This alignment signals a tipping point. For decades, the field has been dominated by theory, niche applications, and academic curiosity. But today, telecom-grade quantum teleportation and boardroom-level buy-in are signs that the ecosystem is converging.

🔮 What Comes Next

Expect rapid growth in:

• Quantum adoption roadmaps from enterprises across finance, healthcare, and defense.
• Public-private collaboration, especially in network infrastructure.
• Investment in quantum communications, building on existing optical fiber systems.

A future where quantum capabilities are embedded in everyday systems is not only plausible—it’s actively under construction. As science pushes the boundaries of what’s possible, the business world is beginning to fund, scale, and deploy.

One foot in the lab. One foot in the boardroom. The quantum leap has already begun.

A few weeks ago Sujit Eapen (fellow Distinguished Engineer) and I shared our views on the benefits of working in fintech and the importance of technology excellence at Morgan Stanley. We highlighted the impact and how junior level employees can be effective and make a difference, dispelling the myths around the lack of innovation, outdated tech and more – we represented the diverse leaders, thinkers, problem solvers, influencers at the firm. The interns of summer 2025 heard from us sharing our differentiated career backgrounds, our industry insights and our unique perspectives representing ourselves and our divisions.

We covered various topics like:

• What does it mean to be a Distinguished Engineer?
• How do you become appointed a Distinguished Engineer?
• What characteristics you should exhibit to be considered becoming a Distinguished Engineer?
• How to build brand in early stages of a career? How does having a personal brand correlate becoming a Distinguished Engineer?
• What keeps me up at night (for me – how is developing with the opensource is, and how to make those capabilities available internally better)?
• How does a day look like – and how do I manage work-life-balance?

And many more anecdotes we told around mishaps and good things and more 😀 Thank you for the organization, Jessica, Abbygaile and Yein, and looking forward to see other fellow Distinguished Engineers’ sessions in the other locations!

“We shape our tools, and thereafter our tools shape us.” – Marshall McLuhan

The interface has always been a negotiation. Between human and machine. Between insight and overload. Between reality and abstraction. But now, the interface is no longer a screen.

The interface is a room.

---

1. From Screens to Spaces

In finance, we’ve lived for decades in a world of rectangles: terminals, dashboards, spreadsheets, and heatmaps. Information arrives in grids, blink rates, and keystrokes. But this flat world is reaching its limit. As data volumes grow and complexity explodes, trying to cram everything into two dimensions is not just inefficient—it’s limiting our cognition.

Extended Reality (XR) – Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) – offers a new contract. One where the user is not just a viewer, but a participant. Where analysis doesn’t sit on a screen: it surrounds you. (Check out https://flowimmersive.com/ if you haven’t done so!)

2. Finance Deserves Better Interfaces

Why XR, and why now?

Finance is the most information-dense domain in the modern world. Every decision, every second, is a negotiation between risk, reward, signal, and noise. Yet we ask traders, analysts, risk managers, and compliance officers to make decisions using input devices invented in the 1970s and paradigms built for yesterday’s data.

XR is not a gimmick. It’s the first interface that scales with you. The human brain evolved to understand space, movement, proximity, and depth. XR brings finance into those evolutionary sweet spots.

3. Use Cases That Transcend Screens

Imagine:

• Trade floor holograms where liquidity clusters literally float between asset classes.
• Risk heatmaps that wrap around a room, allowing you to walk through exposure zones.
• Regulatory audits in AR, highlighting areas of concern in a shared virtual boardroom.
• Data storytelling where charts become environments and insights are spatially anchored.

These are not science fiction. They’re prototypes today—and strategic differentiators tomorrow.

4. Beyond Utility: Collaboration, Presence, and Memory

XR does more than display—it anchors memory.

In spatial computing, ideas are not just read—they’re placed. And once placed in space, they’re easier to remember, navigate, and share. A compliance review conducted in a virtual space can leave behind persistent annotations. A team strategy session becomes a spatially encoded experience—harder to forget, easier to revisit.

Remote collaboration in XR is not a Zoom call. It’s presence. It’s subtle glances, posture shifts, and shared spatial understanding.

5. Open Systems, Not Walled Gardens

To thrive, XR in finance must remain open and interoperable.

The future isn’t an XR app. It’s a composable environment where FINOS-backed APIs, market data, internal analytics, and AI copilots coexist in a spatial web. This requires open standards, common ontologies, and shared governance models—something the financial open-source movement is uniquely positioned to deliver.

6. The Architecture of Rooms

When the interface becomes a room, we must ask:

• What does latency feel like in space?
• How do we balance privacy and persistence in shared XR rooms?
• What happens when the market bell rings in VR?
• What symbols will replace the blinking cursor in a world of gesture, gaze, and voice?

These are design questions, but they’re also human questions. Spatial computing forces us to reimagine not just how we interact – but why.

7. A Call to Action

We don’t need to wait for headsets to reach mass adoption. XR is already here – in pilot projects, in innovation labs, in fintech startups, and on the edges of enterprise. What’s missing is a manifesto. A shared commitment to explore, experiment, and embed finance into spatial computing responsibly.

So here it is:

The room is the interface. The market is multidimensional. And the future of finance is spatial.

---

Join us. Build the rooms. Rewrite the interfaces. Because in this new world – insight is not just a screen away. It’s all around you.

There is a quiet kind of genius in software development that rarely gets the spotlight. It’s not found in systems with a thousand microservices or the cleverest recursive algorithm. Instead, it’s found in the function that’s so clear it reads like a sentence. In the interface that needs no manual. In the system that scales not because it’s complex, but because it’s elegant.

This kind of genius takes a lifetime to develop.

Early in a developer’s career, there’s a desire to prove competence through complexity: elaborate class hierarchies, layers of abstraction, design patterns deployed like trophies. But over time, many learn the truth: anyone can make something complicated. True mastery is the ability to simplify.

Much like in perfumery, where the finest scents are often composed of just a few well-chosen notes, the best software solutions are built from a minimum of high-quality components. These systems are readable, maintainable, and intuitive. They don’t just function—they communicate.

Simplicity in software is not the absence of complexity. It’s the skillful removal of all that is unnecessary. It requires deep understanding of the problem domain, the user, and the trade-offs. It requires discipline to resist the temptation to over-engineer, and wisdom to know when something is “good enough.”

There is a freedom in simplicity. A simple system is easier to reason about, easier to test, and easier to evolve. It’s kinder to future developers—including your future self. It invites collaboration instead of confusion.

It is easy to add complexity. It is easy to fill a codebase with configuration files, dependency injection containers, and sprawling object graphs. But that tends to add clutter and chaos. The real challenge is to convey the essence of a feature, a service, a product—and nothing more.

Seasoned developers often spend more time deleting code than writing it. They refactor, extract, simplify, and iterate until the code says exactly what it needs to say and nothing more. They understand that every line is a liability unless it earns its place.

As with all crafts, this takes time. Years of mistakes, rewrites, and discoveries. Simplicity is not a shortcut; it’s the summit. The path to it is long, but once you arrive, the view is clear.

To code simply is not to code less. It’s to code with purpose. With clarity. With empathy. And in doing so, to write software that lasts.

In today’s digital age, software doesn’t just power our phones and websites—it shapes economies, influences elections, and mediates access to information and opportunity. With this enormous reach comes enormous responsibility. Ethical software governance is no longer a luxury; it’s a necessity.

But what does it really mean for software governance to be ethical? It’s not just about compliance with laws or industry standards. Ethical governance asks deeper questions: Who benefits? Who is harmed? Who decides? Who is accountable?

Let’s explore the key pillars that make software governance truly ethical.

---

1. Transparency: Let People See the Rules and the Rulers

Ethical governance begins with transparency. This means not only documenting processes, decisions, and changes in software, but making them accessible and understandable to stakeholders.

• Are decisions about algorithms and data usage visible to those affected?
• Are open-source contributors aware of how their code is used commercially or socially?
• Is the roadmap open for input, or hidden behind corporate curtains?

Transparency isn’t just a documentation task. It’s a commitment to honest visibility—even when the answers are messy or imperfect.

---

2. Accountability: Decisions Need an Owner

Who gets blamed when an AI system fails? When data is leaked? When a tool discriminates?

Ethical governance ensures that systems are designed with clear lines of accountability. This includes:

• Audit trails for critical decisions (code merges, model deployments, policy changes).
• Role clarity for maintainers, reviewers, and decision-makers.
• Mechanisms to report and address harm—whether technical bugs or ethical violations.

True accountability doesn’t stop at the engineer or the approver. It traces back to organizational culture, incentives, and leadership.

---

3. Inclusion: Governance Can’t Be a Closed Circle

Ethical governance must be inclusive by design. Diverse representation in decision-making not only improves software quality—it surfaces risks others might overlook.

• Are contributors from marginalized communities empowered to participate?
• Is accessibility a core feature or an afterthought?
• Do users have a voice in roadmap decisions or usage constraints?

Ethics isn’t just what the loudest or most privileged voices decide—it’s what’s fair for everyone, especially the underrepresented.

---

4. Consent and Data Stewardship: Use Data Respectfully

Software increasingly relies on data, often from real people. Ethical governance mandates a clear stance on privacy, consent, and data usage.

• Is data collected with meaningful, informed consent?
• Can users opt out of surveillance and still use the service?
• Is personal data treated as a liability—not just an asset?

Governance must shift from a mindset of can we? to should we?

---

5. Bias Awareness and Mitigation: Don’t Encode Inequality

Code is never neutral. Every design decision—what data to train on, what metrics to optimize—carries embedded values. Ethical software governance recognizes and mitigates algorithmic bias.

• Are audits conducted to detect and reduce bias?
• Are impact assessments done before release?
• Are there guardrails in place to prevent harm in high-stakes domains (e.g., health, finance, criminal justice)?

Governance should view fairness not as a feature but as a fundamental constraint.

---

6. Sustainability: Ethical for the Long Haul

Sustainability in software isn’t just about energy-efficient code. It’s about resilience, maintainability, and social impact over time.

• Are dependencies maintained responsibly?
• Is the project funded in a way that aligns with its community and mission?
• Are there policies for deprecation, sunsetting, and offboarding users safely?

Ethical governance looks beyond the next sprint—it considers the next decade.

---

7. Freedom and Autonomy: Empower, Don’t Enslave

Users and contributors alike should retain agency over their choices. Ethical governance avoids vendor lock-in, coercive licensing, and digital overreach.

• Can users understand and tweak how the software works?
• Are contributors informed about how their work will be used downstream?
• Is the project structure welcoming to forks and new maintainers?

Governance should empower people—not trap them in code or communities they didn’t choose.

---

The Ethical Litmus Test: “If this went wrong, who pays the price?”

At the core of ethical software governance is this question: “If this decision ends up harming someone, who pays the price?”

If the answer is a user, a marginalized community, or an underpaid maintainer—without any recourse—then the governance isn’t ethical, no matter how polished the README is.

---

Final Thoughts: From Rules to Responsibility

Ethical governance is about building with care. It’s not just about rules, but relationships—between developers and users, contributors and companies, software and society.

The future belongs to those who don’t just ship fast, but govern wisely.

Because when software rules the world, how it is governed determines what kind of world we end up with.

“I must not fear. Fear is the mind-killer.” – Frank Herbert, Dune

If failure is the villain we blame, then fear is the quiet saboteur no one talks about.

We often mourn lost dreams as casualties of failure—startups that ran out of money, scripts that never got greenlit, careers that derailed. But look closer. Many of those dreams never even left the runway. They weren’t killed by failure. They were strangled by fear long before they got the chance to fail.

Fear Doesn’t Shout — It Whispers

Fear rarely appears as a monstrous threat. It often disguises itself as “being realistic.” It speaks in tones that sound reasonable:

• “What if you’re not good enough?”
• “Now isn’t the right time.”
• “You’ll look foolish.”
• “Someone else is already doing it better.”

These aren’t warnings. They’re tombstones.

While failure offers a postmortem, fear offers no autopsy. You don’t get the dignity of a lesson. You just quietly move on, telling yourself the dream was probably a bad idea anyway.

Failure Hurts. Fear Haunts.

Failure stings, but it teaches. You learn, adapt, and—if you’re brave—try again. Fear, on the other hand, leaves you with what-ifs that echo louder with time.

Many people say they’re afraid of failure. What they really mean is they’re afraid of judgment, rejection, or discomfort. But in avoiding all that, they end up fearing themselves—haunted by what they could have done.

The Illusion of Safety

Fear gives us a false sense of control. It whispers: Stay where it’s safe. But what’s safe today may be suffocating tomorrow.

You don’t outgrow your dreams. You bury them under layers of fear until they stop talking. But they don’t stop living. They twist into frustration, envy, or quiet regret.

Dreams Don’t Need Guarantees. They Need Courage.

You don’t need a perfect plan to start. You need enough courage to try without one.

Starting a podcast, applying to that role, writing the first chapter, pitching the idea—these acts are not reckless. They are resistance to fear. You may fail, sure. But you might also fly. And even if you fall, you’ll land wiser than before.

Every successful person you admire has failed. What they haven’t done is let fear hold the pen.

Let Failure Take the Blame It Deserves—But No More

Failure kills some dreams. It’s true. But far more die quietly in the shadow of fear—unspoken, unlived, unloved.

So next time fear whispers, remind yourself:

Failure is a bruise. Fear is a cage.

And then take one step—just one—toward the dream you’ve been silencing.

“Clean code always looks like it was written by someone who cares.” — Robert C. Martin

“And deterministic cleanups show they cared every day.” — You

---

🌱 What Is Hygiene-Driven Refactoring?

Hygiene-Driven Refactoring is the practice of making small, consistent, and intentional improvements to code—not just when features demand it, but as a habit. It treats code hygiene as non-negotiable, like brushing your teeth: you don’t do it only when there’s a cavity.

It’s not yak-shaving. It’s code stewardship.

---

🧭 The Deterministic Principle

Deterministic Cleanups are predictable, repeatable, and reviewable.

• 🔁 Predictable: Everyone knows when and why the cleanup is happening.
• 🔍 Reviewable: It produces low-noise, high-trust diffs.
• 🧩 Repeatable: It’s not a “drive-by” refactor, it’s part of your sprint hygiene.

Think of it as DevOps for your code quality.

---

📜 The Manifesto

1. Refactor with Purpose, Not Panic

Don’t wait for tech debt to cause pain. Eliminate mold, not just termites.

2. Small Is Strategic

One rename. One extraction. One fix. That’s hygiene. That’s momentum.

3. Automate What You Can

Use linters, formatters, code analyzers. Determinism loves tools.

4. Treat Hygiene Like Testing

Hygiene isn’t a “nice to have”—it’s a pillar of reliability.

5. Leave the Campground Cleaner

You don’t need to fix everything—just fix something.

6. Codify and Share Patterns

Create refactoring checklists. Write before/after examples. Make it a team sport.

7. Make Hygiene Trackable

Track refactoring PRs. Measure code churn vs. quality. Give hygiene visibility.

8. No Feature Left Behind

Every feature PR should include a hygiene pass. Just like writing docs or tests.

9. Refactor Out Loud

Say what you’re cleaning and why. Reviewers will thank you.

10. Celebrate Cleanups

A great refactor deserves a high five. Or at least a GIF in the Slack thread.

---

🔧 Starter Kit: Hygiene Practices You Can Adopt Today

---

🧠 Remember: Hygiene ≠ Perfection

This isn’t about “perfect” code. It’s about continuously cared-for code. The goal is not to rewrite everything—it’s to keep the system in a perpetually healthier state than yesterday.

---

👥 A Call to Teams

Let’s normalize a culture where:

• Hygiene commits are praised.
• Cleanups are part of every sprint.
• Refactoring is routine, not rare.
• New team members inherit clean baselines, not messes.

---

🧭 Your Hygiene-Driven Workflow

1. Start feature branch
2. Refactor (if needed) → Commit: “chore: hygiene pass before feature”
3. Implement feature → Commit: “feat: implement user avatar upload”
4. Final hygiene sweep → Commit: “chore: tighten API naming & remove unused imports”
5. Submit PR → Include hygiene summary 

---

🧼 Make It a Habit, Not a Project

Because the best time to refactor was yesterday. The second best time is every day.