Datasets:
willtheorangeguy
/
2016-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.82k
[2763.96 --> 2764.50] talking about
[2764.50 --> 2765.04] last week.
[2765.70 --> 2766.62] This is Hekka
[2766.62 --> 2767.18] for backups.
[2767.92 --> 2768.58] That's actually a
[2768.58 --> 2769.12] good comparison.
[2769.84 --> 2770.16] Thanks for
[2770.16 --> 2770.58] saying so.
[2772.60 --> 2773.38] I have to make
[2773.38 --> 2773.90] you feel better.
[2775.52 --> 2776.32] After the code
[2776.32 --> 2776.96] reviews I've been
[2776.96 --> 2777.48] through this week,
[2777.52 --> 2778.10] I'll take anything
[2778.10 --> 2778.68] I can get.
[2781.68 --> 2782.36] Another
[2782.36 --> 2783.42] interesting project
[2783.42 --> 2785.34] that I've
[2785.34 --> 2786.12] seen was
[2786.12 --> 2787.90] Zap from
[2787.90 --> 2789.12] Uber, which
[2789.12 --> 2789.82] was a
[2789.82 --> 2790.36] structured
[2790.36 --> 2790.94] logging
[2790.94 --> 2792.80] framework that
[2792.80 --> 2793.66] is supposed to
[2793.66 --> 2794.24] have, I think,
[2794.30 --> 2795.48] zero allocations.
[2795.98 --> 2796.96] That was kind
[2796.96 --> 2797.38] of interesting.
[2798.04 --> 2798.76] We're down here
[2798.76 --> 2799.44] in the south, so
[2799.44 --> 2800.02] we can call that
[2800.02 --> 2800.36] y'all.
[2800.68 --> 2801.14] Yet another
[2801.14 --> 2801.92] leveled logger.
[2801.92 --> 2807.30] I really
[2807.30 --> 2807.90] liked the
[2807.90 --> 2809.18] structured part
[2809.18 --> 2809.82] of that
[2809.82 --> 2810.76] system.
[2811.20 --> 2811.72] I remember
[2811.72 --> 2812.94] when I worked
[2812.94 --> 2814.16] again in the
[2814.16 --> 2814.96] Rails app and
[2814.96 --> 2815.80] we were using
[2815.80 --> 2816.90] Splunk to keep
[2816.90 --> 2817.46] track of our
[2817.46 --> 2819.46] logs and we
[2819.46 --> 2820.80] had to agree
[2820.80 --> 2822.26] upon a specific
[2822.26 --> 2823.24] way to write
[2823.24 --> 2824.18] our code so
[2824.18 --> 2825.00] that it will be
[2825.00 --> 2826.00] easy to find in
[2826.00 --> 2826.62] Splunk and we
[2826.62 --> 2827.44] had to just
[2827.44 --> 2828.96] like certain
[2828.96 --> 2829.96] keywords and the
[2829.96 --> 2831.18] ecosign and the
[2831.18 --> 2832.12] whatever variable
[2832.12 --> 2833.16] we wanted to
[2833.16 --> 2833.80] look at.
[2834.40 --> 2835.40] And we had to
[2835.40 --> 2835.98] rely upon
[2835.98 --> 2836.96] everybody remembering
[2836.96 --> 2837.84] to do that.
[2838.22 --> 2839.04] So with this
[2839.04 --> 2840.40] structure, it
[2840.40 --> 2841.36] just makes life
[2841.36 --> 2842.42] so much simpler
[2842.42 --> 2843.62] for everybody
[2843.62 --> 2845.16] besides the fact
[2845.16 --> 2845.82] that it seems to
[2845.82 --> 2846.48] be very efficient
[2846.48 --> 2848.20] and about the
[2848.20 --> 2848.78] features.
[2849.68 --> 2849.96] All right.
[2850.02 --> 2850.50] Anybody have
[2850.50 --> 2850.96] anything else
[2850.96 --> 2851.28] they want to
[2851.28 --> 2851.92] talk about before
[2851.92 --> 2853.32] we kind of go
[2853.32 --> 2853.86] on our merry
[2853.86 --> 2854.20] way?
[2854.74 --> 2855.14] No, it's been
[2855.14 --> 2855.58] a pretty full
[2855.58 --> 2855.90] show.
[2856.34 --> 2857.06] Or not so merry
[2857.06 --> 2857.82] for Brian who's
[2857.82 --> 2858.70] going to get a
[2858.70 --> 2859.34] beat down in his
[2859.34 --> 2859.72] code review.
[2859.72 --> 2860.12] Go back to my
[2860.12 --> 2860.60] code review.
[2861.74 --> 2862.58] Don't tell
[2862.58 --> 2863.18] Blake if he's
[2863.18 --> 2863.48] listening.
[2866.24 --> 2867.48] So one of the
[2867.48 --> 2868.04] things we like to