TLDR
Part I can be found here, Part II, Part I, Part III, Part IV, Part V, Part VI, Part VII, VII, VIII, IX and the last one (for now) This is part V. I'm senior software engineer specialized in declarative designs and S.O.L.D. and Agile lover. We see several symptoms and situations that make us doubt the quality of our development. We need to use linters to check for Regular Expressions like!not or!isNot as a warning.via the TL;DR App
no story
Written by mcsee | I’m a sr software engineer specialized in Clean Code, Design and TDD
Book "Clean Code Cookbook"
500+ articles written