Presentation given at Pamplona Software Craftsmanship 2017 talking about the things that influence the architecture like our relation with business, deadlines, deploying to production and organisational design.
Web Governance: Where Strategy Meets StructurePeter Morville
The document discusses the topic of web governance. It suggests that web governance is needed to address issues like fragmentation and findability on websites. It presents a framework for web governance that includes establishing a web governance board, having a unified web strategy, and utilizing network intelligence. The framework also discusses establishing local governance structures. It provides examples of levers that can be used to drive change, such as designing for connection, utilizing organizational charts, and establishing pods/teams.
Join Josh Koenig, Co-Founder and Head of Product at Pantheon, as he discusses how to prepare for a major project and ensure that momentum carries into your project.
Whether you plan, design, build, or manage sites for clients or internal projects, you will come away from this webinar with tools to crush your next mega client project.
Dylan Beattie "Architecture: The Stuff That's Hard to Change"Fwdays
We’ve all heard of the idea of ‘software architecture’. We’ve read books about domain-driven design and event sourcing, we’ve been to conferences and learned about microservices and REST APIs. Some of us remember working with n-tiers and stored procedures; some of us are still using them. But the role of a systems architect is still one of the most misunderstood things about the software development process. What does an architect actually do? If you’re working with a systems architect, what can you expect from them? And if you are a systems architect, what is your team expecting from you?
In this talk, Dylan Beattie will share his own insights into the idea of architecture as part of a software development process. We’ll explore some popular architectural patterns and processes – and a couple of obscure ones as well – and look at how, and when, you can incorporate those patterns into your own projects. We’ll talk about how the idea of software architecture has changed over time, and share some tips and advice for developers who find themselves working with architecture as part of their role.
This presentation discusses information architecture in a broad context, connecting technological, business, and user experience perspectives. It provides an overview of information architecture as a practice and defines the presenter's concept of a "RuleSpace," describing the web as a continuum with consistent rules or idioms for user experience. The presentation argues that considering a website's place within this RuleSpace continuum is important for design and for maintaining the interconnected nature of the web.
Accidental Architects - how HR designs software systems - Team Topologies - N...Matthew Skelton
Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture?
Organization architecture and software system architecture need to be co-designed to avid friction from Conway's Law.
---
From a talk given by Matthew Skelton at NAV, Oslo - 2020-01-23
Maximising the value of the Cloud through DevOpsDevOpsGroup
This presentation talks about how the Cloud and DevOps are complementary innovations that can work together to rapidly change the productivity inside organisations.
Learn how DevOps can maximise the value of your investment in the Cloud.
This is part 1 of a 3 part series from a joint DevOpsGuys / Microsoft event held at The Shard, London, 24th January 2017
Web Governance: Where Strategy Meets StructurePeter Morville
The document discusses the topic of web governance. It suggests that web governance is needed to address issues like fragmentation and findability on websites. It presents a framework for web governance that includes establishing a web governance board, having a unified web strategy, and utilizing network intelligence. The framework also discusses establishing local governance structures. It provides examples of levers that can be used to drive change, such as designing for connection, utilizing organizational charts, and establishing pods/teams.
Join Josh Koenig, Co-Founder and Head of Product at Pantheon, as he discusses how to prepare for a major project and ensure that momentum carries into your project.
Whether you plan, design, build, or manage sites for clients or internal projects, you will come away from this webinar with tools to crush your next mega client project.
Dylan Beattie "Architecture: The Stuff That's Hard to Change"Fwdays
We’ve all heard of the idea of ‘software architecture’. We’ve read books about domain-driven design and event sourcing, we’ve been to conferences and learned about microservices and REST APIs. Some of us remember working with n-tiers and stored procedures; some of us are still using them. But the role of a systems architect is still one of the most misunderstood things about the software development process. What does an architect actually do? If you’re working with a systems architect, what can you expect from them? And if you are a systems architect, what is your team expecting from you?
In this talk, Dylan Beattie will share his own insights into the idea of architecture as part of a software development process. We’ll explore some popular architectural patterns and processes – and a couple of obscure ones as well – and look at how, and when, you can incorporate those patterns into your own projects. We’ll talk about how the idea of software architecture has changed over time, and share some tips and advice for developers who find themselves working with architecture as part of their role.
This presentation discusses information architecture in a broad context, connecting technological, business, and user experience perspectives. It provides an overview of information architecture as a practice and defines the presenter's concept of a "RuleSpace," describing the web as a continuum with consistent rules or idioms for user experience. The presentation argues that considering a website's place within this RuleSpace continuum is important for design and for maintaining the interconnected nature of the web.
Accidental Architects - how HR designs software systems - Team Topologies - N...Matthew Skelton
Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture?
Organization architecture and software system architecture need to be co-designed to avid friction from Conway's Law.
---
From a talk given by Matthew Skelton at NAV, Oslo - 2020-01-23
Maximising the value of the Cloud through DevOpsDevOpsGroup
This presentation talks about how the Cloud and DevOps are complementary innovations that can work together to rapidly change the productivity inside organisations.
Learn how DevOps can maximise the value of your investment in the Cloud.
This is part 1 of a 3 part series from a joint DevOpsGuys / Microsoft event held at The Shard, London, 24th January 2017
Information Architecture 3.0 (Second Life)Peter Morville
The document is a presentation by Peter Morville on information architecture (IA). It discusses how IA is evolving from organizing websites and intranets to also include shaping digital experiences and finding information from anywhere at any time. It emphasizes that information that is hard to find will remain hardly found.
Do Learn Repeat: The Startup Way of DesignHarris Rodis
This document provides links to resources about Lean UX, product design, user experience research methods, and data-informed product development. It emphasizes embracing failure as part of the design process, collaborating across teams, and experimenting to validate ideas rather than following prescribed paths to success. The links cover topics like the evolution of Behance, Lean UX principles, the hype cycle, waterfall vs agile development, design feedback, and using data to inform rather than drive decisions.
This document provides an introduction to a computer architecture lecture. It discusses key concepts like abstraction layers in computing systems and the role of computer architects. It uses examples like multi-core processors to illustrate how understanding lower levels can help optimize higher levels. The document emphasizes understanding principles and precedents to enable new, principled designs that consider tradeoffs across abstraction layers. It highlights the importance of computer architecture in enabling innovations and insights.
This document provides an introduction to a lecture on computer architecture given by Prof. Onur Mutlu at ETH Zürich. It discusses several key concepts:
- It introduces assignments for students to visit famous architectural works to appreciate design principles and tradeoffs.
- It discusses levels of abstraction in computing from algorithms to logic gates and electrons. Abstraction improves productivity but understanding lower levels is important for optimization and troubleshooting.
- The role of an architect is defined as considering the past, future, problems in the computing stack, and underlying technologies to design innovative systems that enable new capabilities.
- Principled design based on understanding fundamentals rather than just precedent is emphasized as seen in the works of
This document provides an overview of entrepreneurship in the intelligent transportation systems sector over the past decade. It discusses how entrepreneurs have helped drive innovation and transformation in transportation technologies, such as connected and autonomous vehicles, in the same way entrepreneurs revolutionized transportation in previous centuries through innovations like canals, railroads, automobiles, airlines, and more. The document argues that while large corporations and government agencies also play important roles, entrepreneurs are uniquely motivated to take risks and achieve successes that disrupt outdated systems and help transportation systems to continuously evolve. It notes that entrepreneurship will continue to be important for the ongoing transformation of intelligent transportation.
Slide deck from Henry Stewart DAM Chicago, September 15, 2016.
Session description: The theory and practice of Digital Asset Management can serve as a lens through which the transformation of long-held business practices may be viewed. In this provocative session, Douglas Hegley will combine concepts from Clayton Christensen’s book The Innovator’s Dilemma with best practices in DAMs to demonstrate how the power of systems thinking can drive positive disruption. Such disruptive changes are necessitated by the volatile, uncertain, complex and ambiguous world in which we live. To succeed in that world, businesses need to rely on people - knowledge workers - who can combine agility with disciplined methodology. To do so, it is necessary to re-imagine organizational structures, unleash individual talent, enable teams to self-organize, and evolve leadership models. In essence, it is people who are our greatest assets, because they are at the very core of every aspect of modern business. As any DAMs Manager knows: when important assets are hidden away and difficult to use, their inherent value is lost - but when those assets are clearly identified, easy to find and utilized effectively, innovation and success will follow.
1. The document discusses plans for establishing an installer business and investing in a glass community partnership.
2. It analyzes whether partners Magi and Marcus have enough income and assets to cover the requirements and ongoing warehouse needs while still having gains to invest.
3. The document also lists current partners and provides graphs and tables analyzing partner investments, branching vectors, and changes in the thruput basis.
STUDY ON SCOPE OF PARAMETRIC SOFTWARES IN ARCHITECTUREAnganam
The document discusses the scope of parametric software in architecture. It begins with an introduction to parametric architecture and its significance. The aim and objectives are to study the evolution and existing possibilities of parametric architecture software compared to traditional CAD. The methodology and definitions are provided. The document then discusses the history of parametric architecture, existing parametric software capabilities, and potential for parametric urbanism. A case study of the Hangzhou Olympic Sports Center is presented to illustrate the design process using parametric modeling. The distinctions between parametric and CAD software are analyzed. Finally, the merits, demerits and comparative analysis of parametric architecture are discussed along with conclusions and references.
Those who cannot remember the past are condemned to repeat it. –George Santayana
The past is never dead. It’s not even past. –William Faulkner
Most developers pursue the Latest and Greatest with intense fervor, yet the history of engineering, including software projects, contains rich lessons that we risk repeating ad nauseam. This session recounts a variety of stories of projects that failed…and why. Ranging from the Vasa in 1628 to Knight Capital in 2012, each story tells of a mistaken interpretation of some architectural fundamental principle and the consequences–some good, some less so. I also look at the common threads for these stories, which resonates with problems many companies have but don’t realize.
Pets. Com, San Francisco project, The Vasa, F16, Sagrada Familia, Tacoma Narrows Bridge, null, Ada, Serialization, Knight Capital, Ariane 5, Webvan, Chandler project
Session for IASA ITARC Conference on digital-transformation, London, 26 May 2017: https://www.iasaglobal.org/itarc-london-may/
By definition a transformation will always be complex, often to extremes. So how can we, as architects, address all of that complexity, and still stay somewhat sane?
One long-proven answer is the humble checklist – a list of essential items that people tend to forget when the going gets tough. This session introduces a seven-point transformation-checklist for architects: purpose and story; scope and scale; governance; constraints; structure-flaws; test at the extremes; resistance to change.
This checklist can be used within almost any type of architecture-guided transformation. We’ll explore its practical application, usage and implications in a variety of real-world architecture contexts. But beware: you may be surprised at what a simple checklist can show you…
The Balanced Scorecard for Green Engineering in Digital Design is emulated as begin to MAP Digital Portal Requirements in relation to Digital to Ark Mappings we have already emulated. We approach the Gates in a tentative engineering position to look at what kind of requirements we should be aware of Financially. Our First Foil is explained in Detail and a Detailed Enterprise Map is presented.
This document discusses emerging trends that will shape the future of cities. It identifies eight connected emerging trends: 1) social architecture and social innovation, 2) local economies, 3) city, citizen, and place 2.0, 4) sustainable transportation, 5) disruptive technology, 6) reframing the concept of education and work, 7) holistic infrastructures that are human and bio-centric, and 8) cities as the savior of humanity. It also discusses tools for foresight planning like scenario development and discusses concepts like intentional evolution and integral cities.
The document discusses how systems of systems are changing product design and manufacturing. As products, buildings, and infrastructure become smarter, more connected, and data-rich, design must shift from discrete things to integrated systems. The talk will showcase frog's view of "Big Design," which designs adaptive, modular, intelligent systems that connect the human, enterprise, and urban scales. Big Design uses design and engineering to shape interconnected, intelligent systems across many levels. This represents a shift in value from individual devices to connected systems.
A round up of resources (websites, blogs and other sources) that I've found useful in 2015 and will continue to do so in 2016. This edition is centered around 3 key trends for 2016.
A visible architecture is a physical model of a software system created by architecture teams using Duplo® bricks, with strings representing data flows. Visible architectures enable teams to collaboratively understand the “as-is” architecture and make better choices on the “to-be” architecture. We use Visible Architectures and frameworks like Speed Boat and Prune the Product Tree to help teams succeed. This deck outlines a step-by-step process for how to create a visible architecture.
Rethinking enterprise architecture for DevOps, Agile, and cloud native organi...Michael Coté
The document discusses rethinking enterprise architecture for DevOps, agile, and cloud native organizations. It notes that traditional enterprise architecture focused on governance and standards is at odds with the rapid release cycles of modern software development. A new model treats the platform itself as a product with engineers focused on developer productivity, standardized tools and automation. The CIO takes on a new role of guiding technical decisions while giving teams more autonomy over delivery.
Architecture & IA: Expanding the Metaphor - IA Summit 2016Jessica DuVerneay
This document discusses using physical architecture as a metaphor for information architecture (IA). It notes both strengths and limitations of this metaphor. It argues that current metaphors focus too narrowly on recent Western architecture and proposes expanding the metaphor to include traditional, natural, and indigenous architectures. It provides strategies for improving IA practice by considering sustainability, context, inclusion, and looking beyond individual projects. The document advocates for IA practitioners to help drive cultural and political change through more responsible design.
The use of an architecture–centered development process for delivering information technology began with the introduction of client / server based systems. Early client/server and legacy mainframe applications did not provide the architectural flexibility needed to meet the changing business requirements of the modern manufacturing organization. With the introduction of Object Oriented systems, the need for an architecture–centered process became a critical success factor. Object reuse, layered system components, data abstraction,
web based user interfaces, CORBA, and rapid development and deployment processes all provide economic
incentives for object technologies. However, adopting the latest object oriented technology, without an adequate understanding of how this technology fits a specific architecture, risks the creation of an instant legacy
system.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Elm is a functional programming language inspired by ML and Haskell. It compiles to HTML, CSS, and JavaScript, allowing developers to build web applications in a functional style. Elm uses immutable values and static typing to prevent runtime exceptions. The Elm architecture defines a common pattern for building Elm applications with a model, view, and update function to manage data flow in a declarative way.
More Related Content
Similar to Architecture, architects and other mythological creatures
Information Architecture 3.0 (Second Life)Peter Morville
The document is a presentation by Peter Morville on information architecture (IA). It discusses how IA is evolving from organizing websites and intranets to also include shaping digital experiences and finding information from anywhere at any time. It emphasizes that information that is hard to find will remain hardly found.
Do Learn Repeat: The Startup Way of DesignHarris Rodis
This document provides links to resources about Lean UX, product design, user experience research methods, and data-informed product development. It emphasizes embracing failure as part of the design process, collaborating across teams, and experimenting to validate ideas rather than following prescribed paths to success. The links cover topics like the evolution of Behance, Lean UX principles, the hype cycle, waterfall vs agile development, design feedback, and using data to inform rather than drive decisions.
This document provides an introduction to a computer architecture lecture. It discusses key concepts like abstraction layers in computing systems and the role of computer architects. It uses examples like multi-core processors to illustrate how understanding lower levels can help optimize higher levels. The document emphasizes understanding principles and precedents to enable new, principled designs that consider tradeoffs across abstraction layers. It highlights the importance of computer architecture in enabling innovations and insights.
This document provides an introduction to a lecture on computer architecture given by Prof. Onur Mutlu at ETH Zürich. It discusses several key concepts:
- It introduces assignments for students to visit famous architectural works to appreciate design principles and tradeoffs.
- It discusses levels of abstraction in computing from algorithms to logic gates and electrons. Abstraction improves productivity but understanding lower levels is important for optimization and troubleshooting.
- The role of an architect is defined as considering the past, future, problems in the computing stack, and underlying technologies to design innovative systems that enable new capabilities.
- Principled design based on understanding fundamentals rather than just precedent is emphasized as seen in the works of
This document provides an overview of entrepreneurship in the intelligent transportation systems sector over the past decade. It discusses how entrepreneurs have helped drive innovation and transformation in transportation technologies, such as connected and autonomous vehicles, in the same way entrepreneurs revolutionized transportation in previous centuries through innovations like canals, railroads, automobiles, airlines, and more. The document argues that while large corporations and government agencies also play important roles, entrepreneurs are uniquely motivated to take risks and achieve successes that disrupt outdated systems and help transportation systems to continuously evolve. It notes that entrepreneurship will continue to be important for the ongoing transformation of intelligent transportation.
Slide deck from Henry Stewart DAM Chicago, September 15, 2016.
Session description: The theory and practice of Digital Asset Management can serve as a lens through which the transformation of long-held business practices may be viewed. In this provocative session, Douglas Hegley will combine concepts from Clayton Christensen’s book The Innovator’s Dilemma with best practices in DAMs to demonstrate how the power of systems thinking can drive positive disruption. Such disruptive changes are necessitated by the volatile, uncertain, complex and ambiguous world in which we live. To succeed in that world, businesses need to rely on people - knowledge workers - who can combine agility with disciplined methodology. To do so, it is necessary to re-imagine organizational structures, unleash individual talent, enable teams to self-organize, and evolve leadership models. In essence, it is people who are our greatest assets, because they are at the very core of every aspect of modern business. As any DAMs Manager knows: when important assets are hidden away and difficult to use, their inherent value is lost - but when those assets are clearly identified, easy to find and utilized effectively, innovation and success will follow.
1. The document discusses plans for establishing an installer business and investing in a glass community partnership.
2. It analyzes whether partners Magi and Marcus have enough income and assets to cover the requirements and ongoing warehouse needs while still having gains to invest.
3. The document also lists current partners and provides graphs and tables analyzing partner investments, branching vectors, and changes in the thruput basis.
STUDY ON SCOPE OF PARAMETRIC SOFTWARES IN ARCHITECTUREAnganam
The document discusses the scope of parametric software in architecture. It begins with an introduction to parametric architecture and its significance. The aim and objectives are to study the evolution and existing possibilities of parametric architecture software compared to traditional CAD. The methodology and definitions are provided. The document then discusses the history of parametric architecture, existing parametric software capabilities, and potential for parametric urbanism. A case study of the Hangzhou Olympic Sports Center is presented to illustrate the design process using parametric modeling. The distinctions between parametric and CAD software are analyzed. Finally, the merits, demerits and comparative analysis of parametric architecture are discussed along with conclusions and references.
Those who cannot remember the past are condemned to repeat it. –George Santayana
The past is never dead. It’s not even past. –William Faulkner
Most developers pursue the Latest and Greatest with intense fervor, yet the history of engineering, including software projects, contains rich lessons that we risk repeating ad nauseam. This session recounts a variety of stories of projects that failed…and why. Ranging from the Vasa in 1628 to Knight Capital in 2012, each story tells of a mistaken interpretation of some architectural fundamental principle and the consequences–some good, some less so. I also look at the common threads for these stories, which resonates with problems many companies have but don’t realize.
Pets. Com, San Francisco project, The Vasa, F16, Sagrada Familia, Tacoma Narrows Bridge, null, Ada, Serialization, Knight Capital, Ariane 5, Webvan, Chandler project
Session for IASA ITARC Conference on digital-transformation, London, 26 May 2017: https://www.iasaglobal.org/itarc-london-may/
By definition a transformation will always be complex, often to extremes. So how can we, as architects, address all of that complexity, and still stay somewhat sane?
One long-proven answer is the humble checklist – a list of essential items that people tend to forget when the going gets tough. This session introduces a seven-point transformation-checklist for architects: purpose and story; scope and scale; governance; constraints; structure-flaws; test at the extremes; resistance to change.
This checklist can be used within almost any type of architecture-guided transformation. We’ll explore its practical application, usage and implications in a variety of real-world architecture contexts. But beware: you may be surprised at what a simple checklist can show you…
The Balanced Scorecard for Green Engineering in Digital Design is emulated as begin to MAP Digital Portal Requirements in relation to Digital to Ark Mappings we have already emulated. We approach the Gates in a tentative engineering position to look at what kind of requirements we should be aware of Financially. Our First Foil is explained in Detail and a Detailed Enterprise Map is presented.
This document discusses emerging trends that will shape the future of cities. It identifies eight connected emerging trends: 1) social architecture and social innovation, 2) local economies, 3) city, citizen, and place 2.0, 4) sustainable transportation, 5) disruptive technology, 6) reframing the concept of education and work, 7) holistic infrastructures that are human and bio-centric, and 8) cities as the savior of humanity. It also discusses tools for foresight planning like scenario development and discusses concepts like intentional evolution and integral cities.
The document discusses how systems of systems are changing product design and manufacturing. As products, buildings, and infrastructure become smarter, more connected, and data-rich, design must shift from discrete things to integrated systems. The talk will showcase frog's view of "Big Design," which designs adaptive, modular, intelligent systems that connect the human, enterprise, and urban scales. Big Design uses design and engineering to shape interconnected, intelligent systems across many levels. This represents a shift in value from individual devices to connected systems.
A round up of resources (websites, blogs and other sources) that I've found useful in 2015 and will continue to do so in 2016. This edition is centered around 3 key trends for 2016.
A visible architecture is a physical model of a software system created by architecture teams using Duplo® bricks, with strings representing data flows. Visible architectures enable teams to collaboratively understand the “as-is” architecture and make better choices on the “to-be” architecture. We use Visible Architectures and frameworks like Speed Boat and Prune the Product Tree to help teams succeed. This deck outlines a step-by-step process for how to create a visible architecture.
Rethinking enterprise architecture for DevOps, Agile, and cloud native organi...Michael Coté
The document discusses rethinking enterprise architecture for DevOps, agile, and cloud native organizations. It notes that traditional enterprise architecture focused on governance and standards is at odds with the rapid release cycles of modern software development. A new model treats the platform itself as a product with engineers focused on developer productivity, standardized tools and automation. The CIO takes on a new role of guiding technical decisions while giving teams more autonomy over delivery.
Architecture & IA: Expanding the Metaphor - IA Summit 2016Jessica DuVerneay
This document discusses using physical architecture as a metaphor for information architecture (IA). It notes both strengths and limitations of this metaphor. It argues that current metaphors focus too narrowly on recent Western architecture and proposes expanding the metaphor to include traditional, natural, and indigenous architectures. It provides strategies for improving IA practice by considering sustainability, context, inclusion, and looking beyond individual projects. The document advocates for IA practitioners to help drive cultural and political change through more responsible design.
The use of an architecture–centered development process for delivering information technology began with the introduction of client / server based systems. Early client/server and legacy mainframe applications did not provide the architectural flexibility needed to meet the changing business requirements of the modern manufacturing organization. With the introduction of Object Oriented systems, the need for an architecture–centered process became a critical success factor. Object reuse, layered system components, data abstraction,
web based user interfaces, CORBA, and rapid development and deployment processes all provide economic
incentives for object technologies. However, adopting the latest object oriented technology, without an adequate understanding of how this technology fits a specific architecture, risks the creation of an instant legacy
system.
Similar to Architecture, architects and other mythological creatures (20)
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Elm is a functional programming language inspired by ML and Haskell. It compiles to HTML, CSS, and JavaScript, allowing developers to build web applications in a functional style. Elm uses immutable values and static typing to prevent runtime exceptions. The Elm architecture defines a common pattern for building Elm applications with a model, view, and update function to manage data flow in a declarative way.
Este documento describe varias técnicas para analizar código como una escena del crimen para identificar posibles problemas, incluyendo el análisis de complejidad, tasas de cambio, acoplamientos temporales y de pruebas, y mapas de conocimiento. También advierte que estas técnicas no deben tomarse como verdades absolutas y que cada caso requiere una evaluación individual.
Gestión del ciclo de vida de aplicaciones Web. Continuous deployment.Vicenç García-Altés
Presentación de la charla sobre Gestión del ciclo de vida de aplicaciones Web y Continuous Deployment hecha en el evento realizado en Zaragoza el 4 de febrero de 2014 (www.plainconcepts.com/webzaragoza)
OWIN es un estándar abierto que separa las aplicaciones web .NET de los servidores web, permitiendo que las aplicaciones se ejecuten en cualquier servidor compatible con OWIN. Proporciona acceso a los datos de solicitud y respuesta a través de objetos como Request y Response. Katana es una implementación de referencia de OWIN para ASP.NET.
This document provides references for further reading on behavior-driven development (BDD) including books on BDD in action and bridging communication gaps with acceptance testing, the website for Specification by Example which discusses specifying requirements through examples, and blog posts on doing BDD before tools and an introduction to BDD and its principles.
El documento resume las novedades de .NET 4.5.1, Visual Studio 2013 y Team Foundation Server 2013, incluyendo mejoras en productividad, rendimiento e innovación en el IDE y editor de Visual Studio 2013, así como nuevas funcionalidades para planificación, colaboración y codificación en Team Foundation Server y soporte para Git. También resume las nuevas características y APIs para desarrollo de aplicaciones modernas para Windows Store usando XAML, HTML, JavaScript o C++.
Plain Concepts ALM Tour 2013 - Estamos construyendo lo que el cliente esperaVicenç García-Altés
This document outlines the development lifecycle from planning through requirements, development, testing, and release. It lists several Agile and DevOps tools and practices including Agile portfolio management, Kanban customization, work item tagging, Git, CodeLens indicators, Visual Studio and System Center integration, performance monitoring, .NET memory analysis, integrated release management, configuration-based deployments, web test case management, cross-browser testing, load testing as a service, and cross-device partnerships to deliver working software. The overall message is about applying Agile and DevOps practices throughout the development lifecycle.
Plain Concepts ALM Tour 2013 - Maximizando la productividad de nuestros equiposVicenç García-Altés
Víctor Galtes es un experto en desarrollo .NET y Visual Studio que ofrece servicios como consultoría y formación. Sus áreas de especialización incluyen desarrollo ágil, DevOps, y herramientas de Microsoft como Visual Studio y Azure. Mantiene un blog y sitio web donde comparte consejos y recursos para desarrolladores.
Especificaciones ejecutables, acercando negocio y desarrolloVicenç García-Altés
Presentación en la Conferencia Agile Spain 2013 sobre especificaciones ejecutables, specification by example, bdd. Es un vistazo teórico a las ventajas de esta forma de trabajar.
This document describes an exercise used in a retrospective session to address unsatisfactory retrospectives. Participants were asked to:
1) Organize into groups and discuss a past retrospective experience that was unsatisfactory, choosing one situation to focus on.
2) Use an empathy mapping technique to understand the perspectives and experiences of those involved in the chosen situation.
3) Brainstorm potential solutions to the problem by thinking of the opposite problem and magnifying the original problem to generate ideas for avoiding it in the future.
The goal was to apply techniques from other domains to retrospectives to help participants analyze problematic past experiences and develop strategies for improvement.
Este documento presenta información sobre dos personas, Rodrigo Corral y Vicenç García, incluyendo sus direcciones de correo electrónico, blogs y cuentas de Twitter. Luego proporciona una breve descripción de Scrum, incluyendo roles como Scrum Master, Product Owner y el Equipo, así como eventos como la Reunión Diaria de Scrum, la Reunión de Planificación del Sprint y la Revisión e Retrospectiva del Sprint. Finalmente, menciona algunos desafíos comunes de Scrum.
This document provides an overview of agile inception techniques to help start a project on the right foot. It includes topics like alignment, expectation setting, designing the product box, creating a "not" list of things to avoid, empathy mapping of different personas, effect mapping, and sizing up what will give value and what will be challenging. Additional resources on agile inception are also provided.
This document contains contact information for Vicenç García Altes, including his name, title as a Development Advisor for Plain Concepts, email address, blog URL, and Twitter handle. It lists this information twice.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
5. Architecture is the decisions that
you wish you could get right
early in a project, but that you
are not necessarily more likely
to get them right than any other.
5
Ralph Johnson
10. ACTIVITIES AND ARTIFACTS
■ Domain vision statement creation -> Domain vision statement, List of
business capabilities, Glossary
■ Study business roadmap -> List of business capabilities, Glossary
■ Reference scenario mapping -> List of reference scenarios, Glossary
■ Business process flow mapping -> Business process flow map, List of
business capabilities, List of domain events, Glossary
■ Exception scenario mapping -> Business process flow map, List of domain
events, Glossary
■ System mapping -> High level system diagram, Glossary
■ Context mapping -> Context map, Glossary
■ Domain refactoring -> Subdomain map
■ Domain modeling -> Domain models for each subdomain
10
19. CONWAY’S LAW
19
“organizations which
design systems ... are
constrained to produce
designs which are copies
of the communication
structures of these
organizations”
Mel Conway, 1968
20. We find strong evidence to
support the hypothesis that a
product’s architecture tends to
mirror the structure of the
organization in which it is
developed.
20
MacCormack et al
26. TYPES OF SOFTWARE MONOLITHS
■ Application monolith
■ Joined at the DB
■ Monolithic build (rebuild everything)
■ Monolithic releases (release everything)
■ Monolithic model and implementation (attempted consistency across many
different contexts)
■ Monolithic thinking (apply same solutions for everything)
26
27. FRACTURE PLANES
■ Business domain bounded context
■ Regulatory compliance
■ Change cadence
■ Technology
■ Risk
■ Performance isolation
■ User personas
■ Team location
■Customer responsiveness
27
305 aC
Rodas invadida por Demetrio I de Macedonia -> Poliorcetes, conquistador de ciudades. Pidieron ayuda al dios Helios, protector de la ciudad.
Torres de asedio. La primera hundida por una tormenta
La segunda en tierra, pero hinundada por los Rodios
Ptolomeo envió un ejercito que hizo huir a Poliorcetes
Escultura al dios Helios -> Chares de Lindos
2 curiosidades con relacion al desarrollo de software
- pasta
- terremoto
Calatrava
Cuando hablamos de arquitectura en una organización..
Una gran estructura perfectamente pensada, capacitada para aguantarlo todo, pensada por una mente brillante que lo domina todo.
Pero la realidad acostumbra a ser muy diferente, lo que nos encontramos es que nuestra arquitectura no vive sola en el mundo.
Nuestra arquitectura está rodeada de fuerzas y luchas que la modelan.
Kevlin Henney
A mi esta definición no me acaba de gustar, pq presupone (o eso entiendo yo) que tu proyecto no cambia. Que lo que es válido al final del proyecto era válido al principio. Y eso no tiene que ser así. Tu negocio, con suerte, evolucionará, y la decisión que hoy parece correcta mañana no lo será.
A mi me gusta mucho más esta otra definición:
Si tu aplicación utiliza intensivamente la base de datos, esocoger que tu base de datos será una base de datos relacional o no es una decisión arquitectónica.
Hablábamos antes de lucha. La primera lucha que hay, y que no debería ser tal, es la que hay entre negocio y desarrollo.
los de desarrollo somos para negocio aquellos que lentos que no son capaces de subir nada a producción cuando yo se lo digo,
Y en otros muchos casos los de negocio son para los de desarrollo aquellos pesados que no paran de pedir cosas -> nuevo FW de javascript
Pero esa dicotomía no es real y es dañina.
Y es que las decisiones que tomamos desde desarrollo tienen un impacto directo en el negocio.
Historia Edu Ferro
Carlos Ble -> json en una columna de la tabla relacional
Pero el impacto también puede ser el contrario. Que una decisión nuestra impacte negativamente en el negocio. Eso se ve mucho cuando en nuestra empresa se desarrolla con lo que se dice la arquitectura orientada al curriculum.
Microservices
React <- Angular 2 <- Angular 1 <- Emberjs <- Knockout <- jQuery
tu web no es el New York times ni Facebook ni actualizas zillones de datos a la vez.
Puede cambiar como es el negocio en si. CQRS -> porque puede cambiar como muestro la información a mi usuario y como funciona mi negocio.
Greg Young, versionado con Event Sourcing -> Jodido -> cambiar eventos, rediseñar agregados
Como decíamos, negocio y desarrollo están muy unidos. Están tan unidos, que muchas técnicas que en principio tienen que se aplican cuando se define un negocio son perfectamente aplicables para hablar de arquitectura.
El otro dia hablaba con mi sponsor sobre como empezar una arquitectura -> pensar en capabilities
Otro recurso interesante es el booklet de Nick Tune sobre las prácticas estratégicas de DDD.
Esta es un resumen de la lista que Nick nombra. Como veis, otra vez, muchas de las actividades son actividades que son pensadas para ser utilizadas desde un punto de vista de negocio, pero que son realmente importantes desde un punto de vista técnico también. Una de las nombradas es el business model canvas.
El business model canvas es un template que nos ayuda a definir un nuevo nogocio o a describir uno existente.
En el podemos encontrar áreas como la proposición de valor, …
En la DDDX de este año, Javier Fernández
A parte, Javier explicó que el BMC puede tener un mapeo más o menos directo a patrones estratégicos de DDD.
Si la arquitectura es aquello que pone ciertas limitaciones a nuestra imagincación y eliminar alternativas, nuestra empresa o cliente fija dos limitaciones muy importantes: tiempo y dinero.
Las fechas que pone negocio en muchos casos no son arbitrarias, sino que tienen una fuerte razón de ser.
Videojuegos -> E3
Historia recarding -> retraso seis meses -> BAU tactical vs strategic
El dinero impacta, a parte de en las fechas, en el equipo que se pueda formar.
Desarrolladores como una comodity -> NO
Indra -> BDD
Ahora -> solo seniors -> diversidad
La primera release de nuestro producto no es el final del proyecto, sino el principio de la vida del software.
Diseñamos para QA, sobretodo en consultoria
Cada vez más modelo de you build it, you run it
Problemas en producción vienen por los non functional requirements -> cross functional requirements
Accesibilidad, auditabilidad, compatibilidad
estabilidad y capacidad.
- History
- JustEat
Alguien sabe quien es este hombre? Mel Conway.
Esto quiere decir que si en nuestra organización tenemos este organigrama.
Esto fue estudiado unos cuantos años más tarde (2012 si no me equivoco) y se certificó de una manera un poco más científica.
Se puede (y se va a dar) el caso que este señor necesite hablar con este otro para hacer su trabajo. Y que con estos no hable nadie. Esto hará que haya un coste de comunicación añadido brutal, no solo entre personas y equipos sino que, como cada uno hará su componente, entre piezas de software. Por tanto, entregar valor a nuestros clientes será más complicado.
Historia Lynk and sync?
En 2015 y 2016 apareció en el Tech Radar de ThoughtWorks el concepto de la maniobra inversa de Conway. Esto basicamente quiere decir que si sabemos que la arquitectura acaba siguiendo el modelo organizativo de tu empresa, diseña tu empresa de manera que la arquitectura deseada emerja. Por lo tanto aquí el reto está en la manera que tenemos de formar equipos. Pizza teams de Amazon. Equipos en TransferWise (Keyvan Akvary). Squads en Spotify.
Y es importante hacer este estudio y este esfuerzo.
Historia skills funding agency?
Podemos definir los niveles de colaboración entre equipos de la siguiente manera.
Por ejemplo, en nuestro caso, con algún equipo implementando alguna funcionalidad si que tenemos una comunicación más estrecha y nos influimos mutuamente. En otros casos, otros equipos simplemente utilizan nuestra funcionalidad existente.
Discovery vs predictability.
Puedo consumir esto como un servicio?
Puedo yo ser consumido como un servicio. En contact service nos planteamos extender nuestro as a service.
Una posible separación de los tipos de equipos es la siguiente. Como veis, tenemos cuatro tipos de equipos diferentes:
- Product teams: aquellos encargados del desarrollo de una linea de negocio
- Platform teams: aquellos encargados de implementar un servicio de infrastructura que otros equipos pueden utilizar, como puede ser los encargados de enviar correos, autenticación, etc.
- Productivity teams: aquellos encargados de dar soporte a los equipos para mejorar su productividad, como puede ser equipo de CI, cloud, release, etc. No hacen el trabajo, sino que habilitan a los equipos a hacerlo. (Ultimo artículo de roberto canales). El equipo de SRE que comentó ayer Kini.
- Component teams: encargados del desarrollo de un componente muy especifico, como podria ser un reproductor de video, por ejemplo.
Por lo tanto, el reto aquí será el de partir nuestro monolito (el punto de partida de muchos equipos) en una serie de equipos que puedan aportar el máximo valor posible. Podemos definir un monolito de muchas maneras.
La primera a tener en cuenta tendría que ser los dominios de negocio. => strategic design de DDD
Al final, la más importante es la customer responsiveness. Preferimos un diseño impuro pero que aporte valor antes.