<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brady Clifford on Medium]]></title>
        <description><![CDATA[Stories by Brady Clifford on Medium]]></description>
        <link>https://medium.com/@bradyclifford?source=rss-ae60a26d7a23------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0N9L2n-v-eNX60Lfdd8fag.jpeg</url>
            <title>Stories by Brady Clifford on Medium</title>
            <link>https://medium.com/@bradyclifford?source=rss-ae60a26d7a23------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:07:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bradyclifford/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Merging Operating Models After an Acquisition]]></title>
            <link>https://bradyclifford.medium.com/merging-operating-models-after-an-acquisition-7426025e5a63?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/7426025e5a63</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[conways-law]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Mon, 11 May 2026 20:55:41 GMT</pubDate>
            <atom:updated>2026-05-18T12:48:58.724Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most difficult transformations I have experienced was not a cloud migration, a monolith decomposition, or a platform modernization effort.</p><p>It was attempting to merge two fundamentally different operating models after an acquisition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBbGerXuGuKcRgPDsT6fjg.png" /></figure><p>Most organizations assume the challenge will primarily be:</p><ul><li>Systems integration</li><li>Tooling consolidation</li><li>Vendor rationalization</li><li>Data migration</li><li>Identity integration</li></ul><p>In reality, those are usually secondary problems.</p><p>The real challenge is organizational.</p><p><strong>Specifically:</strong> How two groups think about ownership, delivery, governance, architecture, and accountability.</p><p>&gt; See <a href="https://blog.bradyclifford.me/Merging-Two-Operating-Models/">https://blog.bradyclifford.me/Merging-Two-Operating-Models/</a> for more details</p><h3>The Mistake Most Organizations Make</h3><p>The most common failure pattern I have seen is leadership attempting to standardize too quickly.</p><p>Typically this includes:</p><ul><li>Forcing common tooling</li><li>Forcing common workflows</li><li>Forcing shared governance models</li><li>Centralizing delivery processes</li><li>Unifying team structures</li><li>Enforcing identical SDLC practices</li></ul><p>The assumption is: “If everyone operates the same way, integration becomes easier.”</p><p>In practice, the opposite often occurs.</p><p>Instead of reducing friction, organizations accidentally destroy the strengths that made one or both groups successful in the first place.</p><p>Martin Fowler and Sriram Narayan described this tension well when discussing product-oriented organizations:</p><blockquote>“Organizations operating in product-mode use durable, ideate-build-run teams working on a persistent business issue to continuously deliver value to customers.”</blockquote><blockquote>— Martin Fowler, Programs in Product Mode</blockquote><p>The mistake many acquiring organizations make is assuming those durable operating characteristics can simply be replaced through process standardization.</p><p><em>Accelerate</em> shows what is lost when those conditions are disrupted:</p><blockquote>“Continuous delivery improves both delivery performance and quality, and it helps improve culture and reduces burnout and deployment pain.”</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Forsgren, Humble, Kim)</blockquote><h3>Operating Models Are Architectural Forces</h3><p>Operating models are not simply management preferences.</p><p>They directly shape:</p><ul><li>Team topology</li><li>Communication paths</li><li>Deployment patterns</li><li>Ownership boundaries</li><li>Governance models</li><li>System architecture</li></ul><p>This is <a href="https://martinfowler.com/bliki/ConwaysLaw.html">Conway’s Law</a> at organizational scale.</p><p>For a deeper dive into how this shows up in architecture modernization efforts, see <a href="https://blog.bradyclifford.me/Conways-Law/">The Reverse Conway Maneuver</a>.</p><p>If one company operates with:</p><ul><li>stream-aligned product teams</li><li>CI/CD ownership</li><li>domain-centric architecture</li><li>durable team ownership</li></ul><p>while the other operates with:</p><ul><li>activity-oriented teams</li><li>centralized release management</li><li>heavy governance</li><li>large approval chains</li></ul><p>then the resulting systems will naturally reflect those differences.</p><p>Trying to force both into a single model immediately usually creates organizational instability.</p><p>As Fowler and Narayan describe:</p><blockquote>“It is common for organizations operating in this way to have an organizational structure that mirrors their architecture.”</blockquote><blockquote>— Martin Fowler, Programs in Product Mode</blockquote><p>That relationship between organizational communication and system design becomes critically important during mergers.</p><p><em>Accelerate</em> ties this architectural coupling directly to delivery performance:</p><blockquote>“Our research found that high performers were more likely to have a loosely coupled architecture. A loosely coupled architecture enables teams to make large-scale changes to the design of their system without depending on other teams to make changes in their own systems, and without requiring permission from outside the team.”</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Forsgren, Humble, Kim)</blockquote><h3>Tooling Is Rarely the Real Problem</h3><p>One of the clearest lessons I learned is that tooling debates are usually proxy wars for operating model conflicts.</p><p>The arguments appear to be about:</p><ul><li>work item management platforms (Jira vs ADO, etc.)</li><li>documentation platforms (Confluence, SharePoint, etc.)</li><li>communication mediums (email, chat, etc.)</li><li>GitHub vs centralized SCM</li><li>release pipelines</li><li>approval workflows</li></ul><p>But underneath those discussions are deeper assumptions:</p><ul><li>Who owns delivery?</li><li>Who approves production changes?</li><li>How autonomous are teams?</li><li>Is governance proactive or reactive?</li><li>Are teams aligned to activities or business capabilities?</li><li>Is the organization optimizing for flow or control?</li></ul><p>The tools simply expose those differences.</p><p>In many acquisitions, the tooling debate becomes a surrogate for a much larger argument about organizational trust.</p><h3>Activity-Oriented vs Business-Capability-Centric</h3><p>The largest divide I encountered was between two fundamentally different organizational philosophies.</p><h4>Activity-Oriented Organizations</h4><p>These organizations optimize around:</p><ul><li>specialized functions</li><li>centralized governance</li><li>handoffs</li><li>standardized processes</li><li>resource pooling</li><li>offshore scaling</li><li>operational control</li></ul><p>Examples include:</p><ul><li>centralized testing teams</li><li>separate deployment teams</li><li>ticket-driven infrastructure</li><li>architecture review gates</li><li>release management offices</li></ul><p>This model can work reasonably well for:</p><ul><li>large compliance-heavy environments</li><li>predictable delivery patterns</li><li>highly centralized organizations</li></ul><p>But it tends to create:</p><ul><li>slower flow</li><li>larger coordination overhead</li><li>weaker ownership</li><li>tightly coupled systems</li></ul><p>Martin Fowler’s article on activity-oriented organizations describes the tradeoff directly:</p><blockquote>“Activity-oriented teams are prone to optimize for their own activity and not for the bigger picture of delivering useful software.”</blockquote><blockquote>— Martin Fowler, Activity-Oriented Organizations</blockquote><p>Another important observation:</p><blockquote>“Organizing by activity gets in the way of lowering batch size of work that is handed-off between teams.”</blockquote><blockquote>— Martin Fowler, Activity-Oriented Organizations</blockquote><p>That is exactly the behavior many organizations unintentionally amplify after acquisitions.</p><h4>Business-Capability-Centric Organizations</h4><p>These organizations optimize around:</p><ul><li>durable ownership</li><li>business outcomes</li><li>product thinking</li><li>autonomous delivery</li><li>end-to-end accountability</li><li>rapid feedback loops</li></ul><p>Teams typically own:</p><ul><li>infrastructure</li><li>testing</li><li>deployment</li><li>observability</li><li>operational support</li><li>domain architecture</li></ul><p>This model tends to produce:</p><ul><li>faster learning</li><li>better architectural cohesion</li><li>higher deployment frequency</li><li>stronger accountability</li><li>lower coordination overhead</li></ul><p>But it requires significant organizational trust.</p><p>That sounds deceptively simple, but it fundamentally changes ownership models, incentives, and long-term architectural evolution.</p><p><em>Accelerate</em> confirms the performance advantage this model produces:</p><blockquote>“High performers were more likely to be able to make large-scale changes to the design of their systems on their own, without depending on other teams to make changes in their systems, and without requiring orchestration with other teams.”</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Forsgren, Humble, Kim)</blockquote><h3>Why Standardization Often Fails</h3><p>In acquisitions, one operating model usually becomes dominant.</p><p>The dominant organization often unintentionally encodes its assumptions into:</p><ul><li>tooling</li><li>governance</li><li>workflow states</li><li>reporting structures</li><li>approval models</li><li>architectural standards</li></ul><p>The other organization then experiences growing friction.</p><p>Their teams appear:</p><ul><li>slower</li><li>resistant</li><li>fragmented</li><li>misaligned</li></ul><p>But often the real issue is structural mismatch.</p><p>The organization is measuring one operating model using metrics designed for another.</p><p>In many cases, leadership mistakes reduced autonomy for improved alignment.</p><p>But alignment created through forced process standardization is often fragile.</p><p>The <em>Accelerate</em> research on organizational culture explains why:</p><blockquote>“Organizational culture predicts the way information flows through an organization. Good information flow is critical to the safe and effective operation of high-tempo and complex operations such as software development and delivery.”</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Forsgren, Humble, Kim)</blockquote><h3>Conway’s Law Always Wins</h3><p>One of the hardest truths in enterprise architecture is this:</p><p>You cannot separate organizational structure from system architecture.</p><p>Eventually the systems mirror the communication structure of the organization.</p><p>If you want additional context on applying this organizationally, I also covered it in <a href="https://blog.bradyclifford.me/Conways-Law/">The Reverse Conway Maneuver</a>.</p><p>If organizations:</p><ul><li>centralize decision making</li><li>fragment ownership</li><li>create approval-heavy delivery</li><li>split responsibilities across many teams</li></ul><p>their systems become:</p><ul><li>tightly coupled</li><li>difficult to evolve</li><li>coordination-heavy</li><li>slow to deploy</li></ul><p>Likewise, when organizations align around:</p><ul><li>bounded contexts</li><li>durable ownership</li><li>stream-aligned teams</li><li>platform enablement</li></ul><p>their systems evolve differently.</p><p>This is why organizational integration strategy matters more than most technical integration strategies.</p><p>A merger may consolidate systems relatively quickly.</p><p>But if the communication model remains fragmented, the architecture eventually reflects that fragmentation.</p><h3>The Better Strategy: Align Objectives, Not Everything Else</h3><p>The most successful approach I have seen is not immediate operational unification.</p><p>Instead:</p><ul><li>align around principles</li><li>align around outcomes</li><li>align around architectural direction</li><li>align around governance intent</li></ul><p>while allowing operating models to remain intentionally different where appropriate.</p><p>This means accepting that:</p><ul><li>different SDLC models may coexist</li><li>different team topologies may coexist</li><li>different governance approaches may coexist</li><li>different tooling patterns may coexist</li></ul><p>for a significant period of time.</p><p>That is not failure.</p><p>That is realism.</p><p>As Fowler noted when discussing programs in product-oriented organizations:</p><blockquote>“Programs — where delivering customer value demands orchestration across multiple teams — are a real challenge for product-mode organizations.”</blockquote><blockquote>— Martin Fowler, Programs in Product Mode</blockquote><p>Acquisitions magnify those coordination challenges significantly.</p><h3>Shared Principles Matter More Than Shared Process</h3><p>The healthiest mergers I have seen focused on shared principles instead of forcing identical execution models.</p><p>Examples:</p><ul><li>API-first integration</li><li>domain ownership</li><li>automation-first delivery</li><li>observability standards</li><li>infrastructure as code</li><li>bounded contexts</li><li>platform enablement</li><li>deployment automation</li><li>security guardrails</li></ul><p>Those principles create alignment without forcing every team into identical workflows.</p><p>One of the most important organizational shifts is moving away from measuring local optimization.</p><p>As Fowler observed:</p><blockquote>“Activity-oriented organization may be attractive from the perspective of maximizing utilization but it comes in the way of maximizing value-addition and end-to-end responsiveness.”</blockquote><blockquote>— Martin Fowler, Activity-Oriented Organizations</blockquote><p>That distinction becomes critical during post-acquisition integration.</p><h3>Platform Teams Instead of Centralized Control</h3><p>One of the more effective patterns I have seen is transforming centralized operational groups into platform teams.</p><p>Instead of:</p><ul><li>ticket queues</li><li>deployment approvals</li><li>infrastructure handoffs</li><li>centralized release ownership</li></ul><p>platform teams provide:</p><ul><li>self-service infrastructure</li><li>CI/CD tooling</li><li>observability</li><li>security baselines</li><li>reusable capabilities</li><li>automation guardrails</li></ul><p>This allows multiple operating models to coexist while still maintaining enterprise consistency.</p><p>Healthy platform organizations reduce friction instead of becoming centralized gatekeepers.</p><p>Their purpose is enablement.</p><p>Not control.</p><h3>Governance Through Visibility, Not Friction</h3><p>Organizations often assume mergers require more approval layers.</p><p>In practice, excessive governance friction usually slows integration efforts dramatically.</p><p>A better approach is:</p><ul><li>transparent reporting</li><li>policy automation</li><li>architectural visibility</li><li>observability</li><li>deployment telemetry</li><li>auditability</li></ul><p>This creates trust without creating bottlenecks.</p><p>The goal should be: high visibility with low friction.</p><blockquote>We found that external approvals were negatively correlated with lead time, deployment frequency, and restore time, and had no correlation with change fail rate. In short, approval by an external body (such as a manager or CAB) simply doesn’t work to increase the stability of production systems, measured by the time to restore service and change fail rate. However, it certainly slows things down. It is, in fact, worse than having no change approval process at all.</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Nicole Forsgren, Jez Humble, Gene Kim)</blockquote><p>Many enterprise organizations still underestimate how much coordination friction impacts delivery performance.</p><h3>The Most Important Lesson</h3><p>The biggest lesson I learned from operating model integration is this:</p><p>You cannot force trust, autonomy, and product ownership into existence through process frameworks.</p><p>Those are organizational and leadership decisions.</p><p>If leadership fundamentally distrusts teams, then:</p><ul><li>project-mode dominates</li><li>approvals multiply</li><li>centralized governance expands</li><li>coordination overhead grows</li><li>architecture quality degrades</li></ul><p>No tooling migration or framework adoption will solve that.</p><p>As Fowler wrote in <em>Products Over Projects</em>:</p><blockquote>“For building, running and iterating on the solution or even pivoting to a different solution till the underlying problem is verifiably solved.”</blockquote><blockquote>— Martin Fowler, Products Over Projects</blockquote><p>That level of ownership cannot exist in organizations built entirely around temporary delivery structures and fragmented accountability.</p><p><em>Accelerate</em> identifies organizational culture as the precondition that makes this ownership sustainable:</p><blockquote>“Our research strongly suggests that culture is one of the most important predictors of IT performance and organizational performance in general. High-trust, generative cultures outperform low-trust, bureaucratic ones — and that difference compounds over time.”</blockquote><blockquote>— Accelerate: The Science of Lean Software and DevOps (Forsgren, Humble, Kim)</blockquote><h3>Final Thoughts</h3><p>Acquisitions often fail technologically not because the systems are incompatible, but because the organizations are.</p><p>The most successful long-term integrations I have seen:</p><ul><li>respected operating model differences</li><li>aligned around outcomes instead of process</li><li>invested in platform capabilities</li><li>preserved durable ownership</li><li>reduced unnecessary coordination</li><li>optimized for flow instead of control</li></ul><p>The organizations that struggled most were the ones attempting to standardize everything immediately.</p><p>Integration should focus on:</p><ul><li>shared direction</li><li>shared principles</li><li>shared trust</li></ul><p>not forced uniformity.</p><p>Because in the end, architecture follows communication structures.</p><p>And communication structures follow organizational design.</p><p>Conway’s Law always wins.</p><p><em>Originally published at </em><a href="https://blog.bradyclifford.me/Merging-Two-Operating-Models/"><em>https://blog.bradyclifford.me</em></a><em> on April 4, 2026.</em></p><h3>References</h3><ul><li><a href="https://blog.bradyclifford.me/Conways-Law/">The Reverse Conway Maneuver</a></li><li><a href="https://martinfowler.com/articles/programs-in-product-mode.html">Martin Fowler — Programs in Product Mode</a></li><li><a href="https://martinfowler.com/bliki/ActivityOriented.html">Martin Fowler — Activity-Oriented Organizations</a></li><li><a href="https://martinfowler.com/bliki/BusinessCapabilityCentric.html">Martin Fowler — Business Capability Centric Organizations</a></li><li><a href="https://martinfowler.com/bliki/OutcomeOriented.html">Martin Fowler — Outcome-Oriented Organizations</a></li><li><a href="https://martinfowler.com/articles/products-over-projects.html">Martin Fowler — Products Over Projects</a></li><li><a href="https://martinfowler.com/bliki/TeamTopologies.html">Martin Fowler — Team Topologies</a></li><li><a href="https://martinfowler.com/bliki/ConwaysLaw.html">Martin Fowler — Conway’s Law</a></li><li>Eric Evans — <em>Domain-Driven Design</em></li><li>Matthew Skelton &amp; Manuel Pais — <em>Team Topologies</em></li><li>Forsgren, Humble, Kim — <em>Accelerate: The Science of Lean Software and DevOps</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7426025e5a63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conway’s Law & the Reverse Conway Maneuver]]></title>
            <link>https://bradyclifford.medium.com/conways-law-the-reverse-conway-maneuver-de39fd9e9cfd?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/de39fd9e9cfd</guid>
            <category><![CDATA[team-topologies]]></category>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[conways-law]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Fri, 08 May 2026 20:04:30 GMT</pubDate>
            <atom:updated>2026-05-18T12:53:01.998Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most important lessons I have learned in enterprise software architecture is that organizational structure matters just as much as technical architecture.</p><p>Possibly more.</p><p>Many organizations attempt large-scale modernization efforts:</p><ul><li>microservices</li><li>domain-driven design</li><li>event-driven architectures</li><li>micro-frontends</li><li>CI/CD transformations</li><li>cloud-native migrations</li></ul><p>while leaving their organizational structure fundamentally unchanged.</p><p>Years later, leadership wonders why:</p><ul><li>systems remain tightly coupled</li><li>deployments are still slow</li><li>dependencies continue growing</li><li>ownership remains unclear</li><li>teams struggle with coordination</li><li>architecture quality degrades over time</li></ul><p>The answer is usually Conway’s Law.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DwzIZvnswWffn-0NKx0vBw.png" /></figure><h3>What Conway’s Law Actually Means</h3><p>Melvin Conway observed:</p><blockquote>“Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.”</blockquote><p>In practice, this means:</p><ul><li>centralized organizations produce centralized systems</li><li>siloed organizations produce siloed architectures</li><li>activity-based teams produce tightly coupled systems</li><li>stream-aligned teams produce modular systems</li></ul><p>Architecture is not purely a technical exercise.</p><p>It is a social one.</p><h3>The Architecture Organizations Say They Want</h3><p>Most enterprise organizations today claim they want:</p><ul><li>loosely coupled systems</li><li>autonomous teams</li><li>independent deployments</li><li>rapid delivery</li><li>high resiliency</li><li>scalable ownership</li><li>product-oriented thinking</li></ul><p>This usually leads to technical initiatives around:</p><ul><li>APIs</li><li>event-driven design</li><li>domain-driven design</li><li>microservices</li><li>micro-frontends</li><li>bounded contexts</li></ul><p>But many organizations stop there.</p><p>They modernize the technology stack while preserving:</p><ul><li>project-based funding</li><li>centralized governance</li><li>horizontal teams</li><li>ticket-driven infrastructure</li><li>approval chains</li><li>shared ownership</li><li>release coordination offices</li></ul><p>This creates structural contradiction.</p><h3>You Cannot Build Autonomous Systems with Non-Autonomous Teams</h3><p>This is one of the hardest realities for leadership to accept.</p><p>If teams do not own:</p><ul><li>architecture</li><li>infrastructure</li><li>deployments</li><li>operations</li><li>testing</li><li>observability</li><li>domain decisions</li></ul><p>then the systems themselves will not become autonomous.</p><p>Instead, organizations create distributed monoliths:</p><ul><li>tightly coupled services</li><li>shared databases</li><li>synchronous dependencies</li><li>coordinated releases</li><li>fragile integrations</li></ul><p>The technology changes.</p><p>The operating model does not.</p><p>Conway’s Law wins.</p><h3>The Reverse Conway Maneuver</h3><p>The Reverse Conway Maneuver is the intentional act of designing organizations to produce the architecture you actually want.</p><p>Instead of asking: “How should we structure our systems?”</p><p>you ask: “What organizational structure would naturally produce those systems?”</p><p>That shift is incredibly important.</p><p>If the goal is:</p><ul><li>domain ownership</li><li>bounded contexts</li><li>independent deployments</li><li>event-driven integration</li><li>low coupling</li><li>high cohesion</li></ul><p>then the teams themselves must align around those boundaries.</p><h3>Durable Teams Matter</h3><p>One of the strongest patterns I have seen in successful organizations is durable ownership.</p><p>Teams remain aligned to business capabilities over long periods of time.</p><p>They accumulate:</p><ul><li>domain knowledge</li><li>operational understanding</li><li>architectural context</li><li>customer understanding</li><li>historical decisions</li><li>production experience</li></ul><p>This dramatically improves:</p><ul><li>delivery quality</li><li>incident response</li><li>architectural consistency</li><li>long-term maintainability</li></ul><p>Temporary project teams rarely achieve this.</p><h3>The Failure of Project-Mode Thinking</h3><p>Many organizations still fund work primarily through projects.</p><p>Projects optimize for:</p><ul><li>temporary delivery</li><li>timelines</li><li>milestones</li><li>utilization</li><li>task completion</li></ul><p>Products optimize for:</p><ul><li>outcomes</li><li>ownership</li><li>evolution</li><li>operational excellence</li><li>customer value</li><li>long-term sustainability</li></ul><p>This distinction matters enormously.</p><p>Project funding encourages:</p><ul><li>temporary staffing</li><li>fragmented ownership</li><li>short-term tradeoffs</li><li>architectural shortcuts</li><li>delivery pressure over sustainability</li></ul><p>Product-mode encourages:</p><ul><li>durable ownership</li><li>investment in maintainability</li><li>platform thinking</li><li>long-term accountability</li></ul><p>Without product-mode thinking, Conway’s Law tends to push systems toward fragmentation and coordination overhead.</p><h3>Domain-Driven Design Changes Team Design Too</h3><p>Many organizations adopt the language of Domain-Driven Design without fully embracing the organizational implications.</p><p>Bounded contexts are not just technical boundaries.</p><p>They are ownership boundaries.</p><p>A healthy bounded context typically includes ownership of:</p><ul><li>APIs</li><li>data</li><li>infrastructure</li><li>testing</li><li>deployment</li><li>operational support</li><li>front-end experience</li><li>domain workflows</li></ul><p>This is where Team Topologies becomes extremely valuable.</p><p>When teams align to business capabilities and bounded contexts:</p><ul><li>communication paths simplify</li><li>cognitive load drops</li><li>ownership becomes clear</li><li>deployments become safer</li><li>coordination overhead decreases</li></ul><p>The architecture becomes easier to evolve because the organization itself supports the architecture.</p><h3>Coupling vs Cohesion</h3><p>One of the recurring misunderstandings in enterprise modernization efforts is confusing cohesion with coupling.</p><p>Organizations often attempt to “align” teams by forcing:</p><ul><li>shared databases</li><li>shared infrastructure</li><li>centralized services</li><li>common release cycles</li></ul><p>This increases coupling.</p><p>Healthy architectures instead maximize:</p><ul><li>cohesion inside a bounded context</li><li>loose coupling between bounded contexts</li></ul><p>Bounded contexts should collaborate through:</p><ul><li>APIs</li><li>events</li><li>contracts</li><li>asynchronous messaging</li></ul><p>not through direct database access or organizational dependency chains.</p><p>The same principle applies organizationally.</p><p>Teams should collaborate frequently.</p><p>But they should not require constant coordination to function.</p><h3>Event-Driven Design and Organizational Autonomy</h3><p>One of the strongest architectural patterns I have seen supporting autonomous teams is event-driven design.</p><p>Events reduce direct runtime dependency between systems.</p><p>Instead of:</p><ul><li>tightly coupled synchronous calls</li><li>orchestrated release coordination</li><li>direct database integrations</li></ul><p>systems communicate through published domain events.</p><p>This allows teams to:</p><ul><li>deploy independently</li><li>evolve independently</li><li>scale independently</li><li>operate independently</li></ul><p>But event-driven architecture only works well when organizational ownership boundaries are equally clear.</p><p>Otherwise organizations simply recreate tight coupling through process instead of technology.</p><h3>Governance Without Destroying Flow</h3><p>Large organizations often react to complexity by introducing:</p><ul><li>approvals</li><li>architecture boards</li><li>release committees</li><li>CABs</li><li>centralized reviews</li></ul><p>The intention is usually risk reduction.</p><p>But excessive governance frequently increases:</p><ul><li>lead time</li><li>coordination cost</li><li>deployment risk</li><li>organizational friction</li></ul><p>The highest-performing organizations I have worked with instead relied on:</p><ul><li>automated testing</li><li>CI/CD</li><li>observability</li><li>policy guardrails</li><li>peer review</li><li>platform engineering</li><li>rapid rollback capability</li></ul><p>Governance shifted from gatekeeping to visibility.</p><p>That distinction matters enormously.</p><h3>Product Owners Need Real Authority</h3><p>Another common anti-pattern is organizations attempting to create product-oriented teams while withholding actual authority from Product Owners.</p><p>In many enterprises:</p><ul><li>Product Owners do not control prioritization</li><li>architecture investment is centrally dictated</li><li>operational work is deprioritized</li><li>reliability work requires approval battles</li><li>delivery metrics dominate outcome metrics</li></ul><p>This weakens the entire operating model.</p><p>If organizations want autonomous systems, they must empower autonomous teams.</p><p>That requires trust.</p><h3>Final Thoughts</h3><p>Conway’s Law is not merely an architectural observation.</p><p>It is one of the most important organizational truths in software engineering.</p><p>The systems organizations build inevitably reflect:</p><ul><li>communication structures</li><li>ownership boundaries</li><li>governance models</li><li>funding models</li><li>trust structures</li></ul><p>If organizations want:</p><ul><li>modular architectures</li><li>independent deployments</li><li>product ownership</li><li>faster delivery</li><li>resilient systems</li></ul><p>then they must intentionally design their organizations to support those outcomes.</p><p>That is the Reverse Conway Maneuver.</p><p>Without it, modernization efforts often become expensive technology rewrites wrapped around the same organizational dysfunctions.</p><p>The tools change.</p><p>The architecture diagrams change.</p><p>But the communication structure remains the same.</p><p>And eventually, the systems reflect it again.</p><p><em>Originally published at </em><a href="https://blog.bradyclifford.me/Conways-Law/"><em>https://blog.bradyclifford.me</em></a><em> on April 25, 2025.</em></p><h3>References</h3><ul><li><a href="https://martinfowler.com/articles/programs-in-product-mode.html">Martin Fowler — Programs in Product Mode</a></li><li><a href="https://martinfowler.com/bliki/ActivityOriented.html">Martin Fowler — Activity-Oriented Organizations</a></li><li><a href="https://martinfowler.com/bliki/BusinessCapabilityCentric.html">Martin Fowler — Business Capability Centric Organizations</a></li><li><a href="https://martinfowler.com/bliki/OutcomeOriented.html">Martin Fowler — Outcome-Oriented Organizations</a></li><li><a href="https://martinfowler.com/articles/products-over-projects.html">Martin Fowler — Products Over Projects</a></li><li><a href="https://martinfowler.com/bliki/TeamTopologies.html">Martin Fowler — Team Topologies</a></li><li>Eric Evans — <em>Domain-Driven Design</em></li><li>Martin Fowler — <em>Patterns of Enterprise Application Architecture</em></li><li>Matthew Skelton &amp; Manuel Pais — <em>Team Topologies</em></li><li>Forsgren, Humble, Kim — <em>Accelerate: The Science of Lean Software and DevOps</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de39fd9e9cfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is SAFe the Right Fit?]]></title>
            <link>https://bradyclifford.medium.com/is-safe-the-right-fit-877179146946?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/877179146946</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[conways-law]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team-topologies]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Fri, 08 May 2026 00:00:50 GMT</pubDate>
            <atom:updated>2026-05-18T12:46:29.904Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the years, I have worked with organizations attempting to “become agile” while still preserving traditional operating models, governance structures, approval chains, and project funding practices. In many of those environments, the Scaled Agile Framework (SAFe) was introduced as the solution.</p><p>In practice, I have rarely seen SAFe solve the underlying problem.</p><p>What I <em>have</em> seen is organizations using SAFe as a way to avoid confronting deeper organizational and architectural issues:</p><ul><li><a href="https://blog.bradyclifford.me/Conways-Law/">Conway’s Law misalignment</a></li><li>Project-based funding models</li><li>Activity-oriented organizational structures</li><li>Lack of trust in product ownership</li><li>Centralized governance bottlenecks</li><li>Weak domain ownership</li><li>Large handoff-oriented delivery models</li></ul><p>SAFe often becomes a coordination layer wrapped around those existing problems rather than a mechanism that resolves them.</p><p>As Martin Fowler describes in <em>Activity-Oriented Organizations</em>:</p><blockquote>“Activity-oriented organizations optimize for functional efficiency instead of customer outcomes.”</blockquote><p>That pattern is extremely common in enterprise SAFe transformations. The framework becomes an overlay on top of siloed operating structures rather than a catalyst for redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pdnz0nbYRAnNoulsq8xxSQ.png" /></figure><p>This article builds on concepts discussed in:</p><ul><li><a href="https://blog.bradyclifford.me/Conways-Law/">Conway’s Law and Reverse Conway Maneuver</a></li><li><a href="https://blog.bradyclifford.me/Merging-Two-Operating-Models/">Merging Two Operating Models</a></li></ul><h3>The Appeal of SAFe</h3><p>To be fair, SAFe solves real problems for leadership.</p><p>In large enterprises, executives often struggle with:</p><ul><li>Planning visibility</li><li>Budget forecasting</li><li>Cross-team coordination</li><li>Governance consistency</li><li>Vendor management</li><li>Compliance reporting</li><li>Dependency management</li></ul><p>SAFe provides a framework that makes those concerns easier to manage organizationally.</p><p>In the first year especially, leadership usually feels relief:</p><ul><li>Better reporting</li><li>Standardized ceremonies</li><li>Centralized planning</li><li>Predictable release trains</li><li>Cleaner portfolio dashboards</li></ul><p>From a management perspective, it feels like progress.</p><p>But many organizations confuse improved coordination with improved agility.</p><p>Those are not the same thing.</p><p>Martin Fowler captured this distinction well in <em>Programs in Product Mode</em>:</p><blockquote>“The shift from project to product is fundamentally a shift from temporary delivery structures to persistent ownership.”</blockquote><p>SAFe implementations often improve visibility while still preserving temporary project-oriented thinking underneath.</p><h3>SAFe Often Optimizes for Coordination Over Flow</h3><p>One of the recurring patterns I have observed is that SAFe tends to reinforce activity-oriented operating models rather than outcome-oriented ones.</p><p>Instead of reducing dependencies, organizations frequently use SAFe to manage dependencies at scale.</p><p>That distinction matters.</p><p>There is a major difference between:</p><ul><li>designing systems and teams to minimize coordination needs</li><li>creating larger coordination structures to compensate for tightly coupled systems</li></ul><p>The first approach improves flow.</p><p>The second institutionalizes complexity.</p><p>This is where Conway’s Law becomes unavoidable.</p><p>Organizations structured around:</p><ul><li>centralized governance</li><li>horizontal teams</li><li>shared services</li><li>approval chains</li><li>project funding</li><li>release management offices</li></ul><p>will naturally produce systems reflecting those same communication structures.</p><p>The result is usually:</p><ul><li>tightly coupled systems</li><li>centralized databases</li><li>release coordination overhead</li><li>slow deployments</li><li>architectural friction</li><li>unclear ownership boundaries</li></ul><p>SAFe can manage that complexity operationally, but it does not necessarily reduce it architecturally.</p><p>Martin Fowler described the alternative in <em>Business Capability Centric Organizations</em>:</p><blockquote>“Organizations should be aligned around business capabilities rather than technology layers or activities.”</blockquote><p>That alignment dramatically reduces coordination overhead because ownership boundaries become clearer both organizationally and architecturally.</p><h3>The Hidden Cost: Cognitive Load</h3><p>One of the biggest long-term issues with SAFe is cognitive load.</p><p>As organizations scale coordination layers:</p><ul><li>PI planning</li><li>ART synchronization</li><li>dependency management</li><li>governance reviews</li><li>architecture review boards</li><li>approval workflows</li><li>portfolio alignment meetings</li></ul><p>teams spend increasing amounts of time managing the system around delivery instead of delivering value.</p><p>Strong teams become slower because they inherit the coordination burden of weaker or more fragmented organizational structures.</p><p>Matthew Skelton and Manuel Pais describe this directly in <em>Team Topologies</em>:</p><blockquote>“Cognitive load is a limiting factor for teams.”</blockquote><p>The more coordination structures organizations introduce, the more cognitive capacity gets consumed by the mechanics of delivery instead of solving customer problems.</p><p>This creates an especially painful outcome in organizations that previously had highly autonomous, stream-aligned teams.</p><p>Over time:</p><ul><li>deployment frequency drops</li><li>lead time increases</li><li>ownership becomes diluted</li><li>innovation slows</li><li>teams become risk-averse</li><li>architecture quality degrades</li></ul><p>The organization becomes optimized for predictability instead of adaptability.</p><p>This is where the research from <em>Accelerate</em> becomes particularly important.</p><p>Forsgren, Humble, and Kim found that elite-performing organizations were able to achieve both higher stability and higher throughput simultaneously.</p><p>Some of the findings that directly contradict common enterprise assumptions include:</p><ul><li>High performers deploy code <strong>multiple times per day</strong></li><li>High performers have <strong>lead times measured in hours instead of weeks</strong></li><li>High performers recover from incidents significantly faster</li><li>Change failure rates are <em>lower</em>, not higher, in fast-moving organizations</li></ul><p>One of the most important conclusions from <em>Accelerate</em> was:</p><blockquote>“Speed and stability are not tradeoffs.”</blockquote><p>Many enterprise governance models implicitly assume the opposite.</p><p>Large coordination-heavy frameworks often optimize for perceived safety while unintentionally reducing both adaptability and actual delivery performance.</p><h3>SAFe and the Illusion of Agility</h3><p>Many organizations adopting SAFe still operate fundamentally in waterfall patterns.</p><p>The terminology changes:</p><ul><li>projects become “epics” or “initiatives”</li><li>phases become “program increments”</li><li>release planning becomes “PI planning”</li></ul><p>But structurally, very little changes.</p><p>Funding remains project-oriented.</p><p>Architecture remains centralized.</p><p>Teams remain activity-oriented.</p><p>Product owners remain backlog coordinators rather than empowered business leaders.</p><p>The organization talks about agility while preserving the same command-and-control system underneath.</p><p>This is one of the most common anti-patterns I have seen in enterprise transformations.</p><p>Martin Fowler wrote in <em>Products Over Projects</em>:</p><blockquote>“Projects are temporary; products require long-term ownership.”</blockquote><p>Without changing funding and ownership models, many agile transformations simply relabel project governance using agile terminology.</p><h3>Product Owners Without Product Authority</h3><p>A recurring issue in SAFe implementations is the treatment of Product Owners.</p><p>In healthy product-mode organizations, Product Owners:</p><ul><li>own business outcomes</li><li>control prioritization</li><li>make tradeoff decisions</li><li>balance reliability, architecture, and features</li><li>shape long-term product direction</li></ul><p>In many SAFe implementations, Product Owners instead become:</p><ul><li>backlog administrators</li><li>Jira managers</li><li>dependency coordinators</li><li>sprint planners</li><li>status reporters</li></ul><p>They are held accountable for outcomes without having authority over investment or strategic direction.</p><p>This disconnect creates organizational friction and weakens team autonomy.</p><p>It also undermines one of the core goals of agile delivery: fast learning through empowered teams.</p><p>Martin Fowler describes healthy product organizations this way in <em>Programs in Product Mode</em>:</p><blockquote>“Persistent teams aligned to business outcomes build deeper domain knowledge and better products.”</blockquote><p>That ownership model is difficult to achieve when decision-making remains centralized above the team level.</p><h3>Durable Teams vs Temporary Coordination Structures</h3><p>In my experience, durable, domain-aligned, stream-aligned teams outperform large-scale coordination models over the long term.</p><p>Strong product organizations optimize for:</p><ul><li>bounded contexts</li><li>clear ownership</li><li>high cohesion</li><li>low coupling</li><li>autonomous deployment</li><li>business capability alignment</li><li>fast feedback loops</li></ul><p>This dramatically reduces the need for centralized coordination.</p><p>When organizations instead optimize for:</p><ul><li>resource utilization</li><li>shared activity teams</li><li>project staffing pools</li><li>centralized governance</li><li>offshore task distribution</li></ul><p>they increase coordination complexity.</p><p>SAFe often becomes the mechanism used to manage that growing complexity.</p><p>But managing complexity is not the same thing as reducing it.</p><p>As <em>Team Topologies</em> explains:</p><blockquote>“The team is the means of delivery.”</blockquote><p>Architecture, communication structure, deployment independence, and flow efficiency all emerge from how teams are designed.</p><h3>Reverse Conway Maneuver Matters More Than SAFe</h3><p>One of the most effective organizational strategies I have seen is the Reverse Conway Maneuver: designing team structures intentionally around the architecture and business outcomes you want.</p><p>If you want:</p><ul><li>loosely coupled systems</li><li>autonomous services</li><li>domain ownership</li><li>rapid delivery</li><li>high deployment frequency</li></ul><p>then teams themselves must reflect those boundaries.</p><p>That means:</p><ul><li>stream-aligned teams</li><li>product ownership</li><li>end-to-end accountability</li><li>embedded quality practices</li><li>platform enablement instead of ticket-driven infrastructure</li></ul><p>No framework can compensate for organizational structures fundamentally working against the architecture.</p><p>This idea aligns closely with Conway’s Law itself:</p><blockquote>“Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.”</blockquote><p>The Reverse Conway Maneuver intentionally uses that reality to improve architectural outcomes instead of fighting against it.</p><p><em>See </em><a href="https://blog.bradyclifford.me/Conways-Law/"><em>The Reverse Conway Maneuver</em></a><em> for additional details.</em></p><h3>Governance Without Bottlenecks</h3><p>One of the biggest misconceptions in large enterprises is that governance requires approvals and centralized control.</p><p>The highest-performing organizations I have worked with instead rely on:</p><ul><li>automation</li><li>observability</li><li>policy guardrails</li><li>peer review</li><li>deployment pipelines</li><li>progressive delivery</li><li>rapid rollback capability</li></ul><p>Governance becomes transparent and measurable rather than approval-driven.</p><p>This aligns closely with findings from <em>Accelerate</em>, which showed that external approval processes negatively correlate with software delivery performance.</p><p>Forsgren, Humble, and Kim found that:</p><blockquote>“Approval processes are positively correlated with burnout and negatively correlated with performance.”</blockquote><p>That finding challenges a deeply embedded assumption in many enterprise governance models.</p><p>Organizations become safer not by slowing down changes, but by:</p><ul><li>improving detection</li><li>improving recovery</li><li>reducing batch sizes</li><li>increasing deployment confidence</li></ul><p>Another important finding from <em>Accelerate</em> was that smaller batch sizes and frequent deployments reduce risk because problems become easier to isolate and recover from.</p><p>Large governance-heavy release models often create the exact opposite condition: large risky deployments coordinated across many teams simultaneously.</p><h3>When SAFe Can Work</h3><p>I do think SAFe can serve a purpose in certain environments.</p><p>Particularly:</p><ul><li>highly regulated industries</li><li>organizations with massive dependency networks</li><li>companies early in modernization journeys</li><li>enterprises lacking any delivery discipline</li><li>transitional states between legacy and product-mode</li></ul><p>As a temporary scaffold, SAFe can create organizational consistency.</p><p>But it becomes dangerous when:</p><ul><li>it becomes permanent</li><li>it replaces organizational redesign</li><li>it reinforces project-mode thinking</li><li>it preserves activity-based silos</li><li>it discourages autonomy</li></ul><p>At that point, the framework itself becomes part of the inertia.</p><h3>My Experience and Conclusion</h3><p>The organizations I have seen move fastest long term were not the ones with the most process.</p><p>They were the ones that:</p><ul><li>trusted teams</li><li>aligned ownership to business capabilities</li><li>funded products instead of projects</li><li>reduced handoffs</li><li>invested in architecture</li><li>optimized for flow over reporting</li><li>empowered product owners</li><li>embraced platform engineering</li><li>minimized coordination overhead</li></ul><p>Their systems reflected those structures.</p><p>That is Conway’s Law in action.</p><p>Martin Fowler summarized this well in <em>Outcome-Oriented Organizations</em>:</p><blockquote>“Outcome-oriented organizations focus on results rather than activities.”</blockquote><p>SAFe can improve planning optics and organizational coordination. But if the underlying operating model remains project-centric and activity-oriented, the organization will continue producing tightly coupled systems and slow delivery patterns regardless of the agile terminology being used.</p><p>The data from <em>Accelerate</em> reinforces this reality: the highest-performing technology organizations consistently optimize for:</p><ul><li>fast feedback</li><li>low-friction delivery</li><li>deployment automation</li><li>empowered teams</li><li>reduced handoffs</li><li>smaller batch sizes</li><li>continuous learning</li></ul><p>Not heavier coordination structures.</p><p>In the end, sustainable agility comes less from frameworks and more from:</p><ul><li>trust</li><li>ownership</li><li>architecture</li><li>organizational alignment</li><li>empowered teams</li><li>outcome-oriented thinking</li></ul><p>Frameworks can support those things.</p><p>They cannot replace them.</p><p><em>Originally published at </em><a href="https://blog.bradyclifford.me/Is-Safe-Right-Fit/"><em>https://blog.bradyclifford.me</em></a><em> on May 8, 2026.</em></p><h3>References</h3><ul><li><a href="https://martinfowler.com/articles/programs-in-product-mode.html">Martin Fowler — Programs in Product Mode</a></li><li><a href="https://martinfowler.com/bliki/ActivityOriented.html">Martin Fowler — Activity-Oriented Organizations</a></li><li><a href="https://martinfowler.com/bliki/BusinessCapabilityCentric.html">Martin Fowler — Business Capability Centric Organizations</a></li><li><a href="https://martinfowler.com/bliki/OutcomeOriented.html">Martin Fowler — Outcome-Oriented Organizations</a></li><li><a href="https://martinfowler.com/articles/products-over-projects.html">Martin Fowler — Products Over Projects</a></li><li><a href="https://martinfowler.com/bliki/TeamTopologies.html">Martin Fowler — Team Topologies</a></li><li>Forsgren, Humble, Kim — <em>Accelerate: The Science of Lean Software and DevOps</em></li><li>Eric Evans — <em>Domain-Driven Design</em></li><li>Matthew Skelton &amp; Manuel Pais — <em>Team Topologies</em></li><li>Tradable Quality Hypothesis</li><li>Design Stamina Hypothesis</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=877179146946" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first look at HTTP/2]]></title>
            <link>https://bradyclifford.medium.com/my-first-look-at-http-2-5234196f579d?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/5234196f579d</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[http2]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 20:01:39 GMT</pubDate>
            <atom:updated>2017-02-20T20:01:39.302Z</atom:updated>
            <content:encoded><![CDATA[<p>Great podcast by .NetRocks on the upcoming HTTP/2 with Robert Boedigheimer. The main browsers support it. Waiting for the servers to get up to speed. Windows 10’s IIS already supports it. Need to wait for Windows Server 2016 release and will hopefully see it on Azure.</p><p>It is basically resolving the issue that we currently have how many requests a browser can do in parallel… 6 request at once seems to be cap with HTTP/1.1. HTTP/2 is opening up the flood gates. Not only will it allow for more requests in parallel, it also allows the client to ask for dependencies using a dependency map with priority weight.</p><p>The server also has the ability to send resources to the client without he client first asking. The server knows that client will need this Css file and this JavaScript file. Why not send it in the initial request? The protocol will now transmit using binaries instead of plain basic text.</p><p>With the issue of capped requests gone, Robert is suggesting that we don’t need to package up our Css and JavaScript anymore.<br> No more sprits in Css or embedded binary images. It is still important to minifiy, but no need to package and combine our resources. This brings back the ability for smaller files to be cached. If I change a single line in a large bundle, the entire bundle becomes expired. There will still be a need for compression and expiration. CDNs are still a plus.</p><p>Overall, you will see 5%-15% speed increase from HTTP/1.1 to HTTP/2 not taking advantage of the new features. Image the speed increase you can get once you implement the new features.</p><p>Listen to the <a href="https://www.dotnetrocks.com/?show=1224">Podcast</a>.</p><p><em>Originally published at </em><a href="http://bradyclifford.me/HTTP-2/"><em>bradyclifford.me</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5234196f579d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first look at Go Lang]]></title>
            <link>https://bradyclifford.medium.com/my-first-look-at-go-lang-3717a582a0d8?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/3717a582a0d8</guid>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 20:00:02 GMT</pubDate>
            <atom:updated>2017-02-20T20:02:08.001Z</atom:updated>
            <content:encoded><![CDATA[<p>Had my first look at the Go Lang. Went ahead with a small exercise and wrote a ball clock out of the language.</p><p>Overall, I am impressed. It seems similiar to Swift yet has its own glow. I really liked the ability to return multiple values.</p><p>Take a look at my solution on <a href="https://github.com/bradyclifford/BallClock">GitHub</a>.</p><p><em>Originally published at </em><a href="http://bradyclifford.me/GoBallClock/"><em>bradyclifford.me</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3717a582a0d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Task Runners and Building our JavaScript Code]]></title>
            <link>https://bradyclifford.medium.com/task-runners-and-building-our-javascript-code-1e4fe7f4de00?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e4fe7f4de00</guid>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webpack]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 19:59:22 GMT</pubDate>
            <atom:updated>2017-02-20T19:59:22.674Z</atom:updated>
            <content:encoded><![CDATA[<p>No excuses now, every should be transpiling and building their web application. I put together a <a href="http://www.slideshare.net/bradyclifford/building-javascript">slidedeck</a> that went through the whys and the benefits. <a href="http://www.slideshare.net/bradyclifford/building-javascript">Take a look</a>…</p><p>I based my slidedeck on the presentation <a href="https://youtu.be/VkTCL6Nqm6Y">Peter Hunt</a> gave back in 2014.</p><p><strong>To summarize:</strong></p><ul><li>Spas are the best UX experience</li><li>Con is that the initial load takes too long</li><li>Instagram has 10 SPAs in their architecture</li><li>Reduce amount of HTTP requests &amp; bytes downloaded</li><li>Bundling everything into one file is not the best approach 2.5MB gzip bundled file is too big.</li><li>Utilize a module system to intelligently bundle your packages with a dynamic dependency map.</li></ul><p>The 2 slides from his presentation that impacted me the most:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/0*JTr4NZWC_xSwxvHj.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/0*CmtdmvtC_tIB1pgL.png" /></figure><h3>Overall, I argued the need to build web front end code to enable:</h3><ul><li><strong>Developers to mimic production on their own box</strong>.</li><li>Developers are able to identify concatenation and minification issues before code is checked in.</li><li>The build config is shared amongst all environments Prepares us for AngularJs 2 and ES6</li><li><strong>Automated versioning of shared packaged libraries</strong>.</li><li>Treat our shared libriaries like 3rd parties</li><li>On check-in, build, package and version shared libraries deploying to local package repository like git. This speeds up the build process for the Spa and also removes versioning within a given repository.</li><li>Part of the build process can also incorporate the automation of generating documentation and demos. See how AngularStrap and UI-Boostrap and achieving this from their source code.</li><li><strong>Utilize a package manager and a local rev. repository</strong>.</li><li><strong>Automated builds of documentation and shared component demos</strong>.</li><li><strong>Reduction and even elimination of Glofs and Glogs</strong>.</li><li><strong>Reduce initial Spa loading time</strong> through intelligent bundling: use a module system and an intelligent dependency map bundling tool, like webpack.</li><li><strong>Architecting our web application code so it is web server agnostic</strong>.</li><li>Instead of loading 100+ servers with our web application files, we can upload them to one location</li><li>Avoids the second hop to our F5 and web farm in our current architecture</li><li>Brings us closer to a true micro services SOA architecture; separating the front end from the middle tier.</li><li>Allows us to use redirection only for api calls. Don’t have to perform a browser redirect during login.</li><li>An example of a server agnostic web application:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/0*lNokCBOab2HR_HVq.png" /></figure><p><em>Originally published at </em><a href="http://bradyclifford.me/Build-JavaScript/"><em>bradyclifford.me</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e4fe7f4de00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Importance of a Style Guide]]></title>
            <link>https://bradyclifford.medium.com/importance-of-a-style-guide-5d2e153ce98a?source=rss-ae60a26d7a23------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d2e153ce98a</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brady Clifford]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 19:56:59 GMT</pubDate>
            <atom:updated>2017-02-20T19:56:59.504Z</atom:updated>
            <content:encoded><![CDATA[<p>There is an great AngularJs focus group that meets every month. They have had some great presentations while providing free pizza to those who are present. I recommend anyone getting their hands dirty with AngularJS, attend this focus group.</p><p>One of the topics that has been addressed repeatedly in this focus group is the need for each attendee to generate a best practice style guide for AngularJs development unique to their company. A style guide for syntax, conventions, and structuring AngularJS applications. The groups argument is to never work in a vacuum. Not only is there a need for a syntax reference (which most companies already have), but also live styling examples that lay the foundation for all UI development. These styling examples are hosted on a live site, real-time with the most up-to-date UI color, font and CSS styling and AngularJs directive (module) examples; they are the baseline that should be referenced when generating new content instead of referencing code in the actually application code base. The idea is comparable to the <a href="http://getbootstrap.com/">Bootstrap</a> and <a href="http://ionicframework.com/docs/components/">Ionic Framework</a> public style guides. These are more <strong>UX/UI Pattern Guides</strong>; something I also feel is important to implement.</p><p>This focus groups has primarily centered their eye on a commonly referenced AngularJS standard guide on GitHub maintained by <a href="https://github.com/johnpapa/angular-styleguide">John Papa</a>. It lists AngularJs best practices such as utilizing controllerAs syntax in a view and refactoring data calls into factory services. It not only lists AngularJS best practices but also a lot of JavaScript best practices like implementing ‘use stict’ and removing variables from the global scope with an IIFE. There are other comparable style guides out there by Todd Motto, Minko Gechev, and Topcoder-inc that are also good references; see these links at the end of this post.</p><blockquote><em>I suggest anyone wanting to utilize AngularJS in their projects, reference this style guide and eventually assist in creating our own company’s AngularJs style guide that not only helps us in defining our AngularJS syntax and best practices but also helps in generating live styling examples that can lay the foundation for all future UI development.</em></blockquote><p><em>Originally published at </em><a href="http://bradyclifford.me/AngularJs-Utah/"><em>bradyclifford.me</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d2e153ce98a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>