text stringlengths 0 1.8k |
|---|
\[01:04:23.18\] But yeah, so the path forward for us is very much continuing to work with those customers, continuing to build on the success of Kratix, taking and scaling Syntasso as a company, so we can build out around Kratix. If anyone out there that's listening would like to contribute to Kratix or to try it out, ... |
**Gerhard Lazu:** And that is the Colin that seven years ago convinced me to join CloudCredo. You've just listened to him. Colin in like two minutes. That was it. That was great. |
**Colin Humphreys:** Thank you. I have to do my best, because so far we've had Chris say we don't do testing... |
**Gerhard Lazu:** \[laughs\] That's not true, by the way... As I said, the things -- |
**Colin Humphreys:** ...and Paula say that we've got way too much process. |
**Paula Kennedy:** We love process. We love a bit of process. |
**Colin Humphreys:** So we don't do testing, we've got way too much process... \[laughter\] |
**Chris Hedley:** We hate testing. We love process. |
**Colin Humphreys:** I'm just like, "Where do I even start here?" I have to try and put the best foot of the company forward before somebody shoots it. \[laughter\] |
**Gerhard Lazu:** So my feedback to everything that you've said, all three of you, is the blog doesn't lie; go check out the blog. Go and watch Colin's crazy talks through the years; they're amazing, you'll have so much fun. Go and watch Paula's talk; I haven't seen it, but I've seen your other talks, Paula, and I know... |
So as we are prepared to wrap this up, for someone that's been listening to this, hopefully all the way to the end... |
**Chris Hedley:** If they're still listening... Yeah, fair play... |
**Gerhard Lazu:** \[laughs\] Yeah, if they're still listening... What is the key takeaway? And we can maybe start with Paula. What do you think is the key takeaway, Paula? |
**Paula Kennedy:** \[01:06:41.17\] I think for us a thing that we've learned is people need platforms to help them go faster. And we've seen the pattern. It's interesting how -- I think for me, I feel like I've been talking about this platform as a product, platform gap for quite a long time, and I think a problem that... |
**Gerhard Lazu:** Thank you, Paula. Over to you, Chris. |
**Chris Hedley:** I would +1 what Paula said. I think the key takeaway, as I reflect on what Syntasso can add to the industry - if it's on the platform developers to reduce the cognitive load on their customers, the application developers, for example, then it's on Syntasso and Kratix to help produce the cognitive load... |
**Gerhard Lazu:** Thank you. Colin? |
**Colin Humphreys:** Yeah, I think I'm actually gonna reflect some words back at you, Gerhard... Solomon Hykes, founder of Docker, on your show said "If your platform is generic, then your application is generic." So we know that people wanna build differentiation and value into their apps, therefore you're gonna need ... |
**Gerhard Lazu:** Or Phoenix. It's less corny, Phoenix... Changelog runs Phoenix, and it's great. But yeah, I know what you mean. |
**Colin Humphreys:** So yeah, a framework for building platform as a product is what we're trying to build, and we all know the future of infrastructure is gonna be more declustered Kubernetes. So we are at the intersection of those two technologies, and if you wanna help with building out platforms or products on Kube... |
So if I had one takeaway for people to do, please do reach out to myself, Paula, maybe not Chris as much... \[laughter\] I'm joking, of course. |
**Gerhard Lazu:** Yeah, he's inwards-facing, you already established that. \[laughter\] |
**Colin Humphreys:** It's become quite clear in the whole podcast. You don't wanna talk to me, you wanna talk to Chris. |
**Gerhard Lazu:** He's too polite, yeah. |
**Chris Hedley:** If you're in the marketing pitch, speak to Colin. If you want the honest stances about what really goes on - yes, speak to me. \[laughter\] |
**Colin Humphreys:** That is actually true. |
**Gerhard Lazu:** Yeah, definitely. So thank you very much for today. I had great, great fun. It's been too long since we hung together. This was good... And I'm thinking six months from now... First of all, Team Topologies - I have to add it to my queue. There's eight already, but that's okay, I can manage one more. O... |
**Paula Kennedy:** It's very good. Very, very good. Not too many pages. Very practical advice. |
**Gerhard Lazu:** Thank you. And trying Kratix out. I love playing with tools, and - what did you say? Systems. That's what Colin said; it's not a tool, it's a system. And that's intriguing. There's so much more happening there. So there's one to follow. Thank you very much for today. See you next time. |
**Paula Kennedy:** Thanks! |
**Chris Hedley:** Thanks for having us, Gerhard. |
**Colin Humphreys:** Thanks, Gerhard. Take care. |
• Importance of documentation in coding |
• Personal experiences with documentation as a developer |
• Role of documentation in enabling user experience |
• Connection between documentation and code |
• Documentation as an API to the product |
• Impact of good documentation on user retention and success |
• Challenges of context-switching for developers and potential solutions through documentation |
• Rethinking documentation approaches for better developer experience |
• Importance of documenting code alongside development process |
• Why documentation should not be optional for a product |
• Value of having writers involved in the development process |
• Strategies for smaller teams or teams without dedicated writers (hiring technical writers, product team writing docs, having a champion) |
• Best practices for developers to write documentation during the development process |
• Undervalued technical writers are often overstretched and expected to know everything about complex systems. |
• Documentation can be treated as part of the development process, allowing for ongoing documentation and improved learning experiences. |
• There are three stages of documentation: ignoring documentation, writing basic documents as a developer, and having a dedicated team with technical writers. |
• Effective documentation should consider different learning styles, including visual, interactive, and text-based content. |
• Documentation is not just text, but rather a learning experience that can include videos, interactive elements, and other multimedia content. |
• The goal of documentation is to provide context and clarity for users, rather than simply presenting information. |
• Reevaluating documentation approaches for GitHub Actions |
• Introducing storytelling and visuals to make documentation more engaging |
• Competitive research and incorporating community contributions |
• Prioritizing user needs, including new users and those familiar with the product |
• Revamping the GitHub Actions page with improved discoverability and search functionality |
• The evolution of GitHub Actions' UI and documentation over time |
• Kathy Korevec's efforts to improve GitHub Actions' documentation as part of her broader mandate to enhance documentation at GitHub |
• The importance of community feedback and iteration in improving products like GitHub Actions |
• The concept of earned trust by developers when using GitHub Actions, particularly considering its initial beta release and potential flaws |
• The significance of focusing on details and iterating rapidly to win back user trust and loyalty |
• Documenting code and repository structure |
• Pros and cons of having documentation in a single repository vs. separate from code |
• Benefits of tying documentation to GitHub Actions and workflows |
• Potential for automating documentation flow with templates and synchronization |
• Considerations for small teams vs. larger organizations |
• Use cases for private and public documentation repositories |
• Discussion of potential follow-up interview with Kathy Korevec now at Vercel |
• Importance of embracing failure in the industry and learning from it |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.