text stringlengths 0 2.46k |
|---|
[4928.32 --> 4932.80] business on you know building small websites you know like building five page five page websites |
[4932.80 --> 4937.36] stuff like that you know that that business model didn't last very long and you kind of the business |
[4937.36 --> 4942.40] went into an incubation period and and was reborn out of that you know this that might be what's |
[4942.40 --> 4947.12] about to happen again we'll see you never know that does make sense yeah i mean you got to evolve when |
[4947.12 --> 4952.80] when change happens resilience is change really essentially you got to change with the change that's |
[4952.80 --> 4959.12] right that wise man once said all right was that you maybe martin fowler i don't know |
[4961.04 --> 4965.12] well good luck on that change yeah good luck navigating it i appreciate that and the the |
[4965.12 --> 4968.96] product direction i agree with jared it does sound like the way to go because if you can give i think |
[4968.96 --> 4977.44] so too an executive in i don't know what time frame something that is authoritative and finite in terms of |
[4977.44 --> 4984.40] there is lack of freshness or you're this far behind best practices or some sort of indicator |
[4984.40 --> 4991.44] that says i'm not hearing it from my developers who in quotes whine right or complain that i i lovingly |
[4991.44 --> 4998.16] trust but really i need this authoritative thing that says hey get your stuff together yeah and trying |
[4998.16 --> 5005.84] trying to give you engineering teams a way to translate the data that that the system is collecting in a |
[5005.84 --> 5011.52] way that can be easily consumed by their leadership so you know instead of you know having a graph |
[5011.52 --> 5018.24] with a whole bunch of data on on a web page and then sending you know trying to get your your manager |
[5018.24 --> 5024.16] to log into that instead like generate a powerpoint deck and write something you can toss into an email |
[5024.16 --> 5028.40] and forward to somebody and and in there can be a link to that dashboard like if somebody wants to |
[5028.40 --> 5032.56] see the dash here's our vulnerability score or something like that or here's our staleness factor |
[5032.56 --> 5037.60] right freshness factor or freshly factor or whatever it might be and that could actually be quite good |
[5037.60 --> 5044.88] at marketing too for you yeah you know because then it becomes maybe a a race or a competition of |
[5044.88 --> 5053.76] sorts with executives or yeah ceo to ceo like hey what's your what's your freshness factor and then help |
[5053.76 --> 5058.48] you know even within like a an organization that might have a portfolio of projects are there projects |
[5058.48 --> 5062.72] that are doing better than others what you know and then getting curious about the teams that are |
[5062.72 --> 5067.04] doing better what are they doing differently and is there knowledge that those teams might have |
[5067.60 --> 5072.56] which might make sense to share with other teams yeah good plan yeah man you should do it |
[5072.56 --> 5077.68] thanks working on it it just takes time building software it takes time it takes time even with |
[5077.68 --> 5082.80] like ai's help right it still takes time i can't just hit my fingers and say that's right hey uh hey |
[5082.80 --> 5087.84] hey github copilot you know build this for me or hey aws code whisperer build this for me right |
[5087.84 --> 5092.48] you still gotta fix those bugs that it spits out at you that's right well thanks for stopping by |
[5092.48 --> 5096.40] scott yeah appreciate appreciate you letting me uh chat you bet |
[5100.08 --> 5108.32] well the year is almost done 2024 is almost here you know it's it's the end of a year and it's that |
[5108.32 --> 5114.64] time you think man what's next right what's coming next what's next for me what's next for the world |
[5114.64 --> 5122.00] what's next for tech what's next for software and all the above well i do know what's next for this |
[5122.00 --> 5128.72] podcast i can say that there is an episode of friends coming out momentarily and then i can also |
[5128.72 --> 5136.64] say that next week there is an epic episode jared and i are back for state of the log breakmaster |
[5136.64 --> 5143.12] cylinder helped us up our game this year even more so than years beforehand where well i'll just i'll |
[5143.12 --> 5148.40] just save it for the episode let's just say you want to check it out it's the end of the year but |
[5148.40 --> 5154.88] we're gonna be back next year more good stuff more good things and uh i hope you have a safe holiday |
[5154.88 --> 5161.60] enjoy your family and it's also good to say thank you right thank you to you of course for listening |
[5161.60 --> 5168.72] this podcast thank you to our plus plus subscribers and then thank you to fastly for supporting us all |
[5168.72 --> 5176.08] these years and then of course thank you to fly.io and our friends over there for supporting us all |
[5176.08 --> 5185.60] these years our friends at type sense our friends at century our new friends at neon and everyone in |
[5185.60 --> 5193.60] in between thank you thank you and of course to the beat freak in residence break master cylinder |
[5194.32 --> 5200.80] those beats those beats but hey we'll see you soon on friends we'll see you next week for |
[5201.44 --> 5206.72] state of the log but that's it this show's done we'll see you very soon |
[5215.60 --> 5217.28] well |
[5231.28 --> 5232.88] you |
• All Things Open 2023 conference |
• Matthew Sanabria, former engineer at Hashi Corp, discussed Terraform Enterprise |
• Nithya Ruff, Chief Open Source Officer at Amazon, discussed open source challenges |
• Jordan Harband, open source maintainer, discussed changes in open source |
• Convex platform for full-stack TypeScript development |
• Comparison of Convex to Firebase |
• Infrastructure challenges for application developers |
• James Cowling's experience with Convex and his former job at Hashi Corp |
• Terraform Enterprise and Hashi Corp's license change announcement |
• Discussion of the Terraform license change and its impact on developers |
• Lack of communication about the license change from the Terraform team |
• Shift in engineering culture at HashiCorp towards a more product-focused approach |
• Impact on team morale and job satisfaction |
• Comparison of the Terraform license change to a company's initial success and subsequent actions |
• Discussion of the role of community involvement and communication in the decision-making process |
• Personal reasons for leaving the company, including the shift in engineering culture and loss of involvement in open-source projects |
• Size and composition of the team after layoffs and maternity leave |
• The speaker was considering transferring to an open-source team at Hashicorp a year before their actual transfer due to concerns about the company's license changes. |
• The team's sentiment about the license changes was generally positive, with some people viewing it as an opportunity to make more money. |
• The speaker received backlash on a Slack channel for expressing their opinion about OpenTofu's name change, with some interpreting it as a negative comment towards Hashicorp. |
• The speaker's comment was misinterpreted and brought to the attention of their manager, highlighting the challenges of navigating company politics. |
• The speaker is now set to join Cockroach Labs, citing the opportunity to work on distributed systems problems and interact with those systems directly. |
• The speaker notes that Cockroach Labs has a similar licensing issue as Hashicorp, with the company using the BSL license. |
• The speaker reflects on the licensing conversations at Hashicorp, which were primarily focused on Terraform, and notes that all of Hashicorp's products have undergone license changes. |
• Discussion of Terraform and its relation to Open Tofu |
• Differences in approach between Terraform as a tool and Open Tofu as a service |
• Open Tofu's licensing and its potential impact on the industry |
• Critique of Open Tofu's name and branding |
• Comparison of Terraform's engineering effort to Open Tofu's |
• Concerns about Open Tofu's ability to maintain momentum and support |
• Complexities of maintaining a large and complex tool like Terraform/Open Tofu |
• Discussing the challenges of graphing and dependency resolution in infrastructure |
• Terraform and CockroachDB's use of Terraform provider |
• System Initiative and its potential as a future infrastructure tool |
• The advantages of System Initiative's visual interface and extensibility |
• Comparing System Initiative to Terraform and its extensibility |
• The potential for System Initiative to become a UI on top of Terraform or other infrastructure tools |
• The extensibility of System Initiative and its job functions written in TypeScript |
• Concerns about multilingual support for infrastructure tools |
• Use of TypeScript and its advantages vs. other languages like Go and Rust |
• Trade-off between declarative DSLs and imperative programming languages |
• Challenges of choosing between multiple languages and frameworks |
• Discussion of specific tools like Palumi, Dagger, and Hashicorp's HCL DSL |
• Introduction to the company Bastion and its eye-tracking technology, Eyewear |
• Future of computing and interaction (headsets, eye tracking, 3D screens) |
• Importance of eye tracking in various interfaces and surfaces |
• Hybrid setup combining headsets and other interfaces |
• Domain choice for the company (dot tech) |
• Nitya's background as OSPo (Open Source Program Office) at Amazon |
• Benefits of walking and exercising (compound interest) |
• Nitya's role and responsibilities as OSPo |
• Importance of open source in Amazon's product development and infrastructure |
• Nitya's work in making open source easy to work with for Amazon's developers and builders |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.