One warning about feature flaging probably unused code, in some businesses exists things that are done weekly, monthly, quaterly or yearly (or randomly rare), so it is important to catch such things with responsible persons. Second, especially when logic is spread in SQL, UI etc.. some times skipping such code may give catastrophic results or worse give a results looking "normal" but without some specific information wich is needed for accounting or tax etc. for a month before it will be catched.
This was a great talk, too bad the croud was a bit shy. As someone who is often bought into projects that are exactly in this state, it's great to hear we're on the right track. Culture is probably the hardest part it fix, management really needs to buy into wanting a continuous improvement culture, especially when the code starts to stabailse. Engineers need to speak up too, which is often very difficult to do if disenfranchised.
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
One warning about feature flaging probably unused code, in some businesses exists things that are done weekly, monthly, quaterly or yearly (or randomly rare), so it is important to catch such things with responsible persons.
Second, especially when logic is spread in SQL, UI etc.. some times skipping such code may give catastrophic results or worse give a results looking "normal" but without some specific information wich is needed for accounting or tax etc. for a month before it will be catched.
This was a great talk, too bad the croud was a bit shy.
As someone who is often bought into projects that are exactly in this state, it's great to hear we're on the right track.
Culture is probably the hardest part it fix, management really needs to buy into wanting a continuous improvement culture, especially when the code starts to stabailse. Engineers need to speak up too, which is often very difficult to do if disenfranchised.