init
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Julien Calixte
|
||||
title: Hi!
|
||||
---
|
||||
|
||||
<main>
|
||||
|
||||
24
src/pages/posts/production-flow.mdx
Normal file
24
src/pages/posts/production-flow.mdx
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: An introduction to production flow
|
||||
---
|
||||
|
||||
# {title}
|
||||
|
||||
Dear developers, how clear is it for you the way you build an app?
|
||||
|
||||
You may answer "Easy! There are few steps:"
|
||||
|
||||
1. Talking to the client
|
||||
2. Getting the design
|
||||
3. Coding
|
||||
4. deploying to users
|
||||
|
||||
But how exactly? What does "talking to the client" really mean? And "coding" ?
|
||||
|
||||
In lean, one particular important concept is **Visual Management**: *doing by seeing*. For that, we want to be clear on how we work.
|
||||
|
||||
May I ask you some questions?
|
||||
|
||||
First, can you name your different step before having your app in production?
|
||||
|
||||
<ProductionFlow />
|
||||
Reference in New Issue
Block a user