Software development is best understood as a cooperative game of invention and communication, rather than an engineering process or model building exercise. The primary goal of the game is to deliver useful working software, while the secondary goal is to set up for future projects. Successful software development relies more on the ideas and discussions between team members than on formal work products and models. Programmers function more as communication specialists than non-communicative coders. Building a theory of the problem and solution through communication is more important than documentation.
When going into the development of a software product, a possible source of mistake is the incorrect evaluation of the complexity that lies behind an idea , as well as a clutter coming from the massive amounts of technologies enabled. This presentation explains a possible way to deal with such issues.
Software development is not exactly the same as computer programming. When it comes to a career, development for productization introduces many more things than simply coding. It is important to learn how to accomplish tasks, sharpen skills, develop the career and enjoy it. And last but not the least, how to start?
User Interface Prototyping - Low- and High-Fidelity Prototyping TodayThomas Memmel
Zühlke offers various usability engineering services – get in touch at www.zuehlke.com/usability
User Studies, User Profiling & User Modeling (e.g. Personas), User-Centered Requirements Engineering, Usability Concepts & Modeling (e.g. Scenarios, Storyboards), Agile Development & User Experience (e.g. User Stories combined with elements of Interaction Design), User Interface Prototyping (Low- & High-Fidelity), User Interface Engineering (Integration of Usability Methodology in the Software Development Process), Usability Testing (e.g. with Mobile Usability Lab), User Interface Specification.
Develop your career in the field of software development. Want to learn programming and develop your own applications, the presentation helps you to understanding the technology and the training methodologies required for that.
When going into the development of a software product, a possible source of mistake is the incorrect evaluation of the complexity that lies behind an idea , as well as a clutter coming from the massive amounts of technologies enabled. This presentation explains a possible way to deal with such issues.
Software development is not exactly the same as computer programming. When it comes to a career, development for productization introduces many more things than simply coding. It is important to learn how to accomplish tasks, sharpen skills, develop the career and enjoy it. And last but not the least, how to start?
User Interface Prototyping - Low- and High-Fidelity Prototyping TodayThomas Memmel
Zühlke offers various usability engineering services – get in touch at www.zuehlke.com/usability
User Studies, User Profiling & User Modeling (e.g. Personas), User-Centered Requirements Engineering, Usability Concepts & Modeling (e.g. Scenarios, Storyboards), Agile Development & User Experience (e.g. User Stories combined with elements of Interaction Design), User Interface Prototyping (Low- & High-Fidelity), User Interface Engineering (Integration of Usability Methodology in the Software Development Process), Usability Testing (e.g. with Mobile Usability Lab), User Interface Specification.
Develop your career in the field of software development. Want to learn programming and develop your own applications, the presentation helps you to understanding the technology and the training methodologies required for that.
The Fundamentals of Continuous Software DesignJeremy Miller
Here's my talk from CouchCon on the fundamental ideas and thinking behind doing software design in an Agile Software project
See the whole talk at https://www.youtube.com/watch?v=v9icxKMJ9PA
Research grants from the European Research Council (ERC) are great to have, but hard to get, In this talk, I give twelve personal tips that have been helpful for preparing your grant proposal.
Slides of a talk at INRIA Nancy, 20 December 2017
Learning Solutions 2011 #LS2011 presentation on Learner Experience Design. Address what instructional design can learn from Ux (User Experience Design).
UXPA2019: Voice User Interface Design for Customer Support: Design guidance ...UXPA International
This talk from UXPA 2019 focused on the challenges, lessons learned, and best practices in designing voice user interfaces for customer support reinforced by three recent user studies. It explored both high and low level design issues. It also discussed methodological techniques for testing voice user interfaces including creating flow diagrams for prototypes and conducting usability evaluations of these designs with users. This was an informative session especially for those who are beginning their journey in designing and testing voice user interfaces. The session included audience participation in a VUI design exercise.
The Fundamentals of Continuous Software DesignJeremy Miller
Here's my talk from CouchCon on the fundamental ideas and thinking behind doing software design in an Agile Software project
See the whole talk at https://www.youtube.com/watch?v=v9icxKMJ9PA
Research grants from the European Research Council (ERC) are great to have, but hard to get, In this talk, I give twelve personal tips that have been helpful for preparing your grant proposal.
Slides of a talk at INRIA Nancy, 20 December 2017
Learning Solutions 2011 #LS2011 presentation on Learner Experience Design. Address what instructional design can learn from Ux (User Experience Design).
UXPA2019: Voice User Interface Design for Customer Support: Design guidance ...UXPA International
This talk from UXPA 2019 focused on the challenges, lessons learned, and best practices in designing voice user interfaces for customer support reinforced by three recent user studies. It explored both high and low level design issues. It also discussed methodological techniques for testing voice user interfaces including creating flow diagrams for prototypes and conducting usability evaluations of these designs with users. This was an informative session especially for those who are beginning their journey in designing and testing voice user interfaces. The session included audience participation in a VUI design exercise.
We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure.
I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall.
https://www.youtube.com/watch?v=aZgnY9fAHOA
Critiquing CS Assessment from a CS for All lens: Dagstuhl Seminar PosterMark Guzdial
Poster presented at the Dagstuhl Seminar "Assessing Learning in Introductory Computer Science" (http://www.dagstuhl.de/en/program/calendar/semhp/?semnr=16072). I argue that we have to consider what the learner wants to do and wants to be (i.e., their desired Community of Practice) when assessing learning. Different CoP, different outcomes, different assessments.
Introduction to Software Engineering, Software Process, Perspective and Specialized Process Models – Introduction to Agility – Agile process – Extreme programming – XP process - Estimation-FP,LOC and COCOMO I and II,Risk Management, Project Scheduling.
Steve McConnell is CEO and Chief Software Engineer at Construx Software where he writes books and articles, teaches classes, and oversees Construx’s software engineering practices.
Empirical Methods in Software Engineering - an Overviewalessio_ferrari
A first introductory lecture on empirical methods in software engineering. It includes:
1) Motivation for empirical software engineering studies
2) How to define research questions
3) Measures and data collection methods
4) Formulating theories in software engineering
5) Software engineering research strategies
Find the videos at: https://www.youtube.com/playlist?list=PLSKM4VZcJjV-P3fFJYMu2OhlTjEr9Bjl0
Based on my observations, in IT we suffer from continuous collective amnesia and we are even proud of it.
For at least 50 years meanwhile, we struggle how to build systems, that are easy to understand, to maintain, to change and to operate in a reliable way. Each time we hit the wall again, we start to look for a new silver bullet on the horizon, strongly believing that it will solve the problem for good.
The key word is "new": "New" is good in our community, while "old" is bad, worthless, crap. We suffer from youthism, not only in recruiting, but in all areas. This way we discard any "old" knowledge, no matter if it is valuable or not. We separate by age, not by value.
Additionally we continuously lose our collective memory with every new generation that leaves university as they are also taught not to value anything old and instead only look for the new, shiny stuff.
While not all old knowledge is worth being preserved, admittedly, there is still a lot of valuable old knowledge available, offering answers to the problems that we face today - creating maintainable and reliable systems, dealing with distribution and tackling complexity, just to name a few of the challenges.
This presentation is a journey through some (very) old computer science papers that contain a lot of very valuable knowledge regarding the problems we face today. For each of the papers, some of the key ideas are presented and how they address our current challenges.
Of course, the voice track is missing and there are a lot more papers that would be worth being mentioned in this presentation. Still, I hope that also the slides alone will be of some value for you - and convince you a bit that not everything "old" in IT is automatically worthless ... ;)
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
2. Three Levels of Learning
• Learning new skills
– Following: “one procedure that works”, “at
least this thing works”
– Detaching:”when does it break down?” “learn
limits of procedure”, “adapt it”, “when is it
appropriate?” Survey paper.
– Fluent:”irrelevant whether following a
particular technique”, ”knowledge has become
integrated”.
3. The Three Levels and
Methodology
• Methodology: a series of related methods
and techniques (Miriam-Webster)
• Level 1: processes, techniques and
standards in detail. Detailed templates in
RUP servel level 1 audience. Big
methodologies of Accenture (anderson
Consulting).
4. Three Levels of Methodology
• Level 2/3: The Pragmatic Programmer:
identifies techniques that a practitioner uses.
A useful library of ideas but the beginner
finds it lacking specific rules.
• Avoid level mixup! It confuses.
5. Shu-Ha-Ri
• Three levels are known in other skill areas:
Aikido (self defense technique)
• Shu: learn. Build technical foundation for
the art. Single instructor.
• Ha: detach. Understand meaning and
purpose; not just repetitive practice.
• Ri: transcend. Practitioner; original
thoughts
6. A Cooperative Game of
Invention and Communication
• A fruitful way to think about software
development.
• Games used by mathematicians and
corporate strategiests.
• Kinds of games: zero-sum, positional,
competitive, cooperative, finite, …
7. Software Development
• Group game
• Non-zero-sum: multiple winners and losers.
• Better not viewed as a positional game:
state is recorded.
• Cooperative
• Goal-seeking
• Finite
8. Infinite Games
• Infinite games: organizations, corporations
and countries, a person’s profession.
• Do well in one game to be well positioned
for the next one.
9. Software and Rock Climbing
• Best comparison partner
• Cooperative and goal seeking
– How well they climbed together
– How much they enjoyed themselves
– Reach the top?
• Load bearing
– Climbers must support their weight. Software
must run.
10. Software and Rock Climbing
•
•
•
•
•
•
Team
Individuals with talent
Skill sensitive
Training
Tools
Resource-limited: before nightfall or the
weather changes.
12. A Game of Invention and
Communication
• Software development: group game which
is goal seeking, finite and cooperative
• Team: sponsor, manager, usage specialists,
designers, testers and writers
• Next game: maintenance, build an entirely
different system
13. Cooperative Game of Invention
and Communication
• Measure of quality as a team: how well they
cooperate and communicate during game.
• What are the moves of the game:
– There is nothing in the game but people’s ideas
and the communication of those ideas to their
colleages (including the sponsor) and to the
computer.
14. Emotions, wishes and thoughts
• The task facing the developers:
– They are working on a problem they don’t fully
understand and that lives in emotions, wishes and
thoughts and that changes as they proceed.
– They need to understand.
• Problem space.
• Imagine some mechanism in a viable technology space.
• Express in an executable language which lacks many features
of expression to a system that is unforgiving of mistakes.
15. What is
software development?
• Software Development is a resourcelimited) cooperative game of invention and
communication.
– The primary goal of the game is to deliver
useful, working software.
– The secondary goal of the game is to set up for
the next game. The next game may be to alter
or replace the system or to create a neighboring
system.
Not many people have articulated this before
16. Software and Engineering
• Considering software
development as a game with
moves is profitable.
– Gives us a way to make meaningful
decisions on a project.
• In contrast: speaking of software
development as engineering or
model building does not help.
17. Engineering
• People mostly use engineering to create a
sense of guilt for not having done enough of
something, without being clear of what that
something is.
• Dictionary: The application of science and
mathematics by which the properties of
matter and the sources of energy in nature
are made useful to man (Webster’s Dic.).
18. What is “doing engineering”
• In my experience: involves creating a tradeoff solution in the face of conflicting
demands.
• Also applies to software development.
19. Confusing act and outcome
• Outcome: The factory, which is run while
specific people watch carefully for
variations in quantity and quality of the
items being manufactured.
• Act: ill-defined creative process the
industrial engineer goes through to invent
the manufacturing plant.
20. More like Engineering?
• When people say: “Make software
development more like engineering” they
often mean, “Make it more like running a
plant, with statistical quality control”.
• But: running the plant is not the act of doing
engineering.
21. Look up previous solutions
• The other part of “doing engineering”
• Civil engineers are not supposed to invent
new structures.
– Take soil samples and use the code books to
look for the simplest structure that handles the
required load over the given distance building
on the soil at hand.
– Centuries of tabulation of known solutions
22. Fits marginally
• This only fits marginally the current state of
software development
• We are still in the stage where there is
competition between designs.
• Technologies are changing fast that few
code books exist
• Today there are more variations between
systems than there are commonalities.
23. Return
• Return to consider engineering as thinking
and making trade-offs.
24. Software and Model Building
• Ivar Jacobson: “software development is
model building”
• Leads to inappropriate project decisions
25. Interesting part not in models
• If software development were model
building, then the valid measure of the
quality of the software or of the
development process would be the quality
of the models (fidelity, completeness)
26. But successful project teams say
• The interesting part of what we want to
express doesn’t get captured in those
models. The interesting part is what we say
to each other while drawing on the board.
• We don’t have time to create fancy or
complete models
• Paying attention to the models interfered
with developing the software
27. Sufficiency
• The work products of the team should be
measured for sufficiency with respect to
communicating with the target group.
• It does not matter if incomplete, incorrect
syntax, … if they communicate sufficiently
to the recipients.
29. What is
software development?
• Software Development is a resourcelimited) cooperative game of invention and
communication.
– The primary goal of the game is to deliver
useful, working software.
– The secondary goal of the game is to set up for
the next game. The next game may be to alter
or replace the system or to create a neighboring
system.
Not many people have articulated this before
30. Programmers as
Communications Specialists
• Game of communication: different light on
programmers …
• Stereotyped as noncommunicative individuals
who like to sit in darkened rooms
• High acceptance of programming in pairs …
Programmers thought they would not like it but
they like it! (Extreme Programming)
31. Game of invention
• So far not as a game of communication
• Interest of programmers to discuss
programming matters gets in the way of
them discussing business matters with
sponsors, users and business experts.
32. Universities
• Can reverse the general characteristics by
creating software development curricula
that contain more communication-intensive
courses
• Attracts different students (University of
Aalborg, Denmark).
33. Gaming Faster
• We should not expect orders of magnitude
improvement in program production.
• As much as programming languages may
improve, programminvg will still be limited
by our ability to think through the problem
and the solution.
34. Analogy
• Two other fields of thought expression
– Writing novels
– Writing laws: Lawyers won’t get exponentially
faster at creating contracts and laws!
35. Diminishing Returns
• Because a software development project is
resource limited, spending extra to make an
intermediate work product better than it
needs to be for its purpose is wasteful.
• Work products of every sort are sufficien
37. What goes on in software
development? Intro.
• Most accurate account
• Quality is related to the match between the
theory of the problem and the theory of the
solution.
• The designer’s job is not to pass along the
design but the theories that drive the design.
38. What is programming
• Should be regarded as an activity by which
the programmers form or achieve a certain
kind of insight, a theory, of the matters at
hand.
• Not as a production of a program and other
texts.
39. Programming and the
Programmer’s Knowledge
• Programming = the whole activity of design and
implementation
• Programming = building up knowledge
• What kind of knowledge?
• A theory: a person who has or posses a theory
knows how to do certain things and can support
the actual doing with explanations, justifications
and answers to queries.
40. Theory transcends documentation
in at least 3 essential ways
• How are affairs of the world mapped into the
program text? For any aspect of the world the
programmer can state its manner of mapping into
the program text. [AOSD]
• Can support the program text with some
justification.
• Is able to respond constructively to any demand
for a modification. Similarity of new demand to
similarities already in the system.
41. Problems and Costs of Program
Modifications
• Cost savings by modifying existing
program rather starting from scratch.
• Cheaper? Not supported by other
complicated man-made constructions:
bridges, buildings, etc. Often demolish and
rebuild is most economical.
• Program modification is just text editing?