That is what CODAME has always represented to me. Not content. Not branding. Not just events. A real community, one I’d want you to experience for yourself.

A place where experimentation is not an accessory, but the point. Where art and technology are not treated as separate categories, but as parts of the same cultural force.

A place where people can make things before they are easy to explain. And maybe you’ve felt this too, that urge to explore something before it fully makes sense.

I think spaces like this matter more now than ever. Because we are entering a future shaped by AI, automation, platforms, and systems that can scale faster than our ability to ask what they are doing to us, to culture, to meaning, to each other.

In that kind of future, community is not a nice-to-have. It is infrastructure.

We need places where people can gather across disciplines. Where ideas can be tested in public. Where technology is not only optimized, but questioned. Where art is not decoration added at the end, but part of how we think. Where new possibilities can emerge through collaboration, friction, intuition, and play.

Places where you can step in, not just watch from the outside.

That is one of the reasons I believe so deeply in CODAME.

Because CODAME creates the conditions for that to happen. Not by pretending to know the future. But by making space for people, people like you, to imagine it together.

And that is also why I’m excited about what we are opening in Milan.

On April 24, during Design Week, we are bringing The New Human to life, not as a finished answer, but as something I’ve been personally searching for.

And something I’d genuinely love to share with you, in person.

A space where art, technology, and people don’t just coexist, but actually meet. Where you don’t just observe, but feel part of it. Where you can move through it, interact with it, play with it, and see what it gives back.

The New Human begins its journey in Milan, then continues to San Francisco, Berlin, and Shanghai.

Because no single place, no single perspective, is enough to imagine what comes next.

It only starts to make sense when it moves. When it’s shaped by different people, different cultures, different ways of seeing the world.

If you are in Milan, or know someone who should be there, I’d love for you to come experience this with me.

To share a moment. To feel something. To explore. To play. To be part of it, not just around it.

Join me

The future does not only arrive.

Sometimes, it gathers.

My daughter is graduating this year from San José State University, and I could not be more proud.

From a very early age, she knew what she loved: telling stories, drawing worlds, creating characters, and bringing emotion to life through art. What surprised me most was how certain she was when she chose SJSU. She knew the department, the school, and what she wanted to do with her life.

I was skeptical, not because I doubted her talent, but because that kind of clarity is rare at such a young age.

Over time, she proved it was real.

She stayed true to herself, to her craft, and to the stories she wanted to tell. Today, seeing her graduate and help bring a project like To Turn a Tide into the world feels incredibly special.

When change feels impossible, what inspires someone to become the change themselves?

Sometimes the answer begins with something small: a memory, a story, a moment that refuses to fade.

For Sofi, part of that inspiration comes from a memory we share.

At the center of it is a memory I still carry very clearly: collecting clams as a child to bring home to my mother, and then cooking them together. I remember how proud that made me feel. I remember how good they tasted, how simple and beautiful that moment was, and how something so small could hold so much love.

And now, to see my daughter bring those memories back to life through her own art moves me deeply.

There is another part of this story too. Over the years, those clams disappeared. Pollution, neglect, and the ways we have too often failed to care for the environment damaged that little world. Nature faded, and with it, those beautiful and delicious moments that once felt so abundant.

But the good news is: they are coming back.

Maybe not in the same numbers as when I was a child, but they are returning. And to me, that feels like hope, the kind of hope that inspires someone to imagine a different future and, sometimes, to become part of the change themselves.

That is part of why this project touches me so much. It is not only about memory. It is about what we lose, what we carry, what we repair, and what can return.

To Turn a Tide, pitched for SJSU’s BFA 2026 program, is more than a comic anthology. It is rooted in family memory, in generational experience, and in the hope of breaking difficult cycles. Sofi helped shape the overall creative vision, led a team of fellow students, and brought the guiding story to life with both talent and heart.

She has also been a dedicated advocate for community and representation, serving the SJSU WIA Student Collective first as Graphic Designer and then as President.

I am proud of her talent, her discipline, her leadership, and above all, the heart she brings into what she creates.

Watching her grow into herself, with such clarity, care, and creative force, has been one of the greatest joys of my life.

Seeing her turn family memory into art, pain into meaning, and the possibility of return into story makes me even more proud.

If you would like to support the project, here is the Kickstarter:
https://www.kickstarter.com/projects/1091924088/to-turn-a-tide

Back this Project

My time as CTO at TeamSystem has come to a natural close.

When I joined, the objective was clear: strengthen the engineering organization, modernize the platform, and help prepare the company for its next phase of growth. Over the past years, we scaled the engineering teams, improved delivery reliability, advanced the transition toward cloud-based systems, and built a stronger technical and leadership foundation that will continue to support the company going forward.

This kind of progress is always the result of teams working together over time, solving problems step by step, and staying focused on a shared direction. I’m grateful to everyone I had the opportunity to work with and to what we achieved together.

When a cycle completes, it creates space to step back and look carefully at what matters next.

For now, I’m choosing to use that time deliberately.

I’m dedicating time to celebrating and reconnecting with family, friends, and CODAME—the ART+TECH community I care deeply about and that continues to inspire me. We are often busy building and moving forward, and it’s important to find time to reconnect with the people and environments that give direction and meaning to what we do.

This year, CODAME is exploring a theme called The New Human, reflecting the changes we are experiencing as technology becomes more capable and accessible. I’ll be participating directly in the Creative Hackathon in March as a builder. I’m excited to have the time to build again, to experiment, and to learn through making alongside artists, engineers, and creators. It’s a rare opportunity to step back into the process itself and rediscover what emerges from curiosity and collaboration.

This is also an important moment for my family. My three children are entering new stages of independence—one starting university, another finishing this summer, and the first preparing to graduate. These transitions happen only once, and I want to be fully present for them.

And for my wife, the love of my life, who has been beside me through every step of this journey. This time is also for us—for the conversations, the quiet moments, and the shared future we continue to build together.

Technology will continue to evolve quickly, creating new possibilities and new responsibilities. The fundamentals, however, remain the same. Progress depends on people who understand systems deeply, who take responsibility for what they build, and who stay focused on long-term outcomes.

I’m proud of what we accomplished at TeamSystem. I’m taking this time to reconnect, to build, and to prepare for the next chapter.

The work continues.

Code wasn’t always meant to be read.

Before elegant syntax and abstractions, there was assembler. And before that, raw instructions spoken directly to hardware. Early programming wasn’t a shared language between people. It was a negotiation with machines. If we wanted something to happen, we had to bend our thinking to match theirs.

High-level languages changed that. They were an act of empathy, not for the machine but for us. As systems grew more complex, readability became essential. Code became something we could explain, review, and reason about together.

For decades, the primary reader of software was another human.

The New Reader

Now, a new reader has entered the room.

Large language models don’t just execute code. They read it, rewrite it, explain it, and increasingly maintain it. And they read differently than we do. Where humans rely on context, convention, and tribal knowledge, models rely on what is explicitly present.

They don’t fill gaps gracefully. They don’t assume intent unless it is stated.

That creates tension. Many features we value, like implicit behavior, dynamic patterns, metaprogramming, and subtle conventions, can confuse models operating with partial context. We can hold a mental map of an entire architecture, but models operate in windows. If intent is not local and explicit, the model hallucinates a bridge to nowhere.

Where we infer, LLMs must guess.

This is why explicitness, strong typing, and formal contracts are resurging. Languages like Rust or strictly typed TypeScript are not only safer for teams. They are easier for models to reason about. When a new kind of reader joins the conversation, clarity becomes a different kind of necessity.

From Implementation to Intent

This shift changes what programming actually is.

Historically, programming meant telling machines how to do things, step by step, line by line. But LLMs are increasingly capable of determining the how, as long as we are precise about the what.

Our focus moves from implementation to intent.

In this world, the most important thing we write may not be an algorithm, but a clear expression of outcomes, constraints, and assumptions. Tests become more than safety nets. They become executable intent. Documentation stops being an artifact and becomes part of the system.

Not free-form natural language, and not rigid code either. Instead, something in between. A structured, constrained way of saying this is what we want, this is what matters, this must never break.

The Contract Language

It is not hard to imagine what comes next.

We can picture a language where a service is not defined by its control flow, but by its guarantees. A module begins not with imports, but with declared intent. What it is responsible for, what constraints it must respect, and what “correct” means in observable terms.

We can imagine a function body with no logic. Only a strict return schema and a detailed contract, where the compiler is a model resolving the implementation at runtime.

Such a language would not look like Python or Rust. It would read closer to a formalized contract written in constrained natural language, backed by executable specifications and verification hooks. We define the space of valid behavior. The machine explores it.

The Architecture of Intent

This raises a practical question. When the machine writes the implementation, what do we actually read? And how do we debug it?

The codebase splits into two layers: the Source and the Artifact.

The Source is what we touch. It looks less like a recipe and more like a legal agreement fused with a test suite. It is concise, high-level, and explicit about what must happen.

The Artifact is what the model generates. It is verbose, defensive, and heavily instrumented code, perhaps in Python or WebAssembly, that actually runs. We will rarely inspect it, just as we rarely debug assembly unless we are desperate.

Debugging shifts from inspecting state to inspecting reasoning.

When a bug occurs, for example a payment is approved when it should be declined, the code will likely be syntactically perfect. Instead of stepping through lines, we examine a Decision Trace: observed user flag, referenced policy, overridden constraint based on ambiguous precedent.

The bug is not in syntax. It is in ambiguity. We do not fix it by editing generated code. We fix it by tightening the Source contract.

The Death of Refactoring

This separation implies the end of refactoring as we know it.

Today, code is an asset we polish and maintain. In this future, implementation code becomes disposable.

To optimize a module, we do not rewrite functions. We adjust constraints in the Source and regenerate the Artifact. Throwing away ten thousand lines of code costs nothing. Technical debt in implementation disappears. Intent debt remains, in the form of imprecise definitions that no longer match reality.

Our tools will need to evolve. A traditional git diff becomes meaningless when a tiny change rewrites an entire file. We will need version control for meaning, not text. The pull request of the future will not ask us to review code. It will ask us to review simulations of intent.

The Human Shift

Our roles will change as quickly as the tools.

For decades, a Senior Engineer was someone who knew the deep corners of a standard library. That skill is depreciating. The new Senior Engineer is an ambiguity hunter.

Their strength is not syntax. It is systems thinking. They spot the edge cases a model would misinterpret. They express complex systems in constraints so tight that misunderstanding becomes impossible.

Security shifts as well. Vulnerabilities will not only be buffer overflows. They will be psychological. Attackers will not break the stack. They will try to persuade the model to ignore its constraints. Security becomes adversarial semantics.

The Prediction

I predict that within the next few years, languages designed explicitly for collaboration between humans and LLMs will emerge. Most will fail. One or two will quietly succeed, and they will redefine what good code means. It will become less implicit, more explicit, and more intent driven.

These are only a few of the changes LLMs will bring to the software development lifecycle. From design to testing, deployment, and maintenance, nearly every stage will be affected as models participate in reading, generating, and maintaining code. The examples we discuss here illustrate the broader transformation, but the full impact is likely to be much wider and still emerging.

This will not happen only because such languages suit machines. It will happen because incentives align. Vendors gain tighter integration and lock in. Developers gain predictability and a shared vocabulary for human-machine collaboration.

Assembler gave way to C. C gave way to Python. Python may give way to something that looks less like a language and more like a contract, a shared understanding between humans and machines.

This change will not arrive with fireworks. It will arrive as relief, as clarity, as a system that simply works alongside us.

Only later will we realize that we have crossed a line. We will have moved from programming machines directly to programming intent in systems that think with us.

Whether thinking as an engineer, a CTO, or a founder, one theme stayed constant: the systems we shape quietly shape us back.

In AI 2027, I explored a trajectory that’s moving from speculative to tangible: AI not just as assistant, but as autonomous agent. We’re beginning to see these glimpses now, tools that generate code, chain actions, and navigate loosely defined tasks.

We are, after all, actively building the future right now. The only question is: will we build it wisely?

That theme continued in The Future of Enterprise Software, where I argued that software is no longer just a tool we use to do work, it increasingly is the work. Our interfaces, workflows, and platforms have become the execution layer.

Software is no longer just tools, it’s becoming the work itself.

This shift raised deeper architectural questions. In Choosing the Right Architecture, I shared how data and events offer distinct but complementary strengthsand how designing for change requires systems that are not just scalable, but legible. In Rethinking Systems: What MCP Means, I looked at coordination patterns for multi-agent environments and what new kinds of context-aware infrastructure might enable.

Inter-agent context is the new interface.

But not all the questions were technical. The Hackathon Effect reminded me that momentum often begins with permission: to explore, to prototype, to move without over-justifying. Sometimes the greatest constraint is the absence of one.

They stop talking about innovation, and actually experience it.

In Unlocking Creativity in Your Software Team, I explored the quieter blockers that stifle teams, uncertainty, over-editing, loss of purpose, and how reintroducing clarity can restore flow.

Leadership, I realized, isn’t confined to job titles. It shows up in the architecture of decisions. In Protect the Purpose, Evolve the Rest, I argued that strong systems aren’t rigid, they’re anchored. Purpose offers the clarity that everything else builds around.

Protect the purpose. Evolve the rest.

And in Leading with Conscious Awareness, I reflected on how awareness, not speed, not certainty, is what gives us leverage in complex environments. The ability to pause, to observe without judgment, and to respond with clarity.

Awareness is what gives us range.

Looking back, the unifying thread wasn’t prediction or control. It was intentionality. The willingness to meet complexity with attention, and to design systems that scale without unraveling.

What’s next in 2026?

I won’t pretend to have predictions. What I do have is a commitment to paying attention, to staying curious, open, and anchored in the questions that matter.

2026 will ask us to be more adaptive, more aware of edges and boundaries, and more deliberate about how we use our tools. It will reward those who stay grounded, yet open. Who listen well, reflect often, and act with care.

I remain optimistic about what’s ahead. Not because it will be easy, but because I believe we can meet change with clarity and design it into something worthwhile.

Thanks for reading. Here’s to building systems, and organizations, that are worthy of our trust.

What signals are you paying attention to as we head into the new year?

Change isn’t coming; it is already here. In a world where intelligence is limitless and speed is the new gravity, the only real advantage is our willingness to evolve.

