60 acast.com <![CDATA[Code & Optimism]]> https://shows.acast.com/code-and-optimism en Shane Delamore software, architecture, optimisim, entrepreneurship, philosophy, productivity, essentialisim Shane Delamore Solving Problems Faster with Software

All problems are solvable with enough knowledge -- and software is the most powerful knowledge tool ever invented.


Code & Optimism is a show focused on solving problems faster with software. I created this series to discuss topics related to my passion of accelerating our ability to solve problems with software. In this show I'll dive into everything from practical tips to philosophical musings about optimism, solving problems and this wonderful tool called software and how we can become ever better at software engineering.


Who is it for?

  • Any Software Engineer that wants to level up, particularly in the roles of tech-leads and architects
  • Any Visionary, CEO or product-leader tackling challenging problems with software


About me, your host, Shane Brinkman-Davis Delamore: I write programming languages (e.g. CaffeineScript) and app creation platforms (e.g. ArtSuite) and in my day job (GenUI.com) I help visionaries maximize their impact through software.


AI use notes: I use Discript and sometimes use their voice-fill tech to touch up small portions of my recording. I also use image generators (like MidJourney) for cover and example images. I'll also use ChatGpt for ideation and idea refinement, but the ideas are all mine. Further, I don't read from a script when I do the recording.

Hosted on Acast. See acast.com/privacy for more information.

]]>

All problems are solvable with enough knowledge -- and software is the most powerful knowledge tool ever invented.


Code & Optimism is a show focused on solving problems faster with software. I created this series to discuss topics related to my passion of accelerating our ability to solve problems with software. In this show I'll dive into everything from practical tips to philosophical musings about optimism, solving problems and this wonderful tool called software and how we can become ever better at software engineering.


Who is it for?

  • Any Software Engineer that wants to level up, particularly in the roles of tech-leads and architects
  • Any Visionary, CEO or product-leader tackling challenging problems with software


About me, your host, Shane Brinkman-Davis Delamore: I write programming languages (e.g. CaffeineScript) and app creation platforms (e.g. ArtSuite) and in my day job (GenUI.com) I help visionaries maximize their impact through software.


AI use notes: I use Discript and sometimes use their voice-fill tech to touch up small portions of my recording. I also use image generators (like MidJourney) for cover and example images. I'll also use ChatGpt for ideation and idea refinement, but the ideas are all mine. Further, I don't read from a script when I do the recording.

Hosted on Acast. See acast.com/privacy for more information.

]]> false Shane Delamore info+65808a8eab7b4300163eef72@mg-eu.acast.com 65808a8eab7b4300163eef72 code-and-optimism episodic https://assets.pippa.io/shows/65808a8eab7b4300163eef72/1728833182335-c2e727ab-79ba-4f28-9104-3710d7ddad35.jpeg https://shows.acast.com/code-and-optimism <![CDATA[Code & Optimism]]> <![CDATA[Forget Correctness & Code Quality, Be Verifiable and Agile]]> Mon, 04 Nov 2024 20:28:33 GMT 26:17 6729299aa85028c1d710d63e false https://medium.com/p/c3bffe94ccc3 6729299aa85028c1d710d63e 65808a8eab7b4300163eef72 forget-correctness-code-quality-be-verifiable-and-agile the true first principles of software engineering full 1 40 Why ‘Correctness’ and ‘Code Quality’ Are Misleading: Embrace Verifiability and Agility


In this episode of Code and Optimism, I argue for replacing the subjective terms ‘correctness’ and ‘code quality’ with ‘verifiability’ and ‘agility’ in software development. I explain how these alternatives provide objective measures and practical benefits, driving impactful and adaptable projects. I outline the importance of solving meaningful problems, setting good requirements, and managing code effectively for agility while verifying impact through automation. Discover how pursuing correctness and code quality has been leading your team astray, and rediscover what truly matters for maximizing your impact on the world.


