The truth about Code Quality - What is Code Quality and how to measure it

In this video, I'm going to dispel some of the myths about code quality and tell you what code quality actually is. I'll also show you how to measure code quality, so you can identify and fix any issues as early as possible.

jSparrow is our Java Eclipse IDE and Maven tool, which helps you maintain clean code, refactors your code, removes dead code, technical debt and much more. You can do unit testing and upgrade your web application security and performance of your software in general.

ABOUT US🌐:
In the last years our team has specialized in java code refactoring and has developed our own powerful tool jSparrow.
If you are a java developer and you have code refactoring issues you should try our free version on our website at anytime!✅

Thank you for watching.

#jsparrow #java #codequality
-------------------------------------------

Music by:

[captain_jsparrow]

We hope you appreciate our content! If you have any questions or something to add, we are very happy to discuss it.

Of course we would be very happy about a thumbs up and a subscription! <3

[iftyrahman]

Thanks for explaining it in an awsome WTFs per minute 🤣🤣🤣🤣

[szeredaiakos]

Load of bullshit.

Quality of the code largely depends on the context. That context is different for each project - team combination. Automated code quality relies heavily on best practices. 99% of all best practices are pure miss-informed loads a garbage. Regurgitations of random bloggers with zero or very little actual programming experience.

Each practice has both an upside and a downside. There is no such thing as "best". It all depends.

Take for example DRY (do not repeat yourself). It argues you should consolidate very similar lines of code into a single function, class, module. However, if you do, you open yourself up on building parallel systems. Meaning, changes down the line may influence that single function, class, module to do wildly different things based on input.

One can naturally refactor that, and it should. But the results can ... hell .. WILL lead to increased complexity, which could have been avoided if the consolidation would have been based on empirical data or at least some rudimentary form of consideration for future change. Driven to the extreme, you will end up with 120k lines of code maintained by an army of developers which can be summarised into less than 5k while still accounting for high frequency changes.

If you want examples of that, look at the frontends of the top 5 social networks. Last time I checked, they are bloated to the extreme.

Till automated code quality can execute that depth of thought it will remain a scam.