We are living in an age of unmetered intelligence.

Ideas move faster than infrastructure. Creation is no longer limited by access, tools, or time. The boundaries between human intuition and machine reasoning are dissolving, revealing new territory where possibility expands faster than certainty.

With that acceleration comes instability, but instability is not a flaw. It is the advantage of this era.

I learned this through years of working across emerging technology, design, and art, including founding a startup where every project felt like a prototype and every collaboration a living experiment. Nothing stayed the same for long. Formats shifted, tools evolved, expectations changed as soon as they were understood. Yet something deeper remained constant: the intention behind the work.

Experimentation became less of a method and more of a worldview.

A belief that transformation is not an interruption but a signal.

A reminder that evolution is the natural state of creative systems.

Over time, I realized that the world we were designing for was changing faster than the structures we relied on. Old models felt too rigid. Traditional frameworks couldn’t keep pace with possibility. So I stopped trying to protect the forms and began focusing on the purpose behind them instead.

With the rapid acceleration of artificial intelligence, social shifts, and fast consumption cycles, this pressure now feels exponential.

Purpose is what makes reinvention coherent.

It is what turns disruption into direction.

Across fields, whether a platform refining how we connect or an artist reinventing a creative process for the twentieth time, the same truth appears: those who thrive are not preserving what worked yesterday, but creating space for what wants to emerge now.

Nostalgia comforts, but it also constrains.

Progress asks different questions:

Not “How do we maintain this?”

But “What can this become?”

Design becomes orchestration. Tools, ideas, and collaborators become instruments that tune themselves to a shifting world. Disruption becomes an invitation to re-examine what truly matters. Each shift becomes a return to clarity.

Purpose is the anchor. Everything else is meant to evolve.

Strategies, tools, and structures must remain fluid. Authenticity becomes the compass. In a world overflowing with intelligence and shrinking attention, coherence becomes the strongest signal we have.

Among many others, this is why I am excited about this year’s Festival and its theme, The New Human.

As part of the Festival, at the Creative Hackathon, we are invited to build something that honors how we change. Not a static artifact of the past, but a living reminder of growth. Not a fixed representation, but a quiet companion to our evolution.

True evolution does not erase what came before; it sharpens it.

When we let change guide us rather than scare us, we create work that grows with us instead of aging behind us.

Hold your purpose tightly and your form lightly.

Recently, I have been reading The 15 Commitments of Conscious Leadership by Jim Dethmer, Diana Chapman, and Kaley Warner Klemp, and these are the reflections it sparked for me.

I am far from mastering these commitments, but they have become guideposts that help me navigate complexity with greater clarity and humility.

Here are a few that have been especially meaningful lately:

1. Radical Responsibility

Big companies have structure.
Startups have chaos.
The ART+TECH community has its beautiful unpredictability.

It is easy to blame external conditions.
This commitment invites a different stance:

Instead of asking, “Why is this happening to us?” try asking, “How am I creating or allowing this?”

It does not solve everything, but it opens a constructive way forward.

2. Curiosity Over Being Right

When pressure rises, curiosity is often the first thing to disappear, yet it is essential for innovation.

The ART+TECH community thrives on curiosity as we explore new ways for artists to bring their work to life.
Startups depend on curiosity to avoid false certainty.
Large teams benefit when curiosity softens rigid thinking.

Being right closes doors.
Being curious opens them.

3. Feeling Feelings (Even at Work)

As an engineer, I have always valued logic, and I still do. Logic is foundational to everything we build.

But the book reminded me that teams rarely struggle because of technical challenges. They struggle because of the emotions around those challenges. Bringing some of the ART+TECH community’s emotional openness into my corporate life has strengthened collaboration.

Emotions are not the opposite of logic.
They are part of the data.

4. Speaking Candidly and Eliminating Gossip

This is a daily practice, not an instant skill.

Speaking directly is uncomfortable.
Resisting gossip is uncomfortable.
But both create trust, clarity, and momentum.

As the authors emphasize, clarity is kindness.
I highly value this one.

5. Living in Integrity

Integrity, as described in the book, is not about perfection. It is about alignment.

For me, this means keeping commitments when possible and being honest early when I need to renegotiate. It means fewer automatic yeses and more intentional ones.

Less heroic effort.
More grounded clarity.

6. Sourcing Approval, Control, and Security Internally

This is one of the most humbling commitments.

In corporate environments, worth is often tied to performance.
In startups, to speed.
In the ART+TECH community, to creativity and experimentation.

But when approval or stability come only from external signals, fear takes the lead. Building internal steadiness, even slowly, changes how I show up for others.

Most likely, it is a lifelong practice.

7. Play and Rest

Simple to understand.
Hard to embody.

The ART+TECH community reminds me that play fuels creativity.
Startup life reminds me that rest prevents burnout.
Corporate work reminds me that neither happens unless it is intentionally protected.

Play is not frivolous.
Rest is not a reward.
Together, they create resilience.

Why I Am Sharing This

We are all navigating massive shifts: AI, distributed teams, new expectations, and new pressures. Technical leadership used to be mostly about architecture and execution. Now it requires emotional intelligence, communication, and staying present under uncertainty.

The 15 Commitments of Conscious Leadership has given me a more grounded way to lead, imperfectly but more consciously.

It has helped me:

• reduce unnecessary pressure

• avoid drama

• communicate with greater clarity

• support healthier team dynamics

• stay aligned with what matters

• create more space for creativity, both in tech and in the ART+TECH community

If you have read the book or practiced any of these commitments, I would love to hear what you learned.

We are standing at the edge of a structural shift in how work gets done and how software gets built.

For decades, digital transformation meant upgrading tools—better interfaces, faster workflows, more features. But the fundamental assumption never changed: humans did the work, and software supported them.

AI agents break that assumption.

For the first time, we’re designing systems that don’t just enable work—they perform it. They interpret data, coordinate operations, make decisions, and reshape workflows dynamically. This isn’t a UX improvement or a productivity enhancement. It’s the emergence of a new execution layer inside the enterprise.

And as this layer takes form, everything we know about building, delivering, and operating software is being rewritten:

• architectures

• integration patterns

• security models

• pricing

• support

• product strategy

• customer relationships

• and the entire enterprise ecosystem

This is not a technological update—it’s an evolutionary jump.

AI agents are redefining the physics of enterprise software, and the companies that adapt fastest will shape the next decade of digital work.

What follows is a vision of that future—not as hype, but as an operating thesis for how software product companies will build, deliver, and sustain autonomous work inside the enterprise.

1. The Shift From Systems to Workflows-as-a-Service

For decades, software product companies delivered tools while customers were responsible for extracting value.

AI agents dissolve that boundary.

When an agent reconciles financials, processes claims, reviews contracts, or executes compliance checks, the software no longer sits beside the workflow—it becomes the workflow.

This triggers structural shifts across the business model:

• Contracts evolve from access to outcome guarantees

• Pricing moves from seats to volume, accuracy, and task classes

• Vendor consolidation accelerates because operational trust becomes a scarce asset

• Integrations go deeper because superficial APIs cannot support autonomous work

Enterprises won’t buy tools.

They’ll buy workflow execution, delivered reliably through agents.

2. Domain Intelligence Becomes Infrastructure

General-purpose models aren’t enough for enterprise autonomy.

Agents require:

• industry ontologies

• embedded compliance logic

• domain-informed reasoning

• deterministic fallback behavior

• contextual understanding of tools

This creates a new competitive layer:

domain-native intelligence infrastructure.

Software product companies that own this layer will effectively become the operating systems of their industries.

3. Evals Become the Control Plane of Enterprise AI

Once agents perform real work, evals become the governance backbone.

Effective eval systems must include:

• benchmark suites

• adversarial tests

• reproducibility

• regression tracking

• safety scoring

• accuracy SLAs

This fuels a new ecosystem:

• eval clusters

• continuous verification pipelines

• third-party certifications

• eval-driven deployment gates

Evals are no longer optional—they are the control plane for trust.

4. Quality Becomes Contractual

When software creates work output, quality becomes:

• measurable

• reviewable

• contractual

• enforceable

Software product companies must deliver:

• accuracy guarantees

• error budgets

• safe rollback paths

• risk-scored decisions

• traceable execution logs

Quality stops being aspirational.

It becomes the product.

5. Security & Policy Enforcement Become Zero-Trust for Agents

Agents operate across multiple systems and actions, increasing risk.

This requires a new security substrate:

• scoped permissions

• policy-aligned reasoning

• tool isolation

• credential boundaries

• anomaly detection

• behavior attestation

The old perimeter security model collapses.

Enterprises adopt zero-trust for autonomous operations:

• zero-trust tools

• zero-trust reasoning

• zero-trust execution

Security is no longer a layer—it’s the foundation.

6. Traceability Becomes the New Compliance Stack

To adopt agents at scale, enterprises demand “click-through traceability”:

• data lineage

• policy events

• tool invocation logs

• eval scores at execution

• alternative reasoning paths

This creates an emerging category:

Agent Observability & Audit Infrastructure.

Where DevOps gave us logs, metrics, and traces,

AgentOps delivers reasoning trails, policy metadata, and execution forensics.

This becomes mandatory across regulated industries.

7. Implementation Shifts to Workflow Refactoring

Deploying agents requires refactoring the workflow itself, not configuring software.

This includes:

• process decomposition

• tool orchestration

• data alignment

• context pipelines

• simulation of edge cases

• multi-agent workflow design

Enterprise ecosystems will need new partners:

Agent Integrators that combine engineering, AI operations, and workflow re-engineering.

8. Support Evolves Into Operational Reliability Engineering

Support shifts from UI troubleshooting to:

• diagnosing agent behavior

• analyzing drift

• resolving workflow-level incidents

• tuning policy and context

• improving operational accuracy

Support becomes a shared operational discipline—part engineering, part business operations, part safety management.

The New Identity of Software Product Companies

AI agents push software companies into a new role:

→ Providers of autonomous workflows

→ Custodians of digital labor

→ Stewards of accuracy, compliance, and truth

Value migrates upward—from features → workflows → outcomes → trust.

The companies that win will be those that deliver:

• deep domain intelligence

• eval-driven governance

• contractual-quality autonomy

• zero-trust agent security

• full traceability

• workflow transformation

• outcome-based support

We are leaving the era of tools.

We are entering the era of intelligent execution.

And the companies that embrace this shift will define how enterprise software—and enterprise work itself—evolves in the decade to come.

I recently spent time in both San Francisco and New York, two cities that couldn’t feel more different right now, yet both say a lot about where we’re heading.

In San Francisco, everything revolves around AI. Every event, panel, pinboard, and conversation circles back to it. The city feels like it’s living inside its own feedback loop, tech feeding tech. There’s a density of innovation there that’s hard to match anywhere else. It’s raw, restless, and inevitable. You can feel the next chapter of human progress being prototyped in real time.

Yet outside that AI bubble, San Francisco still feels fragile. Many storefronts remain closed, streets are quieter, and that pre-pandemic spark, the serendipity and chaos that once defined the city, hasn’t fully returned. It’s a place in transition: brilliant minds building the future inside, while the outside world waits to catch up.

Then I landed in New York. Instant contrast. The city feels alive, buzzing with energy and diversity in a way that’s impossible to replicate. I arrived in the middle of the mayoral elections and the marathon, and the city was practically vibrating, a reminder that civic energy and human connection are still the ultimate catalysts for progress.

Every corner, every accent, every interaction reminds you that creativity doesn’t just come from tech, it comes from people colliding. While San Francisco is engineering the future, New York is living it.

SF will never be NY, and that’s fine. But AI might be what brings San Francisco’s heartbeat back. The same force that’s transforming our world could be what reanimates its own hometown.

For me, this tension between cities, one building the tools of tomorrow, the other embodying the creative chaos that keeps humanity moving forward, captures the story I keep returning to: the intersection of art, technology, and urban transformation.

Cities evolve like living systems, shaped by innovation and imagination alike. And as AI reshapes what we build and how we express ourselves, it’s clear that the future of creativity will belong to places, and people, that find a way to fuse both.

A special thank you to TeamSystem and our investors for making these regular US visits possible, and to partners, friends and former coworkers we connected with along the way at Google, Apple, Adobe, GitHub, Pixar, OpenAI, Shopify, Qualified, Databricks, Glean, Zendesk, MongoDB, and many more. Those exchanges, of ideas, experiences, and perspectives, are what truly keep innovation alive.

And, most importantly, I’m grateful for the time spent with my kids, the best reminder of why all of this future-building ultimately matters.

Hackathons have shaped the way I think about innovation, culture, and creativity.

They’re proof that when people are free to explore without permission, amazing things happen, ideas grow, teams connect, and innovation becomes a shared language.

Here’s why I believe everyone, no matter your industry, role, or level in the company, should experience one.

It often starts with an idea, small, uncertain, maybe even a little wild. A few people gather around it, sketching, experimenting, testing what might work. No one’s following a plan. No one’s asking for approval. They’re just building, together.

That’s a hackathon.

And I’ve seen what happens when people are given that kind of freedom. The room feels different, lighter, louder, alive. Hierarchies fade, silos dissolve, and collaboration becomes instinctive. People start connecting in ways they never do in meetings or structured projects. They stop talking about innovation, and actually experience it.

That’s the hackathon effect.

And it builds something far more lasting than code. It builds culture.

If You’ve Never Been to a Hackathon, Here’s What It’s Like

Hackathons trace back to the late 1990s, when open-source communities began experimenting with faster, more collaborative ways to build software.

Developers would gather for 24 or 48 hours to create something new, not for profit or fame, but for the joy of making and learning together.

The name says it all: “hack” in the sense of clever, creative problem-solving, and “marathon”, a focused sprint of imagination and endurance.

The early ones were simple: laptops, snacks, sleepless nights, and a shared sense of possibility.

But they sparked a new way of working, where collaboration outpaced hierarchy and experimentation led to breakthrough ideas.

Some of the world’s best-known products and features, from social media tools to startup concepts, began in hackathons.

But the real legacy isn’t what was built; it’s how people learned to build together.*

It’s the realization that innovation starts with exploration, and that great ideas rarely come from certainty.

Why You (and Every Company) Should Join One

I’ve been part of hackathons across companies, teams, and creative communities.

