Datasets:
willtheorangeguy
/
2016-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.82k
[1225.80 --> 1226.84] and how it interfaces
[1226.84 --> 1227.72] with your code,
[1228.14 --> 1228.32] right?
[1228.32 --> 1230.14] So one of the
[1230.14 --> 1231.38] kind of
[1231.38 --> 1232.26] code generation
[1232.26 --> 1233.60] principle behind Goa
[1233.60 --> 1234.48] is that
[1234.48 --> 1236.00] user code
[1236.00 --> 1237.88] and generated code
[1237.88 --> 1238.60] never mix
[1238.60 --> 1239.78] and there is
[1239.78 --> 1241.16] a very clear interface,
[1241.58 --> 1242.06] an explicit,
[1242.26 --> 1242.38] I mean,
[1242.50 --> 1243.66] a Go interface,
[1243.80 --> 1243.90] right?
[1243.98 --> 1245.46] It's a very
[1245.46 --> 1246.28] explicit interface
[1246.28 --> 1246.92] between the two.
[1247.58 --> 1248.36] It's not just one,
[1248.44 --> 1248.80] it's multiple
[1248.80 --> 1249.80] but the idea
[1249.80 --> 1250.76] is that you have
[1250.76 --> 1252.16] interfaces that are clear
[1252.16 --> 1253.94] between the generated code
[1253.94 --> 1254.78] and the user code
[1254.78 --> 1256.36] and if you regenerate
[1256.36 --> 1256.82] your code,
[1257.08 --> 1257.88] you shouldn't care.
[1257.88 --> 1258.56] I mean,
[1258.60 --> 1259.32] basically the idea
[1259.32 --> 1260.40] is if you
[1260.40 --> 1261.68] change your design
[1261.68 --> 1262.44] and you add,
[1262.52 --> 1263.02] let's say you add
[1263.02 --> 1263.70] a new field
[1263.70 --> 1265.08] to a request payload,
[1265.70 --> 1266.76] you regenerate your code,
[1266.90 --> 1267.46] all that means
[1267.46 --> 1268.46] is now your context
[1268.46 --> 1269.56] subject has a new field
[1269.56 --> 1270.54] and you can use it
[1270.54 --> 1270.98] and that's it.
[1271.14 --> 1271.70] You don't have to
[1271.70 --> 1273.62] worry about anything else.
[1274.90 --> 1275.34] Obviously,
[1275.56 --> 1276.22] there are cases
[1276.22 --> 1278.12] where the interface
[1278.12 --> 1278.70] may break,
[1278.96 --> 1279.70] they may change
[1279.70 --> 1281.00] between different tools
[1281.00 --> 1281.78] but in that case
[1281.78 --> 1282.58] it should be clear,
[1282.72 --> 1283.52] it should be you're moving
[1283.52 --> 1285.00] from 1.0 to 2.0
[1285.00 --> 1285.76] and you're doing
[1285.76 --> 1286.50] that conscientiously.
[1286.64 --> 1287.24] It shouldn't be something
[1287.24 --> 1288.14] that is a side effect.
[1289.20 --> 1289.60] So,
[1289.72 --> 1290.46] I've been very careful
[1290.46 --> 1290.96] about that
[1290.96 --> 1292.96] because in the past
[1292.96 --> 1293.82] I've had experience
[1293.82 --> 1294.18] with,
[1294.18 --> 1294.40] you know,
[1294.48 --> 1294.88] Core Bar,
[1295.02 --> 1295.74] IDL,
[1295.92 --> 1296.62] MIDL
[1296.62 --> 1297.96] and it was always
[1297.96 --> 1298.66] very painful
[1298.66 --> 1299.68] whenever
[1299.68 --> 1301.26] generated code
[1301.26 --> 1302.90] mixed with user code
[1302.90 --> 1304.08] because now
[1304.08 --> 1304.56] what do you do?
[1304.64 --> 1305.12] Do you test
[1305.12 --> 1305.68] the whole thing?
[1306.00 --> 1306.10] So,
[1306.22 --> 1307.44] do you now own
[1307.44 --> 1308.08] the generated code,
[1308.18 --> 1308.32] right?
[1308.40 --> 1309.60] Do you need to test it
[1309.60 --> 1310.42] to maintain it?
[1310.98 --> 1312.12] And then you run into
[1312.12 --> 1313.58] the issues of lifecycle
[1313.58 --> 1314.84] when you change the source
[1314.84 --> 1315.90] then you need to change
[1315.90 --> 1316.38] that code.
[1316.82 --> 1316.90] So,
[1317.00 --> 1317.82] I know sometimes
[1317.82 --> 1318.50] some like some
[1318.50 --> 1319.76] MIDL generators
[1319.76 --> 1320.76] would put markers
[1320.76 --> 1321.78] in comments
[1321.78 --> 1322.38] in your file,
[1322.46 --> 1322.64] right?
[1322.68 --> 1323.24] And then they would
[1323.24 --> 1324.34] find those markers