Musts
Contents
The Lean StartupThe True Corruption of AgileClean Code: A Handbook of Agile Software CraftsmanshipThe Clean Coder: A Code of Conduct for Professional ProgrammersClean Architecture: A Craftsman's Guide to Software Structure and DesignEpics, Stories, Subtasks⌠whatâs the difference?Epics, Stories, Subtasks⌠in Various Tools of ChoiceWhat Is a Story, and Where Does It Come From?Working Effectively with Legacy CodeLegacy Code - North Fireside ChatDesign Patterns: Elements of Reusable Object-Oriented SoftwareThe Five Elements of User Experience
The Lean Startup
Eric Reis, Currency; 1st Edition,
Lean thinking defines value as providing benefit to the customer; anything else is waste.A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.The value hypothesis tests whether a product or service really delivers value to customers once they are using it.
The True Corruption of Agile
Robert C. Martin, The Clean Code Blog
âŚagile is a culture, not a set of practicesâŚ
Clean Code: A Handbook of Agile Software Craftsmanship
Robert C. Martin, Pearson; 1st edition ( )
Even bad code can function. But if code isnât clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesnât have to be that way.
The Clean Coder: A Code of Conduct for Professional Programmers
Robert C. Martin, Pearson; 1st edition ( )
Programmers who endure and succeed amidst swirling uncertainty and nonstop pressure share a common attribute: They care deeply about the practice of creating software. They treat it as a craft. They are professionals.
Clean Architecture: A Craftsman's Guide to Software Structure and Design
Robert C. Martin, Pearson; 1st edition ( )
ââŚThe rules of software architecture are the rules of ordering and assembling the building blocks of programs. And since those building blocks are universal and havenât changed, the rules for ordering them are likewise universal and changeless.But one thing has changed: Back then, we didnât know what the rules were. Consequently, we broke them, over and over again. Now, with half a century of experience behind us, we have a grasp of those rules.And it is those rulesâthose timeless, changeless, rulesâthat this book is all about.â
Epics, Stories, Subtasks⌠whatâs the difference?
Kelly Albrecht, Last Call Media,
Commitments are the currency of trustâŚ
Epics, Stories, Subtasks⌠in Various Tools of Choice
Kelly Albrecht, Last Call Media,
Epics in Jira are just a type of issue meaning the type can be selected on issue creation. Epics can also be created from the Epics pane of the backlog. Stories and Tasks can be âtaggedâ to Epics from their issue during issue creation or they can be dragged into an Epic pane from the Backlog interface. Before Subtasking, Stories can also be split into smaller stories through a handy interface in the backlog. Once the time comes for subtasking, the interface for that is within each Story/Task.
What Is a Story, and Where Does It Come From?
Mark W. Travis, The Wrap,
We are all storytellers; the storyâs first teller is our self and the first listener is our self
Working Effectively with Legacy Code
Michael Feathers, Prentice Hall, 1st ed., 2005
Legacy code is code without tests.
Legacy Code - North Fireside Chat
Robert C. Martin, YouTube,
![Video preview](https://i.ytimg.com/vi/Va79bYiP0us/hqdefault.jpg)
Design Patterns: Elements of Reusable Object-Oriented Software
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Addison Wesley, 1st ed, 1995
The minimum is critical knowledge.
The Five Elements of User Experience
Jesse James Garret, Peachpit Press
Smart organizations recognize that Web design is more than just creating clean code and sharp graphics. A site that really works fulfills your strategic objectives while meeting the needs of your users. Even the best content and the most sophisticated technology won't help you balance those goals without a cohesive, consistent user experience to support it
Â