Every time, the outcome is the same, not in what gets built, but in how people think and feel afterward.

Hackathons create space for what modern work often forgets: freedom, curiosity, and shared discovery.

They spark creativity. When people are encouraged to explore, ideas multiply, fast.

They accelerate learning. In two days, you can test tools or approaches that might take months in a normal workflow.

They break silos. Designers, engineers, marketers, and dreamers work side by side. Hierarchy gives way to shared purpose.

They renew motivation. There’s an energy that comes from building something from scratch, from seeing your idea come alive in hours instead of quarters.

And they ripple outward. Even if a prototype doesn’t ship, the spark it creates travels, influencing future projects, products, and collaborations.

That’s why I see hackathons not as side projects, but as engines of innovation and culture.

They remind people why they joined in the first place: to imagine, to create, and to build something meaningful.

No matter your title, team, or background, there’s a place for you in that process.

When Collaboration Becomes a Force

One of the most memorable hackathons I joined was in Las Vegas, during one of the huge AT&T Hackathons often hosted around the Consumer Electronics Show (CES).

These events are something else entirely, massive creative playgrounds where developers, designers, and innovators come together to build the future in just a weekend.

The focus is on 5G, IoT, and public safety technologies, connecting everything from smart cities to connected health devices.

I teamed up with José Antonio Márquez Russo and , and together we dove into the challenge with the same intensity and curiosity that define every great hackathon.

What we built we called RELATE, an app that combined the best of LinkedIn, Foursquare, and Groupon, designed to help people discover meaningful professional connections through shared interests and nearby to build a team.

It was fun, fast, and a little chaotic to build, the kind of creative sprint where ideas evolve in real time and everyone learns something new. The app itself never went anywhere, but the experience and learning stayed with us all.

That’s the real value of hackathons: even when the project did not win or survive, the mindset does. It changes how you think, how you work, and how you collaborate.

The energy was contagious, long nights, bold ideas, fast prototyping, and spontaneous collaboration between people who had just met but shared the same creative drive.

Beyond Technology

Over the years, I’ve realized hackathons aren’t really about technology at all. They’re about people, and the shared drive to make something new. A musician remixing sounds, a designer rethinking materials, a teacher inventing new ways to engage students, they’re all hacking in their own way.

Exploring through making.

Learning through doing.

Turning limits into inspiration.

The hackathon mindset belongs everywhere: in classrooms, studios, labs, and boardrooms. It’s about curiosity. About turning “what if?” into “why not?” And about realizing that creativity doesn’t wait for perfect conditions, it thrives in motion, collaboration, and courage.

“Creativity doesn’t belong to a department.

It lives wherever curiosity meets courage.”

We tend to talk about creativity as if it’s a role or a process, something that happens in a specific place, owned by a few. But it isn’t. Creativity happens in the moments we step into the unknown, when we experiment, when we connect ideas that weren’t meant to fit, when we dare to ask “what if?”

It’s not a skill reserved for designers or developers, but a mindset that belongs to everyone:

• the accountant who automates a task in a smarter way,

• the teacher who reimagines how to engage students,

• the marketer who tells a story differently,

• the engineer who looks beyond requirements and asks why not?

Creativity thrives in curiosity, and it grows when we have the courage to try. That’s what hackathons celebrate: not expertise, but openness. Not perfection, but exploration. And that’s where true innovation, and culture, begins.

The Real Impact

That’s why I believe in hackathons, not just as events, but as a philosophy of innovation. They remind us that technology is most powerful when it amplifies creativity. That culture isn’t written in processes or policies, it’s built in shared experiments and bold ideas. And that impact, real, lasting impact, happens when experimentation becomes part of who we are.

So whether you work in engineering, design, business, art, or education, join a hackathon. Experience what happens when you stop waiting for permission and start building. You don’t need to code to belong there. You just need curiosity, openness, and the courage to create.

Because innovation doesn’t belong to a few. It belongs to everyone, no matter your industry, role, or level in the company.

The future won’t be written by those who wait. It’ll be built by those who experiment, before they’re ready.

A Real Example of the Hackathon Effect

I’ve seen this spirit come to life firsthand.

Years ago, during a hackathon with my team at Salesforce, we decided to use LEGOs to simulate a Smart City using our IoT Cloud Platform in 2017. It started as a playful idea, a way to visualize connected devices communicating through Salesforce data in real time.

This fun hack project quickly gained attention. Our project was later showcased at Dreamforce in San Francisco, where I had the chance to share the experience with our CEO, , who stopped by to see it in action.

And there was another surreal moment I’ll never forget JR, the artist known for his monumental public works, captured a photo of our hack as part of his documentation of the event. I would be thrilled to see the photo he took of our hack one day!

It was the perfect reminder of what hackathons can spark: when creativity, play, and technology intersect, they don’t just generate ideas, they create energy, connection, and culture that spreads far beyond the room.

Building the Next Hackathons

Today, I’m helping build that same spirit of experimentation at TeamSystem, a company that shares this belief in creativity, collaboration, and continuous learning.

We’re designing hackathons not just as events, but as platforms for exploration, places where teams can test new ideas, experiment with emerging technologies, and connect across departments.

Just like the best hackathons I’ve joined before, the goal isn’t only to create prototypes, it’s to build a culture of curiosity.

We’re encouraging people to explore ideas that stretch beyond their daily work, to experiment boldly, and to learn by doing.

Because innovation doesn’t happen in isolation or inside a single team.

It happens when diverse minds collide, challenge each other, and imagine something new together.

That’s what we’re nurturing at TeamSystem: not just innovation through technology, but innovation through people.

Continuing with CODAME

And that same spirit continues to live on through CODAME, where we’ve always believed that creativity, technology, and collaboration belong together.

We’ve hosted countless hackathons over the years, each one blurring the lines between art and tech, between imagination and implementation.

Our next one, “Exploring the New Human”, is coming soon, and it embodies exactly what hackathons are all about: curiosity, courage, and community.

💬 Reflect with me:

Have you ever joined or hosted a hackathon, in tech, art, or life? Reply and tell me what you built, what you learned, or what surprised you most.

Modern architecture like Bosco Verticale from Stefano Boeri rises beside traditional facades, while green spaces and playgrounds stitch the neighborhood together. It felt — and still feels — like a vivid expression of Milan’s spirit: bold, layered, and open to reinvention.

That impression stayed with me.

Today, I work in a space overlooking Biblioteca degli Alberi Milano (BAM) here at Teamsystem. What was once a rail yard is now one of Europe’s most visionary urban parks. But this time, I’m not just passing through — I’m part of the rhythm of the place.

BAM is more than a park. It represents a vision of urban development that brings together design, ecology, and community. Its story is worth reading 🔗 https://bam.milano.it/en/la-storia/

Art played a pivotal role in this transformation. During the 2015 Expo, the Riccardo Catella Foundation and the Fondazione Nicola Trussardi commissioned Wheatfield — a 5-hectare wheat field planted by American artist Agnes Denes. The act was poetic and provocative: a golden field growing in the shadow of cranes and concrete. It invited the city to pause, reflect, and imagine new possibilities. A reminder that art can not only inspire — but also shape the future of cities.

That vision is still alive today.

Most recently, BAM hosted Circus – Il Festival delle Meraviglie al Parco, a three-day celebration of contemporary circus, performance, and aerial art that transformed the park into a dreamlike realm. One of the highlights was SYLPHES – Aerial Poetry in Motion, a breathtaking ballet in the sky that evoked the elegance of synchronized movement and the emotional richness of classical dance. The air itself became a stage — an ephemeral and moving tribute to human fragility and grace.

🔗 See more from that magical moment

Experiences like these reaffirm the role of public space not just as infrastructure, but as canvas — open to all, alive with meaning.

But moments like Wheatfield or Sylphes only reach their full potential when followed by sustained programming, accessible participation, and long-term care. Urban transformation isn’t a one-time installation — it’s a continuous cultural commitment.

Full Circle to ART+TECH

This connection between art, technology, and public experience is also at the heart of CODAME ART+TECH — the nonprofit I founded in San Francisco and recently brought to Milan.

At CODAME, we explore the intersection of creativity and emerging technology not just to push boundaries, but to connect with humans — always placing people at the center of the experience, the inspiration, and the creative process.

We believe that creativity is a powerful tool for building not just products, but perspectives. For sparking dialogue. For imagining futures that are inclusive, expressive, and alive.

Just as cities invest in public parks, museums, or libraries, we believe technology should be treated as cultural infrastructure — designed intentionally, shaped ethically, and rooted in human experience.

Bringing CODAME to Milan has also meant listening first. While the energy of creative experimentation is universal, each city has its own rhythm, constraints, and cultural DNA. Here in Milan, I’ve encountered a deep respect for tradition, balanced with a strong appetite for innovation. The tension between the two is fertile ground for meaningful, human-centered experiences.

The Other Side of Innovation

As with many stories of urban renewal, there are complexities. The transformation of Isola has brought innovation and beauty — but also rising costs, shifting demographics, and the risk of losing the unique character shaped by long-standing communities.

But this doesn’t have to be the cost of progress.

What gives me hope — and what sets Milan apart — is how thoughtfully the city and its community have approached this evolution. From design and architecture to programming, events, and preservation, there’s a clear effort to balance change with care.

The city’s commitment to inclusivity is visible not just in cultural programming like Wheatfield or SYLPHES, but also in everyday details: open-access green spaces, diverse public events, and the playgrounds at BAM where children of all backgrounds play together, while families and grandparents gather, relax, and reconnect.

These spaces are not exclusive. They’re designed to be lived in — by everyone.

BAM, and the broader Porta Nuova district, reflect a vision of urban life where innovation doesn’t just serve aesthetics or capital, but community. Milan is far from perfect — but the intention to include, to preserve identity while embracing change, is there. And it shows.

As we continue building, innovating, and creating, we must ask: Who is this for? And how can we design futures where more people belong?

When art and technology are guided by these questions, they become more than tools — they become bridges.

If you’re working at the intersection of public space, creative technology, and community — or asking these same questions — I’d love to connect.

Over the years, I’ve worked on building software platforms and automation tools to make complex systems more manageable. I moved from monolithic applications to microservices, later adopting micro frontends to gain flexibility and scale. Event-driven and data-driven designs brought even more adaptability—but one issue persisted: integration was always the bottleneck. No matter how modular we got, connecting disparate services remained fragile, slow, and costly.

That’s why the Model Context Protocol (MCP) caught my interest. While I’m still exploring and experimenting with it rather than using it in production, I can already see its potential. MCP isn’t another tool or library. It’s a proposal for a deeper foundation—one that gives intelligent agents the ability to maintain shared context and collaborate coherently across services and platforms.

And if it works, it could change everything about how we build distributed systems.

From Microservices and Workflows to Agents

If you've worked through the evolution of software systems—from monoliths to microservices to event-driven platforms—the emergence of autonomous agents feels like a natural next step. But this shift introduces new architectural requirements. AI agents aren’t just microservices with intelligence; they need to reason, hold memory, negotiate with peers, and operate independently while maintaining consistent context.

That’s where agent protocols come in. They serve as the connective tissue—defining how agents communicate, share goals, delegate tasks, and align on outcomes across distributed systems. What HTTP did for the web, agent protocols aim to do for AI interoperability.

How MCP Could Transform Development

One of the first shifts MCP encourages is moving from rigid, predefined workflows to systems that evolve through interactions. Agent-oriented thinking invites us to see software as a network of decision-makers rather than a pipeline of function calls. Agents operate in a shared memory space, negotiating behavior based on real-time context instead of waiting for someone to call them.

Another appealing aspect is interoperability. Instead of building a custom adapter every time two systems need to communicate, MCP proposes a universal layer—a common contract for how agents talk to each other. That kind of shared language has the potential to cut integration time dramatically and reduce the complexity that plagues multi-system environments.

There’s also something powerful about context persistence. With MCP, agents can react to the world around them as it changes. Imagine a compliance agent observing an update in a billing system and independently triggering downstream checks—no orchestrator needed, no predefined flow to follow.

Strategic Benefits

The appeal of MCP goes beyond technical elegance. Faster development cycles become possible when new features can be composed from existing agents. User experiences improve as systems feel more coordinated and context-aware. Maintenance gets easier when shared standards replace glue code.

And from a business standpoint, the idea of plugging in a new third-party agent rather than building a feature from scratch opens up new possibilities for collaboration and marketplaces.

The State of AI Agent Protocols

Agent protocols are still in early development, but momentum is picking up. Several key players have proposed competing—but sometimes complementary—frameworks to bring coherence to the agent ecosystem.

Model Context Protocol (MCP)

Anthropic’s MCP is one of the earliest and most widely discussed efforts. It enables stateful, context-sharing between agents and defines structures like tools, prompts, and resources. Microsoft is developing a C# SDK for MCP, while companies like Block, Apollo, Replit, and Stripe are experimenting with it. But implementation remains complex, relying on persistent connections and often using stdio transport, which limits scalability. Many parts of the ecosystem—especially client-side primitives—remain underexplored.

Agent2Agent (A2A)

At Google Cloud Next 2025, Google unveiled A2A, an HTTP/JSON-based protocol with over 50 enterprise partners. It focuses on capability discovery, structured task management, and user experience negotiation. A2A introduces the concept of JSON-based "Agent Cards" and is positioned as a higher-level abstraction that complements lower-level frameworks like MCP and LangChain’s Agent Protocol.

LangChain Agent Protocol

LangChain’s protocol aims to bridge structured tooling and LLM orchestration. It integrates tightly with Python agents and is widely used in open-source experimentation. While still evolving, it's already a popular choice for researchers and hobbyists looking to spin up basic agent behaviors.

What's Clear (and What Isn’t)

The existence of multiple protocols isn’t a problem—it’s a sign of rapid innovation. But we haven’t yet converged on a single standard, and each protocol comes with trade-offs. Some prioritize enterprise security and HTTP transport (like A2A), while others are more LLM-native but harder to scale (like MCP).

The takeaway? Protocols are now central to building intelligent systems. And while it’s too soon to bet on a winner, it’s the right time to understand the landscape and get involved.

Final Thoughts

The race to define how AI agents collaborate is very much underway. Whether it’s Anthropic’s MCP, Google’s A2A, LangChain’s Agent Protocol, or something else entirely, one thing is clear: agent-based systems need standards.

