
Sign up to save your podcasts
Or


Having spent a career as a software engineer, I encountered a world of problems in hundreds of different industries. I knew nothing about the industries at all, but what I did know was that a method to gather their needs, analyze them, design something to solve their needs and build to that design worked. We call that a methodology. When I looked outside of the engineering space, I found a few implementations of methodologies in particular, business methodologies used in large organizations. I guess I naturally use methodologies without thinking, but it provides a way to codify something repeatable. In this episode Im going to offer you a methodology that I use, that has helped me become and continue to be unconstrained.
By [email protected] (Earl Evans and Randy Kindig)5
1010 ratings
Having spent a career as a software engineer, I encountered a world of problems in hundreds of different industries. I knew nothing about the industries at all, but what I did know was that a method to gather their needs, analyze them, design something to solve their needs and build to that design worked. We call that a methodology. When I looked outside of the engineering space, I found a few implementations of methodologies in particular, business methodologies used in large organizations. I guess I naturally use methodologies without thinking, but it provides a way to codify something repeatable. In this episode Im going to offer you a methodology that I use, that has helped me become and continue to be unconstrained.

309 Listeners

38 Listeners

895 Listeners

107 Listeners

20 Listeners

129 Listeners

165 Listeners

984 Listeners

22 Listeners

82 Listeners

197 Listeners

142 Listeners

28 Listeners

5,475 Listeners

18 Listeners