ArchiCraft: Solution Architecture Insights for AI Engineering

Dmytro Golodiuk

ArchiCraft is a podcast about modern software and solution architecture, enterprise strategies, and the future of AI-driven engineering. Each episode is AI-generated from original blog posts by Dmytro Golodiuk, based on real-world experience and hands-on insights. Explore the full archive at https://www.golodiuk.com/news.

  1. 2d ago

    #021 - Process on Paper vs. Process That Works

    Two organizations can both say "we have process" and mean completely different things. One team watches a tested, urgent fix sit in a queue behind a board that meets every other Tuesday -- nobody on it built the system, nobody carries the pager. Another team ships to production the same afternoon, governed by an availability budget and an automated canary release instead of a meeting. Same word. Opposite outcome. This episode digs into what actually separates the two -- and it isn't how much process either organization has. We walk through Ron Westrum's organizational typology, empirically validated by DORA's own research, which explains why the same number of review steps and sign-offs can either help or hurt depending on what they're calibrated against: control, compliance, or outcomes. We look at DORA's own finding that heavyweight external change-approval boards correlate with lower delivery performance, not higher -- and at Boeing's 737 MAX certification as the sharpest, highest-stakes case of a governance gate that existed on paper while the incentive structure routed real engineering signal around it. Then we turn to what actually works: Amazon's API mandate, Google's error budgets, Netflix's paved roads, and ThoughtWorks' architecture advice process -- all examples of the same mechanical shift, from a gate that blocks by default to a guardrail that ships by default and only interrupts on genuine risk. Finally, we cover the mirror-image failure: Spotify's own retrospective on its famous "squads and tribes" model, which shows that autonomy with zero shared alignment fails exactly as badly as control with zero autonomy -- just in the other direction. If you own an architecture review board, a design authority, or a security sign-off step, this episode gives you a concrete way to find out which failure mode you're actually in, instead of guessing. --------- Dmytro Golodiuk is a highly experienced technology professional with over 18 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond great technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #021 - Process on Paper vs. Process That Works
  2. Aug 21

    #020 - The Architecture Leadership Framework: Purpose, Problem, Parameters, Possibilities

    Architecture has more than one right answer -- if there were only one possible solution to a given problem, the creative part of the job would already be over. This episode closes out the Architecture Leadership: Direction or Freedom series with a simple way to hold that conversation together: Purpose, Problem, Parameters, Possibilities. We open on a moment familiar to anyone who has sat through a "migration" project: the option that actually solved the problem -- retire it, change the process instead, do nothing -- was on the table the whole time, and almost didn't get considered, because by the time anyone asked the real question, a vendor had already been picked and a budget line already existed. The first two parts of this series named the failure modes on either side of that menu -- leadership prescribing the solution instead of the problem, and leadership disappearing so completely that nobody frames the problem at all. Both collapse the solution space to one option before anyone has actually explored it. This episode is about protecting that space. We walk through the four-part frame: Purpose and Problem, which leadership owns and states clearly; Parameters, the real constraints -- budget, timeline, compliance, risk appetite -- that leadership also owns, because pretending there are none isn't freedom, it's abdication; and Possibilities, the space the team owns with genuine, accountable authority to explore and decide. We also look at why this isn't just an architecture problem. The same leadership mistake -- handing over an answer instead of a problem -- recurs identically with engineers, product managers, and data scientists. Architecture just makes it easiest to see, because the trade-offs are auditable after the fact. If you lead architecture, product, or engineering decisions and want a concrete way to stop the solution space from narrowing before anyone's looked at the full menu, this episode gives you the four questions to ask before the next big decision gets made. --------- Dmytro Golodiuk is a highly experienced technology professional with over 18 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond great technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #020 - The Architecture Leadership Framework: Purpose, Problem, Parameters, Possibilities
  3. Aug 14

    #019 - Decree Architecture vs. Abdication: How Leaders Break Architecture

    A platform lead opens a kickoff meeting with the line every architecture team thinks it wants to hear: "You have complete freedom to design this." For a few seconds the room feels good. Then the questions start -- optimize for cost or speed? Build or buy? One shared platform, or let every team pick its own stack? Nobody asked for permission to answer those questions. They asked for someone to actually decide them. That's the subject of this episode -- the second failure mode in a two-part series on architecture leadership. Part 1 covered leaders who prescribe a solution instead of stating a problem. This one covers the opposite mistake: leaders who pull back so far that "freedom" becomes unresolved governance, handed to the people least positioned to resolve it on their own. We name the pattern Architecture by Abdication -- a leader disengages from the hard trade-offs, then judges the result after the fact -- and its mirror image, Decree Architecture, where the leader picks the technology up front and expects architects to justify it afterward. The two look like opposites. They produce the same outcome: architects doing work that was never really theirs to do, without the authority that should have come with it. We also dig into why constraints don't suppress architectural creativity -- they define the space where it matters, and why a premature leadership mandate does more damage at enterprise scale than at the level of a single system. A solution architect optimizes one system; an enterprise architect has to check that system against every other one around it. The practical shift: leadership can't demand accountability from architects while refusing to participate in the trade-offs that make accountability possible. Direction and freedom aren't opposites here -- withholding both is the same failure, twice. --- Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond great technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #019 - Decree Architecture vs. Abdication: How Leaders Break Architecture
  4. Aug 11

    #018 - Give Architects the Problem, Not the Architecture

    A design review starts with someone who already has the answer: "We need microservices." Or Kubernetes, or an event-driven architecture, or a new API platform. The room spends the next hour justifying a decision nobody actually discussed. This episode is about that moment, and the mistake underneath it. The mistake isn't giving architects too much direction, or too little. It's giving them direction at the wrong altitude -- a solution instead of a problem. Gregor Hohpe's "Architect Elevator" describes the levels a good architect has to move between; this episode argues leadership's job is to state the destination and the constraints, then get out of the machine room. We walk through why architecture is creative work, but creativity isn't the deliverable -- architects are paid for outcomes like reduced risk and faster delivery, not for diagrams. We use Hershey's 1999 ERP rollout as the real, named case for what happens when a leader fixes the technology and the calendar before anyone defines the actual problem: a Halloween season with empty shelves and a nine-figure loss, from a project that was never really about SAP. And we get into the reflex that causes it: "we need microservices" is a solution dressed up as a requirement. It skips the problem-definition conversation entirely, including the option that's usually invisible on that list -- doing nothing. The practical shift is simple to state and hard to practice: state the problem, the business motivation, and the constraints -- then stop, and leave the design to the people accountable for building it. Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond great technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #018 - Give Architects the Problem, Not the Architecture
  5. Aug 6

    #017 - How to Spot Bad Architects vs. Great Amplifiers

    Most bad architects are easy to spot -- buzzwords, a checklist, an authority that was never earned. The good ones are the hard case: quiet, unremarkable, everything just seems to go well and nobody quite knows why. This episode is about that second group, and about the self-tests that actually separate them from the first. We start with the split at the center of the episode: the oracle, who hands down verdicts from a position nobody is allowed to question, versus the amplifier, who leaves everyone in the room able to solve the next problem themselves. Built around a conversation with Gregor Hohpe, a Google and AWS enterprise architect and author of "The Software Architect Elevator." We walk through the Rubber Duck Test -- a proposed self-check, not an industry standard -- for whether you're actually useful: do people come to you to think better, or because you're a checkpoint they have to clear. We get into why simple architectures are usually the hardest ones to build, why essential complexity can't be negotiated away, and why "too many cooks" produces something worse than any option on the table, not a fair compromise. We close on the line that ties the whole argument together: an architect's real pitch is "I lower your risk," not a stamp of approval on someone else's design. And the current wrinkle -- what that pitch is worth once anyone can paste a chatbot's output into an architecture document. Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond deep technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #017 - How to Spot Bad Architects vs. Great Amplifiers
  6. Jul 29

    #016 - You Probably Do Not Need That Database

    Most systems get a database before anyone has written down a requirement. In this episode we take that reflex apart and ask what the decision would look like if it were actually made rather than assumed. We start by separating the four kinds of state almost every system mixes together: reference, transactional, derived, and ephemeral. Only one of them clearly justifies a networked relational engine, and conflating them is what turns a modest application into an operational burden. From there we look at what a database really costs. Not the licence -- the operational surface: high availability, a restore you have actually verified, patch cadence, schema governance, and a fresh single point of failure carrying its own service level agreement (SLA). We then examine the strongest idea in the "no database" argument, which is not the absence of storage at all but materialization -- a slow, human-paced write path paired with a fully pre-computed read path -- and we are honest about where that simplicity breaks down. The dividing line that matters turns out to be concurrent writers to overlapping state. Not data volume. Not user count. We close with eight decision gates you can walk through in a design review, so that whatever you choose, you can defend it with a reason rather than a habit. Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 MENTORSHIP and WHAT I OFFER A CLEAR ROADMAP: I'll help you forge the path from technical expertise to architectural vision. My focus isn't on specific technologies – you've got that covered. Instead, we'll concentrate on the strategic thinking, communication, and leadership skills that define a successful architect. BRIDGING THE GAPS: Together, we'll identify and close the crucial gaps between a senior engineering role and the holistic view required of an architect. FOSTERING YOUR GROWTH: My mentorship is about cultivating your ability to see the bigger picture, to design robust and effective solutions, and to communicate complex ideas with simplicity and impact. ARCHITECT READY CV PROFILE OPTIMISATION: I'll help you transform your engineering CV into a strategic narrative that compellingly showcases your architectural potential, leadership, and strategic contributions to resonate powerfully with hiring managers. ACE YOUR ARCHITECT INTERVIEW: I’ll prepare you for the full spectrum of interview scenarios. 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond deep technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #016 - You Probably Do Not Need That Database
  7. Feb 17

    #015 - Policy-Based Access Control (PBAC): Debunking the Myths

    Join us for an architectural deep-dive into Policy-Based Access Control (PBAC), the essential framework for modern Zero Trust security. In this episode, we explore why traditional Role-Based Access Control (RBAC) is collapsing under the weight of "role explosion" and how externalizing authorization decouples policy lifecycles from software release cycles. We dissect the core components of the PBAC ecosystem – including PEPs, PDPs, and PIPs – and compare leading engines like Open Policy Agent (OPA) and AWS Cedar. Furthermore, we debunk persistent myths regarding performance latency and implementation complexity, providing a strategic roadmap for enterprise adoption through Policy-as-Code and GitOps workflows. Whether you are dealing with distributed microservices or stringent compliance requirements, this episode offers the technical insights needed to move beyond hardcoded logic and achieve genuine least-privilege access. Thank you for listening! ❤️ Build smart, Architect with intent. 🟦 CONNECT WITH DMYTRO LinkedIn Mentorship Email: ⁠⁠info@golodiuk.com⁠⁠ 🟦 EPISODE LINKS (ORIGINAL BLOG POSTS) Find the full blog post here: Policy-Based Access Control (PBAC): Debunking the Myths - https://www.golodiuk.com/news/pbac-debunking-myths/ 🟦 ABOUT Dmytro | ⁠⁠www.golodiuk.com⁠⁠ Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 MENTORSHIP and WHAT I OFFER A CLEAR ROADMAP: I'll help you forge the path from technical expertise to architectural vision. My focus isn't on specific technologies – you've got that covered. Instead, we'll concentrate on the strategic thinking, communication, and leadership skills that define a successful architect. BRIDGING THE GAPS: Together, we'll identify and close the crucial gaps between a senior engineering role and the holistic view required of an architect. FOSTERING YOUR GROWTH: My mentorship is about cultivating your ability to see the bigger picture, to design robust and effective solutions, and to communicate complex ideas with simplicity and impact. ARCHITECT READY CV PROFILE OPTIMISATION: I'll help you transform your engineering CV into a strategic narrative that compellingly showcases your architectural potential, leadership, and strategic contributions to resonate powerfully with hiring managers. ACE YOUR ARCHITECT INTERVIEW: I’ll prepare you for the full spectrum of interview scenarios. 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognizes the need to develop beyond deep technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #015 - Policy-Based Access Control (PBAC): Debunking the Myths
  8. 11/04/2025

    #014 - How Do You Lead a Team Caught Between Overconfidence and Self-Doubt

    Welcome to the tension between overconfidence and self-doubt — the quiet forces shaping every engineering team. This episode explores how the Dunning-Kruger effect (overestimating competence) and Impostor Syndrome (underestimating competence) represent opposite but connected forms of miscalibrated self-perception. We delve into the toxic team dynamics created when overconfident novices clash with self-doubting experts, a scenario that can undermine project outcomes and erode morale. We examine how these psychological phenomena manifest as concrete risks across the Software Development Lifecycle (SDLC), including resistance to crucial feedback during code reviews and the silencing of valuable expertise during architectural and design decisions. The core risk is that the loudest, least competent voices can drown out the quietest, most competent ones, leading to suboptimal technical decisions. Discover the manager’s playbook for building a resilient organisational culture designed to calibrate confidence. Lasting solutions require embedding systemic processes, not just "fixing" individuals. Learn how to: Build Psychological Safety by modelling vulnerability and implementing blameless post-mortems to decouple mistakes from personal identity. Deploy Objective Feedback using frameworks like the Situation-Behaviour-Impact (SBI) model, which delivers evidence-based feedback that is difficult for the overconfident to dismiss or the self-doubting to internalise as personal failure. Provide External Validation by designing clear career ladders that provide objective, impartial benchmarks for competence, helping engineers internalise their success. Thank you for listening! ❤️ Build smart, Architect with intent. 🟦 CONNECT WITH DMYTRO LinkedIn Mentorship Email: ⁠⁠info@golodiuk.com⁠⁠ 🟦 EPISODE LINKS (ORIGINAL BLOG POSTS) Find the full blog post here: How Do You Lead a Team Caught Between Overconfidence and Self-Doubt 🟦 ABOUT Dmytro | ⁠⁠www.golodiuk.com⁠⁠ Dmytro Golodiuk is a highly experienced technology professional with over 17 years in the software industry. His proficiency spans cloud computing, enterprise platforms, software development, and integration technologies, with deep expertise in the Microsoft ecosystem. Dmytro combines his technical knowledge with formal Enterprise Architecture frameworks like TOGAF and ArchiMate to deliver robust and practical solutions. In addition to his architectural work, Dmytro is a passionate mentor dedicated to helping others grow in their IT careers. https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ 🟦 MENTORSHIP and WHAT I OFFER A CLEAR ROADMAP: I'll help you forge the path from technical expertise to architectural vision. BRIDGING THE GAPS: Together, we'll identify and close the crucial gaps between a senior engineering role and the holistic view required of an architect. FOSTERING YOUR GROWTH: My mentorship is about cultivating your ability to see the bigger picture, to design robust and effective solutions, and to communicate complex ideas with simplicity and impact. ARCHITECT READY CV PROFILE OPTIMISATION: I'll help you transform your engineering CV into a strategic narrative that compellingly showcases your architectural potential, leadership, and strategic contributions to resonate powerfully with hiring managers. ACE YOUR ARCHITECT INTERVIEW: I’ll prepare you for the full spectrum of interview scenarios. 🟦 IF YOU'RE A MID TO SENIOR ENGINEER WHO Aspires to become a Solution Architect. Recognises the need to develop beyond deep technical skills. Is ready to embrace the mindset and responsibilities of an architect. ✅ Then I'm the mentor you're looking for. Let's work together to unlock your potential and lay the bridge to your future as a Solution Architect. ⁠⁠https://mentor.sh/mentors/dmytro_golodiuk⁠⁠ --------- This podcast episode is an AI-narrated version of the original text-based articles from Dmytro's personal blog, which you can find at ⁠⁠⁠⁠www.golodiuk.com/news⁠⁠⁠⁠

    #014 - How Do You Lead a Team Caught Between Overconfidence and Self-Doubt

About

ArchiCraft is a podcast about modern software and solution architecture, enterprise strategies, and the future of AI-driven engineering. Each episode is AI-generated from original blog posts by Dmytro Golodiuk, based on real-world experience and hands-on insights. Explore the full archive at https://www.golodiuk.com/news.

You Might Also Like