Skip to content

Agile Design = Adaptive-Lean Design

Non multa sed multum

  • Home
  • Adaptive Design
  • Adaptive products
  • Practices
  • Mission
  • Agile& Blog

Tag: Technical Debt

Upgrading Refactoring: Clean vs Adapt, Clean Code/Refactor/Re-Design

October 21, 2014 Valentin Tudor Mocanu

If I had to pick one thing that sets XP apart from other approaches, it would be refactoring, the ongoing redesign of software to improve

Continue reading

Follow Agile Design = Adaptive-Lean Design on WordPress.com

Recent Posts

  • Software Mind Palace
  • Evolutionary design?
  • TDD trick: getting effective & efficient design
  • Architecture: 2 n-dimensional layers
  • Refactoring: strategy & collaborative work
  • Limits of inspected-in quality
  • The One-Question Programming Interview
  • New product and Minimum Viable Process with DAD
  • Software architecture – searching for a better definition
  • Just in time and Envisioning versus complexity
  • DRY principle beyond small talks
  • Before DevOps: Delivering more by delivering less
  • Two dimensions: Just in time and Envisioning
  • JIT – Just in time and Software Development
  • “Sending a probe”: alternative to stubs, mocks and service virtualization
  • A product it is … not a product.
  • Agile design events and decisions options
  • Upgrading Refactoring: Clean vs Adapt, Clean Code/Refactor/Re-Design
  • Reactive & Adaptive Products: built-in feedback
  • Roadmap to an agile design

Follow me on Twitter

My Tweets

Enter your email address to follow this blog and receive notifications of new posts by email.

Authors

  • Valentin Tudor Mocanu

© Copyright 2014-2019 Valentin Tudor Mocanu

Blog at WordPress.com.
  • Follow Following
    • Agile Design = Adaptive-Lean Design
    • Already have a WordPress.com account? Log in now.
    • Agile Design = Adaptive-Lean Design
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar