The document outlines various design patterns for building and maintaining successful hacker spaces. It discusses patterns related to sustainability such as ensuring proper infrastructure is in place before projects, starting the space even with uncertainties, using mailing lists, wikis and IRC for community communication, and having a critical mass of initial members. Independence patterns address selecting a supportive landlord and neighbors as well as not allowing long-term residents to avoid disrupting the work space. Further patterns around regularity, conflict resolution and fostering creativity are also described. The document aims to share experiences from existing hacker spaces without providing rigid instructions.
This document provides information on SoftChart dental practice management software. It summarizes SoftChart's features such as customizable charting, integration with clinical technologies like cameras and x-rays, and image management capabilities. It also describes additional modules like PowerCase for case presentations, the Advantage Plan for technical support, and electronic billing and statements services. SoftChart is presented as providing value through efficient clinical workflows and maximum use of technology investments.
The document promotes an upcoming "Year of Worksite Wellness" initiative to connect employers with worksite wellness programs and professionals. It provides supporting information showing that nine out of ten employers understand the benefits of worksite wellness programs and are willing to collaborate and learn from others in their community about establishing these programs. The Year of Worksite Wellness will provide marketing and networking opportunities through monthly convenings and forums on various wellness topics to recruit employers and highlight the value of these programs. It will also recognize outstanding individual and organizational efforts to improve worksite wellness through an annual awards program.
Custom unique, hand rendered artwork: Illustrated maps, perspective drawings and variety of different illustrations, created for clients by professional illustrator Maria Rabinky.
This document provides information on SoftChart dental practice management software. It summarizes SoftChart's features such as customizable charting, integration with clinical technologies like cameras and x-rays, and image management capabilities. It also describes additional modules like PowerCase for case presentations, the Advantage Plan for technical support, and electronic billing and statements services. SoftChart is presented as providing value through efficient clinical workflows and maximum use of technology investments.
The document promotes an upcoming "Year of Worksite Wellness" initiative to connect employers with worksite wellness programs and professionals. It provides supporting information showing that nine out of ten employers understand the benefits of worksite wellness programs and are willing to collaborate and learn from others in their community about establishing these programs. The Year of Worksite Wellness will provide marketing and networking opportunities through monthly convenings and forums on various wellness topics to recruit employers and highlight the value of these programs. It will also recognize outstanding individual and organizational efforts to improve worksite wellness through an annual awards program.
Custom unique, hand rendered artwork: Illustrated maps, perspective drawings and variety of different illustrations, created for clients by professional illustrator Maria Rabinky.
The document discusses the need for a fitness application to log and track workouts that allows users to create and save customized workout templates, view past workouts in a calendar to monitor progress, and features a clean, simple interface that can be extended with future updates through an architecture that utilizes inheritance, multi-threading, and open source code.
Este documento proporciona una introducción a varias formas de mejorar el rendimiento y funcionalidad de Varnish mediante el uso de módulos (vmods). Algunos vmods descritos incluyen cURL para realizar peticiones HTTP, OpenDDR y dClass para la detección de dispositivos, y módulos para autenticación, ordenamiento de parámetros de consulta, reducción de E/S de disco, detección geográfica, firewalling y el uso de Memcached y Redis.
The document is a diagram showing the author's understanding of TPACK (technological pedagogical content knowledge) from a previous module. It indicates their knowledge has broadened slightly in pedagogy, content, and technology, but has developed most in pedagogical content knowledge, technological pedagogical knowledge, and technological content knowledge. The author believes learning about TPACK will benefit their future teaching by providing relevance, importance of pedagogy with technology, and how aspects of TPACK interconnect and apply together.
This diagram shows the author's understanding of TPACK (technological pedagogical content knowledge) from an earlier module and how it has developed. While the author's knowledge of pedagogy, content, and technology has increased slightly, the largest growth has been in the intersecting areas of pedagogical content knowledge, technological pedagogical knowledge, and technological content knowledge. Studying TPACK has benefited the author by providing an understanding of how technology can influence teaching and learning when integrated with pedagogy and content knowledge.
Qualcomm is a technology company founded in 1985 that designs chipsets and patents including Gobi modems and Snapdragon processors. In 2013, Qualcomm had an estimated market cap of $123.26 billion and revenues of $6.48 billion with $1.50 billion in net income for the fourth quarter. Qualcomm's history includes being the first to demonstrate CDMA technology in 1989 and introducing the world's first 3G/LTE multimode chipset in 2007.
Patterns can be found in all areas of your life, from creating grocery lists to crafting robust software applications. This session will introduce you to the concept of patterns, their history and benefits. We'll look at some different uses of patterns in crafting software applications, including design patterns, architectural patterns and user interface design patterns. We'll chase a rabbit and look at where patterns fail or might not be used correctly. You'll leave this session able to identify patterns and successfully use them in all facets of your design and construction of software applications.
Experiences and Creative Process (Semih Energin Technology Stream)IT Arena
Lviv IT Arena is a conference specially designed for programmers, designers, developers, top managers, inverstors, entrepreneurs and startuppers. Annually it takes place at the beginning of October in Lviv at Arena Lviv stadium. In 2016 the conference gathered more than 1800 participants and over 100 speakers from companies like Microsoft, Philips, Twitter, UBER and IBM. More details about the conference at itarena.lviv.ua.
1. The document discusses design patterns and their importance. It begins by introducing Christopher Alexander as the father of patterns and describes how he defined a pattern as a solution to a recurring problem in a context.
2. It then asks questions about what makes a good design and discusses how the Gang of Four identified software design patterns that solve common problems in reusable, generic solutions.
3. The document explains that studying design patterns is useful because it promotes reuse of solutions, establishes a common terminology, and improves team communication, code maintainability, and learning of object-oriented principles. Patterns help developers see both the forest and the trees.
This document provides guidance on how to conduct high-quality research and write good papers. It discusses that research can involve solving existing problems using existing methods, improving existing solutions, or identifying new problems and generalizing solutions. The most innovative and impactful research involves identifying new problems. It emphasizes the importance of conducting new and useful research. It then provides tips for training innovation through extensive reading, writing, and rewriting to develop ideas. It discusses finding meaningful topics by starting from real problems and convincing others of the topic's importance. The document concludes by offering writing techniques such as overcoming language barriers, using an active voice, including visual elements, and being specific rather than vague.
Immersive Recommendation incorporates cross-platform and diverse personal digital traces into recommendations. Our context-aware topic modeling algorithm systematically profiles users' interests based on their traces from different contexts, and our hybrid recommendation algorithm makes high-quality recommendations by fusing users' personal profiles, item profiles, and existing ratings. The proposed model showed significant improvement over the state-of-the-art algorithms, suggesting the value of using this new user-centric recommendation model to improve recommendation quality, including in cold-start situations.
Class-oriented programming, as supported by Java, C++ and C#, helps you develop classes for your customer. Object-oriented programming, on the other hand, lets you focus on networks of cooperating objects that work together to create business value.
This talk describes the trygve open-source programming language and its support for real object-oriented programming the way it was envisioned by those who shaped it in its early days. Learn about trygve and maybe even join the community to help evolve it. And if you’re a working developer, some of the ideas carry over into C# and C++.
More on the philosophy and so forth:
* User manual (the intro might help)
* Original “white paper”
* More academic paper
* fulloo web site
* Past version of a similar talk
About the speaker
Jim Coplien is a Certified Scrum Trainer in Denmark and best-selling author, lecturer, and consultant in the areas of software design, object-oriented programming, lean software development process, and agile development. His earlier work was one of the foundations of Scrum and of XP and he is one of the founders of the software pattern discipline. He helps enterprises solve architectural and organisational problems together and challenges people to question practices they do out of habit or popularity, exhorting people to establish empirical and otherwise provable justifications for their practices.
Getting Started with Architecture Decision RecordsMichael Keeling
Documenting architecture design decisions is commonly considered a good practice and yet many teams don't take the time to write down the decisions they make. In our experience this happens for a few reasons: documentation is rejected as being too heavyweight, documentation has little influence since it is typically out of sight and out of mind, and many developers don’t know what to document. Architecture Decision Records (ADRs) address many of these problems by capturing design decisions in a simple, lightweight templates that is stored close to repositories used by stakeholders -- often in the same repository as code affected by the ADR.
In this hands-on workshop you will learn how to write effective ADRs and how to overcome road bumps teams often experience when first getting started with ADRs. By the end of this session you will have the skills you need to champion ADRs and help your team start (or improve) your design decision log.
Working With Upstream OpenStack Deadlines and Internal DeadlinesJohn Garbutt
You are developer, and you have just been told to work with OpenStack. Welcome to the OpenStack community! You have also just been told you need to release your product next month, you have your all the codeyou’re your new feature complete, and a few bug fixes done. Now you just need to get that pushed upstream. Where do you go next?
You have been working for OpenStack for a while; some internal issues meant you had to stop reading the ML for a month or two. How do you get back in the loop?
You are working hard reviewing specs and code, and the work load is getting crazy, and everyone is saying their use case is the most important thing for OpenStack, and they are all really useful things to consider. What is the right thing to do?
Maybe we can use lessons from Harper Lee's To Kill a Mockingbird improves how new and established OpenStack contributors work together?
https://mitakadesignsummit.sched.org/event/96e68ed6a230394593c567eac2f6ef96
This 2014 Computers in Libraries Conference session begins by looking at several brainstorming techniques, including role-storming, opposites, the long list, and brand-storming. Participants use these techniques to brainstorm new innovative services, technology uses, and training tactics for their libraries. The results of the brainstorms will be documented and posted online for the larger CIL community.
Steven Bell's AISL Summer Institute 2016 Keynote Slide PresentationKArchambault24
This document provides an overview of design thinking and how it can be applied to improve library services. It discusses what design thinking is, why it's important for libraries, and walks through an example design challenge process. The document outlines the main steps in design thinking - empathizing with users to understand their needs, defining problems, brainstorming solutions, prototyping ideas, and getting user feedback. It presents some "wicked problems" libraries may face and argues design thinking can help address issues like diversity and assessing learning outcomes. The document concludes by encouraging attendees to try a small design challenge and apply this approach to their own "wicked problem."
The document discusses mobile prototyping techniques. It outlines plans to review four reasons for mobile prototyping, identify two prototyping genres and methods, review differences between natural and graphical user interfaces, and provide animation principles. Experiential prototyping techniques like bodystorming and speed dating prototypes are suggested to explore unknown contexts and gather user feedback. Concept videos and storyboarding are also covered as ways to communicate ideas early in the design process. The document emphasizes prototyping early and often to improve decision making and fine tune mobile designs.
Creativity is required everywhere. It is believed that creativity is subject to individuals. Breaking the myth that creativity can be learned, sharing some best tips from industry in enhancing creativity.
The document discusses the need for a fitness application to log and track workouts that allows users to create and save customized workout templates, view past workouts in a calendar to monitor progress, and features a clean, simple interface that can be extended with future updates through an architecture that utilizes inheritance, multi-threading, and open source code.
Este documento proporciona una introducción a varias formas de mejorar el rendimiento y funcionalidad de Varnish mediante el uso de módulos (vmods). Algunos vmods descritos incluyen cURL para realizar peticiones HTTP, OpenDDR y dClass para la detección de dispositivos, y módulos para autenticación, ordenamiento de parámetros de consulta, reducción de E/S de disco, detección geográfica, firewalling y el uso de Memcached y Redis.
The document is a diagram showing the author's understanding of TPACK (technological pedagogical content knowledge) from a previous module. It indicates their knowledge has broadened slightly in pedagogy, content, and technology, but has developed most in pedagogical content knowledge, technological pedagogical knowledge, and technological content knowledge. The author believes learning about TPACK will benefit their future teaching by providing relevance, importance of pedagogy with technology, and how aspects of TPACK interconnect and apply together.
This diagram shows the author's understanding of TPACK (technological pedagogical content knowledge) from an earlier module and how it has developed. While the author's knowledge of pedagogy, content, and technology has increased slightly, the largest growth has been in the intersecting areas of pedagogical content knowledge, technological pedagogical knowledge, and technological content knowledge. Studying TPACK has benefited the author by providing an understanding of how technology can influence teaching and learning when integrated with pedagogy and content knowledge.
Qualcomm is a technology company founded in 1985 that designs chipsets and patents including Gobi modems and Snapdragon processors. In 2013, Qualcomm had an estimated market cap of $123.26 billion and revenues of $6.48 billion with $1.50 billion in net income for the fourth quarter. Qualcomm's history includes being the first to demonstrate CDMA technology in 1989 and introducing the world's first 3G/LTE multimode chipset in 2007.
Patterns can be found in all areas of your life, from creating grocery lists to crafting robust software applications. This session will introduce you to the concept of patterns, their history and benefits. We'll look at some different uses of patterns in crafting software applications, including design patterns, architectural patterns and user interface design patterns. We'll chase a rabbit and look at where patterns fail or might not be used correctly. You'll leave this session able to identify patterns and successfully use them in all facets of your design and construction of software applications.
Experiences and Creative Process (Semih Energin Technology Stream)IT Arena
Lviv IT Arena is a conference specially designed for programmers, designers, developers, top managers, inverstors, entrepreneurs and startuppers. Annually it takes place at the beginning of October in Lviv at Arena Lviv stadium. In 2016 the conference gathered more than 1800 participants and over 100 speakers from companies like Microsoft, Philips, Twitter, UBER and IBM. More details about the conference at itarena.lviv.ua.
1. The document discusses design patterns and their importance. It begins by introducing Christopher Alexander as the father of patterns and describes how he defined a pattern as a solution to a recurring problem in a context.
2. It then asks questions about what makes a good design and discusses how the Gang of Four identified software design patterns that solve common problems in reusable, generic solutions.
3. The document explains that studying design patterns is useful because it promotes reuse of solutions, establishes a common terminology, and improves team communication, code maintainability, and learning of object-oriented principles. Patterns help developers see both the forest and the trees.
This document provides guidance on how to conduct high-quality research and write good papers. It discusses that research can involve solving existing problems using existing methods, improving existing solutions, or identifying new problems and generalizing solutions. The most innovative and impactful research involves identifying new problems. It emphasizes the importance of conducting new and useful research. It then provides tips for training innovation through extensive reading, writing, and rewriting to develop ideas. It discusses finding meaningful topics by starting from real problems and convincing others of the topic's importance. The document concludes by offering writing techniques such as overcoming language barriers, using an active voice, including visual elements, and being specific rather than vague.
Immersive Recommendation incorporates cross-platform and diverse personal digital traces into recommendations. Our context-aware topic modeling algorithm systematically profiles users' interests based on their traces from different contexts, and our hybrid recommendation algorithm makes high-quality recommendations by fusing users' personal profiles, item profiles, and existing ratings. The proposed model showed significant improvement over the state-of-the-art algorithms, suggesting the value of using this new user-centric recommendation model to improve recommendation quality, including in cold-start situations.
Class-oriented programming, as supported by Java, C++ and C#, helps you develop classes for your customer. Object-oriented programming, on the other hand, lets you focus on networks of cooperating objects that work together to create business value.
This talk describes the trygve open-source programming language and its support for real object-oriented programming the way it was envisioned by those who shaped it in its early days. Learn about trygve and maybe even join the community to help evolve it. And if you’re a working developer, some of the ideas carry over into C# and C++.
More on the philosophy and so forth:
* User manual (the intro might help)
* Original “white paper”
* More academic paper
* fulloo web site
* Past version of a similar talk
About the speaker
Jim Coplien is a Certified Scrum Trainer in Denmark and best-selling author, lecturer, and consultant in the areas of software design, object-oriented programming, lean software development process, and agile development. His earlier work was one of the foundations of Scrum and of XP and he is one of the founders of the software pattern discipline. He helps enterprises solve architectural and organisational problems together and challenges people to question practices they do out of habit or popularity, exhorting people to establish empirical and otherwise provable justifications for their practices.
Getting Started with Architecture Decision RecordsMichael Keeling
Documenting architecture design decisions is commonly considered a good practice and yet many teams don't take the time to write down the decisions they make. In our experience this happens for a few reasons: documentation is rejected as being too heavyweight, documentation has little influence since it is typically out of sight and out of mind, and many developers don’t know what to document. Architecture Decision Records (ADRs) address many of these problems by capturing design decisions in a simple, lightweight templates that is stored close to repositories used by stakeholders -- often in the same repository as code affected by the ADR.
In this hands-on workshop you will learn how to write effective ADRs and how to overcome road bumps teams often experience when first getting started with ADRs. By the end of this session you will have the skills you need to champion ADRs and help your team start (or improve) your design decision log.
Working With Upstream OpenStack Deadlines and Internal DeadlinesJohn Garbutt
You are developer, and you have just been told to work with OpenStack. Welcome to the OpenStack community! You have also just been told you need to release your product next month, you have your all the codeyou’re your new feature complete, and a few bug fixes done. Now you just need to get that pushed upstream. Where do you go next?
You have been working for OpenStack for a while; some internal issues meant you had to stop reading the ML for a month or two. How do you get back in the loop?
You are working hard reviewing specs and code, and the work load is getting crazy, and everyone is saying their use case is the most important thing for OpenStack, and they are all really useful things to consider. What is the right thing to do?
Maybe we can use lessons from Harper Lee's To Kill a Mockingbird improves how new and established OpenStack contributors work together?
https://mitakadesignsummit.sched.org/event/96e68ed6a230394593c567eac2f6ef96
This 2014 Computers in Libraries Conference session begins by looking at several brainstorming techniques, including role-storming, opposites, the long list, and brand-storming. Participants use these techniques to brainstorm new innovative services, technology uses, and training tactics for their libraries. The results of the brainstorms will be documented and posted online for the larger CIL community.
Steven Bell's AISL Summer Institute 2016 Keynote Slide PresentationKArchambault24
This document provides an overview of design thinking and how it can be applied to improve library services. It discusses what design thinking is, why it's important for libraries, and walks through an example design challenge process. The document outlines the main steps in design thinking - empathizing with users to understand their needs, defining problems, brainstorming solutions, prototyping ideas, and getting user feedback. It presents some "wicked problems" libraries may face and argues design thinking can help address issues like diversity and assessing learning outcomes. The document concludes by encouraging attendees to try a small design challenge and apply this approach to their own "wicked problem."
The document discusses mobile prototyping techniques. It outlines plans to review four reasons for mobile prototyping, identify two prototyping genres and methods, review differences between natural and graphical user interfaces, and provide animation principles. Experiential prototyping techniques like bodystorming and speed dating prototypes are suggested to explore unknown contexts and gather user feedback. Concept videos and storyboarding are also covered as ways to communicate ideas early in the design process. The document emphasizes prototyping early and often to improve decision making and fine tune mobile designs.
Creativity is required everywhere. It is believed that creativity is subject to individuals. Breaking the myth that creativity can be learned, sharing some best tips from industry in enhancing creativity.
This document provides an overview of chatbots, including:
- How chatbots work using pattern matching and knowledge representation in AIML.
- Examples of atomic, default, and recursive categories in AIML.
- The architecture of a typical chatbot including an AIML interpreter and responder.
- References to learn more about developing chatbots and training them using dialogue corpora.
- Suggestions for potential applications of chatbots such as customer service and an interactive encyclopedia.
This document discusses collective management approaches being used at La Fabrique, a cooperative FabLab in Sherbrooke, Quebec. It is currently renting an 8,500 square foot space in an old police station, with four workshops and space for training and rentals. It is partnering with a business incubator and aims to be fully operational in September. The document outlines three approaches being used to engage members and partners in running the FabLab: Art of Hosting for facilitation, Dynamic Governance for decision making, and Human Centered Design for designing based on member needs. Each approach is briefly described in one or two sentences.
GCSE Drama The Crucible C3- design 14 mark questionGareth Hill
This document provides guidance for drama students on preparing a 14-mark question response about using a design element to bring a play extract to life. It discusses set, lighting, sound, realism vs. abstraction, researching productions, and provides a sample answer focusing on set design for an extract from Act II of The Crucible. Students are instructed to submit their own response by email. The teacher notes they will return feedback on students' devising portfolios after Easter and discusses potential future drama work depending on the COVID-19 situation.
An introduction to designers role in the technology products or services. Case studies from both agile and waterfall projects.
Talk and Founders and Coders June 2015
Design thinking for science communicationphysicsdavid
The document outlines David Harris's presentation on using design thinking for science communication, where he defines key terms like design, graphic design, and design thinking; discusses models for solving problems in science communication like the information deficit model and design thinking; and provides examples of using design thinking concepts to improve explaining theoretical physics concepts to lay audiences like the Higgs mechanism and special relativity.
These slides are for a talk that I give at Macquarie University. The offer advice for presenting an academic paper and getting the most out of academic conferences, including preparing slides, basic guidelines for presenting, and taking advantage of opportunities at conferences.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
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.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
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 his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
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.
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:
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
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.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
1. Introduction
Design Patterns
Conclusion
Building a Hacker Space
Jens Ohlig ‹jens@ccc.de› Lars Weiler ‹pylon@ccc.de›
24th Chaos Communication Congress
December 27, 2007
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
3. Introduction
Design Patterns
Conclusion
Who we are
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
4. Introduction
Design Patterns
Conclusion
Who we are
The speakers
Jens
• Co-Founder of Chaos
Computer Club Cologne
(C4)
Pylon
• Co-Founder of Chaos
Computer Club Düsseldorf
(Chaosdorf)
• Still active there
• Now active in Cologne
• CCC-activist for more than
• CCC-activist for more than
15 years
• CCC-spokesman,
board-member etc.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
eight years
• CCC-spokesman,
board-member etc.
24C3
5. Introduction
Design Patterns
Conclusion
Who we are
Chaos Computer Club Cologne
• Founded in 1997
• around 42 members
• currently in Version 3.5 of our hacker space, operational in
that location since 1999
• All pictures in this presentation has been taken in the C4
hacker space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
6. Introduction
Design Patterns
Conclusion
Why this catalogue?
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
7. Introduction
Design Patterns
Conclusion
Why this catalogue?
Thanks to the August 2007 hacker space tour
• A group of American hackers visited hacker spaces in Germany
and Austria
• They wanted to know how our European hacker spaces work
• After the Camp they visited a couple of hacker spaces
• Every hacker space did a presentation about their history
• We created some Design Patterns
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
8. Introduction
Design Patterns
Conclusion
Why this catalogue?
Design Patterns
• Historically used for urban planning
• Transfered for typical situations in software development
• Problem → Implementation
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
9. Introduction
Design Patterns
Conclusion
Why this catalogue?
What we want to tell you
• We want to share our knowledge of building our own hacker
space
• We won’t give you a detailed manual
• Your mileage may vary
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
10. Introduction
Design Patterns
Conclusion
Sustainability Patterns
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
12. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Infrastructure Pattern
Problem
You have a chicken-and-egg-problem: What should come first?
Infrastructure or projects?
Implementation
Make everything infrastructure-driven. Rooms, power, servers,
connectivity, and other facilities come first. Once you have that,
people will come up with the most amazing projects you didn’t
think about in the first place.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
14. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Grace Hopper Pattern
Problem
Is now really the time to start your hacker space? Shouldn’t you
wait? Have you really thought of all the problems?
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
15. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Grace Hopper Pattern
Problem
Is now really the time to start your hacker space? Shouldn’t you
wait? Have you really thought of all the problems?
Implementation
Sure it is the time!
It’s always easier to ask forgiveness than it is to get
permission.
(Grace Hopper, US Navy Rear Admiral and computer scientist)
It’s important to start. Many problems you think of before will
vanish as soon as you get started. When in doubt, do it!
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
17. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Community Pattern
Problem
How should your group communicate?
Implementation
You are hackers, you know what to do. Stop slacking and set up a
mailing list, a wiki, and an IRC channel. You will need all three.
Think about a platform for discussion, storage for
documentation and real-time communication.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
19. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Critical Mass Pattern
Problem
You want to set up a hacker space in your city alone. You fail.
Implementation
The rule of thumb is 2 + 2. You need a partner to get the initial
idea kicked off, making two of you. You need two more people in
order to get real work done. Don’t start before you are at least four
people. From this point it’s easy to recruit more people. Aim for
ten people for a start.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
21. Introduction
Design Patterns
Conclusion
Sustainability Patterns
The Strong Personalities Pattern
Problem
Nothing gets done. You all want the hacker space, but it’s so hard
to get off your asses.
Implementation
Look for strong personalities as members of your original group.
You will need people with experience in building structures.
Look for people who have authority (and get respect), not for
people who use authority (and get laughed at).
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
22. Introduction
Design Patterns
Conclusion
Independence Patterns
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
23. Introduction
Design Patterns
Conclusion
Independence Patterns
The Landlord and Neighbourhood Pattern
Problem
You have found the perfect hacker space, but the landlord seems to
be weird. Also, the neighbours are picky.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
24. Introduction
Design Patterns
Conclusion
Independence Patterns
The Landlord and Neighbourhood Pattern
Problem
You have found the perfect hacker space, but the landlord seems to
be weird. Also, the neighbours are picky.
Implementation
Choose wisely. A benevolent, but uninterested landlord and cool
neighbours can be the decisive reasons why the hacker space takes
off or not. Not so cool neighbours may call the cops at 2 AM.
Depending on your projects, this may be a serious problem. As
hackers you do not live the majority lifestyle—look for neighbours
who are also weird and outside the majority.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
25. Introduction
Design Patterns
Conclusion
Independence Patterns
The Roommate Anti-Pattern
Problem
You need a space for meetings and as a lab, to store and work on
materials for projects. In order to minimize rent or out of sympathy,
you think it’s great when someone lives in your space. But
somehow it doesn’t work, as you cannot use the lab anymore.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
26. Introduction
Design Patterns
Conclusion
Independence Patterns
The Roommate Anti-Pattern
Problem
You need a space for meetings and as a lab, to store and work on
materials for projects. In order to minimize rent or out of sympathy,
you think it’s great when someone lives in your space. But
somehow it doesn’t work, as you cannot use the lab anymore.
Implementation
Guest are fine, but don’t let anyone live there. Kick them out if
necessary.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
27. Introduction
Design Patterns
Conclusion
Independence Patterns
The Séparée Pattern
Problem
You want to chill, discuss, or work in small groups. But the main
room is occupied: There are simply too many people at your space.
Or you want to smoke a cigarette at the space without disturbing
non-smokers.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
28. Introduction
Design Patterns
Conclusion
Independence Patterns
The Séparée Pattern
Problem
You want to chill, discuss, or work in small groups. But the main
room is occupied: There are simply too many people at your space.
Or you want to smoke a cigarette at the space without disturbing
non-smokers.
Implementation
Look for a hacker space with smaller, separate rooms. Use
curtains or doors to separate them from the main room. Separate
rooms can also be used for smokers in a non-smoking hacker space.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
30. Introduction
Design Patterns
Conclusion
Independence Patterns
The Kitchen Pattern
Problem
As a human being, you need food. As a hacker, you need caffeine
and food at odd times.
Implementation
Have a kitchen at your space. Nothing brings people together like
cooking together. Have fridges for Club-Mate. Selling soft-drinks
will help you raise money for the rent. Invest in the single most
important piece of hardware: a dishwasher. Have a freezer for
pizzas and buy decent kitchen equipment. Show nerds how to
cook real food.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
32. Introduction
Design Patterns
Conclusion
Independence Patterns
The Coziness Pattern
Problem
All work and no play makes Jack a dull boy. There must be
something else than only workstations and electronics.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
33. Introduction
Design Patterns
Conclusion
Independence Patterns
The Coziness Pattern
Problem
All work and no play makes Jack a dull boy. There must be
something else than only workstations and electronics.
Implementation
Bring in couches, sofas, comfortable chairs, tables, ashtrays,
ambient light, stereo equipment, a projector, and video game
consoles. Bringing in plants didn’t work for us.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
36. Introduction
Design Patterns
Conclusion
Independence Patterns
The Shower Pattern
Problem
After long hacking sessions, you will start to smell funny. Also,
guests to your space seem to neglect personal hygiene.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
37. Introduction
Design Patterns
Conclusion
Independence Patterns
The Shower Pattern
Problem
After long hacking sessions, you will start to smell funny. Also,
guests to your space seem to neglect personal hygiene.
Implementation
The discriminate hacker space has a bathroom with a shower.
After a long hacking night you’ll have the best ideas while taking a
shower. Guests from other hacker spaces may stay for several days.
Ideally you will buy a washing machine to get rid of all the smelly
towels.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
40. Introduction
Design Patterns
Conclusion
Independence Patterns
The Membership Fees Pattern
Problem
You need to pay your rent and utilities. Larger projects need to be
funded.
Implementation
Collect fees regularly. Make no exceptions, ever. Choose an
appropriate amount. Have discounts for students. Have at least
three months of rent on your account, all the time, no exceptions.
Elect a totalitarian treasurer.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
41. Introduction
Design Patterns
Conclusion
Independence Patterns
The Sponsoring Anti-Pattern
Problem
You think it’s a good idea to meet at a company that likes you or
at a university where most of you study anyway.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
42. Introduction
Design Patterns
Conclusion
Independence Patterns
The Sponsoring Anti-Pattern
Problem
You think it’s a good idea to meet at a company that likes you or
at a university where most of you study anyway.
Implementation
Never ever depend your space on external sponsors. Donations
are great, but remember that companies can go bankrupt and you
won’t be a student forever. Meeting at a university will exclude
high-school kids or people who don’t like the university culture. No
company, no matter how nice, will give away presents forever
without asking for favours in return. That’s capitalism. . .
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
43. Introduction
Design Patterns
Conclusion
Regularity Patterns
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
44. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Plenum Pattern
Problem
You want to resolve internal conflicts, exercise democratic
decision-making, and discuss recent issues and future plans.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
45. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Plenum Pattern
Problem
You want to resolve internal conflicts, exercise democratic
decision-making, and discuss recent issues and future plans.
Implementation
Have a regular meeting with possibly all members. Have an
agenda and set goals. Make people commit themselves to tasks.
Write down minutes of the meeting and post them on a mailing
list and/or Wiki. Go for the only date that works: once a week.
Weird dates like “first full-moon after the third Friday” will never
work. Likewise doesn’t every other week or anything similar.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
46. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Tuesday Pattern
Problem
Every weekday sucks. You will not find any day when every hacker
can attend a meeting. Someone always has an appointment.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
47. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Tuesday Pattern
Problem
Every weekday sucks. You will not find any day when every hacker
can attend a meeting. Someone always has an appointment.
Implementation
Meet on Tuesday. Since all days are equally bad, just pick the
Tuesday. End of discussion.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
49. Introduction
Design Patterns
Conclusion
Regularity Patterns
The OpenChaos Pattern
Problem
You want to draw in new people and provide an interface to the
outside world.
Implementation
Have a monthly, public, and open lecture, talk or workshop.
Announce it at your local time (no UTC, CEST, EST or something
else). Invite interesting visitors to your regular meetings and don’t
tell the weirdos about them.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
51. Introduction
Design Patterns
Conclusion
Regularity Patterns
The U23 Pattern
Problem
Your older members graduate from college or get married. Your
space needs fresh blood.
Implementation
Recruit young people through a challenge you set up for them, in
form of a course that spans several weeks. Overwhelm them
with problems from hardware and software hacking and let them
solve it in teams. Prepare for the challenge and tutor them, but
give them room to experiment. Retire after the team-building and
let the smartest of the young ones run the space.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
52. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Sine Curve Pattern
Problem
You did everything right. You had some big events and a nice time
in your shiny hacker space. But after some time the enthusiasm
goes away and your projects are stagnating.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
53. Introduction
Design Patterns
Conclusion
Regularity Patterns
The Sine Curve Pattern
Problem
You did everything right. You had some big events and a nice time
in your shiny hacker space. But after some time the enthusiasm
goes away and your projects are stagnating.
Implementation
Peak enthusiasm at a hacker space has the form of a sine curve
with a cycle duration of four years. Keep the hacker space
running, even if the feel-good-factor is temporarly on holidays.
Chances are your space will be awesome again in two years. Don’t
give up! Maybe an exciting new member will knock on your door
tomorrow.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
54. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
55. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Consensus Pattern
Problem
You need a group decision and want to make sure no one gets left
behind.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
56. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Consensus Pattern
Problem
You need a group decision and want to make sure no one gets left
behind.
Implementation
Use the weekly plenum for discussion. Don’t take votes—discuss
until everyone agrees.
For some problems this pattern is the best.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
57. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Democracy Pattern
Problem
You need to make a group decision. Discussion does not seem to
lead you anywhere.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
58. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Democracy Pattern
Problem
You need to make a group decision. Discussion does not seem to
lead you anywhere.
Implementation
Use the weekly plenum for discussion. Do take votes—the
strongest minority wins over the weaker minorities.
For some problems this pattern is the best.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
59. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Command Pattern
Problem
Nobody does the dishes. Your hacker space looks crappy. No one
seems to care.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
60. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Command Pattern
Problem
Nobody does the dishes. Your hacker space looks crappy. No one
seems to care.
Implementation
Order people to do the dishes, take out the trash, keep the
infrastructure up and running. Yell, if necessary! But always
participate.
For some problems this pattern is the best.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
61. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The sudo leadership Pattern
Problem
You started as a community of like-minded people, but suddenly
you find yourself in a dictatorship run by a single hacker.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
62. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The sudo leadership Pattern
Problem
You started as a community of like-minded people, but suddenly
you find yourself in a dictatorship run by a single hacker.
Implementation
Do not have ranks. Use leadership temporarily, like for projects
and when you really need it. Don’t have a single root.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
63. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Responsibility Pattern
Problem
You volunteered for the task of running a critical piece of
infrastructure, e.g. the mail server, but you feel the sudden urge to
slack.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
64. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Responsibility Pattern
Problem
You volunteered for the task of running a critical piece of
infrastructure, e.g. the mail server, but you feel the sudden urge to
slack.
Implementation
Just because volunteer work doesn’t get paid doesn’t mean it’s less
important. Remember that you will directly hurt your friends and
the hacker space. Take pride in your volunteer work. It will
make you grow stronger as a person and is satisfying. When you
realise that you really cannot do the job any more, your last task
is to hand it over.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
65. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Debate Culture Pattern
Problem
You are in the middle of your weekly plenum. Everybody’s yelling,
nothing gets done.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
66. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Debate Culture Pattern
Problem
You are in the middle of your weekly plenum. Everybody’s yelling,
nothing gets done.
Implementation
Many geeks have very poor debate skills, the result of years of
flame wars on the Net. Make people with actual social skills
lead the discussion. Those with a background in real-life political
work (e.g. student council) were best for our group. Learn from
them. Learn not to interrupt others.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
67. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Bikeshed Anti-Pattern
Problem
You suggest creating something new for your hacker space, like a
bikeshed. But now everybody discuss about it’s colour. No
bikeshed will be built.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
68. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Bikeshed Anti-Pattern
Problem
You suggest creating something new for your hacker space, like a
bikeshed. But now everybody discuss about it’s colour. No
bikeshed will be built.
Implementation
That’s a known problem. If you suggest something what everybody
else in your hacker space can build, they will take part in the
discussion. And if it’s only the colour of the bikeshed, the design
of the T-shirts, the Linux-distribution on the server, etc. Nerds
tend to discuss trivial problems in epic detail, while more complex
tasks will be ignored. Identify pointless discussion like these and
just end them.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
69. History of the Bikeshed-Problem
C. Northcote Parkinson wrote a book in the early 1960s,
called “Parkinson’s Law”, which contains a lot of insight
into the dynamics of management.
...
In the specific example involving the bike shed, the other
vital component is an atomic power-plant, I guess that
illustrates the age of the book. Parkinson shows how you
can go into the board of directors and get approval for
building a multi-million or even billion dollar atomic power
plant, but if you want to build a bike shed you will be
tangled up in endless discussions.
see http://www.bikeshed.com/
71. Introduction
Design Patterns
Conclusion
Conflict Resolution Patterns
The Private Talk Pattern
Problem
Someone causes a problem that cannot be resolved in the group.
Implementation
Let some experienced member of your group talk to the
trouble-maker in private. Listen to the person. Let them know
how the group feels about the problem without exposing them in
front of the group.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
72. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
73. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Old Hardware Pattern
Problem
You can’t bring in shiny new hardware, as there is no space left.
Your space has become a hardware museum filled with junk.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
74. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Old Hardware Pattern
Problem
You can’t bring in shiny new hardware, as there is no space left.
Your space has become a hardware museum filled with junk.
Implementation
Create a pile/stack where you put that old, unused hardware on.
Let everybody take from it. Anything left within a while should be
thrown away. But make sure you announce that step not only
once, but at least three times with an escalation system.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
75. (Sorry, in German only)
Bereitstellung von Hardware im Chaoslabor
§1 Das Chaoslabor ist ein Bereich vorbildlicher Ordnung
und Sauberkeit, in dem der Chaos Computer Club
Cologne e.V. seine Vereinstätigkeit ausübt.
§2 Unter Aufräumpersonal werden Personen verstanden,
die sich um den Zustand des Clubraumes kümmern.
Aufräumpersonal genießt Heldenstatus und Immunität
gegenüber Anfeindungen von Besitzern nicht
funktionierender Hardware.
...
see http://wiki.koeln.ccc.de/index.php?title=Hacker_
Space/Hardware-Gesetz
77. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Key Pattern
Problem
You want the hacker space accessable all the time. You don not
want to call somebody else during night to lock the hacker space
when you leave.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
78. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Key Pattern
Problem
You want the hacker space accessable all the time. You don not
want to call somebody else during night to lock the hacker space
when you leave.
Implementation
Hand out keys. Track who owns a key. Have a good lock so
that nobody can copy the key without your permission. Collect a
deposit for the key, so that the owner takes care for it. Or build a
nice electronic locking system (with all cool things and all messy
problems). . .
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
79. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Club Mate Pattern
Problem
You need to raise funds. You want to stay up longer during night.
You want to receive really good impressions without drugs.
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
80. Introduction
Design Patterns
Conclusion
Creative Chaos Patterns
The Club Mate Pattern
Problem
You need to raise funds. You want to stay up longer during night.
You want to receive really good impressions without drugs.
Implementation
Buy at least one pallet of Club-Mate and sell it in your hacker
space. You will realise the results very soon!
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
82. Introduction
Design Patterns
Conclusion
This is not a cookbook
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
83. Introduction
Design Patterns
Conclusion
This is not a cookbook
Conclusion
• There is no “golden way” building up a hacker space
• Based on experience there are a couple of patterns which
might match
• Be creative! Try out your own way!
• Question & Answer session @24C3: Day 1, 17:15,
Workshoproom A
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
84. Introduction
Design Patterns
Conclusion
Find your nearest Hacker Space
Outline
1
Introduction
Who we are
Why this catalogue?
2
The Hacker Space Design Patterns Catalogue
Sustainability Patterns
Independence Patterns
Regularity Patterns
Conflict Resolution Patterns
Creative Chaos Patterns
3
Conclusion
This is not a cookbook
Find your nearest Hacker Space
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3
85. Introduction
Design Patterns
Conclusion
Find your nearest Hacker Space
Hacker Spaces (not complete)
Germany, Austria, Switzerland:
• CCC-based → http://www.ccc.de/regional/
• Netzladen → http;//www.netzladen.org/
• Das Labor → http://www.das-labor.org/
• c-base → http://www.c-base.org/
USA:
• NYC Resistor → http://www.nycresistor.com/
• Seattle
• San Francisco
• L.A.
Australia:
• TheHacktory → http://thehacktory.com/
J. Ohlig, L. Weiler
A Hacker Space Design Pattern Catalogue
24C3