Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[214.76 --> 216.00] I'm at the GopherCon UK.
[216.00 --> 218.66] So I'm a Brazilian that's based in Berlin.
[219.16 --> 222.62] But now I'm here in London, directly from an hotel room.
[222.82 --> 223.76] How are you liking it?
[224.22 --> 224.98] Oh, it's really good.
[225.20 --> 225.42] Yeah.
[225.80 --> 227.66] And you're not just saying that because I'm on the call.
[228.36 --> 228.88] No, no.
[229.10 --> 229.62] Okay, good.
[229.74 --> 230.48] I love the UK.
[230.80 --> 233.48] I did an exchange program here for one year and a half in Glasgow.
[233.72 --> 234.12] Oh, awesome.
[234.22 --> 234.86] So, yeah.
[235.28 --> 235.84] I really like it.
[236.18 --> 238.12] I mean, I prefer Edinburgh to Glasgow.
[238.64 --> 239.44] Unpopular opinion.
[239.68 --> 240.46] Yeah, true.
[240.70 --> 242.26] I mean, Edinburgh Castle is so incredible.
[242.40 --> 243.86] Wait, no, that's the end of the show.
[244.26 --> 244.80] Oh, I'm sorry.
[244.86 --> 246.06] Getting ahead of myself, Natalie.
[246.14 --> 246.48] I'm sorry.
[246.58 --> 246.96] I'm sorry.
[249.46 --> 251.82] It's fun to go back to in-person conferences, huh?
[252.52 --> 253.54] Yeah, that's true.
[253.60 --> 254.40] It's really, really good.
[254.76 --> 257.18] Last time that I was here in London, my brother was here.
[257.18 --> 262.12] We were like, okay, the place here is going to be small to go for call UK at some point,
[262.32 --> 264.76] but then the pandemic, and now I think it's smaller.
[265.40 --> 266.10] So, yeah, let's see.
[267.26 --> 267.70] Okay.
[268.18 --> 270.16] So, Anderson, tell us about yourself.
[270.24 --> 270.88] You're doing Go.
[271.50 --> 276.20] Yeah, I'm doing Go since a bit before going to Berlin.
[276.44 --> 278.66] So, I think about five years now.
[279.20 --> 282.34] I did before many Java was a lot of Java.
[282.34 --> 289.02] I started with C, actually, some Python, JavaScript in the back end, and now Go.
[289.08 --> 289.56] I love it.
[289.68 --> 292.06] And then it chooses my language to specialize.
[292.74 --> 294.26] And you're working at Elastic.
[294.70 --> 295.04] Exactly.
[295.58 --> 296.96] I work with the Elastic agent.
[297.32 --> 301.80] Which is the head product for all the products that we know and love, like Elasticsearch.
[302.18 --> 302.82] Yeah, exactly.
[303.20 --> 303.38] Yeah.
[303.86 --> 305.64] Formerly known as the ilk stack.
[306.32 --> 306.62] Yeah.
[306.94 --> 308.12] Now the Elastic stack.
[308.26 --> 308.40] Yeah.
[308.78 --> 309.50] Lots of go there.
[309.50 --> 311.50] I love this stack.
[312.34 --> 313.02] Fun.
[313.38 --> 315.96] And so, as part of the jobs, you do pull requests.
[316.46 --> 316.86] Of course.
[317.22 --> 319.00] Do you also do merge requests?
[319.64 --> 321.06] We call everything pull requests.
[321.94 --> 322.34] Yeah.
[322.52 --> 325.22] Are you going to do the same thing you did last time, where you caught us all off guard,
[325.34 --> 326.40] with the many different...
[326.40 --> 327.08] Just for those.
[327.34 --> 329.94] The many different ways to refer to it.
[330.06 --> 333.40] It's crazy how many ways there, how many names are there for this.
[333.54 --> 333.70] Yeah.
[334.00 --> 336.92] For those who are listening now and have not listened to the previous episode,
[336.92 --> 340.84] to the art of pull requests part one, Angelica and I were discussing,
[340.84 --> 345.72] among other things, also the many different names and what concepts that represents.
[346.36 --> 350.46] So, Anderson, we asked you if you're doing lots of pull requests, but then we started talking about other things.
[350.88 --> 351.34] Yeah.
[351.52 --> 351.78] Do you?
[352.12 --> 352.66] I do.
[353.24 --> 355.70] Do you review more or do you write more?
[355.70 --> 357.14] Now, I write more.
[357.28 --> 359.92] My past job, I read a lot more code.
[360.52 --> 361.84] A lot pull requests.
[362.58 --> 365.76] And funnily enough, I've never worked in a company that didn't have pull requests.
[365.86 --> 371.04] To me, software development as a professional means pull requests and code review.
[371.86 --> 372.80] That's my standard.
[373.40 --> 376.74] Why did you do more reading in your past job?
[376.80 --> 378.78] Is it just a very different area you were working in?
[378.78 --> 379.18] No.
[379.40 --> 385.42] My past company, I joined, among other things, to help to lead the transition to Go.
[385.56 --> 385.88] Right.
[385.98 --> 390.12] So, they were pretty much a ruby shop and they decided to migrate to Go.
[390.56 --> 395.40] They were migrating, but they needed someone with expertise in Go, you know, to bring back
[395.40 --> 396.54] practice, how to do.
[396.54 --> 403.20] So, as that, I did a lot of workshops and, you know, kind of teaching mentoring and involved
[403.20 --> 406.20] a lot of the teams would come to me with pull requests.
[406.78 --> 412.22] So, I do like do like a really extensive review, not only code practice functionality, but also
[412.22 --> 417.30] as an opportunity to teach Go and the standards, the conventions, the best practices.
[418.10 --> 420.36] And then now you've moved to somewhere where Go is bigger.
[420.58 --> 423.50] So, therefore, you don't have to play such a big kind of reviewer role.
[423.70 --> 424.04] Exactly.
[424.04 --> 428.78] And now I am as a soft engineer, right, as a senior, but there I was like a tech lead.
[429.40 --> 433.82] Yeah, I think when you go above senior and in tech lead and stuff, you start coding less,
[433.92 --> 435.58] reading more, writing more, right?
[435.78 --> 436.16] Okay.
[436.64 --> 439.36] I mean, writing more specifications and documentations.
[440.04 --> 446.88] So, do you feel like there's a direct correlation between seniority and how much reading of PR
[446.88 --> 449.04] versus writing you do?
[449.04 --> 454.86] Like if we were to plot it on a graph, how much you read PRs, how much you write, could