Education
Architecture knowledge,delivered by a practitioner.
From individual practitioners deepening their practice to engineering organisations training entire architecture teams. Built from real delivery constraints, not slides.
Education
From individual practitioners deepening their practice to engineering organisations training entire architecture teams. Built from real delivery constraints, not slides.
"The best marketing doesn't feel like marketing."
Tom Fishburne
Most developer content is noise. This isn't.
What I produce isn't built around a publishing calendar or a monetisation strategy. It's built around the same questions I've been working on for twenty years, how systems fail, how teams break, how architecture decisions compound over time.
That's why the audience trusts it. And that's what changes the equation for partners.

From a single sponsored issue to a retained architecture advisory, built around what you're actually trying to achieve.
Webinars, in-person workshops, and multi-week online cohorts for software architects and senior engineers.
Individual practitioners: The InfoQ/QCon Certified Architect Program is the flagship public programme, structured curriculum for individual architects looking to formalise and deepen their practice.
Teams and organisations: For engineering organisations, I offer private cohorts, workshops, and corporate training programmes built around your team's specific context and delivery constraints. These are bespoke. Scope, format, and duration agreed based on what your team actually needs.
Education pillar
Structured learning
Multi-week programmes for teams, online or in person.
Education pillar
Keynotes & internal stages
Keynotes and internal talks for engineering orgs, summits, and conference stages.
Education pillar
Hands-on curriculum
Hands-on workshops on architecture, micro-frontends, and delivery, built around decisions your team is facing now, not toy examples.
I offer strategic architecture advisory for teams navigating distributed systems, micro-frontends, and cloud-native design. Engagements range from a focused one-day review to a long-term retained partnership, structured around the decisions you're actually facing, not a generic assessment framework.
Get in touchFor how I work and what I will not take on, see Standards.
I don't take on engagements where the decision has already been made and the brief is to validate it. I'm not useful as a rubber stamp. If you're looking for someone to tell you what you want to hear, I'm the wrong call.
Consulting pillar
Diagnostic & recommendations
Short diagnostic, usually one to two weeks, with a written report on your riskiest decisions, options, and trade-offs you can act on.
Consulting pillar
Ongoing partnership
Ongoing cadence: regular sessions, async decisions when they matter, and written check-ins. Scope tailored per client, typically three to six months or more.
Consulting pillar
Cross-discipline with content
Positioning and narrative for how technical buyers see the problem. Pair with Content for programme formats and Partner for how sponsorship works end to end.
Go-to-market through educational content, not advertising. When you partner with me, you reach 110,000+ engineers, architects and tech leaders who engage because the content earns their attention, not because they were targeted.
Partnership formats include sponsored newsletter issues, podcast episodes, video series, and multi-channel bundles.
Partner with usEditorial and partnership standards, Standards.
Content pillar
Dear Architects, Token by Token & Building Micro-Frontends
Sponsored issue in Dear Architects, Token by Token, or Building Micro-Frontends, same editorial bar as organic issues.
Content pillar
Cinematic and educational videos
In-studio case study video: your product inside a real architecture story, not a demo reel.
Content pillar
Multi-channel packages
Multi-channel bundles, video, shorts, newsletters, and more, scoped to one campaign narrative.
110,000+ engineers, architects and tech leaders. One consistent voice they have chosen to follow.
350+ sessions across re:Invent, QCon, GOTO, NDC, Devoxx and O'Reilly have built an audience that event programmers trust to fill rooms. If you're programming a conference or planning an internal summit, let's talk.
I spent over 20 years in the rooms where architecture decisions get made. DAZN during a platform migration that couldn't fail. AWS embedded with Fortune 500 companies navigating the same decisions at scale. In 2026 I left to focus full-time on 50 Cents Media.
What I do now is the same work, applied differently: consulting with teams facing the decisions I have already made, educating architects building the skills to make them, and creating content that reaches 110,000+ engineers, architects and tech leaders still in the thick of it.
Jun 2026
50 cents media
Greater London, UK
Independent practice. Architecture consulting, QCon/InfoQ cohort facilitation, and content reaching 110,000+ engineers, architects and tech leaders every week.
remedia
Padua, Veneto, Italy
First professional role. Built interactive media projects in Flash and started understanding how the web worked at the production level.
m.art3
Padua, Veneto, Italy
Ran an independent studio for six years. Client work across interactive media, web, and digital products. First experience owning the technical direction and the commercial relationship at the same time.
Inside a bit
Padova
First engineering leadership role at scale. Led a twelve-person team, shaped product and technology direction, and ran R&D consulting alongside delivery.
Gamesys
London Area, UK
Led agile teams shipping AAA player-first games and reduced delivery time from 9 to 3 months.
Massive Interactive, Inc
London Area, UK
Architecture advisory across TV and web products for distributed teams. First exposure to the scale and complexity of broadcast-adjacent systems.
DAZN
London Area, UK
Joined DAZN as the platform was scaling hard and fast. OTT streaming at a scale where architecture decisions had immediate, visible consequences.
DAZN
London Area, UK
Took ownership of architecture direction across a rapidly expanding multi-market platform. The period where micro-frontends went from an experiment to a production decision.
DAZN
London Area, UK
The role that became the book. Led migration of a streaming platform serving millions of concurrent users to a micro-frontends architecture — the work that would become Building Micro-Frontends (O'Reilly). Led a ten-architect team across forty delivery targets; introduced micro-frontends and serverless at scale.
Amazon Web Services (AWS)
Greater London, UK
Moved from DAZN to AWS. Worked with media and entertainment customers on designing and improving architecture and infrastructure decisions—bringing the perspective of someone who had just helped launch a global platform like DAZN.
Amazon Web Services (AWS)
Greater London, UK
Principal Serverless Specialist Solutions Architect, EMEA. Twelve re:Invent talks. Embedded with Fortune 500 companies defining their serverless architecture strategy across Europe. Helped 100+ teams worldwide with micro-frontends migrations.
50 cents media
Greater London, UK
Independent practice. Architecture consulting, QCon/InfoQ cohort facilitation, and content reaching 110,000+ engineers, architects and tech leaders every week.
If you are building architecture capability in your organisation, or looking for someone who has operated at this scale to advise on what you are building next, let's talk.
The definitive guide to designing, migrating, and scaling micro-frontends.
O'Reilly books authored, including Building Micro-Frontends, the definitive text on the pattern
Conference talks at re:Invent, QCon, GOTO, NDC, O'Reilly, from Silicon Valley to Japan
Combined reach across LinkedIn, X, YouTube, newsletters, and podcast platforms
Years of experience spanning startups, scale-ups and global enterprises
Of video podcasts on Spotify by listener engagement
Active content platforms reaching engineers, architects and tech leaders every week
Four recent posts on architecture, systems, and how technical audiences engage. Hover a card to expand it sideways without shifting the rest of the page.
110,000+ engineers, architects and tech leaders. One consistent voice they have chosen to follow.
If you are trying to reach a technical audience that does not respond to traditional advertising, this is a different kind of conversation. I do not sell ad slots. I help partners reach an audience that trusts me, by working with them to create something that audience will actually want to read, watch, or listen to.
The people who read, watch, and listen to 50 Cents Media content are senior. They have budgets. They make or heavily influence technology decisions. They are not passive consumers. They subscribe, share, and act on content that earns their attention.
This is not a general developer audience. It is a concentrated community of people who take architecture seriously.
The most straightforward format. You share your brief, I frame it for the audience. I know what lands in this context and what does not, so rather than running your copy as-is, I will tell you upfront how to position it for the best result. Fast turnaround, clear labelling, no surprises.
Best for: developer tools, cloud platforms, architecture-adjacent products with a clear technical use case.
More collaborative. We work together from brief through to final episode, shaping the angle, agreeing on the framing, making sure the way your product appears in the conversation is both honest and useful to the listener. The editorial direction stays with me, but the best episodes come from partners who are willing to think alongside me about what the audience actually needs to hear.
Best for: companies with a genuine story to tell about how their product is used in production, ideally with a customer or practitioner who can speak to it directly.
Where the collaboration goes deepest. We co-create from the start. The concept, the narrative, the way your technology is demonstrated. I bring the architectural perspective and the production; you bring the product knowledge and the business context. During post-production, you have a defined number of revision rounds to make sure the technical detail is accurate and the representation feels right. Scope agreed upfront.
Best for: companies that want something that lives beyond a campaign, an educational asset that continues to drive inbound long after the initial release.
Every partnership starts the same way: a short conversation about your goals and your audience. From there I will tell you how I think we can make it work, and if a different format would serve you better, I will say so.
A note on editorial independence: the reason this audience pays attention is that they trust the content is not written for the sponsor. That trust is the asset you are accessing when you partner here. The educational angle, the framing, and the conclusions remain mine, developed collaboratively with you where it serves the content, but never directed by you. Partners who understand this get better results, because the audience can tell the difference.
The conversation about framing, angle, and what the audience will respond to happens before anything is written or filmed. In my experience, that conversation is where most of the value is. Partners leave it with a clearer sense of what they are trying to achieve, regardless of what we decide to do together.
For labelling, independence, and what we do not take on, see Standards.
The formats above are starting points, not the full picture. If you have something in mind that does not fit neatly into a newsletter slot or a video brief, send it through anyway. Some of the best partnerships start with an idea that does not have a name yet. If there is a way to make it work for this audience, we will find it together.
How I create content, and how partnerships work in practice.
Every week I read widely. Papers, posts, threads, talks, conversations with practitioners in the field. My job is not to add more voices to an already noisy space. It is to curate the ideas that matter, stress-test them against twenty years of production experience, and give them back to the community in a form that is actually useful.
I think of it as giving a voice to the people doing the work, not the people talking about it.
That means I am selective about what goes out. Not because I follow a set of rules, but because I know this audience well: what they find useful, what they see through immediately, what makes them close the tab. I have been one of them for two decades. I still am.
When a partner comes to 50 Cents Media, I bring that knowledge into the room with them. My role is not to decide whether their story is worth telling. It is to help them find the version of their story that this audience will actually engage with. That is a collaborative process, and in my experience, it produces better results for the partner than any brief they could have written alone.
110,000+ engineers, architects and tech leaders. One consistent voice they have chosen to follow.
If you are trying to reach a technical audience that does not respond to traditional advertising, this is a different kind of conversation. I do not sell ad slots. I help partners reach an audience that trusts me, by working with them to create something that audience will actually want to read, watch, or listen to.
Here is how that works in practice, across the three formats.
Newsletter placements are the most straightforward format. You share your brief, I frame it for the audience. I know what lands in this context and what does not, so rather than running your copy as-is, I will tell you upfront how to position it for the best result. Fast turnaround, clear labelling, no surprises.
Podcast integrations are more collaborative. We work together from brief through to final episode, shaping the angle, agreeing on the framing, making sure the way your product appears in the conversation is both honest and useful to the listener. The editorial direction stays with me, but the best episodes come from partners who are willing to think alongside me about what the audience actually needs to hear.
Video is where the collaboration goes deepest. We co-create from the start. The concept, the narrative, the way your technology is demonstrated. I bring the architectural perspective and the production; you bring the product knowledge and the business context. During post-production, I allow a defined number of revision rounds so you can make sure the technical detail is accurate and the representation feels right. The number of rounds is agreed upfront, and varies by project.
In all three formats, every sponsored placement is clearly labelled. The audience always knows. That transparency is not a constraint, and it is part of why the placement is worth something.
One thing will not change regardless of who sponsors an issue, an episode, or a video: the editorial judgement is mine. The framing, the argument, the examples, the conclusions. Partners contribute context about their product and can flag factual inaccuracies. They do not shape the angle, select the guests, or influence what I say about anything beyond their own technology. If you are reading or watching something here, you are getting my honest assessment of it, full stop.
If I do not think a partnership is a good fit for this audience, I will say so before we go any further, and I will explain why. Sometimes that means suggesting a different format. Sometimes it means we are not the right match. Either way, you will know early, not after we have both invested time in something that was never going to land.
If I think we can make it work, I will tell you how. The conversation about framing, angle, and what the audience will respond to happens before anything is written or filmed. That conversation is where most of the value is.
For video and podcast, yes. Review rounds are built into the process and agreed upfront. For newsletters, I share the framing approach before anything is written so there are no surprises at publication. In all cases, partners can flag factual inaccuracies about their own product. Editorial direction, architectural argument, and overall framing remain mine.
Sponsored placements are always labelled. Any editorial coverage of a partner, in a separate issue, episode, or video, is based on technical merit and independent of the commercial arrangement. If both exist at the same time, I will say so.
124–128 City Road
London, EC1V 2NX
United Kingdom
Available for projects worldwide
AI in the software development lifecycle, from agentic architecture to the evolving role of the architect. For practitioners navigating the AI era with rigour, not hype.
Subscribe freeToken by Token explores how AI is reshaping the software development lifecycle, not from a researcher's perspective, but from the architect's. Each issue tackles a concrete question: how do you contain agentic systems? What does DDD mean when agents cross subdomain boundaries?
The thesis: AI agents don't change software architecture, they expose every weakness in it. Each issue uses a concrete case to test that argument. Some weeks the thesis holds. Some weeks it breaks. The uncertainty is the point.
Recent issues, coming soon
Practitioners sharing real-world micro-frontend stories, the wins, the mistakes, and the decisions that shaped their systems.
Watch / ListenA video podcast featuring the engineers and architects who have shipped micro-frontend systems at scale. Guests include Manfred Steyer (Native Federation), Peter Eijgermans (Dutch Railways), and more.
Conversations go deep on implementation reality, what the blog posts do not tell you, how teams actually organised themselves, and what they would do differently.
Episode list, coming soon
Video conversations with architects on the decisions that define systems. Honest, deep, practitioner-to-practitioner.
WatchThe Dear Architects video podcast extends the newsletter into long-form conversation. Guests include practitioners like Susanne Kaiser, Vlad, and Jacqui Read, architects with genuine opinions and the experience to back them up.
Each episode picks a specific architectural tension and unpacks it without false resolution. The goal is to model good architectural reasoning, not to hand out easy answers.
Episode list, coming soon
Educational video content produced for brand partners, demonstrating technology through real architectural narrative, not product demos.
Discuss a projectCase study videos produced in partnership with technology companies, telling the story of how their product solves a real architectural problem, presented through Luca's lens as a practitioner. These are not product demos. They are architectural explorations that happen to feature a tool.
Filmed in the purpose-built garden room studio in London, or on location. Full production, scripting, and distribution included.