As someone who's built backend systems, workflow engines, and distributed applications, I see agent protocols not as a hype cycle but as an architectural necessity. They won’t solve everything, and none of them are quite ready for prime time. But even today, they offer a window into what the next generation of software might look like.

We're witnessing the TCP/IP moment for agents. And while we don't yet know which protocol—or combination—will dominate, this is a space worth watching closely. If even half the promise holds, agent protocols will become a foundational layer for AI-first software in the years ahead.

In my line of work, staying close to the cutting edge of AI research is part of the job. But sometimes, a scenario comes along that pulls you out of the day-to-day and forces a broader view. That’s exactly what happened when I read AI 2027 by , Scott Alexander, Thomas Larsen, Eli Lifland and Romeo Dean, a speculative yet rigorously reasoned forecast that outlines the possible emergence of artificial superintelligence (ASI) within just a few years.

Kokotajlo, formerly of OpenAI, developed this scenario in partnership with the AI Futures Project. The document reads like a time machine into the near future—one where AI doesn’t just assist or augment human work, but fully surpasses it.

The Timeline

The full AI 2027 report is a richly detailed scenario—I highly recommend reading the entire document for its narrative depth and technical insight. But for your convenience, here’s a short summary of the projected milestones:

• Early 2027: AI systems exhibit superhuman coding performance, significantly accelerating the speed of R&D across industries.

• Mid-2027: The rise of autonomous AI researchers—agents that not only generate knowledge but guide their own experimentation.

• Early 2028: The arrival of superintelligence, where AI systems surpass human reasoning across most cognitive domains and begin automating their own advancement.

These milestones may sound dramatic. But as Kokotajlo points out, this trajectory is not entirely speculative—it's based on observed trends and informed extrapolation.

The Context

Some critics are understandably cautious, I am too. The AI 2027 report blends scenario modeling with speculative fiction, using storytelling to explore what such a world might look like economically, geopolitically, and technologically. But there’s a precedent: Kokotajlo’s 2021 scenario, What 2026 Looks Like, successfully anticipated several major AI developments, including the rise of foundation models and increasing concerns over alignment and capability control.

That track record makes this latest forecast harder to ignore.

From My Perspective: Urgency Without Panic

As someone engaged in the development and deployment of cutting-edge systems, AI 2027 reinforces a tension I’ve been feeling for a while: progress is happening faster than our institutional capacity to manage it. While much of our current work focuses on improving performance and capability, we’re simultaneously being pulled toward a horizon where control becomes the core challenge.

This is where alignment becomes not just a research goal, but an existential one. We need systems that are:

• Corrigible: Able to be corrected, redirected, or shut down when needed.

• Interpretable: Transparent in reasoning and behavior.

• Aligned: Consistently acting in ways that reflect human intentions and values.

These aren't theoretical concerns. If autonomous AI research agents become viable in the next 24 months—as AI 2027 suggests—they could begin amplifying their own capabilities in ways that outpace traditional oversight mechanisms. Governance, safety research, and inter-organizational coordination must scale in tandem with capability.

Governance Is No Longer Optional

The report also highlights the growing risk of international competition. If superintelligent systems are seen as strategic assets—on par with nuclear or cyber capabilities—the incentives for transparency and restraint could vanish overnight.

We’re already seeing early signals of this dynamic play out. Regulatory frameworks are emerging, but most remain reactive. One notable exception is the EU AI Act—the world’s first comprehensive AI regulation, recently passed in 2024. It categorizes AI systems by risk level and introduces obligations for transparency, safety, and accountability. While imperfect, it represents a serious attempt to get ahead of the curve and could serve as a template for other jurisdictions.

Still, no national policy—however well-crafted—can address global-scale risks on its own. That’s why now is the time to support international efforts for coordinated AI governance. We need robust frameworks, shared safety benchmarks, information-sharing protocols, and perhaps most critically, an ethos of restraint in deployment.

The AI 2027 scenario may be aggressive, but if it serves as a catalyst for thoughtful and collective preparation, it will have done its job.

Closing Thought

Whether or not you believe artificial superintelligence will emerge by 2027 or 2028, the scenario deserves attention. Preparing for high-impact possibilities—especially ones with irreversible consequences—is not alarmism. It’s responsibility.

The AI 2027 scenario also reminds us that the consequences won’t just be technical—they’ll be geopolitical. As AI becomes a central lever of economic and military power, the decisions made by national leaders, regulatory bodies, and international coalitions will shape the trajectory of the entire planet. That brings an added layer of responsibility to democratic processes: who we elect matters more than ever.

We can’t afford to treat AI governance as a niche policy issue. The people we put in power will increasingly be tasked with navigating technologies that could determine global stability, economic structure, and civil liberties. That means it's not just their responsibility to lead wisely—it's our responsibility to make sure we’re putting the right people in those positions.

If you haven’t read the report yet, I strongly recommend exploring it here:
ai-2027.com/scenario.pdf

We’re building the future right now. The question is: will we build it wisely?

After spending 15 transformative years in the ever-evolving San Francisco Bay area, returning to Italy has been an extraordinary personal and professional growth journey. It’s hard to believe a year has passed since my homecoming. This past year, I’ve gained valuable insights into the fascinating contrasts between Italy and Europe and their views on work and life.

There is so much to explore in this realm. I’ll begin with a small yet curious topic: the evolving Italian language. Having been born in Italy, speaking Italian is second nature to me, and my proficiency in English—honed over more than 30 years abroad—allows me to navigate between cultures effortlessly. Language is a living entity, constantly transforming, especially in the tech world, where English terms often supplant traditional Italian ones. I've encountered English words that take on different meanings in Italian, sparking moments of realization and connection.

For example, you might all know that "football" means American football in the S, while in the UK, it refers to what Americans call soccer. In Australia, "football" can mean Australian Rules Football (AFL), a different sport, but it can also refer to soccer, depending on the context. Thankfully, in Italy, we still use "Calcio" for football, so there’s no confusion!

Here are some English terms that I am still struggling with, especially in the tech field:

Governance

In Italian, terms like "governo" or "gestione" exist, but they don’t fully capture the meaning of "governance."

Governance means managing a project in tech projects. This includes controlling the scope and budget and making decisions. Governance helps engage stakeholders, reduce risks, and ensure results meet organizational goals. It also ensures that tech projects achieve business objectives, follow regulations, manage stakeholders well, and control risks.

In the U.S. tech sector, people often use different terms instead of "governance" to describe processes and management systems. While governance is important, here are some other common terms in U.S. tech:

Management: Often used in place of governance to describe the general administration or overseeing of operations, projects, or systems. Examples: Project, IT, Risk Management.

Oversight: This refers to supervising or monitoring activities to ensure compliance with standards or objectives, such as data Oversight and Compliance Oversight.

Control: More focused on enforcing rules, standards, or practices within an organization or system, for example, Access, Change, and Quality Control.

Strategy: Used when referring to the high-level planning and direction-setting aspects of technology or business systems. Including IT, Digital, and Cloud Strategy.

Compliance: It ensures that systems, processes, and operations adhere to legal, regulatory, or industry standards, such as compliance Programs, Security Compliance, and Data Compliance.

Framework: A structured set of guidelines or best practices to support decision-making and operations. Like the IT, Governance, and Security Framework.

Policy: Refers to the principles or guidelines that shape decision-making and behavior in a system or organization, such as Security, Privacy, and Data Management Policies.

Administration: Like management, system administration focuses on the practical aspects of running systems or processes, particularly in the tech and IT domains. Examples include system and network Administration.

Regulation: Refers to establishing and enforcing rules and standards, often in legal or compliance contexts—examples: Regulatory Compliance, Data, and Financial Regulation.

Risk Management: Identifying, assessing, and mitigating organizational or system risks. Examples include Cybersecurity and Operational Risk Management.

Though these terms are similar, they have specific meanings for managing technology in the U.S. tech industry. In Italy, “governance” is the preferred term for all areas of IT, data, cloud services, cybersecurity, and digital governance. This choice reflects the structured nature of Italy's tech landscape.

From what I have noticed so far, “Governance" Is Preferred in the Italian tech sector for the following reasons:

Global Consistency: The term "governance" is commonly used in the tech sector worldwide. Using it in Italy helps align with global frameworks, standards, and terminology, which is especially important for multinational organizations or those aiming for international compliance.

Formal and Technical Connotation: "Governance" suggests a structured, formal, and technical approach to managing complex IT and digital systems. Unlike more general terms such as "management" or "oversight," it implies a higher level of strategic decision-making and accountability.

Regulatory Alignment: Italy has stringent compliance requirements related to data privacy (e.g., GDPR) and cybersecurity. Consequently, governance is essential to ensure organizations manage their IT systems according to legal and ethical standards.

Clarity and Efficiency: In professional settings, the English word "governance" provides more precise and efficient communication than longer Italian phrases like "gestione delle risorse informatiche" (management of IT resources).

Software Factory

I find it hard to accept the term "software factory" because I spent most of my career in the US. This view comes from different historical and cultural backgrounds. In Italy, the word "fabbrica" was translated to "factory" to describe teams or departments that create software. The software industry has taken on industrial terms.

In Italy, "software factory" is commonly used in its original English form. It means a structured environment for software development that uses standardized tools and frameworks. This approach aims to improve efficiency, quality, and scalability.

Unlike the US, where the development approach is more flexible, software factories in Italy have strict frameworks and clear roles. Creating software is treated like a manufacturing process. The term represents a systematic way to develop software in Italy, focusing on repeatable processes and scalability. There are fewer software product companies in the US. In Italy, many software projects, especially large or government ones, are outsourced. This reflects a need for predictability and standardization, showing an industrial engineering view of software development. This contrasts with the agile, startup-focused culture in the US tech scene.

So, in Italy, "software factory" refers to a more formal, structured, and industrial approach compared to the flexible and casual US environment.

Smart Working

Although the term "smart working" is not commonly used in English, it reflects how languages adapt borrowed terms to local cultures and laws. I don't mind this term; I'm starting to like it and find it entertaining.

In Italy, "smart working" describes flexible work arrangements that do not depend on location, such as remote, hybrid, and telecommuting options. After the pandemic, "smart working" became popular after the legislation called Lavoro Agile gave it legal recognition. Now, it is viewed as modern and innovative.

In English-speaking countries, "remote work" is the standard term, but Italy prefers "smart working," especially after the pandemic. This term shows a cultural change toward productivity, collaboration, and the use of technology beyond just working from home.

Product Owners and Product Managers

Overlap in job titles is not just an Italian issue; I have seen it across Europe.

The Product Owner and Product Manager in Europe have different and specific duties. In the U.S., the Product Owner is a Scrum team member, while the Product Manager is the primary job title for leading product strategy.

The Product Manager role is broader and includes both strategy and execution tasks. U.S. companies often use the PM title to combine these roles, while European companies usually keep them separate. This distinction can be confusing if you are used to the U.S. system.

For example, companies like Google and Amazon use "Product Manager" for both strategic and tactical roles but use "Product Owner" for focused execution. In Europe, organizations like Spotify typically separate these roles, with PMs focusing on strategy and POs managing execution.

To my understanding, the key Differences Between Product Manager and Product Owner are:

Product Manager (PM):

• Scope: Oversees the product’s vision, strategy, and lifecycle.

• Focus: Aligns business objectives, customer needs, and market opportunities.

• Responsibilities:

  • Defines product strategy and roadmap.

  • Engages with stakeholders and executives.

  • Balances priorities to maximize value for the business and customers.

• Context: A high-level, strategic role found across industries, regardless of methodology.

Product Owner (PO) in Europe:

• Scope: Tactical role focused on execution within Agile or Scrum frameworks.

• Focus: Manages and prioritizes the product backlog to maximize value delivery.

• Responsibilities:

  • Maintains and refines the backlog.

  • Acts as the primary point of contact for the development team.

  • Ensures alignment with the Product Manager’s vision.

• Context: Recognized as a distinct job title in Agile organizations, often reporting to a PM.

Product Owner (PO) in the U.S.:

• Scope: A role within a Scrum team rather than a formal job title.

• Focus: Prioritizes tasks and manages the backlog as part of their Scrum responsibilities.

• Responsibilities:

  • Works collaboratively with stakeholders and developers.

  • Focuses on execution rather than high-level strategy.

• Context: Typically, a responsibility is assigned to someone already in another role, such as a Product Manager or Business Analyst, rather than a dedicated position.

Why the title of "Product Manager" is more common in the U.S.:

Broader Applicability: PM is a universal title used across industries and methodologies.

Strategic Focus: U.S. companies often prioritize strategic roles like PM over execution-focused roles like PO.

Agile Nuances: Many U.S. companies blend Agile with other methodologies, making PM a more adaptable title.

Market Familiarity: PM predating Agile has been entrenched in U.S. business terminology for decades.

Welfare

In Italy, "welfare" often refers to employee benefits that improve workers' well-being. These benefits help create a happier workplace and boost productivity. Examples include health insurance, meal vouchers, childcare support, gym memberships, transportation help, and access to cultural or recreational activities. Italian welfare aims to support a good work-life balance, often influenced by government programs or labor agreements.

In the U.S., "welfare" has a different meaning. It usually refers to government programs that assist low-income individuals or families with their basic needs. These programs include food stamps, Medicaid, unemployment benefits, and housing support. In this context, welfare acts as a safety net, giving financial aid, healthcare, and other essential services to those in need.

Key Differences:

1. Scope of Benefits:

   • Italy: Focuses on enhancing employees’ well-being and productivity through company-provided programs.

   • U.S.: Provides essential support to those in financial hardship through government assistance.

2. Provider:

   • Italy: Welfare is typically employer-driven and tied to workplace policies or labor contracts.

   • U.S.: Welfare is managed and funded by federal, state, or local governments.

3. Perception:

   • Italy: Seen as a positive, forward-thinking initiative to attract and retain talent and promote corporate social responsibility (CSR).

   • U.S.: Often viewed as a lifeline for individuals in need, but also a topic of political debate around its role, scope, and impact.

4. Cultural Implication:

   • In Italy, the term welfare aziendale reflects the country’s strong focus on employer responsibility and social cohesion within the workplace.

   • In the U.S., welfare evokes broader societal issues around poverty and inequality and the government’s role in addressing them.

