@@ -140,31 +140,28 @@ <h4>From ML experiments to production: </h4>
140
140
< h3 > Versioning and Reproducibility </ br > with MLV-tools</ h3 >
141
141
< p > < i > < small > Stéphanie Bracaloni and Sarah Diot-Girard</ small > </ i > </ p >
142
142
< aside class ="notes ">
143
-
143
+ @SDG
144
144
</ aside >
145
145
</ section >
146
146
< section >
147
147
< h3 > About Us</ h3 >
148
148
< div class ="two-halves ">
149
- < div class ="half ">
149
+ < div class ="half " style =" text-align: left " >
150
150
< b > Sarah Diot-Girard</ b > </ br >
151
151
Data Scientist since 2012 </ br >
152
152
Interested in DataOps and ethics</ br >
153
153
< img class ="icon " src ="./img/GitHub-logo.png "/ alt="PeopleDoc logo" style="width: 1em"> @SgdJlbl
154
154
</ div >
155
- < div class ="half ">
155
+ < div class ="half " style =" text-align: right " >
156
156
< b > Stéphanie Bracaloni</ b > </ br >
157
- Software Engineer [...]</ br >
157
+ Software Engineer since 2013</ br >
158
+ Automation and code Quality</ br >
158
159
< img class ="icon " src ="./img/GitHub-logo.png "/ alt="PeopleDoc logo" style="width: 1em"> @sbracaloni
159
160
</ div >
160
161
</ div >
161
162
< img class ="plain " src ="./img/logo.png "/ alt="PeopleDoc logo" style="width: 4em">
162
163
< aside class ="notes ">
163
- - Sarah : [petit resumé] + Accroche sur les technos => J'utilise des jupyter notebook
164
- et j'ai besoin de ...pouvoir reproduire facilement, garder de la souplesse, ...
165
- - Stephanie: [petit résumé] + Accroche Automatisation, Livaison, Tests
166
- J'ai besoin de... un truc qui se lance facilement, qui se package, qui soit reproductible
167
- sur n'importe quel environnement
164
+ @SDG + @SBI
168
165
</ aside >
169
166
</ section >
170
167
< section >
@@ -178,6 +175,7 @@ <h3>About Us</h3>
178
175
< section >
179
176
Monday morning, 9am
180
177
< aside class ="notes ">
178
+ @SDG
181
179
It's Monday morning, 9am.
182
180
You're an happy DS. Friday night, you finally made a breakthrough in your research project.
183
181
you sent that to your boss.
@@ -186,21 +184,28 @@ <h3>About Us</h3>
186
184
< section >
187
185
This is a picture of a nice graph with POC results.
188
186
< aside class ="notes ">
187
+ @SDG
189
188
You sent the results to your boss.
190
189
She loves it. She want it in production asap.
191
190
</ aside >
192
191
</ section >
193
192
< section >
194
193
Monday morning, 10am
195
194
< aside class ="notes ">
195
+ @SDG (@SBI => "It's me")
196
196
It's Monday morning, 10am.
197
197
You are asking your SE coworker for help. You showed her your POC and now she looks like she's gonna faint
198
198
and she wants to kill you AT THE SAME TIME!
199
199
</ aside >
200
200
</ section >
201
201
< section >
202
- < img src ="./img/poc_worst.jpg "/>
202
+ < div >
203
+ < img class ="fragment current-visible preload " src ="./img/poc_worst1.png ">
204
+ < img class ="fragment current-visible " src ="./img/poc_worst2.png ">
205
+ < img class ="fragment current-visible " src ="./img/poc_worst3.png ">
206
+ </ div >
203
207
< aside class ="notes ">
208
+ @SDG
204
209
- git repo with format not really compatible with git versioning
205
210
- hardcoded stuff (path, user, ...)
206
211
- hardcoded hyperparameters
@@ -209,24 +214,46 @@ <h3>About Us</h3>
209
214
< section >
210
215
Two weeks later
211
216
< aside class ="notes ">
217
+ @SDG
212
218
Two weeks later.
213
219
It's Monday morning, 9am.
214
220
You have worked hard to clean up the POC. It's a bit better but...
215
221
</ aside >
216
222
</ section >
217
223
< section >
218
- < img src ="./img/poc_ml.jpg "/>
224
+ < div >
225
+ < img class ="fragment current-visible preload " src ="./img/poc_ml1.png ">
226
+ < img class ="fragment current-visible " src ="./img/poc_ml2.png ">
227
+ < img class ="fragment current-visible " src ="./img/poc_ml3.png ">
228
+ < img class ="fragment current-visible " src ="./img/poc_ml4.png ">
229
+ </ div >
219
230
< aside class ="notes ">
231
+ @SDG
220
232
Two weeks later.
221
233
It's Monday morning, 9am.
222
234
You have worked hard to clean up the POC. It's a bit better but...
223
235
</ aside >
224
236
</ section >
225
237
< section >
226
- < img src ="./img/poc_dev.jpg "/>
238
+ < div >
239
+ < img class ="fragment current-visible preload " src ="./img/poc_dev1.png ">
240
+ < img class ="fragment current-visible " src ="./img/poc_dev2.png ">
241
+ < img class ="fragment current-visible " src ="./img/poc_dev3.png ">
242
+ < img class ="fragment current-visible " src ="./img/poc_dev4.png ">
243
+ </ div >
227
244
< aside class ="notes ">
228
- It's Monday morning, 10am.
229
- Your coworker is trying to explain what you need to change so that she can bring your POC into production.
245
+ @SBI
246
+ Ok, If I well undstd POC => PROD
247
+ So we need to:
248
+ - remove Jup Nb
249
+ - structure a python module
250
+ - add tests
251
+ - create a CI
252
+ - [Most of all] REMOVE DATA
253
+ => long time we know how to structure CODE PRJ => tests auto and quality checks
254
+ and GIT perfect for versioning
255
+
256
+ @SDG=> Yes, but you reached a point here! It is not just a CODE PRJ
230
257
</ aside >
231
258
</ section >
232
259
</ section >
@@ -236,6 +263,7 @@ <h3>POC vs PROD</h3>
236
263
< h4 class ="fragment fade-up "> vs Data Scientist </ h4 >
237
264
< h4 class ="fragment fade-up "> vs Software Engineer </ h4 >
238
265
< aside class ="notes ">
266
+ @SDG
239
267
This is the story of
240
268
</ aside >
241
269
</ section >
0 commit comments