# code analysis Published articles for code analysis. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Book Review - Troubleshooting Java DevFeed: [Book Review - Troubleshooting Java]() Original publisher: [Read original article]() Author: vladmihalcea Published: 2025-10-15T08:28:01Z Content type: opinion Language: en Sources: [Vlad Mihalcea]() Topics: [Java](), [debugging](), [Optimization](), [ide](), [Logging](), [Query (disambiguation)](), [Databases]() Tags: [book](), [book-review](), [code-analysis](), [debugger](), [debugging](), [developer](), [ide](), [java](), [logging](), [optimization](), [performance](), [performance-tuning](), [review](), [sql](), [troubleshooting]() ### AI overview A review of the second edition of Troubleshooting Java by Laurentiu Spilca. The book covers code analysis, logging, debugging, profiling, SQL query investigation, lock monitoring, and deadlock troubleshooting for Java developers. ### Source excerpt Introduction My friend, Laurentiu Spilca, has been working on the second edition of his Troubleshooting Java book, and when I was asked to review it, I was more than happy to do it since the book features a lot of topics that I'm also very interested in, such as performance tuning and query optimization. Audience This book is useful for any Java developer because it teaches you how to get the best out of your IDE debugger, as well as showing you how to profile Java applications and fix very complex issues,... Read More The post Book Review - Troubleshooting Java appeared first on Vlad Mihalcea. ## 100 Tips to Write Clean Code DevFeed: [100 Tips to Write Clean Code]() Original publisher: [Read original article]() Author: Daniel Moka Published: 2025-09-17T05:03:43Z Content type: article Language: en Sources: [Craft Better Software]() Topics: [clean-code](), [Programming](), [Development]() Tags: [clean-code](), [code](), [code-analysis](), [code-review](), [tips]() ### AI overview This article presents 100 practical tips for writing clean code that remains readable, testable, and maintainable. The covered guidance includes naming, functions, classes, comments, and commits, with recommendations such as using intention-revealing names, keeping functions concise, limiting class responsibilities, and avoiding side effects. ### Source excerpt Clean Functions, Classes, Comments, Commits and everything you need to write Clean Code ## What Is Linting? DevFeed: [What Is Linting?]() Original publisher: [Read original article]() Author: John Caleb Published: 2025-07-04T04:23:28Z Content type: tutorial Language: en Sources: [Baeldung - CS]() Topics: [developer tooling](), [Code quality](), [Parsing](), [JavaScript](), [Programming]() Tags: [automated](), [code-analysis](), [code-quality](), [compilers-and-linkers](), [javascript](), [lint](), [linter](), [parsing](), [programming](), [programming-compilers-and-linkers](), [quality-control](), [readability](), [syntax]() ### AI overview This tutorial explains what linting is, why linters are useful in software development, and how they detect syntax, semantic, formatting, and coding-style problems. It describes parsing source code into an abstract syntax tree and applying rules to identify issues such as undefined variables and incorrect code usage. ### Source excerpt Explore linters, tools for automated code analysis that can capture syntactic, semantic, and stylistic errors in code. The post What Is Linting? first appeared on Baeldung on Computer Science. Related Stories How to Start Building an Operating System Raft Consensus Algorithm What Is a Monad? ## Why you should consider migrating your Gradle scripts to Kotlin DSL DevFeed: [Why you should consider migrating your Gradle scripts to Kotlin DSL]() Original publisher: [Read original article]() Published: 2023-05-10T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Gradle](), [Kotlin](), [domain-specific language](), [Development]() Tags: [build](), [code-analysis](), [code-completion](), [dependencies](), [development-process](), [dsl](), [gradle](), [interoperability](), [kotlin](), [migrate](), [workshop-learning-programming]() ### AI overview This article explains Gradle Kotlin DSL, describing its benefits over Groovy-based Gradle scripts, including static typing, code completion, type-safe APIs, concise syntax, and improved maintainability. It also outlines steps for migrating build scripts to Kotlin DSL. ### Source excerpt Discover the benefits of migrating your Gradle scripts to Kotlin DSL and streamline your development process. ## Autocomplete for Behaviors in PhpStorm with Mixins & Veneers DevFeed: [Autocomplete for Behaviors in PhpStorm with Mixins & Veneers]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-12-20T15:42:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [phpstorm](), [code-completion](), [Content Management System](), [Development]() Tags: [added](), [autocomplete](), [behaviors](), [cms](), [code](), [code-analysis](), [code-completion](), [completion](), [craft](), [insights](), [intellisense](), [learn](), [mixins](), [phpstorm](), [project](), [using](), [veneers]() ### AI overview A tutorial on restoring PhpStorm IntelliSense code completion for behaviors added to Craft CMS projects. It explains how to use mixins and veneer classes so PhpStorm can recognize dynamically added properties and methods through static code analysis. ### Source excerpt Learn how to get PhpStorm IntelliSense code completion for Behaviors added to your Craft CMS project using Mixins & Veneers ## Релиз CLion 2021.3: новый механизм удаленной разработки, тулчейн для Docker, улучшения отладчика и многое другое DevFeed: [Релиз CLion 2021.3: новый механизм удаленной разработки, тулчейн для Docker, улучшения отладчика и многое другое]() Original publisher: [Read original article]() Author: anastasiak2512 (JetBrains) Published: 2021-12-14T13:16:55Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CLion](), [C++](), [C](), [ide](), [Docker](), [jetbrains]() Tags: [c](), [c-plus-plus](), [clion](), [code-analysis](), [docker](), [embedded](), [embedded-software-development](), [hints](), [ide](), [jetbrains](), [remote](), [remote-work](), [tag-75615d22e96e]() ### AI overview This release article presents CLion 2021.3, highlighting a new remote development solution in which the source code, toolchain, and IDE backend run on a remote server while a thin client runs locally. It also covers improvements to toolchains, the debugger, editor, code analysis, file-structure views, and a new Docker toolchain. ### Source excerpt Привет, Хабр! Традиционно начало декабря -- время, когда релизятся все продукты JetBrains. И сегодня я расскажу о CLion 2021.3 -- новой версии нашей кроссплатформенной IDE для разработки на C и C++. Главная новость прошедшей релизной недели -- выпуск нового решения для удаленной разработки. Другие улучшения в CLion: оптимизация и новые возможности по работе с тулчейнами, улучшенное представление данных в отладчике, подсказки для выведенных типов в редакторе, повышение точности и новые возможности анализатора кода, новая опция для представления структуры текущего файла. Читать далее ## Automating Code Analysis in Android Projects DevFeed: [Automating Code Analysis in Android Projects]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2021-09-20T18:11:42Z Content type: tutorial Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [Android](), [Static code analysis](), [Code](), [Java](), [Kotlin](), [ci](), [ide]() Tags: [also](), [android](), [ci](), [code](), [code-analysis](), [code-quality](), [code-quality-tools](), [development](), [ide](), [java](), [kotlin]() ### AI overview This tutorial explains how to automate code analysis in Android projects. It distinguishes static analysis, which can run during development or in CI, from dynamic analysis, which runs the application to detect issues such as memory leaks. It also introduces IDE inspections as a code-analysis tool. ### Source excerpt Source unsplash.com/photos/Tjbk79TARiEAutomation of code analysis in Android projectsHello. My name is Kirill Rozov, and if you are interested in Android development, then most likely you have heard about the Android ResId Telegram channel with daily news for Android developers.https://medium.com/media/ff8acd16dd7b4b03a485bf9baab3c9d6/href Modern mobile applications are already quite serious enterprise projects that are developed by hundreds of developers, contain thousands of lines of code and are constantly changing and developing. The process of automating code checking and application work helps to deal with such a huge codebase. Today I will tell you what tools you can use to improve the stability of your project and avoid mistakes, as well as save time for colleagues during a pull request. Are you developing a project with a small team or alone? Then this article is even more important to you, since you most likely didn't configure any checks for yourself, and I will tell you why this needs to be done. Types of code checking Code analyzers is divided on two types: static code analysis (without starting the application) code analysis while the application is running Android development uses statically typed compiled languages: Java and Kotlin. These are important requirements for languages that allow them to analyze code without having to run it, and they can do it right at the time of writing the code. This type of analysis is called static. This makes it easy to run analyzing on any CI and automate checking for simple errors, such as not closing a stream after reading/writing code. The disadvantage of such checks is that if your code deviates from the template embedded in it, then the code will not work or will work incorrectly. Also, such analyzers can't understand complex code execution scenarios and their effect. More serious checks of your code can be done by automatically analyzing it while the application is running (dynamic). For example, you can tra ## Escape-Analysis Flaws DevFeed: [Escape-Analysis Flaws]() Original publisher: [Read original article]() Published: 2018-01-22T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Compiler](), [Static code analysis](), [toolchain]() Tags: [analysis](), [ardan-labs](), [benchmark](), [blog](), [code-analysis](), [compiler](), [escape-analysis](), [go](), [go-programming](), [golang](), [memory-management](), [pointers](), [programming](), [series]() ### AI overview This article examines unresolved flaws in Go's escape analysis, a compiler analysis that enables memory-management optimizations. It identifies five flaws that had not been fixed at the time of writing and explores their potential impact on existing Go programs, based on the Go 1.9 compiler. ### Source excerpt Prelude It will be helpful to read this four-part series first on escape analysis and data semantics. Details on how to read an escape analysis report and pprof output have been outlined here. https://www.ardanlabs.com/blog/2017/05/language-mechanics-on-stacks-and-pointers.html Introduction Even after working with Go for 4 years, I am continually amazed by the language. Thanks to the static code analysis the compiler performs, the compiler can apply interesting optimizations to the code it produces. One type of analysis the compiler performs is called escape analysis. This produces optimizations and simplifications around memory management. ## Static code analysis for free DevFeed: [Static code analysis for free]() Original publisher: [Read original article]() Published: 2014-10-20T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Static code analysis](), [JavaScript](), [Tooling](), [Jenkins](), [Web Development]() Tags: [code-analysis](), [javascript](), [jenkins](), [npm](), [report](), [reports](), [tooling]() ### AI overview This article introduces Plato, a free tool for static JavaScript analysis and reporting. It explains how to install Plato from npm, run it against a codebase, generate visual reports, and publish those reports through a Jenkins job. ### Source excerpt Lorem ipsum dolor sit amet ## Dump Go Abstract Syntax Tree DevFeed: [Dump Go Abstract Syntax Tree]() Original publisher: [Read original article]() Author: Graham King Published: 2014-06-28T19:09:44Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Go Language](), [code analysis](), [Parsing](), [syntax]() Tags: [analysis](), [ast](), [code](), [code-analysis](), [go](), [software](), [syntax]() ### AI overview A tutorial on parsing Go source code into an abstract syntax tree and displaying the AST for a given Go file. It frames this as a starting point for refactoring and code analysis tools. ### Source excerpt Go has good support for examining and modifying Go source code. This is a huge help in writing refactoring and code analysis tools. The first step is usually to parse a source file into it's Abstract Syntax Tree representation. Here's a complete program to display the AST for a given Go file: Use: - Save that as - Build it: - Run it: ## Using Heartbleed as a starting point DevFeed: [Using Heartbleed as a starting point]() Original publisher: [Read original article]() Published: 2014-04-10T09:06:18Z Content type: opinion Language: en Sources: [Antirez]() Topics: [openssl](), [Security](), [code security](), [Static code analysis](), [C]() Tags: [c](), [code-analysis](), [code-security](), [open-source](), [openssl](), [security]() ### AI overview The article uses the Heartbleed vulnerability in OpenSSL as a starting point for discussing how to improve system software security. It argues for greater investment in security audits, open-source software development, and static and dynamic checks, while noting that changing languages or specifications is unlikely in the near term. ### Source excerpt The strong reactions about the recent OpenSSL bug are understandable: it is not fun when suddenly all the internet needs to be patched. Moreover for me personally how trivial the bug is, is disturbing. I don't want to point the finger to the OpenSSL developers, but you just usually think at those class of issues as a bit more subtle, in the case of a software like OpenSSL. Usually you fail to do sanity checks *correctly*, as opposed to this bug where there is a total *lack* of bound checks in the memcpy() call. However sometimes in the morning I read the code I wrote the night before and I'm deeply embarrassed. Programmers sometimes fail, I for sure do often, so my guess is that what is needed is a different process, and not a different OpenSSL team. There is who proposes a different language safer than C, and who proposes that the specification is broken because it is too complex. Probably there is some truth in both arguments, however it is unlikely that we move to a different specification or system language soon, so the real question is, what we can do now to improve system software security? 1) Throw money at it. Making system code safer is simple if there are investments. If different companies hire security experts to do code auditings in the OpenSSL code base, what happens is that the probability of discovering a bug like heartbleed is greater. I've seen very complex bugs that are triggered by a set of non-trivial conditions being discovered by serious code auditing efforts. A memcpy() without bound checks is something that if you analyze the code security-wise, will stand out in the first read. And guess how heartbleed was discovered? Via security auditings performed at Google. Probably the time to consider open source something that mostly we take from is over. Many companies should follow the example of Google and other companies, using workforce for OSS software development and security. 2) Static and dynamic checks. Static code analysis is, as a side ef