👋 Hi, I’m @enguerran I’m a senior web developer interested in well-crafted web application ✂️, front-end architecure 🧩, useful, used and usable interfaces 🌳, beautiful developer experience ⌨️.

As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value:

Not only working software,

                but also well-crafted software

Not only responding to change,

                but also steadily adding value

Not only individuals and interactions,

                but also a community of professionals

Not only customer collaboration,

                but also productive partnerships

That is, in pursuit of the items on the left we have found the items on the right to be indispensable.

— Manifesto for Software Craftsmanship

• User Stories User stories are written.
• Release planning creates the release schedule.
• Make frequent small releases.
• The project is divided into iterations.
• Iteration planning starts each iteration.

• Give the team a dedicated open work space.
• Set a sustainable pace.
• A stand up meeting starts each day.
• The Project Velocity is measured.
• Move people around.
• Fix XP when it breaks.

• Simplicity.
• Choose a system metaphor.
• Use CRC cards for design sessions.
• Create spike solutions to reduce risk.
• No functionality is added early.
• Refactor whenever and wherever possible.

• The customer is always available.
• Code must be written to agreed standards.
• Code the unit test first.
• All production code is pair programmed.
• Only one pair integrates code at a time.
• Integrate often.
• Set up a dedicated integration computer.
• Use collective ownership.

• All code must have unit tests.
• All code must pass all unit tests before it can be released.
• When a bug is found tests are created.
• Acceptance tests are run often and the score is published.