狠狠撸shows by User: kauerrolemodel
/
http://www.slideshare.net/images/logo.gif狠狠撸shows by User: kauerrolemodel
/
Sat, 10 Sep 2016 02:51:20 GMT狠狠撸Share feed for 狠狠撸shows by User: kauerrolemodelCocoaConf Relationship Between Agility and Expertise
/slideshow/cocoaconf-relationship-between-agility-and-expertise/65879025
cocoaconfrelationshipbetweenagilityandexpertise-160910025120 Many Geeks underestimate the power of collaboration and all of the skills they need to become experts in their craft. They have heard of "Agile" and sometimes do something that smells like it. Software development is about managing complex problems over some period of time to produce something that serves people: the end users, the stakeholders, our colleagues, and ourselves.
Getting better at it - becoming an expert - is not just about obtaining and applying knowledge.
We will discuss why Agility, in its deepest form, contributes to the growth of Expertise and the service of people.]]>
Many Geeks underestimate the power of collaboration and all of the skills they need to become experts in their craft. They have heard of "Agile" and sometimes do something that smells like it. Software development is about managing complex problems over some period of time to produce something that serves people: the end users, the stakeholders, our colleagues, and ourselves.
Getting better at it - becoming an expert - is not just about obtaining and applying knowledge.
We will discuss why Agility, in its deepest form, contributes to the growth of Expertise and the service of people.]]>
Sat, 10 Sep 2016 02:51:20 GMT/slideshow/cocoaconf-relationship-between-agility-and-expertise/65879025kauerrolemodel@slideshare.net(kauerrolemodel)CocoaConf Relationship Between Agility and ExpertisekauerrolemodelMany Geeks underestimate the power of collaboration and all of the skills they need to become experts in their craft. They have heard of "Agile" and sometimes do something that smells like it. Software development is about managing complex problems over some period of time to produce something that serves people: the end users, the stakeholders, our colleagues, and ourselves.
Getting better at it - becoming an expert - is not just about obtaining and applying knowledge.
We will discuss why Agility, in its deepest form, contributes to the growth of Expertise and the service of people.<img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/cocoaconfrelationshipbetweenagilityandexpertise-160910025120-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Many Geeks underestimate the power of collaboration and all of the skills they need to become experts in their craft. They have heard of "Agile" and sometimes do something that smells like it. Software development is about managing complex problems over some period of time to produce something that serves people: the end users, the stakeholders, our colleagues, and ourselves.
Getting better at it - becoming an expert - is not just about obtaining and applying knowledge.
We will discuss why Agility, in its deepest form, contributes to the growth of Expertise and the service of people.
]]>
3954https://cdn.slidesharecdn.com/ss_thumbnails/cocoaconfrelationshipbetweenagilityandexpertise-160910025120-thumbnail.jpg?width=120&height=120&fit=boundspresentationBlackhttp://activitystrea.ms/schema/1.0/posthttp://activitystrea.ms/schema/1.0/posted0The Relationship Between Agility and Expertise
/slideshow/the-relationship-between-agility-and-expertise/48593275
therelationshipbetweenagilityandexpertise-150526055929-lva1-app6892 Some people seem to think that following an Agile process will get you good software. The reality is that Software Craftsmanship is found in the work produced, not the process followed. The Agile Manifesto hints at this, but many have missed it.
How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to look at how the key concepts of Agile Software Development, the makeup of your team, and the nature of your delivery goals should affect each other to build good software.
There is a difference between producing a "consumable app" and producing a "software asset" and the relationship between expertise and agility is crucial to understand, especially for the latter.]]>
Some people seem to think that following an Agile process will get you good software. The reality is that Software Craftsmanship is found in the work produced, not the process followed. The Agile Manifesto hints at this, but many have missed it.
How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to look at how the key concepts of Agile Software Development, the makeup of your team, and the nature of your delivery goals should affect each other to build good software.
There is a difference between producing a "consumable app" and producing a "software asset" and the relationship between expertise and agility is crucial to understand, especially for the latter.]]>
Tue, 26 May 2015 05:59:29 GMT/slideshow/the-relationship-between-agility-and-expertise/48593275kauerrolemodel@slideshare.net(kauerrolemodel)The Relationship Between Agility and ExpertisekauerrolemodelSome people seem to think that following an Agile process will get you good software. The reality is that Software Craftsmanship is found in the work produced, not the process followed. The Agile Manifesto hints at this, but many have missed it.
How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to look at how the key concepts of Agile Software Development, the makeup of your team, and the nature of your delivery goals should affect each other to build good software.
There is a difference between producing a "consumable app" and producing a "software asset" and the relationship between expertise and agility is crucial to understand, especially for the latter.<img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/therelationshipbetweenagilityandexpertise-150526055929-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Some people seem to think that following an Agile process will get you good software. The reality is that Software Craftsmanship is found in the work produced, not the process followed. The Agile Manifesto hints at this, but many have missed it.
How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to look at how the key concepts of Agile Software Development, the makeup of your team, and the nature of your delivery goals should affect each other to build good software.
There is a difference between producing a "consumable app" and producing a "software asset" and the relationship between expertise and agility is crucial to understand, especially for the latter.
]]>
10331https://cdn.slidesharecdn.com/ss_thumbnails/therelationshipbetweenagilityandexpertise-150526055929-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=boundspresentationBlackhttp://activitystrea.ms/schema/1.0/posthttp://activitystrea.ms/schema/1.0/posted0Software Craftsmanship: Agile Is Not Enough
/slideshow/agilenough/37729870
agileisnotenough-140806120308-phpapp01 Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.]]>
Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.]]>
Wed, 06 Aug 2014 12:03:07 GMT/slideshow/agilenough/37729870kauerrolemodel@slideshare.net(kauerrolemodel)Software Craftsmanship: Agile Is Not EnoughkauerrolemodelSome people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.<img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agileisnotenough-140806120308-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.
]]>
17924https://cdn.slidesharecdn.com/ss_thumbnails/agileisnotenough-140806120308-phpapp01-thumbnail.jpg?width=120&height=120&fit=boundspresentationBlackhttp://activitystrea.ms/schema/1.0/posthttp://activitystrea.ms/schema/1.0/posted0UITableView Pain Points
/slideshow/table-view-pain-points/34515002
tableviewpainpoints-140510094734-phpapp02 Most iOS apps use one or more UITableViews for at least some portion of their user interface. Unfortunately, UITableViewController code can often be home to monstrous if/else constructs employed to handle cell configuration and user interaction. This talk will illustrate the typical issues encountered with table view code. Whether form-like table views with a fixed number of rows, such as those found in settings views or those used to edit object data, or dynamic tables with multiple sections and rows within each section, you'll learn how to produce concise, readable, and powerful code.]]>
Most iOS apps use one or more UITableViews for at least some portion of their user interface. Unfortunately, UITableViewController code can often be home to monstrous if/else constructs employed to handle cell configuration and user interaction. This talk will illustrate the typical issues encountered with table view code. Whether form-like table views with a fixed number of rows, such as those found in settings views or those used to edit object data, or dynamic tables with multiple sections and rows within each section, you'll learn how to produce concise, readable, and powerful code.]]>
Sat, 10 May 2014 09:47:34 GMT/slideshow/table-view-pain-points/34515002kauerrolemodel@slideshare.net(kauerrolemodel)UITableView Pain PointskauerrolemodelMost iOS apps use one or more UITableViews for at least some portion of their user interface. Unfortunately, UITableViewController code can often be home to monstrous if/else constructs employed to handle cell configuration and user interaction. This talk will illustrate the typical issues encountered with table view code. Whether form-like table views with a fixed number of rows, such as those found in settings views or those used to edit object data, or dynamic tables with multiple sections and rows within each section, you'll learn how to produce concise, readable, and powerful code.<img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tableviewpainpoints-140510094734-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Most iOS apps use one or more UITableViews for at least some portion of their user interface. Unfortunately, UITableViewController code can often be home to monstrous if/else constructs employed to handle cell configuration and user interaction. This talk will illustrate the typical issues encountered with table view code. Whether form-like table views with a fixed number of rows, such as those found in settings views or those used to edit object data, or dynamic tables with multiple sections and rows within each section, you'll learn how to produce concise, readable, and powerful code.
]]>
6523https://cdn.slidesharecdn.com/ss_thumbnails/tableviewpainpoints-140510094734-phpapp02-thumbnail.jpg?width=120&height=120&fit=boundspresentationWhitehttp://activitystrea.ms/schema/1.0/posthttp://activitystrea.ms/schema/1.0/posted0Software Craftsmanship: Agile is Not Enough
/slideshow/software-craftsmanship-agile-is-not-enough/34514792
agileisnotenough-140510093801-phpapp02 Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.]]>
Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.]]>
Sat, 10 May 2014 09:38:01 GMT/slideshow/software-craftsmanship-agile-is-not-enough/34514792kauerrolemodel@slideshare.net(kauerrolemodel)Software Craftsmanship: Agile is Not EnoughkauerrolemodelSome people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.<img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/agileisnotenough-140510093801-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /><br> Some people seem to think that following an Agile process will get you good software. But, the reality is that Software Craftsmanship is found in the work produced, not in the process followed. The Agile Manifesto hints at this, but many have missed it. How do you get that quality up there, consistently keep it there, and keep raising the bar? Through a combination of some discussion on the nature of Skills Acquisition, and an analysis of common practices in software development (from Tests to Pull Requests to Pair Programming), we鈥檒l paint a picture of how to become a true expert that you can鈥檛 get from 鈥淎gile alone鈥�.
]]>
10453https://cdn.slidesharecdn.com/ss_thumbnails/agileisnotenough-140510093801-phpapp02-thumbnail.jpg?width=120&height=120&fit=boundspresentationWhitehttp://activitystrea.ms/schema/1.0/posthttp://activitystrea.ms/schema/1.0/posted0https://cdn.slidesharecdn.com/profile-photo-kauerrolemodel-48x48.jpg?cb=1522931499Sets and directs the vision and implementation of the world's first and premiere eXtreme Programming Software Studio(tm) where software craftsmen, journeymen, and apprentices build unusually adaptable software that meets our clients' needs. Also consults to clients who want to improve their own software development process.
RoleModel Software creates custom web and mobile applications, delivering a user experience that enables our customers to achieve a higher return on their investment. You bring the business knowledge and unique ideas. We bring the technical expertise and experience to deliver those ideas in working software.
RoleModel鈥檚 team has deep and varied skills in both 鈥�...http://rolemodelsoftware.comhttps://cdn.slidesharecdn.com/ss_thumbnails/cocoaconfrelationshipbetweenagilityandexpertise-160910025120-thumbnail.jpg?width=320&height=320&fit=boundsslideshow/cocoaconf-relationship-between-agility-and-expertise/65879025CocoaConf Relationship...https://cdn.slidesharecdn.com/ss_thumbnails/therelationshipbetweenagilityandexpertise-150526055929-lva1-app6892-thumbnail.jpg?width=320&height=320&fit=boundsslideshow/the-relationship-between-agility-and-expertise/48593275The Relationship Betwe...https://cdn.slidesharecdn.com/ss_thumbnails/agileisnotenough-140806120308-phpapp01-thumbnail.jpg?width=320&height=320&fit=boundsslideshow/agilenough/37729870Software Craftsmanship...