text stringlengths 0 1.8k |
|---|
[238.68 --> 241.18] So did you play much in the last three, four years? |
[241.40 --> 242.18] Not at all. |
[242.30 --> 242.82] Not at all. |
[242.94 --> 244.52] I mean, it was entirely a Pivotal thing. |
[244.62 --> 246.60] It was like part of, built into the Pivotal culture. |
[246.78 --> 250.72] You know, you're pair programming and you need a quick 15 minute break where you get |
[250.72 --> 255.80] up and you jump around and there's table tennis tables right there and you're playing doubles. |
[255.94 --> 256.76] So you're a pair. |
[256.98 --> 258.72] You find another pair that also needs a break. |
[258.78 --> 261.34] I mean, everything about it was just built around Pivotal. |
[261.60 --> 261.80] Yeah. |
[261.90 --> 262.70] I really miss that. |
[262.70 --> 267.24] Like from the whole office culture, which seems to be slowly disappearing when it comes |
[267.24 --> 268.26] to remote work. |
[268.26 --> 273.66] And, you know, this is like the new norm and we're in it for the long drive, shall I say. |
[273.66 --> 278.98] I really miss that table tennis, that social aspect, that, I mean, pairing is great. |
[279.06 --> 279.80] You can do it remotely. |
[279.80 --> 282.36] But what you can't do remotely is play table tennis. |
[282.36 --> 283.10] It's true. |
[283.20 --> 287.44] I mean, I've always been very passionately 100% remote. |
[287.54 --> 291.12] Our company has always been 100% remote, even before the apocalypse. |
[291.50 --> 295.04] And that made the apocalypse a little bit easier for us to weather as a company. |
[295.04 --> 299.92] But I do miss that camaraderie of going out to lunch together, that camaraderie of playing |
[299.92 --> 301.48] a game of table tennis together. |
[302.00 --> 307.20] And obviously there's a tax to being remote when it comes to communication, right? |
[307.38 --> 310.54] Communication is just more fluid when you're sitting right there. |
[310.96 --> 313.82] At the same time, there's always benefits one side or the other. |
[314.26 --> 321.46] And I think the benefits of being able to find amazing talent who's uninterested in moving |
[321.46 --> 327.20] to some central location and the benefit of everyone in the company being on equal footing. |
[327.66 --> 331.92] You know, the companies that do remote where there's a mothership and small offices, the |
[331.92 --> 335.76] small offices always feel like their growth is going to be stunted. |
[335.76 --> 340.36] And it is because they're not close to leadership and close to where the decisions are made. |
[340.74 --> 346.54] And even more important, and this is, I think this is more of a, about American culture and |
[346.54 --> 351.44] what's been happening to American culture over the past, I don't know, 20, 30, 40 years. |
[352.10 --> 357.72] As people congregate more into the cities, we are getting a very strong cultural divide. |
[357.80 --> 361.20] It's probably happening in other places too, but for us, it's incredibly strong between |
[361.20 --> 363.90] the cities and the countryside, right? |
[364.62 --> 371.94] And I feel like the more fully remote various companies move towards, the better it's going |
[371.94 --> 377.68] to be for society because you get people from different backgrounds all working together |
[377.68 --> 379.56] and you start to flatten out the cities. |
[379.56 --> 383.98] I think cities are not a great thing from a cultural point of view, right? |
[384.36 --> 388.16] They're a huge strain on infrastructure and it would just be much better if we could just |
[388.16 --> 392.40] flatten them a bit and have the small towns grow a bit bigger in the countrysides. |
[392.56 --> 394.22] And I think fully remote allows that. |
[394.52 --> 395.44] Yeah, I can see that. |
[395.52 --> 399.24] And I do have to say, having left a big city not that long ago, I mean, I'm still around |
[399.24 --> 399.38] it. |
[399.42 --> 402.26] I'm still around London, but I'm not living in London anymore. |
[402.26 --> 408.00] And I do appreciate the advantages to that, but I can also see some of the trade-offs. |
[408.16 --> 409.98] So there's always some trade-offs. |
[410.26 --> 411.46] We miss the really good dinners. |
[412.14 --> 412.54] Yeah. |
[412.94 --> 413.90] And the table tennis. |
[414.30 --> 415.40] And the table tennis, yeah. |
[415.86 --> 416.14] Okay. |
[416.58 --> 421.38] Now, one other topic that I know that you're really passionate about besides dinners and |
[421.38 --> 422.64] table tennis is Kubernetes. |
[423.06 --> 423.78] It's true. |
[423.86 --> 424.32] It's true. |
[424.80 --> 425.40] Same here. |
[425.50 --> 425.88] Same here. |
[425.94 --> 426.44] Big fans. |
[426.44 --> 433.36] So I know that you're seeing so many things around Kubernetes, so many social interactions, |
[433.92 --> 436.86] so many teams interacting with Kubernetes. |
[437.58 --> 437.70] Yeah. |
[437.90 --> 444.70] And I see companies these days, they no longer say, oh, Kubernetes is interesting. |
[444.94 --> 445.88] Maybe I should try it out. |
[445.98 --> 447.68] They need Kubernetes. |
[448.26 --> 453.42] And that's a very interesting mind shift which happened, I think, in the last maybe year, |
[453.50 --> 453.94] two years. |
[453.94 --> 460.16] So a company, when they start with Kubernetes, what problems do you see them having? |
[460.44 --> 461.36] Yeah, that's a great question. |
[461.70 --> 463.26] And just to put a little bit of context in it. |
[463.54 --> 466.48] So at Super Orbital, we have kind of two lines of business. |
[466.72 --> 470.36] One of the lines of business is, the biggest one is our engineering services. |
[470.52 --> 474.10] We help companies out with very difficult Kubernetes-related problems. |
[474.30 --> 480.70] We have a very small team of very senior, seasoned engineers with a lot of judgment. |
[480.70 --> 487.38] And when one of our clients has a very unusual and challenging problem with Kubernetes, like |
[487.38 --> 492.76] going on-premise via Kubernetes or doing some very deep security stuff with Kubernetes. |
[492.92 --> 495.40] That's when they bring us on board for short-term engagements, whatever. |
[495.54 --> 495.96] We help out. |
[496.26 --> 501.74] We also have a smaller part of our business, which is producing workshops and training. |
[501.74 --> 506.78] And the reason that I bring this up is because when we are doing our workshops, that's when |
[506.78 --> 512.38] we engage more with companies who are just starting to embrace Kubernetes, right? |
[512.46 --> 520.68] So we don't help those customers on the engineering front as often, but more likely, we get to train |
[520.68 --> 525.18] them and show them how complex Kubernetes is. |
[525.46 --> 527.42] That's the key problem with Kubernetes. |
[527.42 --> 533.32] I mean, everybody who's used it knows it, but the complexity is huge. |
[533.62 --> 541.52] I mean, there's something like 80 different resource types that the Kubernetes API understands |
[541.52 --> 542.28] the last time I looked. |
[542.50 --> 549.94] And each one of those can have dozens or hundreds of attributes that you have to, to some degree, |
[550.06 --> 550.66] understand. |
[550.66 --> 557.64] And especially as you're doing production workloads in Kubernetes, the defaults are not always |
[557.64 --> 559.06] in your favor, right? |
[559.14 --> 564.22] So things like affinity rules and stuff, which this stuff is improving, but affinity rules, |
[564.64 --> 569.86] security, all that stuff is things that are kind of left as an exercise to the reader with |
[569.86 --> 570.20] Kubernetes. |
[570.58 --> 572.54] And so the complexity is just enormous. |
[573.04 --> 577.86] And new releases, they used to happen quarterly and now literally slowed it down because quarterly |
[577.86 --> 578.56] was too fast. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.