際際滷

際際滷Share a Scribd company logo

How to protect your code against a destructive influence of client | Codesushi - Rzeszow 2017

Krzysztof (Chris) Ozog
Krzysztof (Chris) Ozog

The document discusses how to protect code from a destructive client influence. It recommends (1) correctly communicating with the client and planning for refactoring time, (2) introducing rules like SOLID for code creation, and (3) performing code reviews by outsiders and using PHP tools like Mess Detector and Code Sniffer. The goal is to maintain responsibility for the code quality and prevent a good start from leading to a bad finish due to changes.

1 of 10
Download to read offline
How to protect your code against a destructive influence of client Chris Ozog - Codesushi CTO
Agenda: A bit about me... No code is written with the idea that it will be bad Is there a pilot on the plane? Who is writing the code, you or the client? And what now? So a thing or two about proper communication and a clear message! A soft way the correct mindset A hard way the tools which will help us to do it Rome wasnt built in a day! The time for refactoring is the most valuable time Summary
A bit about me... Creator of web apps for more than a decade now Addicted to clean code Technical leader at Codesushi A passionate CodeReviewer A Philosopher and Developer in one Whats worse, is that its documented by two diplomas
No code is written with the idea that it will be bad A good start to a bad finish Changes Changes for changes Changes for changes, for changes
Who is writing the code, you or the client? You are writing the code and not the client! At some point we make the first mistake negligence And then it goes downhill
And what now? So a thing or two about proper communication and a clear message! Despair and pointing the finger! But can it be done differently? Two ways, a soft one and a hard one?!
The soft way when the client constantly changes his mind A headstrong programmer and a cursed PM Thats not the right way The golden mean Trilateral discussions: the client - PM - dev team Planning should include refactoring The semi-hard way SOLID code Code review best performed by someone from outside the team
The hard way so the tools which will help us to do it PHP Code sniffer PHP Mess detector
Summary: Usually, we are the ones responsible for a bad code In order to efficiently prevent a bad code: Correctly communicate with the client Predict the time needed for refactoring Introduce clear rules for creating software, like for example SOLID Code Review should be performed by someone from outside the project Implement the PHP Mess detector and PHP Code Sniffer tools
Thank you for your attention :) e-mail: hello@codesushi.co www: codesushi.coChris Ozog Codesushi CTO

More Related Content

How to protect your code against a destructive influence of client | Codesushi - Rzeszow 2017

  • 1. How to protect your code against a destructive influence of client Chris Ozog - Codesushi CTO
  • 2. Agenda: A bit about me... No code is written with the idea that it will be bad Is there a pilot on the plane? Who is writing the code, you or the client? And what now? So a thing or two about proper communication and a clear message! A soft way the correct mindset A hard way the tools which will help us to do it Rome wasnt built in a day! The time for refactoring is the most valuable time Summary
  • 3. A bit about me... Creator of web apps for more than a decade now Addicted to clean code Technical leader at Codesushi A passionate CodeReviewer A Philosopher and Developer in one Whats worse, is that its documented by two diplomas
  • 4. No code is written with the idea that it will be bad A good start to a bad finish Changes Changes for changes Changes for changes, for changes
  • 5. Who is writing the code, you or the client? You are writing the code and not the client! At some point we make the first mistake negligence And then it goes downhill
  • 6. And what now? So a thing or two about proper communication and a clear message! Despair and pointing the finger! But can it be done differently? Two ways, a soft one and a hard one?!
  • 7. The soft way when the client constantly changes his mind A headstrong programmer and a cursed PM Thats not the right way The golden mean Trilateral discussions: the client - PM - dev team Planning should include refactoring The semi-hard way SOLID code Code review best performed by someone from outside the team
  • 8. The hard way so the tools which will help us to do it PHP Code sniffer PHP Mess detector
  • 9. Summary: Usually, we are the ones responsible for a bad code In order to efficiently prevent a bad code: Correctly communicate with the client Predict the time needed for refactoring Introduce clear rules for creating software, like for example SOLID Code Review should be performed by someone from outside the project Implement the PHP Mess detector and PHP Code Sniffer tools
  • 10. Thank you for your attention :) e-mail: hello@codesushi.co www: codesushi.coChris Ozog Codesushi CTO