Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[412.38 --> 417.12] It is more focusing on what do you really want to achieve.
[417.64 --> 420.94] And focus on changing these things.
[420.94 --> 425.74] And that's also why he said, don't use a scaled HL framework.
[425.74 --> 432.76] Because there you focus on the process and on changing terminology.
[433.16 --> 437.20] It is more shifting to what do you really want to achieve.
[437.62 --> 439.72] Identify really what you want.
[439.98 --> 441.84] And then changing these things.
[441.84 --> 447.04] Not having that huge IT transformation that many people are doing.
[447.04 --> 451.40] So really focusing on what really matters for you.
[451.40 --> 452.96] I think I seem to remember.
[453.36 --> 453.68] Well, no.
[453.98 --> 459.00] I remember that in the Agile Manifesto, as we initially captured, one of the core principles
[459.00 --> 461.18] were people over processes.
[461.80 --> 462.14] Exactly.
[462.46 --> 462.70] Okay.
[462.80 --> 463.72] So that's what this is.
[463.78 --> 463.98] Okay.
[464.10 --> 464.80] That makes sense.
[465.62 --> 467.60] So that was an interesting one.
[467.78 --> 472.42] Now, I know that all the talks are available online as videos to catch up on demand.
[472.60 --> 474.48] Again, I'll add a link in the show notes.
[474.48 --> 475.90] I've also seen the pictures.
[476.10 --> 481.08] So if you want to see how this meetup was, you can go and look at those pictures.
[481.42 --> 483.72] I'm wondering, this is a yearly thing, right?
[483.78 --> 485.32] So next year, it's going to happen again.
[485.52 --> 485.70] Yeah.
[485.78 --> 487.48] Also in person, I'm imagining.
[487.86 --> 488.28] Exactly.
[488.40 --> 488.76] Exactly.
[489.00 --> 493.80] I think the next one will be on the 31st of May.
[494.48 --> 497.08] And we will do it again in person.
[497.50 --> 502.92] And it will be again in Zurich or in Winterthur, as we call it.
[502.92 --> 505.24] And in the same building.
[505.62 --> 505.76] Okay.
[505.98 --> 509.18] When do you open Call for Papers?
[509.30 --> 511.54] When can people start submitting their talk proposals?
[512.58 --> 513.84] Very good question.
[513.98 --> 514.70] We don't know yet.
[514.74 --> 521.52] We are currently closing off all of the stuff which we need to do for the past conference.
[522.10 --> 529.54] But my opinion, I think it will be perhaps December or it will be January round where we
[529.54 --> 531.62] will open up the Call for Papers.
[531.62 --> 531.86] When they open up.
[532.10 --> 532.22] Yeah.
[532.22 --> 532.62] Okay.
[532.92 --> 540.54] Are there any specific topics that you'd like to see more of in the next DevOps Days conference?
[540.94 --> 541.62] What do you call it?
[541.66 --> 541.92] Conference?
[542.28 --> 542.52] Summit?
[542.80 --> 543.22] Conference.
[543.48 --> 543.76] Conference.
[543.78 --> 544.02] Conference.
[544.44 --> 544.64] Yeah.
[544.92 --> 545.30] Yeah.
[545.76 --> 547.20] Don't come with the Kubernetes.
[548.10 --> 548.58] Okay.
[549.10 --> 550.06] No Kubernetes.
[550.52 --> 550.68] No.
[551.06 --> 551.62] All good.
[551.74 --> 551.96] All good.
[552.62 --> 556.10] We have so many proposals on Kubernetes usually.
[556.10 --> 556.72] No.
[556.72 --> 556.74] No.
[556.92 --> 563.56] What I really liked about the past conference or what we are focusing on is diversity.
[563.56 --> 567.18] And not only diversity, women or men.
[567.18 --> 571.24] It's all about diversity also in different mindsets.
[571.24 --> 573.86] That's why we also have different talks.
[573.86 --> 576.90] And that's what I also like to see.
[577.70 --> 580.36] Big diversity on different topics.
[580.36 --> 582.36] We had talks on culture.
[582.36 --> 590.56] We had talks on, for example, the role of UX in DevOps, which is also quite a special topic,
[590.56 --> 593.24] but it's an important topic.
[593.24 --> 594.54] And that's my wish.
[594.70 --> 603.40] I have that diversity on topics and not only focusing, for example, on technology or only on the process.
[603.72 --> 606.70] It's more also on the people side.
[606.98 --> 607.42] I love that.
[607.56 --> 612.62] I mean, that really speaks to my heart because we keep forgetting it's human beings, fallible,
[613.00 --> 615.76] that get easily bored and they keep chasing shiny new things.
[616.18 --> 620.56] And granted, Kubernetes may not be the shiny new thing anymore, but then it's comfort, right?
[620.60 --> 621.56] People are comfortable with that.
[621.56 --> 625.06] So, yeah, there's a lot there.
[625.50 --> 631.08] Now, I know that you're into DevOps, like big time into DevOps, but I don't know why.
[631.38 --> 632.48] Why are you into DevOps?
[633.98 --> 635.12] Very good point.
[635.60 --> 639.74] When I started my career, I was a .NET developer.
[640.46 --> 643.32] And this was back in 2002.
[644.34 --> 650.04] And we were doing their development of application of rich client applications.
[650.04 --> 658.88] And one of the things also in the early times which struck me is how can I ensure the quality of what I'm doing?
[659.40 --> 665.78] And yeah, of course, you could do testing also there, but it was not so automated.
[665.78 --> 669.84] And I was always a little bit lazy and I wanted to automate things.
[669.84 --> 678.06] So, I went into this area where we were starting automating the tests and then also the deployment.
[678.24 --> 681.20] So, I went into continuous integration, continuous deployment.
[681.20 --> 685.28] And the applications were getting bigger and distributed.
[685.64 --> 687.64] I was becoming an architect.
[688.14 --> 693.34] And slowly, I moved into the direction of these continuous delivery pipelines.
[694.06 --> 708.76] And when the whole DevOps movement started, I jumped on that because this was really one of my hard topics where I wanted to create these pipelines to continuously deliver value to the customer.
[708.76 --> 721.68] So, my understanding is that you were passionate about how value gets delivered, which got you into DevOps, which seems to have made that almost like at the center of its activity.
[722.02 --> 727.90] How do you move this code from a repository into customer hands, wherever that may be?
[728.12 --> 732.14] And there's like a whole lot of automation because you can do it manually, but there is a better way.
[732.36 --> 733.32] And automating that.
[733.52 --> 734.22] Okay, interesting.