InfoQ Homepage Software Craftsmanship Content on InfoQ
-
Legacy Code: Using Domain-Driven Design to Carve Out Areas of Sanity
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
/presentations/Legacy-Code-DDD/en/smallimage/Robert.JPG)
-
The FT Web App: Coding Responsively
Rob Shilston discusses the need for coding responsively, not just designing responsively, along with the development process in place at Financial Times.
/presentations/FT-Coding-Responsively/en/smallimage/Robert.JPG)
-
High-quality, Impactful, Fast UX Research for Engineers
Tomer Sharon discusses the psychology of attitude & behavior and shares tips for conducting a high-quality, impactful, and fast UX research.
/presentations/UX-Research/en/smallimage/Tom.JPG)
-
3 Patterns for Cleaner Code
Cory Maksymchuk introduces 3 patterns for writing cleaner code: Predicates, Classifiers, and Transformer.
/presentations/3-Patterns-Cleaner-Code/en/smallimage/Cory.JPG)
-
Assessing and Improving Model Quality
Darius Silingas emphasized the need for quality models in MDD, presenting a number of anti-patterns along with best practices for creating them.
/presentations/Model-Quality/en/smallimage/Darius.JPG)
-
Software for Your Head
Jim McCarthy makes a passionate call for developers to rise up to their call and make their software great, sharing their light with the entire world.
/presentations/Call-for-Great-Software/en/smallimage/Jim2.jpg)
-
The Ideal Programmer - Why They Don't Exist and How to Manage Without Them?
Mike Williams outlines some of the main characteristics that make developers and teams perform better than the average.
/presentations/Ideal-Programmer/en/smallimage/Mike.JPG)
-
Entirely Predictable Failures
Poul-Henning Kamp considers that if developers are not getting better, we are going to repeat many of the major IT project failures. He exemplifies with major Denmark project failures.
/presentations/Predictable-Failures/en/smallimage/Poul.JPG)
-
Technical Debt, Process and Culture
Michael Feathers advices on creating an organizational process and culture that can enhance software development in a way that reduces technical debt.
/presentations/Technical-Debt-Process-Culture/en/smallimage/Michael.JPG)
-
Accruing Technical Debt: Practical Decision-Making and Its Business Relevance
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
/presentations/Technical-Debt-Practices/en/smallimage/Ebe.JPG)
-
Beauty is in The Eye of the Beholder
Alex Papadimoulis attempts to define ugly code, how one can recognize it, providing advice on avoiding writing such code and refactoring old code to get rid of it.
/presentations/Ugly-Code/en/smallimage/Alex.JPG)
/presentations/From-Crap-to-App/en/smallimage/Lee.JPG)