Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[1341.74 --> 1341.98] Yeah.
[1342.14 --> 1344.52] He was asking everyone to have Go 18 because of that.
[1344.64 --> 1346.72] He was like, okay, you're going to use any, so please.
[1346.72 --> 1363.26] This episode is brought to you by our friends at FireHydrant.
[1363.68 --> 1366.32] FireHydrant is a reliability platform for every developer.
[1366.82 --> 1369.32] Incidents are a win, not an if situation.
[1369.78 --> 1373.80] And they impact everyone in the organization, not just SREs.
[1373.80 --> 1377.44] And I'm here with Robert Ross, founder and CEO of FireHydrant.
[1377.78 --> 1380.10] Robert, what is it about teams getting distracted by incidents
[1380.10 --> 1383.42] and not being able to focus on the core product that upsets you?
[1383.72 --> 1387.72] I think that incidents bring a lot of anxiety and sometimes fear
[1387.72 --> 1391.94] and maybe even a level of shame that can cause this paralysis
[1391.94 --> 1394.60] in an organization from progress.
[1395.18 --> 1398.10] And when you have the confidence to manage incidents
[1398.10 --> 1401.02] at any scale of any variety,
[1401.02 --> 1403.30] everyone just has this breath of fresh air
[1403.30 --> 1406.08] that they can go build the core product even more.
[1406.44 --> 1408.42] I don't know if anyone's had the opportunity,
[1408.72 --> 1410.98] maybe is the word, to call the fire department.
[1411.18 --> 1413.70] But no matter what, when the fire department shows up,
[1413.90 --> 1416.84] it doesn't matter if the building is hugely on fire.
[1417.00 --> 1418.46] They are calm, cool, and collected
[1418.46 --> 1420.50] because they know exactly what they're going to do.
[1420.78 --> 1423.70] And that's what FireHydrant is built to help people achieve.
[1424.18 --> 1424.48] Very cool.
[1424.56 --> 1425.10] Thank you, Robert.
[1425.10 --> 1429.48] If you want to operate as a calm, cool, collected team
[1429.48 --> 1431.86] when incidents happen, you got to check out FireHydrant.
[1432.18 --> 1434.82] Small teams, up to 10 people can get started for free
[1434.82 --> 1437.78] with all the features, no credit card required to sign up.
[1438.08 --> 1439.76] Get started at firehydrant.com.
[1440.12 --> 1442.12] Again, firehydrant.com.
[1452.42 --> 1456.32] What do you do when you have a very large pull request?
[1456.68 --> 1458.96] Lots of files, lots of comments, lots of lines.
[1458.96 --> 1460.18] I sit and cry.
[1460.38 --> 1461.84] How do you get on top of that?
[1462.64 --> 1463.30] No, I...
[1463.96 --> 1464.78] That's a tough one.
[1465.42 --> 1467.42] I try to review at once.
[1468.14 --> 1469.36] Sometimes it's not possible.
[1470.68 --> 1472.90] I think there's no magic.
[1473.08 --> 1474.70] You just have to go through it, right?
[1475.12 --> 1477.28] Do you review everything on a high level?
[1477.42 --> 1479.16] Kind of, you know, see the list of the commits
[1479.16 --> 1481.62] if they tell some story or maybe look at the list of the files?
[1481.76 --> 1483.24] Or do you just dive to the first one
[1483.24 --> 1486.02] and one by one until it starts making sense?
[1486.02 --> 1487.98] I never look at the commits.
[1488.16 --> 1491.74] I don't know if because when I'm coding and committing,
[1491.94 --> 1493.76] I'm going to squash everything before morning.
[1493.94 --> 1494.52] Like, first things first.
[1494.62 --> 1497.30] So to me, the commits itself, they don't matter so much.
[1497.38 --> 1500.62] I try to put in a way if I need to revert something, right?
[1500.70 --> 1501.24] I do.
[1501.50 --> 1503.46] But at the end of the day, there's a good chance
[1503.46 --> 1505.04] that I'm going to just do one commit.
[1505.04 --> 1506.72] So I never look at the...
[1506.72 --> 1508.64] Neither the rep commit history,
[1508.82 --> 1511.02] only if I need to understand why it happened.
[1511.52 --> 1513.72] But in a pull request, I never look at the commit history.
[1513.90 --> 1514.78] Just look at the diff.
[1515.36 --> 1516.76] And it's always on GitHub.
[1517.22 --> 1519.54] And look at the files by the name, basically.
[1519.82 --> 1521.64] The big ones are just, you know, go clicking.
[1521.74 --> 1522.46] I've seen this file.
[1522.60 --> 1523.24] I've seen this file.
[1524.18 --> 1526.22] So just by the order of appearance.
[1526.22 --> 1529.92] Because sometimes it's not always the correct flow, kind of.
[1529.92 --> 1530.36] Yeah.
[1530.86 --> 1533.56] If it's hard to understand, I get the code.
[1533.68 --> 1536.32] I check out the feature branch.
[1537.00 --> 1537.76] And I go to see.
[1537.92 --> 1541.50] Because also sometimes you'll see, you know,
[1541.54 --> 1543.12] there are more stuff going on.
[1543.20 --> 1543.84] You want to jump.
[1543.98 --> 1546.34] You want to understand how it was called or something.
[1546.66 --> 1549.56] And then it's easier on an IDE when you have the code.
[1550.06 --> 1552.24] And also if you want to suggest a change.
[1553.02 --> 1555.12] So either it's something really simple.
[1555.20 --> 1556.56] I'm 100% sure that it works.
[1556.56 --> 1560.38] Or I'm going to probably write it in the code itself.
[1560.52 --> 1561.50] And it might test it.
[1561.62 --> 1562.02] Right.
[1562.10 --> 1564.28] To not suggest something that it's broken.
[1564.88 --> 1566.36] Maybe even a few steps, Mac.
[1566.48 --> 1569.40] When you go to read the review of pull request.
[1569.48 --> 1570.88] Do you start by reading the issue?
[1571.42 --> 1573.18] So the first thing you do is read the issue.
[1573.60 --> 1573.80] Yeah.
[1573.96 --> 1575.48] I have to understand what's happened there.
[1575.88 --> 1581.00] Then do you review it, the diff, you know, on GitHub or in your IDE?
[1581.72 --> 1582.30] No, on GitHub.
[1583.08 --> 1585.32] So you go kind of file by file on GitHub.
[1585.32 --> 1586.06] I never.
[1587.34 --> 1588.20] No, you know, because.
[1588.62 --> 1589.40] Philosophical questions.
[1589.80 --> 1590.22] Good point.
[1590.54 --> 1592.64] Because to me, the review.
[1593.38 --> 1595.32] Actually, going back to the other episode.
[1595.66 --> 1596.64] We are doing code review.