Day 3 typos

This commit is contained in:
2024-03-26 15:09:33 +01:00
parent 7b1203c7a3
commit daf83861af
7 changed files with 85 additions and 74 deletions

View File

@@ -6,7 +6,7 @@ tags:
- dx
---
Mitch from aviatrix -a former software engineer who has now switched over to product managment.
Mitch from aviatrix -a former software engineer who has now switched over to product management.
## Opening Thesis
@@ -14,19 +14,19 @@ Opening with the Atari 2600 E.T. game as very bad fit sample.
Thesis: Missing user empathy
* A very hard game aimed at children without the will to trail and error
* Other aspect: Some of the devalopers were pulled together from throughout the company -> No passion needed
* Other aspect: Some devalopers were pulled together from throughout the company -> No passion needed
### Another sample
* Idea: SCADA system with sensors that can be moved and the current location get's tracked via iPad.
* Result: Nobody used the iPad app - only the desktop webapp
* Problem: Sensor get's moved, location not updated, the measurements for the wrong location get reported until update
* Idea: SCADA system with sensors that can be moved, and the current location gets tracked via iPad.
* Result: Nobody used the iPad app - only the desktop Web-app
* Problem: Sensor gets moved, location not updated, the measurements for the wrong location get reported until update
* Source: Moving a sensor is a pretty involved process including high pressure aka no priority for iPad
* Empathy loss: Different working endvironments result in drastic work experience missmatch
* Empathy loss: Different working environments result in drastic work experience mismatch
## The source
* Idea: A software engineer writes software, that someone else has to use, not themselfes
* Idea: A software engineer writes software, that someone else has to use, not themselves
* Problem: Distance between user and dev is high and their perspectives differ heavily
## User empathy
@@ -37,43 +37,43 @@ Thesis: Missing user empathy
## Stories from Istio
* Classic implementation: Sidecar Proxy
* Question: Can the same value be provided without a sidecar anywhers
* Question: Can the same value be provided without a sidecar anywhere
* Answer: Ambient mode -> split into l4 (proxy per node) and l7 (no sharing)
* Problem: After alpha release ther was a lack of exitement and feedback
* Problem: After alpha release there was a lack of excitement and feedback
* Result: Twitter Space event for feedback
### Ideas and feedback
* Idea: Sidecar is somewhat magical
* Feedback: Sidecars are a pain, but after integrating istio can be automated -> a problem gets solved, that already had a solution
* Feedback: Sidecars are a pain, but after integrating Istio can be automated -> a problem gets solved, that already had a solution
* Result: Highly overvalued the pain of sidecars
* Idea: Building istio into a platform sounds easy
* Idea: Building Istio into a platform sounds easy
* Feedback: The platform has to be changed for the new ambient mode -> High time investment while engineers are hard
* Result: The cost of platform changes was highly undervalued
* Idea: Sidecar compute sound expensive and networking itself pretty cheap
* Feedback: Many users have multi-region clusters -> Egress is whery expoenive
* Feedback: Many users have multi-region clusters -> Egress is very expensive
* Result: The relation between compute and egress cost was pretty much swapped
### What now?
* Ambient is the right solution for new users (fresh service mesehes)
* Existing users probaly won't upgrade
* Result: They will move forward with ambient mdoe
* Ambient is the right solution for new users (fresh service meshes)
* Existing users probably won't upgrade
* Result: They will move forward with ambient mode
## So what did we lern
## So what did we learn
### Basic questions
* Who are my intended users?
* What exites/worries them?
* What excites/worries them?
* What do they find easy/hard?
* What is ther biggest expense and what is inexpensive?
* What is the biggest expense and what is inexpensive?
### How to get better empathy
1. Shared perspective comes from proximity
1. Where they are
2. What they do -> Dogfood everything related to the platform (not just your own products)
2. What they do -> Dog food everything related to the platform (not just your own products)
2. Never stop listening
1. Even if you love your product
2. Especially if you love your product
@@ -81,4 +81,4 @@ Thesis: Missing user empathy
### Takeaways
* Don't ship a puzzlebox (landscape) but a picture (this integrates with this and that)
* Don't ship a puzzle box (landscape) but a picture (this integrates with this and that)