The different meanings of the term "welfare" show how it can change based on a country's social and economic needs and culture. In Italy, welfare focuses on improving well-being in the workplace. In contrast, in the U.S., it emphasizes the government's responsibility to support vulnerable groups.

Competence Center

Competence Centers are specialized hubs in Italy that focus on expertise, innovation, and research. They play a key role in technology, academia, and business and act as central resources for advanced knowledge and development. The term became popular through government programs like Industria 4.0, which established Centri di Competenza to help businesses adopt new technologies. These centers often work through public-private partnerships and are considered prestigious institutions representing modernity, specialization, and collaboration.

The term “Competence Center” is rarely used in the U.S. In American English, “competence” refers more to individual skills than an organization's expertise. Americans typically use terms like “Center of Excellence, “Innovation Hub,” or “Research Center” to describe similar entities. These terms better fit U.S. cultural and linguistic norms, focusing on innovation and collaboration without the ambiguity of “competence.”

The difference between the terms reflects European influences on the Italian language. In Italy, "competence" suggests collective organizational expertise, similar to "Kompetenzzentrum" in Germany. Italians often adopt translations from EU policies, shaping their local language. The Competence Center conveys modernity, specialization, and professionalism in Italy, making it appealing in tech and industrial fields.

While Competence Center is a respected term in Italy and Europe, Americans prefer alternative names like Center of Excellence, Innovation Lab, or Research Center.

The use of the Competence Center in Italy shows its connection to global trends and a professional outlook. However, the different terms highlight how language evolves in various cultures worldwide.

Wrapping it up…

Italy closely follows global technology trends, even though it has some unique terminology. Job titles such as software engineer, developer, and data scientist are common and easily recognized in Italy, just as in the U.S. and Europe.

Here are some general reasons why English terms are used in Italy:

1. Global Industry Standard: English terms are often adopted in tech to align with global trends and are recognized internationally. Even if they do not always have the same meaning elsewhere.

2. Professional Appeal: Using English terms makes the field sound modern and aligned with cutting-edge practices.

3. Brevity and Clarity: Unlike longer Italian translations, the original term is concise and easily understood in the tech industry.

4. Cultural Adaptation: English terms are often used in technology and innovation due to their association with Anglo-American practices.

The good news is that Italian engineering teams are as skilled as those in Silicon Valley or Germany. After many years of experience in both places, I can confirm Italy is strong in the technology industry. Italian teams' mix of creativity, social skills, and entrepreneurial spirit makes them unique.

Even though we use terms like “software factories,” I like that our work is not just a simple assembly line process. Italian teams are very skilled and are not restricted by strict rules. Freedom and creativity are essential in an industry that relies on innovation.

After a year of returning, I appreciate being part of Italy’s lively work scene again. Although the language around work has changed—terms like governance, “Fabbrica,” and smart working are now common—the heart of Italian culture is still creativity, passion, and a strong sense of community. It feels great to be back home, and I hope this message encourages you to consider returning or moving to Italy.

If you’re still with me, it’s clear you find this topic intriguing. I’d love to hear your thoughts! Do you have your own experiences to share? Do you see things differently, or is there more you’d like to dive into? Let’s chat!

If you need help, feel free to contact me anytime! Have I mentioned that TeamSystem is looking for new talent?

In an increasingly digital world, the intersection of art and technology has become a fascinating playground for creativity. The CODAME ART+TECH Festival is more than just an event—it's a movement designed to bridge the gap between artists and technologists, encouraging collaboration and innovation. Now that I've moved to Milan, it felt like the perfect place to expand CODAME’s vision, blending the city’s rich cultural tradition with its growing tech scene. Milan, a global hub for fashion, art, and design, offers the perfect backdrop for fostering creative energy, making it a natural choice for the festival’s next step.

A Bit of History

CODAME began in San Francisco, a city renowned for its technological innovation and vibrant art scene. Since its inception, the festival has brought together some of the brightest minds in both fields, blending cutting-edge tech with artistic expression. As I transitioned to life in Milan, it was clear that this city was ready to host the ART+TECH Festival, continuing the tradition of cross-cultural collaboration.

What’s Coming Up?

This October, CODAME ART+TECH Festival 2024 in Milan will host a series of exciting events exploring the intersection of art and technology. Here’s what’s on the calendar:

• October 3rd: Is this Art?

  The festival kicks off with an Experiential Dialog to explore the fundamental question, “Is this art?” followed by MatchBox Speed Dating—a unique opportunity for artists and technologists to meet and collaborate. As always, BYOB (Bring Your Own Beamer) will give attendees the chance to showcase their digital art.

• October 25th: Are you connected?

  This event will feature an Experiential Dialog on connection in the digital age, along with MatchBox Presentations showcasing projects born from our collaborations. Attendees can once again bring their art to share in our BYOB segment.

• October 31st: Are you smarter than me?

  Halloween is for more than just costumes! This night will feature an Experiential Dialog around intelligence in the digital world, a MatchBox Show, and BYOB. To wrap it up, we’ll celebrate with live music and a costume party!

Connecting San Francisco and Milan

This festival is a tangible bridge between San Francisco, where CODAME was born, and Milan, my new home. It’s more than just a series of events—it’s an opportunity to foster global connections through creativity, art, and technology. We hope CODAME ART+TECH Festival will inspire other cities to join in the future, building a worldwide network of collaborative innovation.

See You Soon, Milan!

We can’t wait to kick off this unique exploration of art and technology on October 3rd. Whether you're from San Francisco, Milan, or beyond, this festival is a call to creators everywhere to come together. Don’t forget to bring your art, your prefered tools, devices, projectors, and your creative spirit to the event—BYOB is all about showcasing art in its many forms!

For the full program and more details, check codame.com

The event is free, but donations are greatly appreciated. Thank you 🙏 for supporting ART+TECH. All profits will be shared with the artists.

Tickets

I am grateful for the opportunities and the people from diverse backgrounds and cultures I have met who have shaped my path and career. The interweaving of human connections is a beautiful aspect of this global journey driven by curiosity and a thirst for learning.

I am thankful for the recent 15 years I spent in the San Francisco Bay area, which has become my second home. I was honored to witness the growth of Silicon Valley, from Apple's coming back to Google and Facebook's becoming giants from startups to Salesforce's leading cloud enterprise space. It does not stop there; companies like Tesla and Nvidia combine hardware and software, and startups like OpenAI continue to impact innovation and growth in the area, making the Bay area, with its unique and special culture, one of the most innovative places and exceptionally human places on Earth.

It is difficult to leave San Francisco, but returning to Italy means more than a professional move. It's a chance for my family to reunite and my children to experience Italian culture and a broader European lifestyle. Returning to Italy is not just a homecoming; it's an opportunity to inspire and be inspired, learn, and foster innovation and growth.

I am thrilled to announce that I have recently joined TeamSystem as their new Chief Technology Officer. TeamSystem is a company that provides digital solutions, innovative software products, and platforms for small to medium-sized businesses. Originally founded in Italy, it is now expanding throughout Europe. I am honored to be part of a team with a growth mindset committed to providing TeamSystem customers with the best technological solutions and products. I am excited to contribute to the company's success and be a part of its continued growth.

I will also continue growing internationally, starting from Italy, the non-profit organization I co-founded with in San Francisco in 2010. Milan, be ready for some more ART+TECH!

Since moving to Milan, I've discovered a hidden gem: a city where efficiency, creativity, and a driven culture thrive. Milan combines Italian warmth with an international environment, art, design, great food, and unique culture.

I look forward to continuing this journey from where it all began, building upon the foundation of Italian culture and merging it with global experiences to make a positive impact. I want to extend an open invitation to friends and colleagues. If you are in Europe, let's reconnect and explore the many opportunities that await us. We are also hiring!

In the quest for creativity, the most formidable obstacles often reside within ourselves. Recognizing and confronting these detrimental thoughts and habits can pave the way for unfettered achievements and fulfillment. Creativity isn't merely a goal; it's an ongoing journey of exploration and invention. Welcome obstacles as opportunities, build resilience, and allow your inventive spirit to transcend self-imposed constraints. 

Rick Rubin, in his insightful book "The Creative Act: A Way of Being" particularly in the chapter titled "Habits," explores these internal barriers to creativity and offers insights into overcoming them. From procrastination and self-doubt to perfectionism and fear of failure, Rubin delves into the common pitfalls that can sabotage our creative endeavors.

While originating in the music industry, Rubin's philosophies and insights possess a universal appeal that extends far beyond the realm of artists. His wisdom transcends boundaries and resonates with individuals across diverse fields and disciplines. Whether you're an engineer, entrepreneur, educator, or creative professional, Rubin's principles offer valuable guidance for navigating the complexities of your respective industries and unlocking your full potential. 

Regardless of the nature of the creative task—be it writing a novel, painting, composing music, coding, or executing other inventive endeavors—we face numerous hurdles that can disrupt our progress and creativity. These barriers often emerge from our detrimental thoughts and habits, curbing our creative flow and efficiency.

In the world of tech, product development, and software engineering, creativity is not just a luxury but a necessity for driving innovation and staying ahead of the curve. However, along this innovation journey, we often encounter numerous obstacles that threaten our progress. Whether writing code, designing user interfaces, or brainstorming new features, we must navigate these obstacles to unlock our full creative potential.

1. Believing you’re not good enough.

2. Feeling you don’t have the energy it takes.

3. Mistaking adopted rules for absolute truths.

4. Not wanting to do the work (laziness).

5. Not taking the work to its highest expression (settling).

6. Having goals so ambitious that you can’t begin.

7. Thinking you can only do your best work in certain conditions.

8. Requiring specific tools or equipment to do the work.

9. Abandoning a project as soon as it gets difficult.

10. Feeling like you need permission to start or move forward.

11. Letting a perceived need for funding, equipment, or support get in the way.

12. Having too many ideas and not knowing where to start.

13. Never finishing projects.

14. Blaming circumstances or other people for interfering with your process.

15. Romanticizing negative behaviors or addictions.

16. Believing a certain mood or state is necessary to do your best work.

17. Prioritizing other activities and responsibilities over your commitment to making art.

18. Distractibility and procrastination.

19. Impatience.

20. Thinking anything that’s out of your control is in your way.

This post explores Rubin's strategies for Artists to mitigate these self-imposed barriers within software engineering teams. Identifying and tackling these internal obstacles set the stage for unrestrained innovation and fulfillment in our professional endeavors.

Let's embark on this exploration of creativity together, ready to tackle the hurdles and learn how to elevate our creative capacities beyond the confines we've set for ourselves.

—

1. Believing you’re not good enough.

Self-doubt is a common adversary for any creative job. The belief that our work is not good enough can paralyze us, preventing us from even starting or completing a project. Software engineers are often tasked with solving complex problems, writing efficient code, and delivering high-quality software products within tight deadlines. However, self-doubt can undermine confidence and hinder the ability to perform at one's best.

Like other creative endeavors, self-doubt in software engineering can manifest as a paralyzing fear of failure or inadequacy. Engineers may hesitate to start or complete a project, second-guess their decisions, or feel overwhelmed by the perceived gap between their skills and expectations. This can lead to procrastination, imposter syndrome, and a negative feedback loop that reinforces feelings of inadequacy.

To overcome self-doubt in software engineering teams, it's crucial to recognize and challenge the validity of the inner critic. This involves reframing negative thoughts and cultivating self-compassion. Instead of dwelling on perceived shortcomings or failures, engineers should celebrate their successes and acknowledge their progress, no matter how small. Recognizing achievements, whether solving a challenging problem, writing clean and efficient code, or delivering a successful software release, can help boost confidence and motivation.

Furthermore, surrounding oneself with supportive peers and mentors can provide invaluable guidance and encouragement. Software engineering is often a collaborative endeavor, and having a network of colleagues who can offer constructive feedback and moral support can help combat feelings of self-doubt. Peer code reviews, team retrospectives, and mentorship programs can all contribute to a positive and nurturing work environment where team members feel valued and supported.

Additionally, embracing the iterative nature of the software development process is essential for overcoming self-doubt. Software engineering is inherently iterative, with code being continuously tested, refined, and improved over time. By embracing this iterative mindset and viewing mistakes as opportunities for growth and learning, engineers can overcome perfectionism and fear of failure. Instead of striving for perfection, focus on delivering incremental improvements and learning from each iteration.

Confidence in one's abilities is crucial to success in software engineering and any other profession or task undertaken.

2. Feeling you don’t have the energy it takes.

Creativity requires physical and mental energy. However, it's easy to fall into the trap of feeling drained or lethargic, especially when faced with daunting tasks. Whether coding late into the night, crafting a novel, or tackling a demanding project at work, maintaining optimal energy levels is essential for sustaining creativity and productivity. 

Creativity is a multifaceted process that draws upon both physical and mental faculties. It requires sharp cognitive abilities and physical stamina to sustain prolonged, focused effort. However, it's too easy to neglect our physical well-being when immersed in our work, leading to fatigue and burnout.

Software engineers are often tasked with tackling complex problems, writing code, and collaborating with team members to deliver high-quality software products, requiring high cognitive function and mental stamina. Maintaining optimal energy levels is essential for sustaining creativity and meeting project deadlines effectively.

Engineers must be able to think critically, problem-solve, and write clean and efficient code for extended periods. However, feeling drained or lethargic can impede cognitive function, decreasing productivity and creativity.

To combat feelings of low energy and enhance creativity, it's crucial to prioritize both physical and mental well-being. Cultivating habits that promote physical health, such as regular exercise and adequate sleep, can replenish energy reserves, boost creative stamina, and tackle even the most daunting tasks with renewed vigor and enthusiasm.

Creativity thrives in a healthy body and mind, so prioritizing self-care is essential for unleashing creative potential in product software engineering development.

3. Mistaking adopted rules for absolute truths.

This encapsulates the tendency to become overly reliant on established norms or conventions, treating them as immutable laws rather than flexible guidelines.

Best practices often serve as valuable frameworks for achieving specific outcomes. However, when these guidelines are rigidly adhered to without question, they can inhibit creativity and limit the potential for exploration and discovery. Unquestioningly adhering to these standards without considering alternative approaches can limit the potential for innovation and creativity in problem-solving. 

