deararchitects

955 posts

deararchitects

@deararchitects

A newsletter by architects, for architects—sharing tips and inspiration every week! by @lucamezzalira #software #architecture #tech #cloud #devops #genAI

Global Beigetreten Ağustos 2020

2.3K Folgt10.6K Follower

deararchitects retweetet

Luca Mezzalira@lucamezzalira·1d

The April @InfoQ cohort is in session. The May cohort starts in six days. The thing that surprises people most about this cohort isn't the material. It's the room. #Architects and senior engineers from fintech, healthcare, logistics, gaming, all in the same conversations. The angles you get on a problem from someone who's solved something adjacent in a completely different context? That's the part you can't replicate anywhere else. Five weeks with senior practitioners from different companies who will tell you whether your call is right. Enrollment closes 6 May. Two groups: 09:30 BST or 10:00 EDT. Here $30 discount code: LucaON202630 Grab your ticket today 👉 certification.qconferences.com #cohort #learning #architecture #AI

English

413

deararchitects@deararchitects·4d

Quote that stuck: “The only thing I can do is make sure I am better than I was yesterday.” Full #287 here: preview.mailerlite.io/preview/123540… Subscribe → deararchitects.xyz More on #AI coding assistants and strategic #DDD too.

English

497

deararchitects@deararchitects·4d

Anyone else fighting the constant feeling that you’re “not technical enough” or distracted by the next hot framework? What’s one thing that actually helped you move past it? #SoftwareArchitecture

English

341

deararchitects@deararchitects·4d

No CS degree. No straight path. Still became an AWS architect. @plantpowerjames story in the latest issue hits different: imposter syndrome at ProServe, Magpie syndrome chasing every shiny tech, and finally accepting that architecture is all tradeoffs, not right vs wrong answers

English

992

deararchitects retweetet

Luca Mezzalira@lucamezzalira·5d

I'm 2 weeks into facilitating the April @InfoQ architecture cohort, and something keeps coming up that I want to share. Most architects know what they're building. Fewer can articulate why, and fewer still can surface the tradeoffs of a decision in a way that lands across an entire organisation. That gap is where good architecture goes quiet. The cohort works through tools that force that clarity. Architecture canvases to make the thinking visible. ADRs and RFCs to externalise the reasoning and invite challenge. Decentralisation patterns to understand where decisions should actually live inside a sociotechnical system. None of these are documentation exercises. They are communication mechanisms. They change how you frame a decision before you've even opened your mouth. What emerges after 5 weeks is something I see consistently: participants start understanding not just what they are building, but why, and how to surface the tradeoffs honestly. Because in architecture there are no perfect decisions. There are only the least wrong ones for your context, your team topology, and the constraints you're operating under. Being able to communicate that, to leadership, to peers, to teams, is what separates an architect from a senior engineer with opinions. Chinmay Sawaji at Klaviyo said it directly: "I can now articulate trade-offs in a way that improves my proposals at work." That's not a curriculum outcome. It's a side effect of having to be precise with people who won't fill in the gaps for you. The May cohort starts 7 May. I'd like to see some of you in it 😉 Details in the comments 👇

English

693

deararchitects@deararchitects·21 Nis

The 4th episode of Dear architects podcast is available now! do you wanna know how to think like an architect or becoming one? That's the discussion between @plantpowerjames and @lucamezzalira Career progression, AI, impostor syndrome and much much more! 👇

Luca Mezzalira@lucamezzalira

All of this and more in the new episode of @deararchitects #podcast! 👉 Watch it now: youtu.be/C6zkoMR7MTw

English

432

deararchitects@deararchitects·20 Nis

You don't wanna miss the hands-on architecture cohort, do you? 5 weeks of peer-learning led by our own @lucamezzalira! Check it out here 👇

Luca Mezzalira@lucamezzalira

Facilitating the first session of the new @InfoQ Certified Architect cohort this week reminded me why external validation is so critical at the senior level. We spent 4 hours in a live working group and instead of just talking about Strategic Domain-Driven Design, the attendees actually broke into groups to map out subdomains and define the architecture characteristics to apply on each of them. Then each group had to explain their technical reasoning and let peers from other enterprise companies challenge their approach. We capped it off by analyzing the @BBC news modernization, great talk from delivered during Qcon London, and I challenged everyone to apply an architecture canvas to their own systems for this week. The real knowledge required to think like an architect is found when you discover how people in completely different industries tackle the exact same problems you face. If you want to move from making architectural calls on your own to pressure-testing them with a trusted peer group, I would love to see you in the May or June cohorts. Take a look at the syllabus and join us here: certification.qconferences.com #SoftwareArchitecture #TechLeadership #InfoQ #QCon #DDD

English

450

deararchitects@deararchitects·19 Nis

One line that hit hard: AI accelerates development, but teams are losing visibility into why things work (or don’t). Full #286 here: preview.mailerlite.io/preview/123540… Subscribe → deararchitects.xyz More on modularity skills and timeless principles too.

English

400

deararchitects@deararchitects·19 Nis

Architectural inefficiencies that used to take years to explode can now become a big ball of mud in months. Are we building the future or just creating faster technical debt? Be honest, how much control do you actually feel you still have? #SoftwareArchitecture #GenAI

English

452

deararchitects@deararchitects·19 Nis

AI is generating code faster than we can understand it. ThoughtWorks Technology Radar just called it: we're accumulating massive "cognitive debt" and losing control of our own systems. The scary part? ... 👇

English

1.1K

deararchitects retweetet