00:00 Forget Correctness and Code Quality

01:53 Start with Solving a Real World Problem

05:05 Good Requirements

07:21 Correctness vs Verifiability

12:12 Quality vs Agility

14:37 Lint Rant

17:26 Agility and Code Debt

22:15 Verifiability AND Agility

25:51 Outro


Related:


Hosted on Acast. See acast.com/privacy for more information.

]]> Why ‘Correctness’ and ‘Code Quality’ Are Misleading: Embrace Verifiability and Agility


In this episode of Code and Optimism, I argue for replacing the subjective terms ‘correctness’ and ‘code quality’ with ‘verifiability’ and ‘agility’ in software development. I explain how these alternatives provide objective measures and practical benefits, driving impactful and adaptable projects. I outline the importance of solving meaningful problems, setting good requirements, and managing code effectively for agility while verifying impact through automation. Discover how pursuing correctness and code quality has been leading your team astray, and rediscover what truly matters for maximizing your impact on the world.


00:00 Forget Correctness and Code Quality

01:53 Start with Solving a Real World Problem

05:05 Good Requirements

07:21 Correctness vs Verifiability

12:12 Quality vs Agility

14:37 Lint Rant

17:26 Agility and Code Debt

22:15 Verifiability AND Agility

25:51 Outro


Related:


Hosted on Acast. See acast.com/privacy for more information.

]]> Organic Modular Design Organic Modular Design Fri, 11 Oct 2024 09:51:21 GMT 28:49 6708f519011dc7d6443dd33b false https://shows.acast.com/code-and-optimism/episodes/organic-modular-design 6708f519011dc7d6443dd33b 65808a8eab7b4300163eef72 organic-modular-design The Lifecycle of Modular Design in Real-World Projects full 1 39 Most software teams are drowning in complexity—but with your help, we can change that story.

In my latest episode of Code and Optimism, I share a little-known secret: modular design, when done right, isn’t just for architects or the early stages of a project. It’s something every developer should be doing every day. I call it Organic Modular Design—a real-world approach where modules grow naturally as the code evolves.

Here’s the kicker: if we’re not constantly maximizing modularity—from the project’s inception through the very last code edit—our project’s complexity will spiral out of control. But it doesn’t have to be this way. With a few key principles, we can stop the chaos and keep our codebase healthy and scalable.

The payoff? Logarithmic complexity scaling instead of the quadratic-scaling mess that kills most projects. Curious? This episode might just change the way you code forever.

As always, I don't claim to have all the answers. Anyone who says they do is either a fool or is selling something. For my part, I'm always trying to learn how to solve problems faster with software, and I'd love to learn with you. Send some feedback my way. Let's talk!

Timestamps

00:00 Introduction to Modular Design

00:55 Organic Modular Design (OMD)

02:12 The Modular Life Cycle

02:49 DRY Principle and Function Modules

04:43 File and Folder Modules

07:46 Encapsulation and Interface

17:07 Packaging Modules

23:58 Conclusion and Key Takeaways


Tool Recommendations

Related Episodes

Related Blog post:

Hosted on Acast. See acast.com/privacy for more information.

]]> Most software teams are drowning in complexity—but with your help, we can change that story.

In my latest episode of Code and Optimism, I share a little-known secret: modular design, when done right, isn’t just for architects or the early stages of a project. It’s something every developer should be doing every day. I call it Organic Modular Design—a real-world approach where modules grow naturally as the code evolves.

Here’s the kicker: if we’re not constantly maximizing modularity—from the project’s inception through the very last code edit—our project’s complexity will spiral out of control. But it doesn’t have to be this way. With a few key principles, we can stop the chaos and keep our codebase healthy and scalable.

The payoff? Logarithmic complexity scaling instead of the quadratic-scaling mess that kills most projects. Curious? This episode might just change the way you code forever.