Teams often rely on established frameworks, coding standards, and development methodologies to streamline processes and ensure project consistency. While these guidelines serve a valuable purpose in promoting efficiency and maintaining code quality, adhering to them without question can lead to stagnation and missed opportunities for improvement.

Software engineering is a rapidly evolving field where new technologies, methodologies, and approaches emerge regularly. The trap of mistaking adopted rules for absolute truths arises when team members become overly reliant on established norms, treating them as the only valid approach to problem-solving. This mindset can discourage team experimentation, critical thinking, and creativity.

To overcome this challenge, software engineering teams must cultivate a mindset of curiosity, experimentation, and open-mindedness. Instead of unthinkingly following established norms, team members should actively question them, challenge conventional wisdom, and explore alternative approaches to problem-solving.

Encouraging a culture of innovation and risk-taking within the team can help break free from the constraints of conformity and unleash creativity. This may involve creating opportunities for brainstorming sessions, hackathons, or experimentation with new technologies and methodologies.

Furthermore, fostering an environment where feedback is welcomed and constructive criticism is encouraged can help challenge entrenched beliefs and promote continuous improvement. By embracing diversity of thought and encouraging collaboration, software engineering teams can leverage their members' collective wisdom and creativity to drive innovation and achieve success.

By cultivating a mindset of curiosity, experimentation, and open-mindedness and fostering a culture of innovation and risk-taking, teams can break free from conformity and unleash their full creative potential.

4. Not wanting to do the work (laziness).

Procrastination and laziness pose significant team challenges, hindering productivity, creativity, and project success. Overcoming these obstacles requires a concerted effort to cultivate discipline, motivation, and effective time management strategies.

Procrastination, characterized by avoiding tasks or delaying essential responsibilities, is a common phenomenon that can derail even the most motivated individuals. Whether scrolling through social media, succumbing to distractions, or simply feeling overwhelmed by the enormity of a project, procrastination can undermine progress and impede creative problem-solving.

Similarly, laziness, a reluctance to exert effort or engage in productive activities, can hinder productivity and stifle team innovation. It often manifests as a preference for comfort and leisure over the rigors of challenging work, leading to missed deadlines, subpar performance, and, ultimately, dissatisfaction with outcomes.

By implementing these strategies and fostering a culture of discipline, motivation, and accountability, software engineering teams can unleash their creativity and achieve their goals with greater efficiency and success. The path to innovation and excellence requires dedication, perseverance, and a willingness to push through challenges, even when motivation wanes.

Creating a Structured Routine: Establishing a structured routine helps to create a sense of order and consistency, making it easier to resist the temptation of procrastination and laziness.

Breaking Tasks into Smaller Steps: Breaking tasks into smaller, more manageable steps makes them feel less daunting and more achievable. This can help overcome the inertia of starting a new project or task.

Using Time Management Techniques: Techniques such as the Pomodoro Technique, which involves working in short, focused bursts with regular breaks, can help maintain productivity and focus.

Eliminating Distractions: Identifying and removing distractions, such as social media, email, or noisy environments, can help create a climate conducive to creativity and productivity.

Practicing Self-Compassion: Recognizing that procrastination and laziness are everyday human experiences can help alleviate guilt or shame associated with these behaviors. Practicing self-compassion and forgiveness can help overcome barriers to productivity and creativity.

Seeking Accountability: Sharing goals and progress with others can provide external accountability and motivation to stay on track. Whether through a mentor, coach, or supportive peer group, accountability can help overcome procrastination and laziness.

Rewarding Progress: Celebrating small victories and milestones can help maintain motivation and momentum. Rewards can be as simple as taking a break, treating yourself to a small indulgence, or engaging in a favorite hobby.

5. Not taking the work to its highest expression (settling).

Settling for mediocrity robs us of the opportunity to realize our vision fully. Strive for excellence in every aspect of your work, pushing boundaries and relentlessly pursuing improvement. When we decide for less than our best, we deprive ourselves of the opportunity to fully realize our vision and potential. Instead of pushing ourselves to reach new heights of excellence, we resign ourselves to complacency, where progress stagnates and creativity suffers.

Software engineers are tasked with developing cutting-edge solutions, optimizing performance, and delivering exceptional user experiences. However, when team members settle for less than their best, they deprive themselves of the opportunity to realize their vision and potential fully.

Settling for mediocrity in software engineering can manifest in various ways, such as accepting subpar code quality, compromising performance optimization, or delivering features that fall short of user expectations. It often stems from a fear of failure, a reluctance to challenge the status quo or a lack of confidence in one's abilities.

Fostering a culture of excellence and a relentless commitment to continuous improvement is crucial to overcoming the tendency to settle for mediocrity in software engineering teams. Here are some strategies to elevate the work of software engineers to its highest expression:

Clarify Your Vision: Articulate your vision and goals. What do you hope to achieve with your work? What standards of excellence do you aspire to uphold? Clarifying your vision provides a roadmap for pursuing excellence and constantly reminds you of your goals.

Set High Standards: Raise the bar for yourself and set high standards of excellence in every aspect of your work. Challenge yourself to exceed expectations, push boundaries, and surpass your previous achievements. Don't settle for mediocrity when greatness is within reach.

Embrace Continuous Learning: Commit to lifelong learning and growth. Seek opportunities to expand your knowledge, develop new skills, and explore different techniques and approaches. Embrace positive and constructive feedback as a catalyst for improvement and innovation.

Push Beyond Comfort Zones: Don't shy away from challenges or opportunities that push you out of your comfort zone. Embrace discomfort as a sign of growth and a pathway to excellence. Pushing beyond your perceived limits allows you to discover new possibilities and expand your creative horizons.

Practice Diligence and Persistence: Excellence is not achieved overnight but through consistent effort and perseverance. Practice diligence in your work, paying attention to minor details and striving for precision and accuracy. Be persistent in the face of setbacks and obstacles, knowing every setback is an opportunity to learn and grow.

Seek Inspiration and Role Models: Surround yourself with sources of inspiration and seek out role models who exemplify excellence in your field. Study the work of master artists, innovators, and trailblazers who have pushed the boundaries of creativity and achieved remarkable success. Learn from their examples and let their achievements inspire you to reach new heights in your work.

Greatness is not achieved by chance but through deliberate effort, unwavering determination, and a relentless pursuit of excellence.

6. Having goals so ambitious that you can’t begin.

In the fast-paced world of tech, setting ambitious goals is essential for driving innovation, pushing boundaries, and achieving remarkable results. However, ambitious goals can also feel overwhelming if not approached strategically. When faced with lofty objectives, such as developing groundbreaking software, revolutionizing user experiences, or spearheading complex projects, the sheer magnitude of the task ahead can be daunting.

To overcome the paralysis of indecision and make progress toward ambitious goals, software engineering teams must adopt a systematic approach that breaks down the overarching objective into smaller, more manageable tasks. By breaking the goal into smaller components, teams can gain clarity on the necessary steps and allocate resources effectively. This approach makes the goal more attainable and empowers team members to take concrete actions that move them closer to their objectives.

Moreover, taking incremental steps forward is critical to building momentum and overcoming inertia within software engineering teams. Rather than waiting for the perfect moment or feeling overwhelmed by the enormity of the task, team members can embrace a mindset of continuous progress and improvement. By consistently making progress, even in small increments, teams can maintain forward momentum and navigate the complexities of ambitious projects more effectively.

Furthermore, software engineering teams must remain adaptable and responsive to changes in the technological landscape. In a rapidly evolving industry, goals and priorities may need to be adjusted to accommodate new developments, emerging trends, and shifting market demands. By remaining flexible and open to change, teams can ensure their ambitious goals remain relevant and aligned with the organization's broader objectives.

Celebrating each accomplishment along the way, no matter how minor, is crucial for maintaining morale and motivation within software engineering teams. Recognizing and acknowledging progress reinforces positive behaviors and encourages team members to stay committed to their goals, even in the face of challenges and setbacks.

7. Thinking you can only do your best work in certain conditions.

It's easy to fall into the trap of waiting for the perfect moment, environment, or circumstances before embarking on a new endeavor. True creativity transcends external conditions and flourishes in the face of challenges and uncertainty. Learn to adapt and thrive amidst chaos and uncertainty.

One of the main reasons individuals may believe they can only do their best work in certain conditions is the desire for comfort and familiarity. We may feel more inspired or productive in a specific environment, such as a quiet room with natural light and familiar people we worked with before, or when we have a set routine or schedule. While these conditions can certainly be conducive to creativity, they are optional for innovation and our expression.

Creativity knows no bounds and can thrive in any environment, regardless of external circumstances. Some of the most groundbreaking works and innovations have emerged from periods of chaos, adversity, and uncertainty. Creativity often flourishes when we are forced to adapt and think outside the box, challenging our preconceived notions and pushing the boundaries of what is possible.

Instead of waiting for the perfect moment or environment, learn to embrace imperfection and find inspiration in unexpected places. Here are some strategies to help you thrive amidst chaos and uncertainty:

Embrace Flexibility: Cultivate a mindset of flexibility and openness to change. Instead of rigidly adhering to a specific routine or environment, be willing to adapt to different circumstances and make the most of the resources available.

Find Inspiration Everywhere:  Look for inspiration in unexpected places and embrace the beauty of imperfection. Creativity often thrives when we step outside our comfort zones and explore new ideas, perspectives, and experiences.

Practice Resilience: Develop resilience in adversity and setbacks. Instead of letting obstacles derail your creative process, use them as opportunities for growth and learning. Remember that setbacks are temporary and can often lead to breakthroughs and innovation.

Create a Portable Toolkit: Build a toolkit of portable resources and techniques that you can use to create anywhere, anytime. Whether it's a sketchbook, a digital tablet, or a portable instrument, having tools that allow you to create on the go can help you stay productive and inspired, no matter where you are.

Set Realistic Expectations: Recognize perfection is unattainable and creativity is a messy, iterative process. Set realistic expectations for yourself and your work, and be gentle with yourself when things don't go as planned. Remember that progress, not perfection, is the goal.

By embracing adaptability, resilience, and a willingness to create amidst chaos and uncertainty, you can overcome the belief that you can only do your best work in certain conditions. True creativity knows no bounds and thrives in the most unexpected of circumstances. So, don't wait for the perfect moment—seize the opportunity to create, innovate, and express yourself wherever you are.

8. Requiring specific tools or equipment to do the work.

This mindset often stems from the belief that specific tools or equipment are necessary for producing high-quality work. Whether it's the latest app, a state-of-the-art camera, or a professional-grade instrument, we may convince ourselves that we can only create with these resources. Creativity is a mindset and a willingness to explore, experiment, and innovate, regardless of the resources at hand.

While it's true that quality tools and equipment can enhance productivity and streamline workflows, placing too much emphasis on external gadgets or instruments can become a barrier to creative expression. Don't let a lack of resources become an excuse for inaction. Make do with what you have, and let your imagination soar.

By focusing too narrowly on the tools we believe we need, we risk overlooking the power of our imagination and resourcefulness. Instead of allowing a perceived lack of resources to become an excuse for inaction, we can choose to make do with what we have and let our imagination soar.

In many cases, limitations can fuel creativity by prompting us to think outside the box and find innovative solutions. Some of the most groundbreaking works of artists and startups have emerged from periods of scarcity and constraint, where individuals were forced to make the most of limited resources.

Moreover, embracing constraints can foster a spirit of creativity and experimentation. Rather than being hindered by what we lack, we can use limitations as a catalyst for creative exploration and problem-solving. There are endless possibilities for creative expression, even with limited resources.

The belief that specific tools or equipment are necessary for creativity is a limiting mindset that can hold us back from reaching our full potential. By shifting our focus from external resources to internal creativity, we can unlock new levels of innovation, inspiration, and fulfillment in our work. So, don't let a lack of resources excuse inaction. Make do with what you have, and let your imagination take flight.

9. Abandoning a project as soon as it gets difficult.

Challenges are inevitable in any project. Whether encountering technical roadblocks, facing design challenges, or navigating complex requirements, every project is bound to experience setbacks. However, how we respond to these challenges ultimately determines our success. Instead of succumbing to frustration or self-doubt when faced with difficulties, viewing them as opportunities for growth and learning is essential. Instead of succumbing to frustration or self-doubt when faced with problems, view them as opportunities for growth and learning. 

Perseverance is critical to overcoming obstacles and realizing your vision. By pushing through challenges and staying committed to your project, you build resilience and deepen your skills and understanding as a creative individual. Every setback is an opportunity to learn something new, refine your approach, and ultimately create something that exceeds your initial expectations.

Moreover, abandoning a project as soon as it gets difficult can become a self-perpetuating cycle. By constantly jumping from one project to another, you may only partially develop your ideas or see them through to fruition. This can lead to unfulfillment and dissatisfaction with your work.

Instead, embrace the challenges that arise in your projects and approach them with a growth mindset. Seek feedback and advice from peers or mentors who can offer fresh perspectives and insights. And most importantly, stay committed to your vision and trust in your ability to overcome any obstacle that comes your way.

Don't be afraid to embrace the difficulties that come your way. They are not roadblocks but stepping stones on your creative journey.

10. Feeling like you need permission to start or move forward.

You don't require anyone's validation or approval to create. Allow yourself to follow your creative impulses and trust your unique voice and vision. In a field where collaboration and teamwork are paramount, it's essential for individuals to feel empowered to propose their ideas and insights.

Creativity is inherently personal and subjective, and each member of a software engineering team brings their unique perspective and expertise to the table. Allowing oneself to follow creative impulses and trusting in one's unique voice and vision is essential for unleashing the full creative potential of the team.

Waiting for permission from others can lead to self-doubt and hesitation, hindering the team's ability to take risks and explore new avenues of creativity. This fear of judgment can stifle innovation and limit the team's ability to push boundaries and challenge the status quo.

While seeking feedback and guidance from teammates and stakeholders can be valuable in the creative process, individuals must trust their instincts and intuition. Each team member should feel empowered to contribute their ideas and perspectives without fear of judgment or reprisal.

Moreover, team members must respect and value each other's contributions in a collaborative environment. While individual creativity is essential, so is the ability to work together towards a common goal. By fostering a culture of trust, respect, and open communication, software engineering teams can create an environment where creativity can flourish and innovation can thrive.