Luca Mezzalira@lucamezzalira·13 Nis

Last year someone replied to a @deararchitects issue with three words. "I saved this." Not "great issue." Not "loved this one." Just that. I was curious and I replied to the message. He told me he keeps a folder on his mail app because it's part of the things he actually wants to come back to. Most newsletters never make it there. I asked why Dear Architects did. "There's always something in it for me. But it never tries to give me everything." I've thought about that a lot since. That's the bar for @tokenbytoken_ai too. First issue THIS week. SUBSCRIBE NOW -> tokenbytoken.ai What's the last thing you actually saved to come back to? And did you? #ai #newsletter #upcominglaunch #engineers #architects #tech

English

830

deararchitects@deararchitects·12 Nis

Birgitta Boeckeler’s piece on Harness Engineering frames it as strategic investment rather than overhead. Curious how that plays out at different org sizes. Full #285 here: preview.mailerlite.io/preview/123540… Subscribe → deararchitects.xyz

English

323

deararchitects@deararchitects·12 Nis

Is this genuine acceleration or just moving the bottleneck from delivery to platform operations? Anyone scaled a harness/platform successfully without creating new coordination hell? Real outcomes welcome... good or bad 😉

English

388

deararchitects@deararchitects·12 Nis

Building internal platforms and “Harness Engineering” sounds like the obvious next step for faster delivery. But it’s also another layer of infrastructure that teams now have to own and maintain. 🧵

English

867

deararchitects retweetet

Luca Mezzalira@lucamezzalira·7 Nis

The internet has infinite AI takes. What it doesn't have is a filter. A few years ago I started @deararchitects with a simple idea: one newsletter a week, 5 pieces of content, nothing more. No walls of text. No 47-item reading lists. Just 5 topics, so every reader finds at least one thing worth their time. What surprised me was how people read it. Not everyone read everything in one go. Over the week, they'd come back to it. One piece on Monday, another on Thursday. Some told me they still had issues open from a month ago. That's when I understood what a newsletter can actually be. Not a publishing schedule. A companion for the week. I'm building @tokenbytoken_ai with the exact same philosophy but for AI, from an engineering perspective, for all the engineers, architects and tech leaders out there 5 things per issue, curated, varied and no overwhelm. First issue lands next week, become a funding subscriber today! tokenbytoken.ai #ai #ml #whitepaper #newsletter

English

584

deararchitects@deararchitects·6 Nis

Now you can have a double appointment! The first with Dear Architects on software architecture including AI but also we double down with @tokenbytoken_ai focused solely on #AI for engineers, architects and tech leaders And yes, it's all free for you!

Luca Mezzalira@lucamezzalira

Many readers of @deararchitects started reaching out, not only about architecture, but about #AI as well. How to understand it beyond the hype. How to apply it in real systems. How to keep up without feeling constantly behind. At the same time, I found myself going deeper into it as well, reading more, experimenting more, trying to connect the dots from an engineering perspective. Dear Architects helped many people navigate complexity in software architecture. And just to be clear: it’s not going anywhere! I love architecture and it is one of my biggest passions by far. But I thought to learn in public again, and apply a similar approach for AI. I’ve started a new weekly newsletter called Token by Token @tokenbytoken_ai One edition a week. Just like Dear Architects. Just the few things per issue that are actually worth understanding. If you’re exploring AI from a practical, engineering perspective, you might find it useful. Check it out: tokenbytoken.ai The first issue will be available very very soon! I wanna make this journey together, because: If you want to go fast, go alone. If you want to go far, go together 😉 #newsletter #announcement #tech #ai #aiengineering #engineers #architects #techleaders

English

563

deararchitects@deararchitects·4 Nis

One painful reality: #AI cycles are so fast that traditional gates become bottlenecks, but removing them entirely feels reckless. Full #284 here: preview.mailerlite.io/preview/123540… Subscribe → deararchitects.xyz More on context for AI agents and responsible AI too.

English

437

deararchitects@deararchitects·4 Nis

@InfoQ piece got me thinking: are we slowing innovation with heavy governance, or are we sleepwalking into unmaintainable systems by moving too fast? How are you handling governance in AI projects right now, tightening controls or loosening them? #SoftwareArchitecture #GenAI

English

480

deararchitects@deararchitects·4 Nis

Traditional architectural governance is getting crushed by AI development speed. The latest issue highlights how old approval processes just can't keep up, yet skipping them risks architectural chaos. 👇

English

781

deararchitects retweetet

Luca Mezzalira@lucamezzalira·1 Nis

Just dropped a new episode of #Microfrontends in the Trenches 🎙️ I got to sit down with @ManfredSteyer, Angular GDE and the creator of Native Federation. We went deep on stuff I get asked about all the time: → When do micro-frontends actually make sense (and when they don't) → Why Manfred built Native Federation as an alternative to Module Federation → How import maps & ES modules power it under the hood → Mixing Angular versions across a distributed system... is it worth it? → The #1 mistake teams make when splitting a monolith → His top 3 tips for devs getting started with micro frontends One thing that stuck with me: Manfred said the hardest part isn't the tech but the domain thinking. Getting your boundaries right before you write a single line of federation config. If you're working with Angular at scale, this one's for you. 👇 youtu.be/2KePdr9igLg #angular #web #MFEs #scale #engineering #javascript

YouTube

English

2.3K

Entdecken

@InfoQ @plantpowerjames @lucamezzalira @tokenbytoken_ai @ManfredSteyer @elonmusk @BarackObama @taylorswift13