From 485b831ea6b92a8ad5fae6487f5e2f1f926218f5 Mon Sep 17 00:00:00 2001 From: Benjamin Bach Date: Tue, 9 Jul 2024 19:35:36 +0200 Subject: [PATCH] Clarify some differences co-realization vs rapid development --- content/_index.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/_index.md b/content/_index.md index aed7854..d023bcc 100644 --- a/content/_index.md +++ b/content/_index.md @@ -118,6 +118,8 @@ One of the reasons for minimizing a tech stack or being fairly skeptic about tec Sharing contexts means to take part in the world of users and other stakeholders. There are several reasons why it makes sense for developers and designers to share as much context as possible with other stakeholders, especially users. Firstly, it makes developers able to become designers and make more qualified proposals. But secondly, it also helps to prioritize in harmony. + +Co-realizing is also said to grow the "design space". This means that by *directly* sharing technical understanding with users and vice-versa sharing user experience with the developer, everyone's understanding and ability to generate relevant ideas grows. @@ -133,9 +135,11 @@ There are several reasons why it makes sense for developers and designers to sha The idea of "rapid development" has a long historical run-way, leading up to ideas like "ship early, ship often", agile programming methodologies etc. -With rapid development, we mean that the developer should participate in the context/domain that the software seeks to solve problems and create value in. The developer needs direct feedback from seeing the software in use. +As with co-realization, in our understanding of rapid development, we place the developer in the context/domain that the software seeks to solve problems and create value in. The developer needs direct feedback from seeing the software in use. -This in turn saves costly interactions and translations across actors. By fixing the problem here and now, we don't risk that the context is diluted, nor that elements are lost in transmission or translation between designers and managers. By letting the programmer be the designer, we in turn push responsibility and initiative to the user that gets to instruct the programmer directly. These methods are known also as co-realization and to expand "design space". +The short and tight feedback-loop enables developers to act as designers and to generate instant feedback for new features. + +This in turn saves costly interactions and translations across actors. By fixing the problem here and now, we don't risk that the context is diluted, nor that elements are lost in transmission or translation between designers and managers. By letting the programmer be the designer, we in turn push responsibility and initiative to the user that gets to instruct the programmer directly.