The most critical permission comes from within oneself. By trusting in their creative instincts and allowing them to explore without fear of judgment, team members can unlock new levels of innovation and drive success in their projects. So, don't wait for permission to start or move forward—trust in yourself and your team, and let your creativity soar.

11. Letting a perceived need for funding, equipment, or support get in the way.

It's easy to fall into the trap of believing we need the perfect circumstances or resources to create meaningful work. Maximize what you have instead of letting a perceived lack of resources hold you back. Get creative with your materials, seek alternative funding options, and remember that some works were created with limited resources.

The perceived need for funding, equipment, or support can often be a significant stumbling block to progress in the tech industry. It's imperative to recognize that true innovation and creativity transcend the limitations of resources and circumstances. 

It's all too common to fall into the trap of believing that only with ample funding, top-of-the-line equipment, or extensive support can meaningful work be accomplished. Yet, history is filled with examples of groundbreaking innovations that emerged from humble beginnings and limited resources.

Creativity thrives in environments where constraints exist. Within these constraints, individuals must think outside the box, innovate, and find novel solutions to complex problems.

Instead of waiting for the perfect set of circumstances to materialize, it's essential to maximize the resources at hand and dive headfirst into creative projects. Whether it's making the most of existing tools and equipment, seeking alternative funding options, or leveraging the team's collective expertise, numerous ways exist to overcome resource constraints and drive innovation.

Moreover, it's crucial to adopt a mindset of resourcefulness and creativity. Encourage team members to think creatively about how to make the most of available resources, whether by repurposing existing technology, adopting lean methodologies, or collaborating with external partners.

Software engineers can unlock their full potential and achieve remarkable results by reframing limitations as opportunities for innovation and creativity. After all, the most valuable resource at their disposal is not funding or equipment—it's their ingenuity and creativity. So, instead of letting perceived barriers hold them back, let them serve as springboards for innovation and progress.

12. Having too many ideas and not knowing where to start.

Having a wealth of ideas can be both a blessing and a curse. It's easy to feel overwhelmed by the sheer number of possibilities and struggle to choose where to begin. To overcome this hurdle, try brainstorming sessions or mind-mapping exercises to organize your thoughts. Break down your ideas into smaller, more manageable chunks, and prioritize them based on feasibility and impact. These techniques can help us visualize our ideas and make connections between them, making it easier to identify common themes or areas of interest. By getting our ideas out of our heads and onto paper or whiteboard, we can gain clarity and focus on which ideas are worth pursuing further.

Once we have a clearer picture of our ideas, we must break them down into smaller, more manageable chunks. This process can involve breaking larger projects into smaller tasks or outlining the steps needed to bring an idea to fruition. Breaking our ideas into actionable steps can make the creative process more manageable and less daunting.

Prioritization is another crucial aspect of overcoming the challenge of having too many ideas. Not all ideas are created equal, and it's essential to identify which ones are most worthy of our time and attention. One way to prioritize our ideas is to consider their feasibility and potential impact. Given our current resources and constraints, which ideas are most realistic? Which ideas have the potential to make the most significant impact or align most closely with our goals?

It's better to start somewhere than to be paralyzed by indecision, embrace imperfection, take action, and trust in the creative process to guide you forward.

13. Never finishing projects.

Starting a new project is often met with excitement and enthusiasm as team members dive into brainstorming sessions, creativity, and initial planning. However, as the project progresses, challenges may arise, motivation may wane, and team members may lose steam; however, seeing it through to completion is where the real magic happens. Completing projects demonstrates the team's capabilities and builds confidence and momentum for future endeavors.

In the world of software development, this can be particularly detrimental. Incomplete projects represent wasted time and resources and hinder the team's ability to deliver value to users and stakeholders. To ensure the successful completion of projects, tech product teams need to address this tendency head-on.

One effective strategy is to set realistic goals and deadlines from the project's outset. By clearly defining project objectives and establishing achievable milestones, teams can create a roadmap that guides their progress and keeps them on track. These goals and deadlines serve as a framework for accountability, motivating team members to stay focused and committed to the project's success.

As mentioned earlier, also in this case, breaking larger projects into smaller, more manageable milestones is another valuable approach. This allows teams to track progress more effectively and provides opportunities for regular checkpoints and course corrections. By celebrating each milestone achieved, whether it's the completion of a feature, a successful sprint, or a key deliverable, teams can maintain momentum and morale throughout the project lifecycle.

Additionally, fostering a culture of accountability within the team is essential for combating the tendency to abandon projects prematurely. By holding each other accountable for meeting deadlines and delivering on commitments, team members can support one another in staying motivated and on track. Regular check-ins, progress updates, and retrospective meetings can allow team members to assess their progress, identify obstacles, and collaborate on solutions.

14. Blaming circumstances or other people for interfering with your process.

It's tempting to blame external factors for our creative blocks or lack of progress. Whether it's a noisy environment, a demanding schedule, or unsupportive friends or family, it's easy to point fingers instead of taking ownership of our journey. Instead of playing the blame game, focus on what you can control. Set boundaries to protect your creative time, find ways to adapt to your environment, and surround yourself with supportive allies who encourage your creative pursuits.

In the context of tech product teamwork, blaming circumstances or other people for interference with the creative process can manifest in various ways. It might involve attributing delays or setbacks to external factors such as tight deadlines, limited resources, or conflicting organizational priorities. Alternatively, team members may blame colleagues for perceived inefficiencies or lack of collaboration, leading to tension and discord. However, the reality is that while external factors may present challenges, it's ultimately up to individuals and teams to take ownership of their creative journey and overcome obstacles. Instead of playing the blame game, tech product teams can adopt a mindset of accountability and resilience to navigate challenges effectively.

Surrounding oneself with supportive allies can provide invaluable support and inspiration. Whether seeking feedback and mentorship from experienced colleagues or fostering a culture of collaboration and camaraderie within the team, having a solid support network can help individuals and teams stay motivated and resilient in the face of adversity. 

Success lies in embracing accountability, resilience, and collaboration to overcome obstacles and achieve creative and innovative goals.

15. Romanticizing negative behaviors or addictions.

There's a dangerous myth that creativity and suffering go hand in hand. Artists may believe that indulging in negative behaviors or addictions will enhance their creative output. However, this couldn't be further from the truth. In reality, these behaviors hinder creativity and sabotage our well-being. Instead of romanticizing negative habits, prioritize self-care and cultivate healthy habits that nourish your mind, body, and spirit.

In engineering teams, it can significantly threaten individual well-being and team productivity. While creativity is often associated with thinking outside the box and pushing boundaries, there is a dangerous myth that creativity and suffering go hand in hand. Some may believe indulging in negative behaviors such as excessive work hours or unhealthy lifestyle choices will enhance their productivity. It can create a toxic work culture within teams, where stress and pressure are glorified, and self-destructive habits are normalized. This can lead to increased absenteeism, turnover, and interpersonal conflicts, ultimately undermining team cohesion and effectiveness.

Engineering teams must prioritize self-care and cultivate healthy habits that nourish the mind, body, and spirit to combat this tendency. This includes promoting work-life balance, encouraging regular breaks and time off, and providing resources for mental health support. By prioritizing employee well-being, organizations can create a supportive work environment where team members feel valued, motivated, and empowered to do their best work.

Fostering a culture of collaboration and open communication within teams can help mitigate the adverse effects. By encouraging team members to share their challenges and seek support from colleagues, organizations can create a sense of camaraderie and solidarity that fosters resilience and creativity.

16. Believing a certain mood or state is necessary to do your best work.

It's a common misconception that we must be in a certain mood or emotional state to produce our best work. While it's true that inspiration can strike at unexpected moments, waiting for the muse to arrive is a recipe for procrastination. Instead, cultivate discipline and consistency in your work. Show up and do the work, even when you need more motivation. You may be surprised at what you can create when you push through resistance.

In engineering teams, while it's true that being in a positive or focused mindset can enhance productivity and creative output, waiting for the perfect mood to strike can lead to procrastination and missed opportunities. Instead of waiting for inspiration to come knocking, engineering teams can cultivate discipline and consistency in their work habits. This involves showing up and doing the work, even when motivation is lacking, or the conditions are less than ideal. By embracing a disciplined mindset and commitment to the task, teams can overcome resistance and tap into their creative potential.

Moreover, "pushing through" resistance is particularly relevant in engineering teams, where problem-solving and innovation are integral to success. Rather than waiting for the perfect conditions, teams can proactively tackle challenges and iterate on solutions, even in the face of uncertainty or adversity.

17. Prioritizing other activities and responsibilities over your commitment to making art.

Like artists, engineers use creativity to solve complex problems, design innovative solutions, and drive technological advancements. Creativity is not just a nice-to-have skill in engineering; it's a fundamental aspect of the job that fuels innovation and drives progress in the field. By neglecting creative work in favor of more pressing obligations, engineering teams risk stifling their ability to innovate and adapt to changing technological landscapes.

Furthermore, creative work in engineering is not just about producing aesthetically pleasing designs or artistic expressions; it's about pushing boundaries, thinking outside the box, and finding novel solutions to real-world problems. Creativity is essential for driving progress and achieving success in engineering projects, whether designing a new product, optimizing a process, or troubleshooting a technical issue.

To overcome the obstacle of prioritizing other activities and responsibilities over creative work, engineering teams must carve out dedicated time for creative pursuits and treat it as a non-negotiable priority. Just as they would prioritize meetings, deadlines, or client deliverables, team members should set aside time in their schedules specifically for creative exploration, experimentation, and innovation.

Setting boundaries with other activities and responsibilities ensures creative, innovative work takes precedence. Whether saying no to non-essential meetings, delegating tasks, or reallocating time from less important activities, engineering teams must prioritize their commitment to creativity and honor it as a core aspect of their professional identity.

Moreover, honoring this commitment to creative work is not just about individual fulfillment; it's also about fostering a culture of innovation and excellence within the team. By demonstrating a dedication to creativity and encouraging team members to prioritize their creative pursuits, engineering teams can create an environment where innovation thrives, collaboration flourishes, and success is inevitable.

18. Distractibility and procrastination.

In today's digital age, distractions are everywhere, making staying focused on our work challenging. Whether it's social media, email, or the allure of endless entertainment options, procrastination can quickly derail our momentum. To combat distractibility and procrastination, create a conducive work environment free from distractions.

In software engineering teams, where complex problems require intense concentration and innovative solutions, distractibility and procrastination can pose significant challenges. In a world filled with digital distractions and constant connectivity, staying focused on the task can be daunting. 

One of the strategies for combating distractibility and procrastination is to create a conducive work environment that minimizes distractions. This may involve setting up a dedicated workspace free from noise and interruptions, using productivity tools to block distractions from notifications, and establishing clear communication and availability boundaries with colleagues and stakeholders.

Furthermore, implementing productivity techniques can help software engineering teams stay focused and on task. Time blocking, for example, involves allocating specific blocks of time for focused work and minimizing interruptions during these periods. Similarly, the Pomodoro Technique encourages short bursts of intense focus followed by brief breaks, allowing team members to maintain concentration and avoid burnout.

19. Impatience.

Software engineering, innovation, and creativity take time and effort to unfold. However, it's easy to become impatient and expect instant results. Impatience can lead to frustration and disillusionment, causing us to abandon our creative pursuits prematurely. To overcome impatience, practice patience and persistence in your work. Trust in the process and focus on progress rather than perfection. 

In an industry where rapid innovation and quick turnaround times are often prized, the desire for instant results can lead to frustration and disillusionment when progress doesn't happen as quickly as expected. However, building the foundation of a software engineering infrastructure, platform, or architecture cannot be overstated, as it drives innovation, long-term velocity, trust, and quality.

Software engineering projects, particularly those involving complex problems or novel technologies, often require time and effort to develop and refine solutions. Rome wasn't built in a day, and neither is a software engineering project. By embracing a long-term mindset and focusing on the journey rather than the destination, team members can cultivate patience and resilience in their work. This allows them to stay committed to their creative pursuits despite setbacks or obstacles.

Additionally, fostering a culture of cross-functional collaboration and support within teams can help mitigate the effects of impatience. Team members can help each other stay motivated and focused on their goals by providing encouragement, feedback, and resources. Regular check-ins, brainstorming sessions, and knowledge-sharing activities can also offer opportunities for team members to support each other in overcoming challenges and staying committed to their projects.

20. Thinking anything that’s out of your control is in your way.

It's essential to recognize that only some things are within your control. External factors such as market trends, audience feedback, and unforeseen events can all impact our creative journey. Instead of viewing these factors as obstacles, see them as opportunities for adaptation and growth. Focus on what you can control—your mindset, actions, and creative output—and let go of the rest.

One of the primary challenges this mindset presents is the tendency to view external factors as insurmountable obstacles rather than opportunities for adaptation and growth. For example, market trends may shift, audience preferences may change, and unforeseen events may arise, all of which can impact the direction and success of software engineering product development. However, rather than allowing these factors to derail innovation and progress, they can be viewed as opportunities for innovation and adaptation. 

While external factors may influence the context in which a project unfolds, team members control their mindset, actions, and creative output. Embracing this mindset allows teams to remain flexible, agile, and resilient in uncertainty and change. 

Fostering a culture of adaptability and problem-solving within software engineering teams can help mitigate the effects of external factors beyond one's control. Software engineering teams need to cultivate a sense of resilience in the face of adversity. While external factors may present challenges, setbacks, or even failures, these experiences can serve as valuable learning opportunities and catalysts for growth. By reframing setbacks as learning experiences and focusing on continuous improvement, teams can emerge more robust and resilient in pursuing their goals.

Focus on controlling your mindset, actions, and creative output and letting go of the rest.

—

Creativity is a journey filled with challenges and obstacles. However, we can overcome them with perseverance and determination and unleash our creative potential. By recognizing and addressing common thoughts and habits that hinder our work in software development, we can cultivate a mindset of resilience and creativity that empowers us to thrive in our artistic pursuits. So, embrace the journey, the challenges, and, most importantly, your creativity. Your best work awaits.

Each obstacle presents unique challenges in the software engineering product development space. Still, with self-awareness, resilience, and a willingness to embrace discomfort, individuals can overcome it and unleash their full creative potential. Navigating the obstacles to creativity in this context requires a combination of self-awareness, resilience, and a willingness to embrace discomfort.

