text stringlengths 0 2.46k |
|---|
[1865.84 --> 1867.90] I want to make sure that I have as few bugs as possible. |
[1868.24 --> 1871.64] I want to make sure that I've thought of all the errors and all the edge cases and whatnot. |
[1872.18 --> 1874.24] And Sentry is the flip side of that. |
[1874.48 --> 1877.20] It says, hey, what happens when you hit production, right? |
[1877.22 --> 1880.86] When you have a bug and you need to understand what's happening in that bug, you need to understand |
[1880.86 --> 1881.80] the context around it. |
[1881.80 --> 1885.06] You need to understand where it's happening, what the stack trace looks like, what other |
[1885.06 --> 1888.82] local variables exist at that time so that you can debug that. |
[1889.18 --> 1891.50] And hopefully you don't see that error case again. |
[1891.76 --> 1896.18] When I think of like, oh, what can Sentry do with CodeCov or what can CodeCov do for Sentry? |
[1896.60 --> 1900.86] It's sort of taking that entire spectrum of the developer lifecycle of, hey, what can we |
[1900.86 --> 1905.26] do to make sure that you ship the least buggy code that you can? |
[1905.66 --> 1910.18] And when you do come to a bug that is unexpected, you can fix it as quickly as possible, right? |
[1910.18 --> 1913.24] Because, you know, as developers, we want to write good code. |
[1913.36 --> 1916.34] We want to make sure that people can use the code that we've written. |
[1916.66 --> 1919.50] We want to make sure that they're happy with the product, they're happy with the software, |
[1919.50 --> 1921.16] and it works the way that we expect it to. |
[1921.52 --> 1926.58] If we can build a product, you know, the Sentry plus CodeCov thing to make sure that you are |
[1926.58 --> 1932.72] de-risking your code changes and de-risking your software, then, you know, we've hopefully |
[1932.72 --> 1935.16] done the developer community as service. |
[1935.16 --> 1938.66] So, Tom, you say bring your tests and you'll handle the rest. |
[1938.76 --> 1939.42] Break it down for me. |
[1939.48 --> 1942.90] How does a team get started with CodeCov? |
[1943.36 --> 1947.58] You know, what you bring to the table is like testing and you bring your coverage reports. |
[1948.00 --> 1951.88] And what CodeCov does is we say, hey, give us your coverage reports, give us access to |
[1951.88 --> 1956.40] your code base so that we can, you know, overlay code coverage on top of it and give us access |
[1956.40 --> 1957.16] to your CICD. |
[1957.16 --> 1963.24] And so with those things, what we do and what CodeCov is really powerful at is that it's |
[1963.24 --> 1965.28] not just, hey, like this is your code coverage number. |
[1965.68 --> 1970.82] It's, hey, here's a code coverage number and your viewer also knows and other parts of your |
[1970.82 --> 1972.20] organization know as well. |
[1972.32 --> 1975.72] So it's not just you dealing with code coverage and saying, I don't really know what to do |
[1975.72 --> 1976.18] with this. |
[1976.46 --> 1980.88] Because we take your code coverage, we analyze it and we throw it back to you into your |
[1980.88 --> 1981.64] developer workflow. |
[1982.20 --> 1985.16] And by developer workflow, I mean your pull request, your merge request. |
[1985.16 --> 1989.58] And we give it to you as a comment so that you can see, oh, great, this was my code coverage |
[1989.58 --> 1989.96] change. |
[1990.34 --> 1993.94] But not only do you see this sort of information, but your viewer also sees it. |
[1994.06 --> 1997.00] And they can tell, oh, great, you've tested your code or you haven't tested your code. |
[1997.44 --> 2001.84] And we also give you a status check, which says, hey, like you've met whatever your team's |
[2001.84 --> 2005.66] decision on what your code coverage should be, or you haven't met that goal, whatever it |
[2005.66 --> 2006.26] happens to be. |
[2006.54 --> 2011.30] And so CodeCov is particularly powerful in making sure that code coverage is not just a thing |
[2011.30 --> 2015.12] that you're doing on your own island as a developer, but that your entire team |
[2015.12 --> 2017.28] can get involved with and can make decisions. |
[2017.90 --> 2018.10] Very cool. |
[2018.16 --> 2018.66] Thank you, Tom. |
[2018.80 --> 2022.04] So, hey, listeners, head to Sentry and check them out. |
[2022.18 --> 2025.76] Sentry.io and use our code changelog. |
[2026.10 --> 2031.82] So the cool thing is, is our listeners, you get the team plan for free for three months. |
[2032.10 --> 2035.38] Not one month, not two months, three months. |
[2035.38 --> 2035.86] Yes. |
[2035.86 --> 2036.10] Yes. |
[2036.42 --> 2038.10] The team plan for free for three months. |
[2038.32 --> 2039.38] Use the code changelog. |
[2039.46 --> 2042.22] Again, Sentry.io. |
[2042.48 --> 2045.90] That's S-E-N-T-R-Y.io. |
[2046.28 --> 2047.74] And use the code changelog. |
[2047.86 --> 2050.68] Also check out our friends over at CodeCov. |
[2050.80 --> 2053.02] That's CodeCov.io. |
[2053.36 --> 2055.96] Like code coverage, but just shortened to CodeCov. |
[2056.44 --> 2057.60] CodeCov.io. |
[2057.60 --> 2058.56] Enjoy. |
[2058.56 --> 2058.72] Enjoy. |
[2058.72 --> 2058.78] Enjoy. |
[2058.78 --> 2058.82] Enjoy. |
[2058.82 --> 2058.84] Enjoy. |
[2058.84 --> 2059.32] Enjoy. |
[2059.32 --> 2059.72] Enjoy. |
[2059.72 --> 2060.72] Enjoy. |
[2060.72 --> 2062.72] Enjoy. |
[2062.72 --> 2063.72] Enjoy. |
[2063.72 --> 2082.68] So we're here with Dawn Foster from VMware. |
[2082.94 --> 2083.32] How are you doing? |
[2083.70 --> 2084.42] I'm good, thanks. |
[2084.50 --> 2085.10] Thanks for having me. |
[2085.46 --> 2088.34] What do you enjoy about conferences like these? |
[2088.44 --> 2089.18] What's your favorite part? |
[2089.56 --> 2090.34] Oh, my God, it's the people. |
[2090.34 --> 2093.74] So you get to run into people that you've known for years. |
[2093.92 --> 2095.28] You get to meet new people. |
[2095.50 --> 2095.72] Yeah. |
[2095.94 --> 2097.08] You get to reconnect with people. |
[2097.16 --> 2098.32] You get to have interesting conversations. |
[2098.92 --> 2103.62] And, you know, when we were all virtual through, you know, the pandemic and lockdowns and things, |
[2103.66 --> 2104.56] it just wasn't the same. |
[2104.56 --> 2105.20] It wasn't the same. |
[2105.66 --> 2108.14] Because you don't get those serendipitous conversations, right? |
[2108.14 --> 2108.50] That's right. |
[2108.50 --> 2109.16] You don't. |
[2109.22 --> 2112.66] You know, Kara's not going to, like, drag me across the room to do this podcast. |
[2112.76 --> 2113.04] Right. |
[2113.04 --> 2114.08] On a virtual environment, right? |
[2114.08 --> 2114.94] I never went to drag. |
[2115.12 --> 2115.68] That's not quite. |
[2115.70 --> 2116.32] But did she drag you? |
[2116.34 --> 2116.92] No, she didn't drag me. |
[2116.92 --> 2119.86] She very kindly asked me if I would like to do one right now. |
[2119.86 --> 2120.86] You were a willing party. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.