> I don't think I disagree on any of this, but is there any actionable advice in this post? I also think this article was buzzword-inspired and has no substanc

> I don't think I disagree on any of this, but is there any actionable advice in this post? I also think this article was buzzword-inspired and has no substance beyond that point. I mean, do you need a buzzword to argue you need to write correct code, readable code, idiomatic code, simple, and performant? It borders on the vaccuous nonsense. Say what you want about Clean Code, but at least each and every single recommendation is actionable, has clear guidelines, a rationale, and verifiable output. This CRISP nonsense has none of that.