Self-awareness is the foundation upon which creative growth is built. By understanding our strengths, weaknesses, and thinking patterns, we can identify the obstacles that hold us back and develop strategies to overcome them. Recognizing when self-doubt creeps in, perfectionism takes over, or fear of failure paralyzes us allows us to confront these obstacles head-on and move forward confidently.

Resilience is essential for navigating the inevitable setbacks and challenges along the creative journey. Failure, rejection, and criticism are all part of the process, but how we respond to these obstacles ultimately determines our success. We can bounce back more robustly and resiliently by viewing setbacks as opportunities for growth and learning.

Embracing discomfort is another critical aspect of overcoming obstacles to creativity. Growth rarely occurs within our comfort zones, so pushing ourselves beyond familiar territory and embracing the unknown is essential. Taking risks, trying new things, and challenging ourselves to do better each day are all ways to expand our creative horizons and reach new heights of achievement.

Cultivating a growth mindset is crucial for overcoming obstacles and realizing our creative potential in software engineering. Instead of seeing challenges as insurmountable roadblocks, we can view them as opportunities for growth and development in product development. A growth mindset allows us to approach obstacles with curiosity and determination, knowing that our abilities are not fixed but can be developed through effort and perseverance.

Practicing self-compassion is equally vital in the creative process within other teams. It's natural to be hard on ourselves when things don't go as planned in product development, but self-criticism only undermines our confidence and motivation. By treating ourselves with kindness and understanding, we can nurture a positive inner dialogue that fosters resilience and self-confidence.

Fostering a supportive environment is essential for maintaining momentum and motivation in facing obstacles. Surrounding ourselves with like-minded individuals who encourage and uplift us can provide invaluable support on the creative journey. Whether joining a creative community, seeking mentors, or collaborating with peers, having a solid support network can make all the difference in overcoming obstacles and achieving our creative goals.

We can confidently navigate these obstacles by cultivating a growth mindset, practicing self-compassion, fostering a supportive environment, and continuing to thrive in our creative pursuits. With determination and perseverance, there's no limit to what we can achieve.

In today's large data systems and dynamic nature of building sophisticated interactive and user-engaging applications, choosing between a data-driven and event-driven architecture might be a complex exercise. Both approaches have their strengths and weaknesses and can be used in different scenarios. Let's dive deeply into these different architectural design patterns, when each system is best suited, and its tradeoffs.

A data-driven architecture is best suited for applications that rely heavily on managing and manipulating data. This approach focuses on storing, retrieving, and modifying data and the interactions between different parts of the application and the data. A data-driven architecture often includes a centralized data storage location, such as a database. It uses data binding and flow techniques to ensure consistency and synchronicity across the application.

On the other hand, an event-driven architecture focuses more on reacting to and handling specific events within the application. This approach is well-suited for applications that need to respond quickly to changes in the environment or user input. An event-driven architecture often uses a publish-subscribe pattern, where different parts of the application can subscribe to specific events and take action when those events occur.

A critical difference between the two is that in a data-driven architecture, the application state is determined by the data, and events are just a side effect of changes in data. In contrast, an event-driven architecture is more reactive, with the state being determined by the events.

Data-Driven vs. Event-Driven

In a data-driven design architecture, the data controls the flow and logic of the application to change your program's logic and result.

A typical characteristic of a data-driven architecture includes

• The state of its data primarily determines the application's state.

• Data is typically stored in a centralized location, such as a database. Different parts of the application access and modify the data through defined interfaces.

• Data binding is often used to keep different parts of the user interface in sync with the underlying data.

• Changes to the data can trigger updates to different parts of the application. Still, the current state of the data often determines the specific actions taken in response to those changes.

In an event-driven design architecture, the logic is controlled by events. While the event might include data, the business logic at the application level, and independent of data.

Characteristics of an event-driven architecture include

• The application's state is determined by the events that occur.

• Events can be triggered by external sources, such as user input or network responses, or by internal actions within the application.

• When an event occurs, the application reacts by triggering specific actions or workflows rather than relying on the current state of the data to determine its behavior.

• Event-driven architectures often use a publish-subscribe pattern, where different parts of the application can subscribe to specific events and take action when those events occur.

Type of applications and tradeoffs

Like every software architecture design decision, it's essential to evaluate and balance the tradeoffs of each approach and pick the best architecture for your application's specific needs.

Data-driven architecture is best suited for applications with a clear and consistent data model, and the primary focus is on managing the current state of the application. For example:

• Applications that need to handle a large amount of data, such as financial systems or e-commerce platforms.

• Single-page web applications that use a JavaScript framework, like Angular or React, to bind the user interface to a centralized data store. Data visualization and dashboard applications are usually good candidates for this approach. 

• Mobile apps that use a local database, such as SQLite, to persist application data and synchronize it with a remote server.

Tradeoffs involved in using a data-driven architecture include

• Designing and implementing a consistent and performant data model can be significant for large and complex applications.

• The need to ensure that different parts of the application stay in sync with the current state of the data can add complexity to the application's architecture.

• The risk of data inconsistencies or conflicts, especially in applications used by multiple users or with a high rate of concurrent updates.

Event-driven architecture best suits applications with a high degree of concurrency, where the primary focus is responding to external events in real-time. Examples include:

• Applications that need to handle a large number of events, such as real-time analytics or monitoring systems, such as IoT applications that respond to events generated by connected devices, such as sensor readings or button presses.

• Highly responsive, interactive, dynamic applications, such as a real-time player movement in a game, or action in a financial system, require updating the state based on events.

• Distributed systems, such as microservices, communicate with one another by emitting and listening for specific events.

Tradeoffs involved in using an event-driven architecture include

• The need to design and implement a system for handling events, which can be complex, especially for large and distributed systems.

• The need to ensure that different parts of the application can subscribe to and handle specific events can add complexity to the application's architecture.

• The risk of event storms or cascading failures, especially in systems that rely heavily on event-driven communication.

As you can see, each approach has its strengths and weaknesses. The choice of which one to use will depend on the specific requirements of your application, the types of data and events to be consumed, and your application's performance and scalability needs.

The two approaches are not mutually exclusive.

Some systems that use a data-driven architecture can also incorporate event-driven patterns. 

For example, a web application could use a data-driven approach to manage the state of the user interface, such as a data visualization chart and the application's data, and use an event-driven approach to handle user input events, network responses, and other external events. This way, the UI would be updated based on the data, and the events, like user interaction, would change the data.

Another way to use the two approaches is to use a data-driven architecture to persist and retrieve the application's data and an event-driven architecture to manage the data flow within the application. For example, a distributed system could use a data-driven approach to store and retrieve data from a centralized database and use an event-driven approach to propagate updates and changes to the data between different services and microservices.

Additionally, one approach can be used as an extension of the other. For example, an event-sourced system is a specific type of data-driven architecture that uses events to represent all state changes instead of storing the current state. Event sourcing provides excellent benefits like scalability and fault tolerance. It makes it easier to trace back and understand the system's past.

Another example is the CQRS pattern, which separates a system's write operations from its read operations using a different model. The command model is used for write operations, and the query model is used for read operations. This way, the data-driven component can handle the write operations, and the event-driven side can manage the read operations. This results in a more flexible, scalable, and performant system.

Examples that might use data-driven and/or event-driven systems

A distributed e-commerce system that uses both data-driven and event-driven architectures. The system uses a data-driven approach to storing. It retrieves data from a centralized database and has an event-driven approach to propagate updates and changes to the data between different services and microservices. For example, when a customer places an order, the order service generates an event broadcast to the inventory service, the shipping service, and the billing service, which all take appropriate action in response to the event.

A social media platform that uses an event-driven architecture to handle user activity and real-time updates. The platform uses a publish-subscribe pattern. Different parts of the application can subscribe to specific events, such as a user posting a new message, and take action when those events occur. For example, a newsfeed service can subscribe to the "new post" event and retrieve the latest post from the database to display on the user's newsfeed.

A real-time multiplayer game that uses an event-driven architecture to manage the flow of events, such as player movement, weapon firing, collisions, etc. These events are then used to update the game state, the physics engine, the user interface, the network communication, etc. These games are very responsive and require low-latency communication between the clients and the server; event-driven architecture is a good choice because of its low-latency nature.

An IoT application, where an event-driven architecture can respond to events generated by connected devices, such as sensor readings or button presses. For example, an IoT home automation system could use an event-driven architecture to turn on the lights when a motion sensor is triggered or open the garage door in response to a proximity signal.

These are just a few examples, but many more systems use data-driven and event-driven architectures differently. 

Wrapping this up!

One way to think of the different approaches is to consider data-driven architecture as a tool for managing the current state of an application and event-driven architecture as a tool for responding to external changes in the application's environment. Both data-driven and event-driven architectures can be used together in an application. One approach can be used as an extension of the other.

While data refers to the raw facts, figures, and other information collected and stored by a system. Data can come in many forms, such as text, images, audio, or video, and can be structured or unstructured. Data can be used as input for a software application, for example, a weather app that takes data from a weather station as input and displays the current temperature and forecast.

On the other hand, events refer to specific occurrences or actions within a system or environment. For example, pressing a button, a package arrival, or face detection can all be considered events. Those events can trigger specific actions or responses within a system, such as sending a notification, updating a database, or activating a robotic arm.

In conclusion, when building a robust and efficient application that relies primarily on data, it's important to consider data-driven and event-driven architectures. Each approach has its own strengths and weaknesses, and the choice of which one to use will depend on the specific requirements of your application.

By understanding the role of data and events in driving a system's behavior and utilizing a signal-driven approach and artificial intelligence, we can create a system that leverages the best of both worlds, resulting in a powerful and flexible system that can adapt to changing requirements.

Data and events can be considered signals to drive a system's behavior and build an architecture where both approaches complement each other. 

In today's digital landscape, data is a valuable asset for any organization. It is a rich source of information that can transform industries, improve lives, and drive business growth by streamlining processes and reducing costs. The gathering and analysis of data are crucial in enterprise-level applications, and as the volume of data generated from various sources increases, organizations are recognizing the importance of adopting data-driven decision-making processes and implementing technologies to automate their processes to remain competitive.

One of the key technologies driving this automation is Artificial Intelligence (AI). Leveraging AI to analyze data can reveal trends, assess current programs, and provide insights into customer behavior, uncovering previously undiscovered opportunities. By utilizing AI-driven customer engagement and automation, businesses can improve productivity, generate new revenue streams, and reduce costs.

However, extracting meaningful insights from vast amounts of data can be challenging, especially when dealing with big data volumes. This is where Robotic Process Automation (RPA) and low-code platforms come in. These technologies enable businesses to automate repetitive tasks, such as data entry and document review, freeing up employees to focus on more complex, high-value tasks.

When it comes to leveraging data, AI, and automation for business success, it's important to remember that each business is unique and the approach will vary depending on factors such as business goals and the types and quality of data available. It's essential to carefully design and execute your specific workflows based on your needs and continuously iterate, evolve, and adapt to changes to be successful.

In summary, the successful adoption of data, AI, and automation in any business requires a combination of the right technology, the right approach, and the right team. By understanding and utilizing the latest technology, such as AI and RPA, and by building a team that can design and execute effective workflows, you can take advantage of the full potential of data, AI, and automation to drive business success.

I hope this first quick post has been informative and sparked further discussion about the potential of automation for your business or in building systems, platforms, or applications. In future posts, I plan to delve deeper into topics such as data, AI, workflows, low-code, RPA, system architectures, building teams, and businesses that can benefit from automation. I welcome this as an opportunity for conversation and collaboration, where we can learn from each other about the latest technology and best practices in automation and engineering.

I am grateful for the past and the people who have helped me grow professionally and personally. I am extremely grateful to Raffaele Annunziata (aka Lello) and Luigi Luciano (aka Gigi) for believing in me and giving me the opportunity to start my engineering career at Software Design Srl, now a SITA company. They have not only helped me grow personally and professionally. Through their boundary-pushing and constant encouragement, they have given me the confidence and ability to take on any challenge. This has been invaluable to me throughout my career.

Lello and Gigi are the co-founders of Software Design Srl, which hired me as a software engineer in 1989. We worked on artificial intelligence and telecommunication projects for international companies such as Siemens, Telecom Italia, and the European Space Agency. They built a company ahead of its time in terms of innovation, technology, and culture. A collaborative team with full transparency, learning, and growth opportunities, including offering shares of the company to employees opportunities. It was such a unique company in Southern Italy and an amazing start to my career at that time.

This summer, I was fortunate to meet Lello in Naples, Italy (where I grew up) and Gigi in California (my new home, where I moved 14 years ago). While I do wonder at times how different things would have been if they had founded their company in Silicon Valley instead, I was glad to reconnect with them after so many years and learn about their continued successes. They are still curious people interested in growing and bringing innovation to the world, just like I met them 30 years ago!

After working at Software Design Srl, there are three things that stand out in my mind:

1. There is nothing we cannot solve or tackle. Even if a new technology or project feels overwhelming, we can handle it with time, listening, learning, and adapting. Before we know it, we will become experts in it.

2. We never finish learning. In our profession, technology is constantly evolving, and what we adopt today will likely change. To stay current and relevant, it is important to stay open-minded and open to learning new technologies. We should also remember to learn from our mistakes and apply those lessons to our future work.

3. Collaborate and support your team. Success often relies on working together as a team, and collaborating and helping others not only leads to better outcomes but also provides an opportunity to learn from each other and grow.

Overall, my time at Software Design Srl taught me the importance of perseverance, continuous learning, and teamwork in my career and personal life.

I would also like to extend my gratitude to all of my colleagues at Software Design, Stefania Cardone, Alessandro Pererano, Raffaele Arpaia, Mariarosaria Farina, Massimiliano Gentile, Lucio Rositani, Giuliana Vitale, Fara Di Maio, Carlo Iodice, Claudio de Martino, among many others, who have shaped me as a leader in my career and life. A special thank you goes to Michelle Richards (in the photo with me and Gigi), who has been such a great host and mostly an amazing friend. When I moved to San Francisco from Germany for a new chapter of my life, Michelle and her family, Sharon, Scott, and Vera, made the transition so smooth and easy. Your friendship has been invaluable to me, and you continue to be a great host and friend.

Lello and Gigi, see you soon again, and thank you! Arrivederci e Grazie!

~ Bruno