[
https://issues.apache.org/jira/browse/CAMEL-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20206:
-----------------------------------------
Description:
We have a large incidence of [excessively complex
methods|https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&id=apache_camel].
Problems with excessively long and complex methods:
* [makes the code much harder to
maintain|https://martinfowler.com/bliki/FunctionLength.html]
* reduce community ability to step in and provide easy fixes
* [increases the cognitive effort to read code by quickly exhausting the limits
of a human short term memory
|https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two]
* reduce the JIT compiler ability to optimize code by inlining because the
generated code is larger than 325 bytes.
* lead to poor reuse and duplication of code
We should start by breaking down this complex code and, in the future, apply
proper design to it.
The components catalog, tooling and dsl are specifically bad for this.
was:
We have a large incidence of [excessively complex
methods|https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&id=apache_camel].
Excessively long and complex
* [methods makes the code much harder to
maintain|https://martinfowler.com/bliki/FunctionLength.html]
* reduce community ability to step in and provide easy fixes
* [increases the cognitive effort to read code by quickly exhausting the limits
of a human short term memory
|https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two]
* reduce the JIT compiler ability to optimize code by inlining because the
generated code is larger than 325 bytes.
* lead to poor reuse and duplication of code
We should start by breaking down this complex code and, in the future, apply
proper design to it.
The components catalog, tooling and dsl are specifically bad for this.
> Cleanup overly complex methods
> ------------------------------
>
> Key: CAMEL-20206
> URL: https://issues.apache.org/jira/browse/CAMEL-20206
> Project: Camel
> Issue Type: Task
> Components: Catalog, core, dsl, tooling
> Reporter: Otavio Rodolfo Piske
> Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> We have a large incidence of [excessively complex
> methods|https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS3776&id=apache_camel].
> Problems with excessively long and complex methods:
> * [makes the code much harder to
> maintain|https://martinfowler.com/bliki/FunctionLength.html]
> * reduce community ability to step in and provide easy fixes
> * [increases the cognitive effort to read code by quickly exhausting the
> limits of a human short term memory
> |https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two]
> * reduce the JIT compiler ability to optimize code by inlining because the
> generated code is larger than 325 bytes.
> * lead to poor reuse and duplication of code
> We should start by breaking down this complex code and, in the future, apply
> proper design to it.
> The components catalog, tooling and dsl are specifically bad for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