As always, I don't claim to have all the answers. Anyone who says they do is either a fool or is selling something. For my part, I'm always trying to learn how to solve problems faster with software, and I'd love to learn with you. Send some feedback my way. Let's talk!

Timestamps

00:00 Introduction to Modular Design

00:55 Organic Modular Design (OMD)

02:12 The Modular Life Cycle

02:49 DRY Principle and Function Modules

04:43 File and Folder Modules

07:46 Encapsulation and Interface

17:07 Packaging Modules

23:58 Conclusion and Key Takeaways


Tool Recommendations

Related Episodes

Related Blog post:

Hosted on Acast. See acast.com/privacy for more information.

]]> Modular Testing Modular Testing Sat, 10 Aug 2024 08:51:24 GMT 26:35 66b71f5c491100609f6ad37a false https://shows.acast.com/code-and-optimism/episodes/modular-testing 66b71f5c491100609f6ad37a 65808a8eab7b4300163eef72 modular-testing Stop unit testing! full 1 38 Why You Should Stop Doing Unit and Integration Testing - Embrace Modular Testing Instead!


In this episode, I challenge conventional testing methods and present a new approach—modular testing. I argue against traditional unit, integration, and system end-to-end testing, highlighting their inefficiencies and complexities. Instead, I introduce modular testing, where the focus is on testing only the external API of a module. This method aligns with good modular design principles and significantly reduces test maintenance effort. By testing just the API, the process becomes simpler, more agile, and scalable. I provide insights into the five essential elements of modular design and discuss how modular testing can enhance overall software quality while keeping testing efforts manageable.


  • 00:00 Introduction to Automated Testing
  • 01:03 Standard Testing - A Review
  • 01:43 Unit Testing
  • 03:06 Integration Testing
  • 04:57 System Testing
  • 06:59 Modular Testing
  • 08:25 Modular Design Recap
  • 12:11 Benefits of Modular Testing
  • 16:30 Modular Testing IS Unit Testing, but better...
  • 18:40 Modular Testing IS Integration Testing, but better...
  • 22:46 System Testing? It's Modules All the Way Down...
  • 24:23 Conclusion and Final Thoughts
  • 25:48 Outro


Related C&O Episodes:


Hosted on Acast. See acast.com/privacy for more information.

]]> Why You Should Stop Doing Unit and Integration Testing - Embrace Modular Testing Instead!


In this episode, I challenge conventional testing methods and present a new approach—modular testing. I argue against traditional unit, integration, and system end-to-end testing, highlighting their inefficiencies and complexities. Instead, I introduce modular testing, where the focus is on testing only the external API of a module. This method aligns with good modular design principles and significantly reduces test maintenance effort. By testing just the API, the process becomes simpler, more agile, and scalable. I provide insights into the five essential elements of modular design and discuss how modular testing can enhance overall software quality while keeping testing efforts manageable.


  • 00:00 Introduction to Automated Testing
  • 01:03 Standard Testing - A Review
  • 01:43 Unit Testing
  • 03:06 Integration Testing
  • 04:57 System Testing
  • 06:59 Modular Testing
  • 08:25 Modular Design Recap
  • 12:11 Benefits of Modular Testing
  • 16:30 Modular Testing IS Unit Testing, but better...
  • 18:40 Modular Testing IS Integration Testing, but better...
  • 22:46 System Testing? It's Modules All the Way Down...
  • 24:23 Conclusion and Final Thoughts
  • 25:48 Outro


Related C&O Episodes:


Hosted on Acast. See acast.com/privacy for more information.

]]> The Guiding Principle of Automated Testing The Guiding Principle of Automated Testing Sat, 27 Jan 2024 09:40:58 GMT 7:45 65b4cfaa912de90017f79e73 false https://shows.acast.com/code-and-optimism/episodes/e37-the-guiding-principle-of-automated-testing 65b4cfaa912de90017f79e73 65808a8eab7b4300163eef72 e37-the-guiding-principle-of-automated-testing full 1 37 Before we can get into the nuts and bolts about how to do automated testing well, we have to understand what it means to do testing well. And for that, we need a guiding principle. 


Automated testing, like so many aspects of solving problems with software, is a path of mastery. You can forever get better and better at it, and the magnitude of potential benefits are unbounded. However, it will be difficult to impossible to continually make progress without some guiding light showing us what way to go. A well constructed guiding principle can do exactly that for us. It provides a semi-objective way to assess progress and help make choices along the way.


In this episode I synthesize the benefits we explored in the last episode with some observations about the essential nature of automated testing. From that I propose a guiding principle that should help us all agree on what is and is not good automated testing.


Timestamps

0:44 - definition

1:17 - as proof

2:23 - metacode

3:00 - recap of benefits

3:56 - The Guiding Principle

5:28 - summary

6:40 - next time

7:08 - outro


Related C&O Episodes:


Hosted on Acast. See acast.com/privacy for more information.

]]> Before we can get into the nuts and bolts about how to do automated testing well, we have to understand what it means to do testing well. And for that, we need a guiding principle. 


Automated testing, like so many aspects of solving problems with software, is a path of mastery. You can forever get better and better at it, and the magnitude of potential benefits are unbounded. However, it will be difficult to impossible to continually make progress without some guiding light showing us what way to go. A well constructed guiding principle can do exactly that for us. It provides a semi-objective way to assess progress and help make choices along the way.


In this episode I synthesize the benefits we explored in the last episode with some observations about the essential nature of automated testing. From that I propose a guiding principle that should help us all agree on what is and is not good automated testing.


Timestamps

0:44 - definition

1:17 - as proof

2:23 - metacode

3:00 - recap of benefits

3:56 - The Guiding Principle

5:28 - summary

6:40 - next time

7:08 - outro


Related C&O Episodes:


Hosted on Acast. See acast.com/privacy for more information.

]]> 3 Surprising Benefits of Automated Testing 3 Surprising Benefits of Automated Testing Mon, 18 Dec 2023 18:11:28 GMT 7:20 65808b502fdc17001762a57a false https://youtu.be/pBNzAB45_Hc 65808b502fdc17001762a57a 65808a8eab7b4300163eef72 surprising-benefits-of-automated-testing How I came to love automated testing... full 1 36 I have a confession to make. I love automated testing. When done well, automated tests can help write better code, provide the best possible documentation, and most of all, automated testing can help write code faster:


Code + Tests 
SOLVES PROBLEMS FASTER
than just Code


Seriously. 


And, when done well, writing and maintaining automated tests suites can actually be a lot of fun. After all, it’s a chance to get paid to play with your code…


Timestamps

  • 0:19 - #1 Write better code
  • 1:43 - #2 Best form of Doc
  • 3:32 - #3 Accelerate your Code
  • 4:41 - Imikimi story - an cautionary tail
  • 6:00 - Recap
  • 6:13 - Why I Love writing tests…
  • 7:02 - Outro


Related C&O Episodes:

Hosted on Acast. See acast.com/privacy for more information.

]]> I have a confession to make. I love automated testing. When done well, automated tests can help write better code, provide the best possible documentation, and most of all, automated testing can help write code faster:


Code + Tests 
SOLVES PROBLEMS FASTER
than just Code


Seriously. 


And, when done well, writing and maintaining automated tests suites can actually be a lot of fun. After all, it’s a chance to get paid to play with your code…


Timestamps

  • 0:19 - #1 Write better code
  • 1:43 - #2 Best form of Doc
  • 3:32 - #3 Accelerate your Code
  • 4:41 - Imikimi story - an cautionary tail
  • 6:00 - Recap
  • 6:13 - Why I Love writing tests…
  • 7:02 - Outro


Related C&O Episodes:

Hosted on Acast. See acast.com/privacy for more information.

]]>