Our blogs walk you through usecases and show you how to make the most of CodeScene and your code. Our developers share best practices and cover topics less explored, but so valuable to development organizations.
I started my career working for an enterprise, but after a while I changed my path and started working for CodeScene, which is still a startup. I thought it would be fun to share my experience of working with these two types of organizations. But I'll also share my thoughts on why I believe everyone should have a startup experience. Coming to CodeScene breaks all my stereotypes about the IT world and the way it works.
Let me tell you a story about debugging a problem with our CI build including unexpected dependencies via lein uberjar.
Work, on a software project is often linear. Point A to point B. From bug to fix. From task to release. Of course, the process might be complex, with iterations, reviews, forks and branches. In the end, those are just the wheels of train taking the project to where it needs to be. Ideally, cards just speed across the kanban, left to right.
This is a description of a high-level performance optimization workflow, primarily focusing on optimizing the design of our program, it's algorithms and data structures, and ignoring low-level optimizations unless its absolutely necessary.
If you know the size of your input beforehand, it should be safe to leave out the padding character ('=') so you don’t need to percent-encode it for safe usage in URLs.
Software development productivity and quality of work is notoriously hard to measure. This complicates hiring decisions as there isn't an easy way to evaluate a developer's true skill set. Consequently, many companies fall back on proxies in an attempt to assess competency. One popular proxy is the dreaded white board coding exercise.
While onboarding a few on-prem customers we faced issues with slow analyses. CodeScene is usually pretty fast (running Linux analysis in ~40 minutes on a Macbook Pro laptop with a solid SSD disk) but two customers were trying to analyze their big repositories and their analyses were running for more than one day.
If you have used CodeScene's Virtual Code Review or PR integrations, then you already know that complexity is a frequent target of CodeScene's Code Health penalties.
We've been working on better refactoring tools for teams that want to improve their code, and we're happy to present our new Refactoring Recommendations feature - a refactoring catalog created from the improvements made to your own team's code.
