Comments on: #13 Code Review – are we too busy to improve? http://swifting.io/blog/2016/04/18/13-code-review-are-we-too-busy-to-improve/ Sharing passion in Swift Wed, 17 May 2017 09:51:00 +0000 hourly 1 https://wordpress.org/?v=5.2.2 By: Maciej Piotrowski http://swifting.io/blog/2016/04/18/13-code-review-are-we-too-busy-to-improve/#comment-46 Sat, 11 Jun 2016 17:19:07 +0000 http://swifting.io/?p=363#comment-46 Unfortunately I don’t have such statistics. But you’re right, that would be a great example on how not to produce software. I hope I will never get a chance again to gather these stats ;).

In our case, the solution hasn’t been presented to stakeholders before ‘refactoring’ on our side.

]]> By: Tomasz Korzeniowski http://swifting.io/blog/2016/04/18/13-code-review-are-we-too-busy-to-improve/#comment-27 Tue, 19 Apr 2016 21:07:20 +0000 http://swifting.io/?p=363#comment-27 It would be interesting to present correlation between number of crashes with code quality.

In my opinion it could help to stress importance of code review and quality mindset for all project stakeholders. It could be a fantastic way to present that shitty code results in shitty user experience 🙂

]]>