text stringlengths 0 1.8k |
|---|
[2035.02 --> 2035.54] It's still modern. |
[2035.54 --> 2038.40] So I'm wondering what that would have looked like with this technology. |
[2038.52 --> 2040.44] But obviously, you need to know your technology. |
[2040.62 --> 2042.06] You need to know what suits you. |
[2042.20 --> 2043.34] And you need to own it. |
[2043.60 --> 2047.70] So whatever you decide to use, you need to be confident that I will make this work. |
[2047.86 --> 2049.62] And if it doesn't work, I will course correct. |
[2050.08 --> 2051.38] Because, hey, I was wrong. |
[2051.50 --> 2052.38] And that's perfectly fine. |
[2052.46 --> 2059.90] Saying I was wrong, I think a lot of people are so afraid of saying they were wrong that they never admit that in the first place. |
[2060.18 --> 2061.72] And as a result, they can never course correct. |
[2062.14 --> 2063.18] And then they hit the iceberg. |
[2063.38 --> 2064.78] And then we know what happens next. |
[2064.78 --> 2065.38] Right? |
[2065.92 --> 2066.18] Yeah. |
[2066.30 --> 2066.54] Okay. |
[2066.94 --> 2072.16] And one of the important thing is you should not be afraid of the sunk cost. |
[2072.30 --> 2074.82] Because that's always a bad thing. |
[2074.90 --> 2078.78] And you always hear that term quite a lot. |
[2078.86 --> 2078.96] Yeah. |
[2079.04 --> 2080.60] But then we have sunk cost. |
[2081.36 --> 2081.50] Yeah. |
[2081.50 --> 2083.40] Of course, you have sunk cost. |
[2083.40 --> 2091.00] But throwing more money after a bad idea or a bad solution is also a very, very bad thing. |
[2091.20 --> 2091.36] Yeah. |
[2091.42 --> 2092.74] It's not going to make it better, right? |
[2092.74 --> 2094.66] Like, the focus is on learning. |
[2095.14 --> 2098.14] The focus is not on the time spent to learn. |
[2098.44 --> 2099.12] What did you learn? |
[2099.20 --> 2100.04] Is this a good thing? |
[2100.22 --> 2101.60] And can you build on top of that? |
[2101.98 --> 2105.16] So if you switch your mindset and you think, well, that's okay. |
[2105.26 --> 2106.56] We know not to do that again. |
[2106.56 --> 2110.08] And we know that that's like an area that we're not comfortable with. |
[2110.24 --> 2112.68] And the longer you delay it, the worse it gets. |
[2113.10 --> 2114.04] We all know that, right? |
[2114.34 --> 2116.72] Like, just stop thinking about things like that. |
[2117.10 --> 2117.26] Okay. |
[2117.26 --> 2124.22] Now, talking about technology, I'm wondering what role does specific technology play in |
[2124.22 --> 2124.78] these decisions? |
[2125.22 --> 2129.82] So I know that many teams get excited about something like Kubernetes or they get excited |
[2129.82 --> 2131.20] about, you mentioned Angular. |
[2131.48 --> 2134.92] I'm not sure who gets excited about Angular these days, but I'm sure there are people out |
[2134.92 --> 2138.68] there which love it or some other, you know, JavaScript framework. |
[2138.68 --> 2140.28] And they say, no, we have to use this. |
[2140.62 --> 2143.86] How do you deal with those types of scenarios? |
[2143.94 --> 2146.64] Well, first of all, have you been in those types of scenarios? |
[2146.64 --> 2149.10] And if you have, how did you deal with them successfully? |
[2149.38 --> 2153.62] I have been in these types of scenarios quite a lot. |
[2153.82 --> 2155.04] The thing is the following. |
[2155.38 --> 2162.16] It's what you need to do is you need to understand what the real need is, what you need to do. |
[2162.80 --> 2166.16] So getting excited about the technology is a great thing. |
[2166.62 --> 2173.32] Trying out this technology is also a great thing, but you should not do that in a huge |
[2173.32 --> 2173.90] project. |
[2174.34 --> 2176.22] So trying out things. |
[2176.64 --> 2184.40] So what I usually do is I really want to understand what exactly our need is and what |
[2184.40 --> 2186.66] problem we are trying to solve. |
[2186.78 --> 2191.06] So what is the underlying problem we are trying to solve with this technology? |
[2191.06 --> 2196.32] And there is technology out there which perfectly fits the problem. |
[2196.52 --> 2204.72] But just looking at the technology and not knowing what problems we are trying to solve is a very |
[2204.72 --> 2205.50] bad thing. |
[2205.96 --> 2212.58] So what I do is when we have such a case, I really try to identify what the problem is. |
[2212.58 --> 2217.90] And of course, you then have different technology or different decisions you can do. |
[2218.34 --> 2228.94] And what I then do is I do sort of an analysis of the different possibilities where I say, OK, |
[2229.14 --> 2230.62] this is technology. |
[2230.62 --> 2231.62] technology, why? |
[2231.62 --> 2234.22] And this has these advantages. |
[2234.22 --> 2236.86] It solves us these problems. |
[2236.86 --> 2240.64] But it also could potentially introduce these problems. |
[2240.64 --> 2244.14] And this is the other technology which we are having. |
[2244.14 --> 2251.02] And then you have something which you can compare and which you also can say, OK, should we go |
[2251.02 --> 2254.80] into this direction or should we go in more in this direction? |
[2254.80 --> 2264.16] And after that, I usually also do some prototypes on these technologies to get my hands dirty on that so |
[2264.16 --> 2267.92] that I can see, does it really work or does it not work? |
[2268.48 --> 2271.06] Who decides which technology should be used? |
[2271.12 --> 2276.22] Do you let the developers decide the ones doing the work or do you let the architects decide or the |
[2276.22 --> 2276.56] management? |
[2276.92 --> 2277.68] How does that look like? |
[2277.80 --> 2282.64] In my opinion, it should always be a decision of the team. |
[2282.64 --> 2289.76] The team which needs to work with this technology, they need to take the decision. |
[2290.40 --> 2297.62] Because if someone else takes the decision, the team does not stand behind this decision. |
[2297.86 --> 2306.36] So that's why I usually want that the team takes the decision and also does the analysis and |
[2306.36 --> 2306.94] everything. |
[2306.94 --> 2313.90] And so they sort of need to come up with the idea and also with the decision. |
[2314.26 --> 2318.40] Of course, there are companies out there where this is not really possible. |
[2319.32 --> 2322.16] And then I also try to do that. |
[2322.42 --> 2328.98] But then I try to convince, for example, the central architecture or the management about |
[2328.98 --> 2331.24] this solution which we should do. |
[2336.94 --> 2342.90] Hey, shippers. |
[2343.06 --> 2346.42] This episode is brought to you by our friends at Equinix Metal. |
[2346.72 --> 2351.02] If you want the choice and control of hardware with low overhead and the developer experience |
[2351.02 --> 2353.32] of the cloud, check out Equinix Metal. |
[2353.72 --> 2357.78] Deploying minutes across 18 global locations from Silicon Valley to Sydney. |
[2358.22 --> 2363.16] Visit metal.equinix.com slash just add metal and receive $100 in credit to play with. |
[2363.16 --> 2367.12] Again, metal.equinix.com slash just add metal. |
[2367.34 --> 2369.84] And by our friends at FireHydrant. |
[2369.98 --> 2372.88] FireHydrant is the reliability platform for teams of all sizes. |
[2373.40 --> 2378.62] With FireHydrant, teams achieve reliability at scale by enabling speed and consistency from |
[2378.62 --> 2381.08] a service deployment to an unexpected outage. |
[2381.42 --> 2381.86] Here's the thing. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.