text stringlengths 0 2.35k |
|---|
[2668.66 --> 2669.08] And that |
[2669.08 --> 2669.70] could create |
[2669.70 --> 2670.18] those, you |
[2670.18 --> 2670.88] know, those |
[2670.88 --> 2672.02] intermediate layers |
[2672.02 --> 2673.08] between code |
[2673.08 --> 2673.64] that is just |
[2673.64 --> 2674.56] a proxy, |
[2674.80 --> 2675.16] which just |
[2675.16 --> 2675.78] invokes more |
[2675.78 --> 2676.14] code and |
[2676.14 --> 2676.66] invokes more |
[2676.66 --> 2676.98] code. |
[2677.40 --> 2678.02] And then at |
[2678.02 --> 2678.36] the end of |
[2678.36 --> 2678.66] the day, |
[2678.74 --> 2679.08] if you want |
[2679.08 --> 2679.70] to perform |
[2679.70 --> 2680.52] a simple |
[2680.52 --> 2680.92] lookup, |
[2681.26 --> 2682.00] it can look |
[2682.00 --> 2683.02] like something |
[2683.02 --> 2683.46] that will |
[2683.46 --> 2684.12] create this |
[2684.12 --> 2684.98] very chaotic |
[2684.98 --> 2686.02] code base |
[2686.02 --> 2687.44] for something |
[2687.44 --> 2687.96] very, very |
[2687.96 --> 2688.36] simple. |
[2689.18 --> 2689.66] But then |
[2689.66 --> 2690.78] in Go, |
[2691.06 --> 2691.72] I always say |
[2691.72 --> 2692.12] that everything |
[2692.12 --> 2692.80] is explicit |
[2692.80 --> 2693.50] in Go |
[2693.50 --> 2693.96] except for |
[2693.96 --> 2694.32] the things |
[2694.32 --> 2694.78] that aren't. |
[2695.46 --> 2695.90] And what I |
[2695.90 --> 2696.40] mean by the |
[2696.40 --> 2696.82] things that |
[2696.82 --> 2697.30] aren't are |
[2697.30 --> 2698.04] like stringers, |
[2698.16 --> 2698.60] for instance, |
[2698.74 --> 2699.86] where we |
[2699.86 --> 2700.88] invoke some |
[2700.88 --> 2702.24] functionality by |
[2702.24 --> 2703.26] performing some |
[2703.26 --> 2704.42] type assertion |
[2704.42 --> 2706.22] that nobody |
[2706.22 --> 2706.90] is aware of |
[2706.90 --> 2707.18] somewhere. |
[2708.12 --> 2708.34] But yeah, |
[2708.42 --> 2708.84] but generally |
[2708.84 --> 2709.34] speaking, |
[2709.44 --> 2709.80] Go is |
[2709.80 --> 2710.24] explicit. |
[2710.90 --> 2711.62] If you have |
[2711.62 --> 2712.46] a package and |
[2712.46 --> 2712.88] it's well |
[2712.88 --> 2713.28] written, |
[2714.00 --> 2715.16] then it |
[2715.16 --> 2716.18] should meet |
[2716.18 --> 2716.90] the open |
[2716.90 --> 2718.12] close principles |
[2718.12 --> 2719.98] and then you |
[2719.98 --> 2720.98] should be able |
[2720.98 --> 2722.34] to wrap this |
[2722.34 --> 2722.78] type with |
[2722.78 --> 2723.16] whatever, |
[2723.68 --> 2723.98] you know, |
[2724.02 --> 2724.94] or extend |
[2724.94 --> 2725.76] the functionality |
[2725.76 --> 2726.68] of whatever it |
[2726.68 --> 2727.10] is that you |
[2727.10 --> 2727.30] want. |
[2727.86 --> 2728.46] I understand |
[2728.46 --> 2728.94] why people |
[2728.94 --> 2729.56] struggle with |
[2729.56 --> 2729.76] that. |
[2730.08 --> 2730.62] I think that |
[2730.62 --> 2731.26] is the biggest |
[2731.26 --> 2732.54] issue is |
[2732.54 --> 2734.08] how we |
[2734.08 --> 2734.54] don't write |
[2734.54 --> 2735.30] packages very |
[2735.30 --> 2735.58] well. |
[2735.64 --> 2735.98] By the way, |
[2736.06 --> 2736.38] for the |
[2736.38 --> 2736.74] workshop, |
[2737.04 --> 2738.08] I had to |
[2738.08 --> 2739.44] revise my |
[2739.44 --> 2740.10] code multiple |
[2740.10 --> 2741.06] times because |
[2741.06 --> 2741.76] I realized that |
[2741.76 --> 2742.40] my design |
[2742.40 --> 2743.02] choices were |
[2743.02 --> 2744.38] so far, |
[2744.84 --> 2745.30] let's say. |
[2745.52 --> 2746.08] Less common |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.