text
stringlengths
0
2.35k
[2095.16 --> 2095.54] Yes.
[2097.10 --> 2098.40] That's something that I love.
[2098.66 --> 2107.36] If I'm reading documentation that it's easy to open a pull request and to see a failure or inconsistence or something, I open the pull request.
[2107.50 --> 2112.30] I think it's such a valuable contribution and so easy most of the times.
[2112.86 --> 2118.48] I love these docs that they have the button edit and then you go direct to GitHub to create a pull request.
[2118.54 --> 2119.08] That's fantastic.
[2119.54 --> 2119.74] Yeah.
[2119.74 --> 2122.14] I feel like I get into a bit of a rabbit hole.
[2122.14 --> 2134.42] I had to stop myself editing documentation because it went from actually making it correct to actually just implying my personal stylistic choices when writing documentation and phrasing.
[2134.94 --> 2138.00] I like this adjective slightly better actually.
[2138.00 --> 2143.38] So I had to pull back to be like, okay, review for correctness, not for like, I want a comma here.
[2144.40 --> 2145.78] I think that's so hard.
[2146.26 --> 2152.02] And for me, as a known native speaker, sometimes I was like, I don't think this sentence is correct.
[2152.16 --> 2153.04] I think it's missing a comma.
[2153.14 --> 2154.06] I think it's missing an article.
[2154.42 --> 2156.66] And I was like, honestly, you don't know English so much.
[2157.28 --> 2160.72] I don't even know if you could do that in proper Portuguese, like a proper grammar.
[2160.72 --> 2162.16] But I think it's important.
[2162.54 --> 2170.02] My take is if I believe it's compromising their understanding, I'm going to probably suggest something.
[2170.52 --> 2170.64] Right.
[2171.06 --> 2178.20] And also sometimes when the comment is there for a long time, I just, I make the change and suggest someone is going to review that.
[2178.28 --> 2178.44] Is it?
[2178.84 --> 2184.90] I sometimes put into some AI if I don't understand something and I read two, three times and I keep staring at it.
[2184.90 --> 2187.16] I'm like, just explain that to me in other words.
[2187.36 --> 2188.00] And that helps.
[2188.74 --> 2189.26] Good AI.
[2190.22 --> 2191.86] It's like pinging somebody, but yeah.
[2192.54 --> 2198.92] But also make the changes just like you, because I think if I'm as a non-native don't understand this, there must be another non-native that gets lost there.
[2199.30 --> 2199.60] Yeah.
[2199.84 --> 2200.96] And clarity is important.
[2201.90 --> 2208.70] And let's say you're interviewing, whether you are the candidate or you are the interviewing person.
[2209.34 --> 2214.18] And part of the interview is reviewing a pull request from somebody from your team.
[2214.90 --> 2217.98] What tips do you have for somebody to do this well?
[2218.66 --> 2223.36] Actually, never been really on these shoes, neither side.
[2224.04 --> 2229.72] I've been asking, oh yeah, in one of your code bases, any of your code base, what you would change or something.
[2230.32 --> 2237.14] I think at the end of the day, a lot of the time we, to interview for culture fit, right?
[2237.22 --> 2239.62] And a person that's nice, it's good to work with.
[2240.34 --> 2241.26] This is super important.
[2241.26 --> 2247.98] So I think it's, if you're on an interview, just be sure to be nice, right?
[2248.04 --> 2251.28] In your comments and everything, don't go like, oh yeah, this is crap.
[2251.38 --> 2252.10] This is bad.
[2252.36 --> 2253.48] Just be nice.
[2253.58 --> 2254.18] Be polite.
[2254.92 --> 2255.98] Link the commentations.
[2256.28 --> 2260.10] And I advise you to bring arguments, right?
[2260.10 --> 2264.60] Don't say, okay, do that or change that or this need change without a reason, right?
[2264.60 --> 2268.48] If an interview, usually an interview don't have so much time, right?
[2268.56 --> 2273.14] So I would go for, oh yeah, you know, this name is not ideal.
[2273.62 --> 2279.38] You know, the goal, effective goal, there is a section on name convention that explain why it should be like that.
[2279.52 --> 2282.38] So as it's in goal, it's better to be like that.
[2282.68 --> 2286.94] So try always to, to bring something to support your views.
[2286.94 --> 2293.08] And when it's opinion, and that's something that I really do on pre-request, when it's like, it's my opinion, I say like, look, this is my opinion.
[2293.20 --> 2298.74] I believe that's better because this, this, and this is up to you because I don't see a flaw here.
[2299.00 --> 2301.70] I just think it can be better about any opinion.
[2302.56 --> 2311.52] If you were interviewing someone and their task was to review a PR, what would be things that they did that would maybe be like, oh no, I don't know about that?
[2311.52 --> 2315.00] I think it would be to be aggressive, right?
[2315.10 --> 2320.88] And impolite to just diminishing the code and say like the code is bad or something.
[2321.60 --> 2326.48] In interviews, they really, they show that they know, don't know what they're doing.
[2326.90 --> 2333.24] I think if you interview people, you know, some people, they don't know what they're doing or just trying to fool you.
[2333.62 --> 2333.98] Right?
[2334.04 --> 2336.02] If it's hard to see that it's like, oh, no, no.
[2336.42 --> 2337.74] It's better to say you don't know.
[2337.92 --> 2338.74] It's not like that.
[2338.78 --> 2339.30] It's like, great.
[2339.30 --> 2339.86] Just go.
[2339.96 --> 2341.44] And you know, I just, okay.
[2341.52 --> 2341.76] Yeah.
[2342.04 --> 2342.38] Mm-hmm.
[2342.52 --> 2343.76] It's just an incentivize.
[2343.84 --> 2344.20] Yeah, go.
[2344.44 --> 2344.92] Go, please.
[2345.62 --> 2347.18] And then, oh yeah, thank you very much.
[2347.20 --> 2348.04] You're going to be in contact.
[2349.36 --> 2349.72] Yeah.
[2349.86 --> 2352.88] And definitely staying honest is a lot better than making things up.
[2353.30 --> 2353.50] Yeah.
[2353.54 --> 2354.42] Please say, I don't know.
[2354.46 --> 2357.34] I think if someone to me in an interview say, look, I don't know.
[2357.38 --> 2358.00] I don't remember.
[2358.50 --> 2359.52] Oh, I don't know.
[2359.58 --> 2361.72] And I think in that place I can get information.
[2362.14 --> 2365.30] Dude, folk, you're like scoring a hundred points with me.
[2365.54 --> 2368.58] If you're trying to just BS me through.
[2369.06 --> 2369.18] Nah.
[2369.60 --> 2370.04] That's fair.
[2370.04 --> 2371.94] Anderson will not be having that.
[2371.94 --> 2401.92] this episode is brought to you by our friends at chronosphere scaling cloud native is complicated
[2401.92 --> 2407.20] and chronosphere helps teams take back control of observability team rampant data growth reduce
[2407.20 --> 2412.08] cloud native complexity and increase confidence of the business and i'm here with martin mal co-founder
[2412.08 --> 2416.96] and ceo of chronosphere martin when it comes to cloud native observability what are the pain points
[2416.96 --> 2422.06] of kubernetes and making sure it's reliable you know i think the shift to kubernetes has really
[2422.06 --> 2428.60] changed the way we design applications it's changed the way we it's changed our infrastructure as well
[2428.60 --> 2432.56] so it's introduced a lot of change i would say and that's probably why it's causing a lot of
[2432.56 --> 2438.76] issues in the observability space i think one thing we're finding is that a lot of companies out there
[2438.76 --> 2445.12] are focused on producing a lot more data and there's a lot of focus on more metrics more traces more logs
[2445.12 --> 2450.00] because these environments we're trying to monitor are far more complex these days i think that's
[2450.00 --> 2454.68] maybe one of the mistakes the industry is running into and it's interesting because obviously for
[2454.68 --> 2459.20] all the solutions out there the vendors out there the more data that gets produced the better it is
[2459.20 --> 2464.94] for all the vendors out there but what's interesting is that along with that increased volume of data
[2464.94 --> 2470.38] people aren't actually getting better outcomes out of it people's number of incidents that people are