Is your code too complicated?

[Kent Sharkey]

Sourcery[^]:

Measuring complexity of your code with two different metrics - Cyclomatic Complexity & Cognitive Complexity

"The complexity that we despise is the complexity that leads to difficulty"

[trønderen]

Right. If the problem is super-complicated, then you can't expect the solution to be super-simple. If the complexity of the problem really isn't that bad, the code shouldn't be bad either. But how would you know that the problem really isn't that bad? It simply isn't the agile style. The modern way is to start by coding 'void main(int argc, char** argv) { ...' long before you start asking what the real problem is. At the time when you begin to really grasp the nature of the problem, you have already written a whole lot of code, based on an incomplete understanding. You will be living with that code as 'technical debt' for a long, long, time. In the style of agility, you will be programming around the old, badly (non)designed code, adding numerous 'ToDo's. Most real problems are really far less complex than the software written to solve them.

[BillWoodruff]

I can tell why the explanation of why you don't like Agile is too complex :wtf:

«The mind is not a vessel to be filled but a fire to be kindled» Plutarch

[trønderen]

One of the System Engineering textbooks we used at the University summarizes in a bullet list "Reasons why the project did not complete on schedule". Every second bullet point said "Poor planning". So some people said "Hey, that is a great idea for making our project last!" So they sat down and developed agile methods.