text
stringlengths
0
2.35k
[745.48 --> 747.96] And enums is one that I hear quite a lot, actually.
[748.04 --> 749.54] People actually want enums.
[749.70 --> 752.32] Did enums, lack of enums hold us back, Ron?
[752.78 --> 754.08] Oh, so much.
[754.44 --> 758.66] You don't realize, okay, if you just can't figure out,
[758.66 --> 762.14] is it this or that or the other thing or something else yet again?
[762.62 --> 765.92] Like, you know, for us developers, like we could figure that out.
[765.96 --> 770.96] But then all of a sudden, these people started making programs using things like no code
[770.96 --> 773.26] with no code and no rules and no enums.
[773.40 --> 777.30] And they were just making up their own like three and a half and 16 and three quarters.
[777.30 --> 781.12] And then suddenly they were bringing back imperial units and they were making up new units
[781.12 --> 784.06] that no one had ever heard of, moon units and stuff like that.
[784.06 --> 790.90] If only they had enums, okay, then probably those would have held things in place and
[790.90 --> 798.32] they would have prevented the silicon virus of 2027, which actually that was an actual
[798.32 --> 799.20] silicon virus.
[799.34 --> 800.72] The chips were passing it to each other.
[801.04 --> 801.56] Oh, physically.
[801.88 --> 802.80] Yeah, it was terrible.
[803.00 --> 805.18] My mobile phone actually died before my eyes.
[805.24 --> 805.66] It was terrible.
[806.50 --> 807.26] Oh, I'm so sorry.
[807.72 --> 808.42] Okay, well, enums.
[808.84 --> 810.50] I mean, honestly, I'd like to see enums.
[811.08 --> 814.10] And Valentin on Twitter also agrees they'd like to see enums.
[814.88 --> 819.02] We should do that probably then if it's going to cause that silicon thing Ron talked about.
[819.18 --> 819.30] Yeah.
[819.60 --> 822.92] I can't say, but just remember what might happen if you don't.
[822.98 --> 823.10] Yeah.
[823.56 --> 824.26] Why stop there?
[824.42 --> 828.76] How about tooling and third-party libraries for things like image library and Go, like
[828.76 --> 830.20] the GoLine Cafe is recommended?
[830.74 --> 834.20] Oh, well, that is a really big thing.
[834.20 --> 841.84] The standard library, at some point, it went from, I don't know, like code to suddenly
[841.84 --> 843.28] like a whole belief system.
[844.22 --> 846.60] Like we never had even seen anything like it.
[846.74 --> 851.08] Like, hey, you know, there were like standard library purists and then there were not.
[851.38 --> 855.52] There were the heretics that were like thrown out of the community that went on to all these
[855.52 --> 857.02] other languages like Lisp.
[857.02 --> 865.50] You know, I mean, and so it was all simply because of not being able to accept ideas that
[865.50 --> 870.86] came from other places that were totally valid and that, you know, deserve their own little
[870.86 --> 872.28] niche in the ecosystem.
[872.28 --> 874.16] And they didn't get fed and watered.
[874.26 --> 877.92] And eventually they migrated to another island, I guess.
[877.98 --> 878.42] I don't know.
[878.50 --> 879.58] Maybe another space station.
[879.76 --> 882.46] I can't really get transmissions through to those stations.
[882.72 --> 883.72] They cut me off.
[884.00 --> 884.82] Oh, you're joking.
[884.98 --> 885.42] I wonder why.
[885.42 --> 887.82] I hope they had this bad silicon with them.
[888.12 --> 888.78] I don't know.
[888.98 --> 889.90] Cutting you off like that.
[890.10 --> 892.24] Too soon, Natalie, talking about the silicon virus.
[892.58 --> 896.40] Lord Emperor Musk said I couldn't make any more transmissions of that kind.
[896.68 --> 899.60] So and I need to maintain some Go code for them.
[900.20 --> 903.46] So for the Teslas, I can't say it's a non-disclosure agreement.
[903.80 --> 905.66] But remember, I am the last Go programmer.
[906.02 --> 907.26] So I'm very, very busy.
[907.54 --> 908.24] Yeah, good for you.
[908.32 --> 909.50] I mean, it's good work if you can get it.
[909.56 --> 911.34] If you're the last one, it's pretty good.
[911.54 --> 912.64] There's no feature development.
[912.74 --> 913.56] It's all bug fixes.
[913.56 --> 915.86] It's all bug fixes, Matt.
[916.06 --> 918.20] Imagine the last 20 years of my life.
[918.50 --> 919.36] I mean, it's good money.
[919.66 --> 921.10] OK, I will tell you that.
[921.20 --> 921.96] We still have money.
[922.06 --> 926.12] And I need that to get the blood transfusions that keep me looking so young and beautiful.
[926.30 --> 926.58] You do.
[926.66 --> 926.86] Yeah.
[927.08 --> 927.72] I was thinking that.
[927.72 --> 943.68] This episode is brought to you by our friends at FireHydrant.
[943.90 --> 946.74] FireHydrant is the reliability platform for every developer.
[947.16 --> 950.94] Incidents, they impact everyone, not just SREs.
[950.94 --> 955.66] They give teams the tools to maintain service catalogs, respond to incidents, communicate
[955.66 --> 958.84] through status pages, and learn with retrospectives.
[959.20 --> 964.14] What would normally be manual error-prone tasks across the entire spectrum of responding to
[964.14 --> 964.52] an incident.
[964.88 --> 968.06] They can all be automated in every way with FireHydrant.
[968.06 --> 973.44] They have incident tooling to manage incidents of any type with any severity with consistency.
[974.00 --> 977.12] Declare and mitigate incidents all from inside Slack.
[977.50 --> 982.22] Service catalogs allow service owners to improve operational maturity and document all your
[982.22 --> 983.82] deploys in your service catalog.
[984.42 --> 989.20] Incident analytics allow you to extract meaningful insights about your reliability over any facet
[989.20 --> 991.78] of your incident or the people who respond to them.
[991.78 --> 996.10] And at the heart of it all, incident runbooks, they let you create custom automation rules,
[996.34 --> 1001.56] convert manual tasks into automated, reliable, repeatable sequences that run when you want.
[1001.94 --> 1005.96] You can create Slack channels, Jira tickets, Zoom bridges instantly after declaring an incident.
[1006.42 --> 1009.02] Now your processes can be consistent and automatic.
[1009.48 --> 1011.16] The next step is to try it free.
[1011.30 --> 1015.66] Small teams up to 10 people can get started for free with all FireHydrant features included.
[1015.98 --> 1017.40] No credit card is required.
[1017.86 --> 1020.02] Get started at firehydrant.io.
[1020.02 --> 1022.34] Again, firehydrant.io.
[1035.76 --> 1037.86] What about tabs versus spaces then?
[1038.16 --> 1038.86] What happened with that?
[1038.98 --> 1039.70] That was a whole war.
[1039.94 --> 1040.22] Oh yeah?
[1041.14 --> 1047.42] The thing you don't realize is there was a whole sub war that went on between carriage return