POPULARITY
CitationsCrafting Science: A Sociohistory of the Quest for the Genetics of Cancer, Joan Fujimura, 1997. Contingency, Irony, and Solidarity, Richard Rorty, 1989. Smalltalk Best Practice Patterns, Kent Beck, 1996.Ward Cunningham on "working the program", 2004.The Mathematical Experience, Phillip J. Davis and Reuben Hersh, 1980."Elephant Talk", King Crimson, 1981 (audio)."Hammock-Driven Development", Rich Hickey, 2010 (video)."What is Hammock-Driven Development?", Keagan Stokoe, 2021CreditsImage of contrasting words from Flickr user andeecollard, Creative Commons License CC BY-SA 2.0
In this episode of the iPhreaks Show, the panel discusses iOS and other development books that are great resources to help during the course of the iOS developers’ journey. Sponsor CacheFly Panel Alex Bush Charles Wood Links iOS Programming: The Big Nerd Ranch Guide Cocoa Design Patterns Pragmatic Programmer Soft Skills Complete Software Developer’s Career Guide MaxCoder’s Guid to Finding Your Dream Developer Job Refactoring Working Effectively with Legacy Code Clean Code Design Patterns Clean Architecture Structure and Interpretation of Computer Programs Growing Object Oriented Programming, Guided by Tests Reactive Programming with RxJS Practical Object-Oriented Design Using Ruby Test Driven Development by Example SmallTalk Best Practice Patterns Extreme Programming Explained Picks Alex Bush: Robert Heinlein, Author Charles Wood: Breath of the Wild The Church of Jesus Christ of Latter-day Saints Follow iPhreaks Show on Twitter > @iphreaks
In this episode of the iPhreaks Show, the panel discusses iOS and other development books that are great resources to help during the course of the iOS developers’ journey. Sponsor CacheFly Panel Alex Bush Charles Wood Links iOS Programming: The Big Nerd Ranch Guide Cocoa Design Patterns Pragmatic Programmer Soft Skills Complete Software Developer’s Career Guide MaxCoder’s Guid to Finding Your Dream Developer Job Refactoring Working Effectively with Legacy Code Clean Code Design Patterns Clean Architecture Structure and Interpretation of Computer Programs Growing Object Oriented Programming, Guided by Tests Reactive Programming with RxJS Practical Object-Oriented Design Using Ruby Test Driven Development by Example SmallTalk Best Practice Patterns Extreme Programming Explained Picks Alex Bush: Robert Heinlein, Author Charles Wood: Breath of the Wild The Church of Jesus Christ of Latter-day Saints Follow iPhreaks Show on Twitter > @iphreaks
Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey
Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey
Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey
Ruby Tapas and Avoiding Code with Avdi Grimm Follow us on Twitter @techdoneright (https://twitter.com/tech_done_right), and please leave us a review on Apple Podcasts (https://itunes.apple.com/us/podcast/tech-done-right/id1195695341?mt=2)! Guest Avdi Grimm (https://twitter.com/avdi): Creator of the RubyTapas Screencast Series (https://www.rubytapas.com/) and author of Exceptional Ruby (http://exceptionalruby.com/) and Confident Ruby (http://www.confidentruby.com/). avdi.codes (https://avdi.codes/) Summary Avdi Grimm has been creating the RubyTapas screencast series for five years. In this episode Avdi and I talk about why he decided to do RubyTapas, and what makes a good episode. We also talk about the resources that helped us when we were learning to code. Then Avdi talks about his experience building the RubyTapas web site and explains how sometimes avoiding code can be the best business decision of all. Notes 01:20 - Starting and Sustaining RubyTapas 04:59 - Shorter Episodes Vs Longer Episodes 08:00 - Creating an Example for a Topic 10:49 - Future-proofing Episodes 12:51 - Helpful Resources When Avdi and Noel Were Learning How to Code - Programming Perl (The Camel Book) (https://en.wikipedia.org/wiki/Programming_Perl) - The Pragmatic Programmer (https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X) - Code Complete (https://www.amazon.com/Code-Complete-Practical-Handbook-Construction/dp/0735619670) - Smalltalk Best Practice Patterns (https://www.amazon.com/Smalltalk-Best-Practice-Patterns-Kent/dp/013476904X/ref=sr_1_1?s=books&ie=UTF8&qid=1508781341&sr=1-1&keywords=smalltalk+best+practice+patterns) - Ruby Midwest 2011 Confident Code by Avdi Grimm (https://www.youtube.com/watch?v=T8J0j2xJFgQ) 18:31 - Learning New Things Now; Online Marketing - Copyblogger (https://www.copyblogger.com/) 26:12 - Avoiding Code
02:37 - Dave Thomas Introduction Twitter Blog The Pragmatic Bookshelf 04:17 - How Dave Got Started in Programming 06:34 - Tools and Constraints “An Enthusiast’s Problem”? Is the focus on tools a form of cargo culting? Leadism Over Chosen Technologies and Its’ Effect on Innovation Switching Tools and Making Excuses 19:29 - Limerence Love and Limerence: The Experience of Being in Love by Dorothy Tennov Irrational Interest and Defensiveness 28:54 - Ruby = Happiness: Does it Hurt? 31:00 - Tools and Falling in Love with Tools Fear of Falling Behind; Fear of Irrelevancy Different Tools for Different Contexts 35:08 - When Do You Learn? When Do You Train? (Not Falling Behind) 38:01 - Choosing Similar Tools and Technologies vs Choosing Different Tools and Technologies Gulp => Grunt => Browserify Example Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt 43:36 - Relationships and Identities 46:08 - Looking Forward vs Looking Back (Knowing Your History) Resources, Curriculum: Structure and Interpretation of Computer Programs - 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson (SICP) Smalltalk Best Practice Patterns by Kent Beck Types and Programming Languages by Benjamin C. Pierce The Art of Computer Programming by Donald Knuth (Series) Communicating Sequential Processes (CSP) Brainstorming Example 01:01:48 - Is the rampant use of social media hindering the learning of big ideas? Self-Curation = Key 01:08:15 - How You Learn a Language / Decide You Like a Language Sudoku Solver Markdown Parser Picks Slack (Dave) Why Does E=mc2? (And Why Should We Care?) by Brian Cox and Jeff Forshaw (Dave) Philly Emerging Tech Conference (Dave)
02:37 - Dave Thomas Introduction Twitter Blog The Pragmatic Bookshelf 04:17 - How Dave Got Started in Programming 06:34 - Tools and Constraints “An Enthusiast’s Problem”? Is the focus on tools a form of cargo culting? Leadism Over Chosen Technologies and Its’ Effect on Innovation Switching Tools and Making Excuses 19:29 - Limerence Love and Limerence: The Experience of Being in Love by Dorothy Tennov Irrational Interest and Defensiveness 28:54 - Ruby = Happiness: Does it Hurt? 31:00 - Tools and Falling in Love with Tools Fear of Falling Behind; Fear of Irrelevancy Different Tools for Different Contexts 35:08 - When Do You Learn? When Do You Train? (Not Falling Behind) 38:01 - Choosing Similar Tools and Technologies vs Choosing Different Tools and Technologies Gulp => Grunt => Browserify Example Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt 43:36 - Relationships and Identities 46:08 - Looking Forward vs Looking Back (Knowing Your History) Resources, Curriculum: Structure and Interpretation of Computer Programs - 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson (SICP) Smalltalk Best Practice Patterns by Kent Beck Types and Programming Languages by Benjamin C. Pierce The Art of Computer Programming by Donald Knuth (Series) Communicating Sequential Processes (CSP) Brainstorming Example 01:01:48 - Is the rampant use of social media hindering the learning of big ideas? Self-Curation = Key 01:08:15 - How You Learn a Language / Decide You Like a Language Sudoku Solver Markdown Parser Picks Slack (Dave) Why Does E=mc2? (And Why Should We Care?) by Brian Cox and Jeff Forshaw (Dave) Philly Emerging Tech Conference (Dave)
02:37 - Dave Thomas Introduction Twitter Blog The Pragmatic Bookshelf 04:17 - How Dave Got Started in Programming 06:34 - Tools and Constraints “An Enthusiast’s Problem”? Is the focus on tools a form of cargo culting? Leadism Over Chosen Technologies and Its’ Effect on Innovation Switching Tools and Making Excuses 19:29 - Limerence Love and Limerence: The Experience of Being in Love by Dorothy Tennov Irrational Interest and Defensiveness 28:54 - Ruby = Happiness: Does it Hurt? 31:00 - Tools and Falling in Love with Tools Fear of Falling Behind; Fear of Irrelevancy Different Tools for Different Contexts 35:08 - When Do You Learn? When Do You Train? (Not Falling Behind) 38:01 - Choosing Similar Tools and Technologies vs Choosing Different Tools and Technologies Gulp => Grunt => Browserify Example Pragmatic Thinking and Learning: Refactor Your Wetware by Andy Hunt 43:36 - Relationships and Identities 46:08 - Looking Forward vs Looking Back (Knowing Your History) Resources, Curriculum: Structure and Interpretation of Computer Programs - 2nd Edition (MIT Electrical Engineering and Computer Science) by Harold Abelson (SICP) Smalltalk Best Practice Patterns by Kent Beck Types and Programming Languages by Benjamin C. Pierce The Art of Computer Programming by Donald Knuth (Series) Communicating Sequential Processes (CSP) Brainstorming Example 01:01:48 - Is the rampant use of social media hindering the learning of big ideas? Self-Curation = Key 01:08:15 - How You Learn a Language / Decide You Like a Language Sudoku Solver Markdown Parser Picks Slack (Dave) Why Does E=mc2? (And Why Should We Care?) by Brian Cox and Jeff Forshaw (Dave) Philly Emerging Tech Conference (Dave)
In this episode, Adam talks to Philip J. Sturgeon about designing and testing APIs at Ride. They also talk about building microservices with Go, and some of the new features coming in PHP 7. This episode is brought to you by Hired. Phil's Blog Ride Go JSON Patch RFC Recent changes to JSON API Troy Hunt on API versioning "Build APIs You Won't Hate", Phil's book "Dredd: Do Your HTTP API Justice" HATEOAS RAML "Smalltalk Best Practice Patterns" by Kent Beck Sponsored by Hired
Avdi Grimm 是 Ruby 社区知名的资深程序员,作者和社区领袖。在这期节目中我们请来 Avdi 来聊聊怎样突破“中级天花板”来达到更高的层次。 About Avdi Grimm: Avdi Grimm Avdi's Publications Ruby Rogues Growing Object Oriented Software Guided by Tests Practical Object Oriented Design in Ruby Smalltalk Best Practice Patterns Factoring How Developers Stop Learning: Rise of the Expert Beginner Go ahead and make a mess (Sandi Metz) Who I want to hire (Chad Fowler) I feel the opposite of burn out, interview with Chad Fowler Software Engineering Radio Pair Programming with me Corey Haines, Software Journeyman The hitchhiker's guide to the galaxy Wide Teams DivShot FantastiCal Domain Driven Design Destroy All Software RubyTapas Special Guest: Avdi Grimm.
Ben Orenstein is joined by David Heinemeier Hansson, the creator of Ruby on Rails and a partner at 37signals. David and Ben discuss David's normal day, his working relationship with Jason Fried, how their blog, Signal vs. Noise, is important to the company, how he got into programming, where he draws his inspiration from, some good books he's read and how he learns today, how he overcomes fear and why he takes risks, how he got into racing, why he enjoys it, what he learns from it, and how feedback loops and goal posts help you learn, inspire you, and help you know how good you are. They then go on to explore what David would, or wouldn't, change about Rails, and how he sees Rails evolving into the future. David also talks a little bit about the new product 37signals has in development, and 37signals' overall product strategy, coding at 37signals and his approach to providing guidance to the team, what role he plays on Rails core, what he cares about, and what he pays attention to, and much, much more. David's website Signal vs. Noise Domain-Driven Design: Tackling Complexity in the Heart of Software Patterns of Enterprise Application Architecture Refactoring: Improving the Design of Existing Code Extreme Programming Explained: Embrace Change Smalltalk Best Practice Patterns Code Complete: A Practical Handbook of Software Construction David Heinemeier Hansson's racing Sinatra Node.js Follow @thoughtbot, @dhh, and @r00k on twitter.
The Rogues have a follow-up conversation about Kent Beck's Smalltalk Best Practice Patterns book.
The Rogues have a follow-up conversation about Kent Beck's Smalltalk Best Practice Patterns book.
In this Book Club episode, the Rogues talk to Kent Beck about his book, Smalltalk Best Practice Patterns.
In this Book Club episode, the Rogues talk to Kent Beck about his book, Smalltalk Best Practice Patterns.
In this Book Club episode, the Rogues talk to Kent Beck about his book, Smalltalk Best Practice Patterns.