text stringlengths 0 2.35k |
|---|
**Bill Kennedy:** I may anyway, so I'm starting local... |
**Natalie Pistunovich:** Yeah, it's slowly happening. |
**Bill Kennedy:** So my unpopular opinion is -- you heard about the whole FTX crash, right? And everything that's now falling behind it. So my opinion here is that the FTX crash shouldn't be associated with the blockchain technology directly. It wasn't the blockchain technology that caused that. It was people that caus... |
**Natalie Pistunovich:** I am interested in seeing how that goes... |
**Bill Kennedy:** There we go, everybody is quiet! \[laughs\] |
**Natalie Pistunovich:** That is an interesting one. |
**Mat Ryer:** I'll be very interested to see the results when they get polled out on whichever platform survives... |
**Bill Kennedy:** Hey, you know, if you're gonna do this, do it right. \[laughter\] |
**Natalie Pistunovich:** Although it will be a new, interesting bias, given that more and more people are just not on Twitter. So the people that leave are the ones that more agree with you, or less. |
**Bill Kennedy:** Well, I've moved to TechHub.social. I'm actually moderating that instance... So if people are looking to jump, and they're looking for an instance that's being moderated in the same way GoBridge would moderate anything, TechHub.social is a great place to check it out. |
**Natalie Pistunovich:** We'll add that in the show notes. Chris, do you have an unpopular opinion? |
**Chris James:** I don't know, I completely forgot about this segment, and I feel under pressure... |
**Mat Ryer:** That's unpopular, mate... |
**Chris James:** Football's coming home? There you go. Football's coming home. \[laughter\] It's the wrong audience, but I don't care. Football is coming home. |
**Mat Ryer:** Is that the one with the green floor? |
**Chris James:** Yeah. And the ball, and they're kicking it around. |
**Mat Ryer:** Yeah, I've seen it. |
**Chris James:** It's that one. |
**Natalie Pistunovich:** The round ball, or the one with the... |
**Bill Kennedy:** Yes. |
**Mat Ryer:** Is that an egg? |
**Chris James:** Not the egg. Not the egg ball. |
**Natalie Pistunovich:** Not the egg. |
**Mat Ryer:** But is that an egg? Because they're not very careful with it, if that's like a, like an egg... Do you know what I mean? They're proper just kicking -- they throw it around all sorts... |
**Natalie Pistunovich:** It's a spiky one. |
**Mat Ryer:** It's a very strong egg, ain't it? |
**Natalie Pistunovich:** Matt, I heard you have an unpopular opinion. |
**Mat Ryer:** Oh, yeah, I did have an unpopular opinion, actually... I thought of one, and I thought "I must write that down", and then I distinctly remember not writing it down, thinking it's so good I'll definitely remember it... |
**Natalie Pistunovich:** It's just building up for the next episode. I see where this is going... |
**Chris James:** It's a great story. |
**Mat Ryer:** But then I thought, "I should write it down", but then I still didn't. I can't remember. |
**Natalie Pistunovich:** Well, next episode, tune in for Mat's unpopular opinion. Thank you, Mat, for joining. Thank you, Chris and Bill, for sharing your thoughts. It was very interesting. Thanks everyone who tuned in to listen and was super-active on our Slack. That's super-fun. It is very interesting, and it looks l... |
**Mat Ryer:** Bye! |
**Chris James:** Cheers! |
• Brownfield projects: definition and benefits |
• Characteristics of brownfield projects (e.g. clarity, fewer gotchas) |
• Technical debt in brownfield projects |
• Value streams and how they contribute to brownfields |
• Addressing technical debt in brownfield projects |
• Possibility of creating greenfield projects that avoid becoming brownfields |
• Discussion on the challenges of transitioning from greenfield (new) projects to brownfield (mature) projects |
• Recognizing that the distinction between greenfield and brownfield is often a matter of mindset and expectations rather than an intrinsic property of the project |
• Importance of planning and design in preventing brownfield issues, but acknowledging the tendency to avoid upfront design in favor of agility and flexibility |
• The role of time and change in causing projects to become brownfield: changes in scope, requirements, or goals can quickly lead to a mature and complex system |
• Analogies between project development and agriculture (e.g. using manure to grow new things) to highlight the need to "embrace" the complexities and imperfections of existing systems |
• Sharing personal anecdotes and experiences with transitioning from greenfield to brownfield projects, including difficulties in predicting future changes and adapting to evolving requirements. |
• Refactoring complex legacy codebases requires a thoughtful and gradual approach |
• Avoiding the "fix everything at once" mindset can lead to successful long-term changes |
• Engineers may not be in the best position to determine which aspects of the codebase to prioritize for refactoring |
• Having staff-level engineers who understand both the technical and business needs can help with prioritization |
• Using metrics, observability tools, and data-driven decision-making can make it easier to argue for refactoring efforts |
• The importance of tying engineering pain points to business pain points |
• Misconceptions about "technical debt" and the assumption that refactoring a codebase will instantly improve its quality |
• The "Grass is Greener on the Other Side" phenomenon, where teams idealize past projects and think they can replicate their successes elsewhere |
• The value of being honest with oneself and the team about the time required to fix technical debt, even if it's uncomfortable or requires limits on refactoring time |
• Brownfield projects require humility and understanding of the existing system |
• Watching YouTube videos or reading books is not enough; local knowledge from experienced team members is crucial |
• It's better to optimize for codebase health over productivity |
• Greenfield vs brownfield mentality: new projects require throwing effort in multiple directions, while existing ones require targeted interventions |
• Momentum and inertia are important considerations when working with legacy codebases. |
• The importance of understanding the context and effort required for brownfield projects |
• The need to maintain existing codebases rather than declaring them "bad" or starting from scratch |
• Characteristics of a healthy software system, including resilience and adaptability |
• Properties of a resilient codebase, such as failure locality and clear separations of responsibility |
• Challenges in rearchitecting brownfield codebases, including the need for justification and consideration of potential impact |
• Understanding the underlying principles and concepts behind software development is key to creating a resilient codebase. |
• The importance of learning from experience and knowledge captured in books, such as patterns and design principles (e.g. open-closed principle). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.