The term design can mean different things to people from different backgrounds. This talk from the PyGRAZ and UX Graz meetup from 2023-07-25 acts as basis for an open discussion between these two user groups. It describes the "minimum viable everything" design of an actual application under development. Starting from the problem to solve it explores the evolution of the data models and visualizes a major rework. It also showcases a few approaches to "low effort" UI in the early phase of a project when concepts are still in flux.
Slides for application prototyping workshop on web and mobile application design.
We discussed
- product and project requirements definition
- rationale for wireframes, mockups, prototypes
- functional prototypes vs production sw
- tools: Balsamiq, myBalsamiq, Webflow
- MVP (minimum viable product) implementation in Javascript, HTML/CSS on node.js
- The document discusses various business development processes including subtraction, multiplication, division, task unification, and attribute dependency change as ways to modify a product. It then discusses prototyping and getting customer feedback as important parts of the development process. Specifically, it recommends creating minimum viable products and landing pages to test assumptions with customers before fully developing ideas. The key messages are that business plans should evolve based on customer feedback, prototyping allows early testing of ideas, and pivoting a business model based on learning is normal.
Making a website is more then making pretty picture and some sales jargon. You have to fully understand the project, your audience, current traffic trends and the even more important – the business goals before every writing a line of code.
Resilient Enterprise Design (Craig Villamor at Enterprise UX 2017)Rosenfeld Media
This document discusses the need for resilient enterprise application design. It advocates adopting a platform mindset by starting with specific solutions and generalizing, designing for the ecosystem not just features. A design system with guidelines, code, and components can create flexibility, consistency and scale. Influence over control is important - make it easy for users to do the "right" thing. Design principles should drive decisions and be prioritized, distinct and consumable. Consumerization and customization are increasingly important for enterprise applications.
Fast prototypes and customer development for start upsSerdar Temiz
This document discusses using prototypes and customer development in the startup process. It emphasizes testing assumptions with customers from the beginning rather than relying on predictions. Prototypes like mockups, paper prototypes, landing pages, and working prototypes allow startups to get early feedback before fully developing an idea. The presentation argues for an agile process that pivots based on learning through prototyping and customer development. It provides examples of companies like Twitter that pivoted successfully and cautions that failure can be avoided through this approach.
Kevinjohn Gallagher's: Emperors new clothes (WordUp Glasgow 2012)kevinjohngallagher
The document discusses responsive design and some of its limitations. It argues that responsive design is really about adapting to mobile rather than different contexts. While the goals of responsive design are good, it cannot truly account for all contexts and instead relies on screen size as a proxy. This leads to problems with things like images. The document concludes that responsive design alone is not enough and that information architecture must also be considered to properly adapt a site for different contexts beyond just screen size.
Planning, Directing, and Editing Successful Video Projects (part 2)Richard Harrington
(This is part two)
Are you looking to add, or have already added video to your
client offerings? Video is a team sport and getting it wrong
can be really expensive. This course tackles everything you
need to create better-looking videos that please your clients
and are enjoyable to watch. Join Director Rich Harrington,
as he shares practical experiences.
Get part one here – https://www.slideshare.net/rhedpixel/planning-directing-and-editing-successful-video-projects-part-1
Software Developer Career Unplugged - GeeCon 2013Wojciech Seliga
This is my quite subjective take on various less technical aspects of a software developer career. I delivered this presentation and GeeCon 2013 (video hopefully coming soon) and quite compressed/abridged version at InfoSHARE.
Slides for application prototyping workshop on web and mobile application design.
We discussed
- product and project requirements definition
- rationale for wireframes, mockups, prototypes
- functional prototypes vs production sw
- tools: Balsamiq, myBalsamiq, Webflow
- MVP (minimum viable product) implementation in Javascript, HTML/CSS on node.js
- The document discusses various business development processes including subtraction, multiplication, division, task unification, and attribute dependency change as ways to modify a product. It then discusses prototyping and getting customer feedback as important parts of the development process. Specifically, it recommends creating minimum viable products and landing pages to test assumptions with customers before fully developing ideas. The key messages are that business plans should evolve based on customer feedback, prototyping allows early testing of ideas, and pivoting a business model based on learning is normal.
Making a website is more then making pretty picture and some sales jargon. You have to fully understand the project, your audience, current traffic trends and the even more important – the business goals before every writing a line of code.
Resilient Enterprise Design (Craig Villamor at Enterprise UX 2017)Rosenfeld Media
This document discusses the need for resilient enterprise application design. It advocates adopting a platform mindset by starting with specific solutions and generalizing, designing for the ecosystem not just features. A design system with guidelines, code, and components can create flexibility, consistency and scale. Influence over control is important - make it easy for users to do the "right" thing. Design principles should drive decisions and be prioritized, distinct and consumable. Consumerization and customization are increasingly important for enterprise applications.
Fast prototypes and customer development for start upsSerdar Temiz
This document discusses using prototypes and customer development in the startup process. It emphasizes testing assumptions with customers from the beginning rather than relying on predictions. Prototypes like mockups, paper prototypes, landing pages, and working prototypes allow startups to get early feedback before fully developing an idea. The presentation argues for an agile process that pivots based on learning through prototyping and customer development. It provides examples of companies like Twitter that pivoted successfully and cautions that failure can be avoided through this approach.
Kevinjohn Gallagher's: Emperors new clothes (WordUp Glasgow 2012)kevinjohngallagher
The document discusses responsive design and some of its limitations. It argues that responsive design is really about adapting to mobile rather than different contexts. While the goals of responsive design are good, it cannot truly account for all contexts and instead relies on screen size as a proxy. This leads to problems with things like images. The document concludes that responsive design alone is not enough and that information architecture must also be considered to properly adapt a site for different contexts beyond just screen size.
Planning, Directing, and Editing Successful Video Projects (part 2)Richard Harrington
(This is part two)
Are you looking to add, or have already added video to your
client offerings? Video is a team sport and getting it wrong
can be really expensive. This course tackles everything you
need to create better-looking videos that please your clients
and are enjoyable to watch. Join Director Rich Harrington,
as he shares practical experiences.
Get part one here – https://www.slideshare.net/rhedpixel/planning-directing-and-editing-successful-video-projects-part-1
Software Developer Career Unplugged - GeeCon 2013Wojciech Seliga
This is my quite subjective take on various less technical aspects of a software developer career. I delivered this presentation and GeeCon 2013 (video hopefully coming soon) and quite compressed/abridged version at InfoSHARE.
Building a homepage is not about coding, it's about letting your customer’s business meet their customers’ needs (okay it's also about coding).
This includes defining the purpose, meeting the users, going from needs to function, doing the framing and the design of the UX, and finally how to set up the Umbraco backend to support the needed data output in a way that is easy to use for the editors.
This document discusses various iterative software development models, including the spiral model, win-win spiral model, and cleanroom methodology. The spiral model is risk-driven and involves iterating through phases of planning, risk assessment, engineering, and evaluation. The win-win spiral model seeks to reconcile stakeholder objectives through negotiation. Cleanroom methodology emphasizes technical reviews, incremental development, and testing to reduce defects. Alternative models like hacking are also discussed for low-risk or disposable projects. Overall, the iterative models attempt to address limitations of the traditional waterfall model by incorporating feedback loops, prototyping, and incremental delivery.
Radical Requirements: Tips For Delivering What They WantRob Bogue
Requirements are the bedrock in the software development process. Here are some tips for creating requirements and recording them in a way that people can use them.
This presentation can be now be downloaded by visiting https://www.thorprojects.com/connect/gifts/presentations/radical-requirements-tips-for-delivering-what-they-want.
The document discusses various topics related to web development such as responsive design, HTML5, and open source software. It questions whether responsive design is truly about screen size or more about context. It also argues that CSS alone cannot account for all the factors like bandwidth, purpose, and context that are needed for responsive design. The document suggests that responsive design requires more than just CSS and needs an information architecture approach. It also discusses issues with images in responsive design and argues that responsive design may lead to bloated mobile pages if not implemented carefully. The document questions whether open source software is truly "free" and whether people have unrealistic expectations about ongoing support and updates without cost. Overall it advocates for a more balanced view of various web technologies and
The document discusses various topics related to web development such as responsive design, HTML5, and open source software. It questions whether responsive design is truly about screen size or more about context. It also argues that CSS alone cannot account for all the factors like bandwidth, purpose, and context that are needed for responsive design. The document suggests that open source software is often expected to be free when in reality development costs money. It advocates that people's time has value and should not be expected for free.
The conventional wisdom is if you are a non-technical person who wants to build an app, you need to a.) learn how to code, b.) find a technical cofounder, and/or c.) pay an outside agency tens of thousands of dollars to develop it for you.
Now, mobile expert Drew Gorham demonstrates why each of these assumptions is misguided, and shows how you can tap into a global pool of top-notch developers as a non-technical founder.
By leveraging your domain expertise and existing skill sets, including your soft skills, your ability to manage people, etc... you can learn to translate your vision in a way that can be easily understood and executed by expert developers around the world -- getting quick and affordable development work without sacrificing quality.
A New Toolbox: Artifact Providence 2013Kevin Sharon
Kevin and Sophie reveal Happy Cog’s design process through their experience building a responsive site from beginning to end, including: kicking off the project, the collaborative design process, and the tools they tweaked along the way. Find out what worked and what they learned. In the end, it should be clear that this is a time for experimentation and finding new approaches for new tasks.
Никита Галкин "Technical backlog: инструкция к применению"Fwdays
Дилемма “новые фичи быстро VS технический долг” известна всем. Одним из инструментов её решения является ведение технического бэклога. В ходе доклада мы поговорим:
что такое технический бэклог;
чем и как его наполнять;
как “продавать” элементы технического бэклога заказчику и команде;
и, конечно, как проводить демо элементов техбэклога.
Содержимое доклада будет интересно, всем членам команды. Результатом применение идей и инструментов из доклада станут улучшение эстимейтов, налаженность технических процессов и управляемость техническим долгом.
Second part of presentation from AnDevCon V in Boston. Looks at parts of the marketing funnel that occur after the install and how to increase conversions.
Requirements Gathering for SharePoint DevelopersRob Bogue
This document provides an overview of requirements gathering for SharePoint developers. It discusses scoping a project, capturing stakeholder needs through requirements, and documenting them. Key project activities are scoping, requirements, design/architecture, development/testing, and delivery. Common requirement types include business, user, functional, system, and quality requirements. The document also outlines tools and techniques for eliciting requirements such as interviews, personas, use cases, prototypes, and diagrams.
Slides from the "Much ado about Agile", Agile Vancouver Conference 2015. This talk is around examples of MVP on small startups and Enterprise level. What's the ultimate MVP?
Integrating user insights and validation on a weekly basis to product teams
* Building team capabilities to create low and high fidelity prototypes (design, engineering, and product management)
* Experience prototyping events as a method to de-risk and learn from end-users
* Evolutionary and lean iterations that create a revolutionary product
The document discusses responsive design and some of its challenges. It notes that while responsive design aims to apply different styles based on screen size, screen size is really just a proxy for context. It argues that responsive design cannot fully account for factors like bandwidth, purpose, and context. The document concludes that responsive design is limited because CSS was not designed to make complex decisions based on non-visual factors, and a better approach is to focus on information architecture rather than trying to shoehorn everything into CSS.
High Quality, Low Budget: How to not go broke while making great contentRichard Harrington
Creating a quality production has much more to do with planning than spending money. In this class, you’ll learn effective strategies that work to improve the quality of any project. Learn essential project management skills to improve your planning abilities. Discover how to write a treatment or outline as well as when to use a script. Plus, tie it all together with these budget trimming ideas.
Mike Long is a product designer and manager with experience living and working in San Francisco, Austin, New York, and Seattle. He has worked for and with various companies from 2009-2014 and 2014-2019. Some of his project experiences include developing a user onboarding experience for Pivotal Platform, bootstrapping application development, and designing an enterprise identity service. He emphasizes vision, feedback, growth, and reflection in his work approach and management style.
DevOpsDays Baltimore 2017.
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Magento Live 2014 Customer Expectation PresentationBrent W Peterson
This document discusses aligning customer expectations for Magento projects. It emphasizes the importance of educating clients about Magento's flexibility and complexity. Key recommendations include learning about the client's past experiences, creating a clear statement of work, communicating how additions may impact timelines, and managing assumptions. Constant, consistent communication through various channels and clear expectations are vital for success. Potential issues arise from unclear requirements, technical limitations, and emotional involvement.
Die Kombination von Django als Backend und Flutter als mobile App oder Frontend ermöglicht die Entwicklung von Anwendungen in kurzer Zeit mit gut wartbarem Quellcode. Dieser Vortrag von der enterPy 22 Konferenz zeigt an Hand einer Beispielanwendung, wie das geht.
Multiple django applications on a single server with nginxroskakori
This talk explains how to install and setup multiple Django applications on a single server.
The general principle is to setup a systend service for each application that runs in nginx and gunicorn on Ubunto 20 LTS. This results in a lightweight installation that requires only a few and small configuration files that is well integrated in the existing tool chain around systemd.
Weitere ähnliche Inhalte
Ähnlich wie Expanding skill sets - Broaden your perspective on design
Building a homepage is not about coding, it's about letting your customer’s business meet their customers’ needs (okay it's also about coding).
This includes defining the purpose, meeting the users, going from needs to function, doing the framing and the design of the UX, and finally how to set up the Umbraco backend to support the needed data output in a way that is easy to use for the editors.
This document discusses various iterative software development models, including the spiral model, win-win spiral model, and cleanroom methodology. The spiral model is risk-driven and involves iterating through phases of planning, risk assessment, engineering, and evaluation. The win-win spiral model seeks to reconcile stakeholder objectives through negotiation. Cleanroom methodology emphasizes technical reviews, incremental development, and testing to reduce defects. Alternative models like hacking are also discussed for low-risk or disposable projects. Overall, the iterative models attempt to address limitations of the traditional waterfall model by incorporating feedback loops, prototyping, and incremental delivery.
Radical Requirements: Tips For Delivering What They WantRob Bogue
Requirements are the bedrock in the software development process. Here are some tips for creating requirements and recording them in a way that people can use them.
This presentation can be now be downloaded by visiting https://www.thorprojects.com/connect/gifts/presentations/radical-requirements-tips-for-delivering-what-they-want.
The document discusses various topics related to web development such as responsive design, HTML5, and open source software. It questions whether responsive design is truly about screen size or more about context. It also argues that CSS alone cannot account for all the factors like bandwidth, purpose, and context that are needed for responsive design. The document suggests that responsive design requires more than just CSS and needs an information architecture approach. It also discusses issues with images in responsive design and argues that responsive design may lead to bloated mobile pages if not implemented carefully. The document questions whether open source software is truly "free" and whether people have unrealistic expectations about ongoing support and updates without cost. Overall it advocates for a more balanced view of various web technologies and
The document discusses various topics related to web development such as responsive design, HTML5, and open source software. It questions whether responsive design is truly about screen size or more about context. It also argues that CSS alone cannot account for all the factors like bandwidth, purpose, and context that are needed for responsive design. The document suggests that open source software is often expected to be free when in reality development costs money. It advocates that people's time has value and should not be expected for free.
The conventional wisdom is if you are a non-technical person who wants to build an app, you need to a.) learn how to code, b.) find a technical cofounder, and/or c.) pay an outside agency tens of thousands of dollars to develop it for you.
Now, mobile expert Drew Gorham demonstrates why each of these assumptions is misguided, and shows how you can tap into a global pool of top-notch developers as a non-technical founder.
By leveraging your domain expertise and existing skill sets, including your soft skills, your ability to manage people, etc... you can learn to translate your vision in a way that can be easily understood and executed by expert developers around the world -- getting quick and affordable development work without sacrificing quality.
A New Toolbox: Artifact Providence 2013Kevin Sharon
Kevin and Sophie reveal Happy Cog’s design process through their experience building a responsive site from beginning to end, including: kicking off the project, the collaborative design process, and the tools they tweaked along the way. Find out what worked and what they learned. In the end, it should be clear that this is a time for experimentation and finding new approaches for new tasks.
Никита Галкин "Technical backlog: инструкция к применению"Fwdays
Дилемма “новые фичи быстро VS технический долг” известна всем. Одним из инструментов её решения является ведение технического бэклога. В ходе доклада мы поговорим:
что такое технический бэклог;
чем и как его наполнять;
как “продавать” элементы технического бэклога заказчику и команде;
и, конечно, как проводить демо элементов техбэклога.
Содержимое доклада будет интересно, всем членам команды. Результатом применение идей и инструментов из доклада станут улучшение эстимейтов, налаженность технических процессов и управляемость техническим долгом.
Second part of presentation from AnDevCon V in Boston. Looks at parts of the marketing funnel that occur after the install and how to increase conversions.
Requirements Gathering for SharePoint DevelopersRob Bogue
This document provides an overview of requirements gathering for SharePoint developers. It discusses scoping a project, capturing stakeholder needs through requirements, and documenting them. Key project activities are scoping, requirements, design/architecture, development/testing, and delivery. Common requirement types include business, user, functional, system, and quality requirements. The document also outlines tools and techniques for eliciting requirements such as interviews, personas, use cases, prototypes, and diagrams.
Slides from the "Much ado about Agile", Agile Vancouver Conference 2015. This talk is around examples of MVP on small startups and Enterprise level. What's the ultimate MVP?
Integrating user insights and validation on a weekly basis to product teams
* Building team capabilities to create low and high fidelity prototypes (design, engineering, and product management)
* Experience prototyping events as a method to de-risk and learn from end-users
* Evolutionary and lean iterations that create a revolutionary product
The document discusses responsive design and some of its challenges. It notes that while responsive design aims to apply different styles based on screen size, screen size is really just a proxy for context. It argues that responsive design cannot fully account for factors like bandwidth, purpose, and context. The document concludes that responsive design is limited because CSS was not designed to make complex decisions based on non-visual factors, and a better approach is to focus on information architecture rather than trying to shoehorn everything into CSS.
High Quality, Low Budget: How to not go broke while making great contentRichard Harrington
Creating a quality production has much more to do with planning than spending money. In this class, you’ll learn effective strategies that work to improve the quality of any project. Learn essential project management skills to improve your planning abilities. Discover how to write a treatment or outline as well as when to use a script. Plus, tie it all together with these budget trimming ideas.
Mike Long is a product designer and manager with experience living and working in San Francisco, Austin, New York, and Seattle. He has worked for and with various companies from 2009-2014 and 2014-2019. Some of his project experiences include developing a user onboarding experience for Pivotal Platform, bootstrapping application development, and designing an enterprise identity service. He emphasizes vision, feedback, growth, and reflection in his work approach and management style.
DevOpsDays Baltimore 2017.
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Magento Live 2014 Customer Expectation PresentationBrent W Peterson
This document discusses aligning customer expectations for Magento projects. It emphasizes the importance of educating clients about Magento's flexibility and complexity. Key recommendations include learning about the client's past experiences, creating a clear statement of work, communicating how additions may impact timelines, and managing assumptions. Constant, consistent communication through various channels and clear expectations are vital for success. Potential issues arise from unclear requirements, technical limitations, and emotional involvement.
Ähnlich wie Expanding skill sets - Broaden your perspective on design (20)
Die Kombination von Django als Backend und Flutter als mobile App oder Frontend ermöglicht die Entwicklung von Anwendungen in kurzer Zeit mit gut wartbarem Quellcode. Dieser Vortrag von der enterPy 22 Konferenz zeigt an Hand einer Beispielanwendung, wie das geht.
Multiple django applications on a single server with nginxroskakori
This talk explains how to install and setup multiple Django applications on a single server.
The general principle is to setup a systend service for each application that runs in nginx and gunicorn on Ubunto 20 LTS. This results in a lightweight installation that requires only a few and small configuration files that is well integrated in the existing tool chain around systemd.
Helpful pre commit hooks for Python and Djangoroskakori
Pre-commit hooks can help to keep your source code consistent and discover broken code before it makes it into the repository. This lightning talk describes pre-commit hooks that can be helpful when developing with Python, especially when using the Django framework. It also provides consistent example configurations for hooks that have conflicting defaults.
While the Python logging module makes it simple to add flexible logging to your application, wording log messages and choosing the appropriate level to maximize their helpfulness is a topic hardly covered in the documentation. This talk give guidelines on when to choose a certain log level, what information to include and which wording templates to use.
While the technical aspects of using Java logging frameworks are well described in the respective documentation and various blogs, less thought is given on how to actually word log messages, which information to include/exclude and in which situations to apply certain log levels. In this talk we are going to take a closer look at these topics in order to make your software easier to debug and support.
Einführung in Kommunikation und Konfliktmanagement für Software-Entwicklerroskakori
Die Einführung gibt Anregungen, wie Software-Entwickler strukturiert auch in emotionalen Situationen mit underterministischen Zielen effizient zu sachlichen Lösungsansätzen kommen können.
Analyzing natural language feedback using pythonroskakori
This talk outlines how to analyze natural language feedback from restauranteering using Python. It is accompanied by a Jupyter notebook that shows how to use spaCy to split long texts into sentences and token, access the lemma of a token. Next a lexicon is used to match the tokens and assign a topic and rating to each sentence.While the presented algorithm is quite simple to implement and understand it can resolve that constructs like "not very tasty" represent a sentiment of "somewhat bad" despite the positive word "tasty".
Microsoft SQL Server with Linux and Dockerroskakori
This slightly tongue in cheek lightning talk shows how to get started with Microsoft SQL server on Linux in Docker.It explains installation, startup, data base creation on a local volume and how to connect using ODBC or JDBC.
This talk describes the design decisions, implementation steps and collected experiences related to migrating data oriented financial applications from Python 2.6 to Python 3.5 in the Raiffeisen Rechenzentrum.
Pygments is a Python package to syntax hightlight over 300 programming languages and text formats. This talk gives an overview on using the pygmentize tool to render source code as HTML, RTF or latex. It then explains the basics of lexers and tokens and show how to use the pygments API to implement source code converters. Finally a step by step life coding section describes how to implement your own lexer step by step.
This document discusses processing XML documents in Python. It introduces XML and its features like namespaces and provides an example XML file. It explains how to use the lxml library to read the XML file into a document object model, extract elements and attributes using XPath queries, and access element tags and text. Namespaces are important in XML and are represented in Clark notation when examining element tags. The document shows how to parse the example XML, extract specific elements matching an XPath, and print out names and other attributes or text of the elements.
Die Darstellung von Unicode-Zeichen in Python ist teilweise nicht ganz einfach nachvollziehbare Thematik. Diese Präsentation gibt Hilfstellungen, um den berüchtigten UnicodeError zu vermeiden. Behandelte Themen sind die Wahl eines Encodings, der richtige Zeitpunkt zum en- und decoden sowie die Erkennung eines verwendeten Encodings ohne entsprechende Dokumentation.
This document introduces how to build a simple trading bot using Python. It outlines communicating with exchanges via APIs, performing trades, analyzing data, and testing without real transactions. The bot queries balances, orders, and market data, applies trading algorithms, and logs statistics. Mock connections allow testing bot decisions against scenario files to validate functionality without financial risk. Overall, Python provides libraries to easily create initial trading bots for learning, even if profits are unlikely.
Python offers several tool and public services that simplify starting and maintaining an open source project. This presentation show cases some of the most helpful one and explains the process, beginning with an empty folder and finishing with a published PyPI package.
Ant ist ein Build-Werkzeug aus der Java-Welt, das auch für Python Projekte verwendbar ist. Diese Präsentation zeigt Beispiele für häufige Aufgaben und beschreibt, wie eine Einbindung in Jenkins zur continuous integration erfolgeb kann.
Kanban zur Abwicklung von Reporting-Anforderungenroskakori
Aufträge zu Auswertungen im Bankwesen stelle durch ihre eine hohe Anzahl möglicher Auftraggeber, eine breite Streuung in der Komplexität und Umsetzungszeit sowie das weit gestreute Technologie-Set eine Herausforderung dar. Kanban ist eine schlanke und flexible Abwicklung, die unterstützt, solche Aufträge produktiv und prompt zu erledigen, so dass sowohl der Kunde als auch der Bearbeiter zufrieden sind. Eine Präsentation erfolgte auf der 9. Anwenderkonferenz für Software Qualität und Test (ASQT) 2011.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
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
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
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.
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.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
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
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.
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
2. Goals
• Bringing developers and UX folks
together
• Creating a broader view of what
design can mean for software
application development
• Mix of talk and open discussion
Picture by KawaiiArt1980: https://www.pexels.com/de-de/foto/jungen-und-madchen-sitzen-auf-bank-spielzeug-1767434/
3. Agenda
• About design
• Example application
• Problem description
• Early design phase
• Data model rework
• Low e
ff
ort UI
• "minimum viable everything"
• Continuous discussion
• What might be applicable in your situation?
• What would you have done di
ff
erently in my situation?
• What can we learn from each other?
5. About me
Thomas Aglassinger
• "Software developer" in a general sense
• I enjoy coding
• I also look past the plain coding
• 20+ years IT industry experience in various sectors
and companies
• Sole proprietor since April 2023
• Developing my own product
• Casual freelancer: https://aglassinger.at/
• Social links
• Homepage: https://roskakori.at/
• LinkedIn: https://www.linkedin.com/in/
thomas-aglassinger/
• GitHub: https://github.com/roskakori
• Mastodon: https://graz.social/@roskakori
7. What is design?
Di
ff
erent perspectives
• Developers: Data model, business logic,
algorithms, ...
Photo by Christina Morillo: https://www.pexels.com/de-de/foto/frauenprogrammierung-auf-einem-notizbuch-1181359/
8. What is design?
Di
ff
erent perspectives
• Developers: Data model, business logic,
algorithms, ...
• UX folks: touch points, channels, dialogs,
work
fl
ows, ...
Picture by Alvaro Reyes https://unsplash.com/de/fotos/qWwpHwip31M
9. What is design?
Di
ff
erent perspectives
• Developers: Data model, business logic,
algorithms, ...
• UX folks: touch points, channels, dialogs,
work
fl
ows, ...
• Wikipedia: "A design is a concept of either an
object, a process, or a system that is speci
fi
c and,
in most cases, detailed. Design refers to
something that is or has been intentionally created
by a thinking agent, though it is sometimes used
to refer to the nature of something."
Photo by cottonbro studio: https://www.pexels.com/de-de/foto/mann-der-schmeckt-was-er-kocht-3338536/
12. The problem
A potential customer has a contract and opens call for bids
Estimate effort 🤔 Submit offer 😨
13. The problem
A potential customer has a contract and opens call for bids
Estimate effort 🤔 Submit offer 😨
Too high → no contract 😭
14. The problem
A potential customer has a contract and opens call for bids
Estimate effort 🤔 Submit offer 😨
Too high → no contract 😭
Too low → contract but no pro
fi
t 😔
15. The problem
A potential customer has a contract and opens call for bids
Estimate effort 🤔 Submit offer 😨
Too high → no contract 😭
Just right → contract with pro
fi
t 🎉
Too low → contract but no pro
fi
t 😔
16. What to do about it?
Improve your estimations!
17. What to do about it?
Improve your estimations!
18. What to do about it?
Improve your estimations!
19. What to do about it?
Improve your estimations!
20. What to do about it?
Improve your estimations!
21. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
22. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
Get task and
time tracker💡
23. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
Get task and
time tracker💡
One combined solution
to compare and
rule them all 👊
24. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
Get task and
time tracker💡
One combined solution
to compare and
rule them all 👊
Marketing: 😡
"WTF Wiki syntax?"
Developer: 😡
"WTF no repo link?"
Accounting: 😡
"WTF no import?"
25. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
Get task and
time tracker💡
One combined solution
to compare and
rule them all 👊
Develop and maintain
complex in-house application
for comparison (€10-100k) 🤑
Marketing: 😡
"WTF Wiki syntax?"
Developer: 😡
"WTF no repo link?"
Accounting: 😡
"WTF no import?"
26. The problem
How to track and compare e
ff
ort?
How to track and
compare effort? 🤔
Get task and
time tracker💡
One combined solution
to compare and
rule them all 👊
Develop and maintain
complex in-house application
for comparison (€10-100k) 🤑
Develop and maintain crappy scripts
and macros for comparison 🤪
Marketing: 😡
"WTF Wiki syntax?"
Developer: 😡
"WTF no repo link?"
Accounting: 😡
"WTF no import?"
35. The problem
Agile development: "Embrace change!"
Developers
estimate 200K 🛠
Customer takes
offer 🎉
Features get added
and changed 🌪
36. The problem
Agile development: "Embrace change!"
Developers
estimate 200K 🛠
Customer takes
offer 🎉
Project costs
300K💰
Features get added
and changed 🌪
37. The problem
Agile development: "Embrace change!"
Developers
estimate 200K 🛠
Customer takes
offer 🎉
Project costs
300K💰
Features get added
and changed 🌪
Customer:
"WTF budget?"😱
39. Early design phase
Pre-evaluation
• Leave old company due to con
fl
ict of values
• Decide to become self employed for a
change
• A couple of product ideas in mind
• Roughly evaluate them by talking to people
in close vicinity (friends, relatives, former
colleagues, gamer mates, ...)
• Pick the one that triggers people to tell their
own stories and has most emotional
reactions → project estimation
Picture by Miriam Espacio: https://www.pexels.com/de-de/foto/person-die-in-der-nahe-von-baumen-steht-3354135/
40. Pitch phase
Con
fi
rmation
• Compile a set of slides that pitches the entire
thing somewhat coherently.
• Run it on a couple of acquaintances.
• Integrate feedback.
• De
fi
ne target audience and possible revenue
streams.
• Re
fi
ne and con
fi
rm features for minimum
viable product.
41. Execution phase
Let's go!
• Find a couple of people to periodically interact with.
• Draw a few sketches.
• Start coding.
• (Out of scope: Found a sole proprietor company
(German: Einzelpersonenunternehmen)
• Pitch and recruit initial test customers.
• ...This is the story so far
Picture from Kelly : https://www.pexels.com/de-de/foto/foto-des-mannes-der-steht-wahrend-er-spitzhacke-halt-2382665/
46. Initial data model
• Worked reasonably well for GitHub and clocko:do
• Matches work to task using the task code in the description
• Turned out to be ugly for GitLab
• Tracks both tasks and work
• Matches work to task using internal references
51. Data model changes
E
ff
ort depends on kind
Simple
• Add
fi
eld
• Rename
fi
eld
• Changed
fi
eld parameters like length or
valid range
• Remove unused
fi
eld
• Add default to
fi
eld
• ...
Complex
• Split
fi
elds
• Add new
fi
eld that must hold a
meaningful value from the start
• Major moving and renaming of
entire model hierarchies
• Change relations and dependencies
52. Visualization of change impact
Gource movie about the source code repository
• Link: https://youtu.be/kmBJf_dQodQ
• Interesting points in time line:
• 0:00 Quickly establish basic structures
• 1:00 Start of a period of iterative improvement
• 4:20 Start of major data model rework
• 5:20 Continue iterative improvement with reword data model
56. From data model to user interface
Example: Project
• Organization: reference
• Code: text
• Name: text
• "Demo Inc."
• 23-0074-s
• "Cooking App"
57. From data model to user interface
Example: Project
• Organization: reference
• Code: text
• Name: text
• created_at: date and time
• modi
fi
ed_at: date and time
58. Code for data model
class Project(SiiModel):
organization: Organization = models.ForeignKey(
Organization,
on_delete=models.PROTECT,
related_name="project",
verbose_name=_("organization")
)
code: str = models.CharField(
max_length=MAX_CODE_LENGTH,
validators=[validate_code],
verbose_name=_("code"),
)
created_at: datetime = models.DateTimeField(
auto_now_add=True, verbose_name=_("created at")
)
modi
fi
ed_at: datetime = models.DateTimeField(
auto_now=True, verbose_name=_("modi
fi
ed at")
)
name: str = models.CharField(
max_length=MAX_NAME_LENGTH,
verbose_name=_("name"),
)
59. Code for data model and user interface
class Project(models.Model):
organization: Organization = models.ForeignKey(
Organization,
on_delete=models.PROTECT,
related_name="project",
verbose_name=_("organization")
)
code: str = models.CharField(
max_length=MAX_CODE_LENGTH,
validators=[validate_code],
verbose_name=_("code"),
)
created_at: datetime = models.DateTimeField(
auto_now_add=True, verbose_name=_("created at")
)
modi
fi
ed_at: datetime = models.DateTimeField(
auto_now=True, verbose_name=_("modi
fi
ed at")
)
name: str = models.CharField(
max_length=MAX_NAME_LENGTH,
verbose_name=_("name"),
)
@admin.register(Project)
class ProjectAdmin(admin.ModelAdmin):
fi
eldsets = (
(
None,
{
"
fi
elds": (
"organization",
"code",
"name",
)
},
),
(_("administration"), {"
fi
elds": ("created_at", "modi
fi
ed_at")}),
)
readonly_
fi
elds = ("created_at", "modi
fi
ed_at")
)
60. Code for data model and user interface
Summary
class Project(models.Model):
organization: Organization = models.ForeignKey(
Organization,
on_delete=models.PROTECT,
related_name="project",
verbose_name=_("organization")
)
code: str = models.CharField(
max_length=MAX_CODE_LENGTH,
validators=[validate_code],
verbose_name=_("code"),
)
created_at: datetime = models.DateTimeField(
auto_now_add=True, verbose_name=_("created at")
)
modi
fi
ed_at: datetime = models.DateTimeField(
auto_now=True, verbose_name=_("modi
fi
ed at")
)
name: str = models.CharField(
max_length=MAX_NAME_LENGTH,
verbose_name=_("name"),
)
@admin.register(Project)
class ProjectAdmin(admin.ModelAdmin):
fi
eldsets = (
(
None,
{
"
fi
elds": (
"organization",
"code",
"name",
)
},
),
(_("administration"), {"
fi
elds": ("created_at",
"modi
fi
ed_at")}),
)
readonly_
fi
elds = ("created_at", "modi
fi
ed_at")
)
• Organization: reference
• Code: text
• Name: text
• created_at: date and time
• modi
fi
ed_at: date and time
62. Edit project and everything related
The problem
• Project model itself is simple
• But many things related to it:
• Task trackers
• Work trackers
• Users
• Estimation
• ....
• Encompasses large parts of the entire data model
• Complexity will grow as features are added
Photo by Linh Ha https://unsplash.com/de/fotos/KN8W0Q8H3gI
63. Edit project and everything related
Solution 1:
• Spend n+1 person days with Figma et al.
• Spend m+1 person days coding away
• Wait for requirements to change
• Repeat
64. Edit project and everything related
Solution 1:
• Spend n+1 person days with Figma et al.
• Spend m+1 person days coding away
• Wait for requirements to change
• Repeat
65. Edit project and everything related
Solution 1:
• Spend n+1 person days with Figma et al.
• Spend m+1 person days coding away
• Wait for requirements to change
• Repeat
66. Edit project and everything related
Solution 2
• Con
fi
gure project in YAML
fi
le
• When changed, upload via form
67. Edit project and everything related
Solution 2
• Con
fi
gure project in YAML
fi
le
• When changed, upload via form
organization:
name: Demo Inc.
timezone: Europe/Vienna
projects:
- code: siisurit
name: Siisurit
trackers:
- name: siisurit-demo
api_kind: gitlab
api_location: https://gitlab.com/xxxx/siisurit-demo
api_token: ...
68. Edit project and everything related
Solution 2
• Con
fi
gure project in YAML
fi
le
• When changed, upload via form
70. Summary
• Example of explorative design and major data model rework
• Cheap vs expensive data model changes
• Python+Django keep you nimble
71. Conclusion
• Design user experience early
• Design user interface late. Meanwhile:
• Use generated user interfaces for simple interaction
• Use descriptive text
fi
les and uploads for complex structures and
relationships
• Helpful: Developers and designers that understand each others needs