Over the years I’ve been asked to evaluate an array of closed source codebases, many with several years' history. Without even running an application, I can identify a lot about the project state, the people involved, and the business behind it.
Your codebase and more importantly the version control history tells an incredible story. This history gives you a list chronological list of every change made and who made it.
Looking through version control history is like reading someone’s diary. All the secrets are on the table.
You find out the following right away
- How many developers have worked on the application? Individuals or teams?
- What was the engagement like? In house, freelancers or a consulting company?
- Who was there when the project started?
- How much impact has each developer made on the project?
- When was the majority of the project developed?
- What’s the developer churn look like?
- What’s the code quality like? Has it been hacked together or is it well factored? Is it well-architected or is it a mess?
- How up to date are the dependencies within the project?
- Is there a test suite?
- Have aspects of the codebase been replaced many times before?
Based on what you’ve now learnt, you have to ask yourself the harder questions
- If no one seems to stick around on this project, why? Is it the business direction? The people? Was the state of the project beyond repair?
- What level of skill did the developers that worked on it have? How well was the knowledge transferred through the team?
- What security risks exist within the dependencies and the codebase itself?
Next you can start to get a picture of the business
- Based on when and how many people were added you can estimate the development expenditure.
- Has the project been hacked together possibly due to the way the development funding was spent? Or was there a lead developer that stuck around and took responsibility for the project’s health?
- Who was the key person responsible for the technical aspects of the project and did they establish a clear direction?
- Is it going to be easy to attract new developers to work on this project or is it dated and frustrating to work with?
- Is there evidence of specific business problems within the codebase?
Now that you know how to listen to your codebase, what is it saying about you?
Let's work together
Tell us about your project and we'll get back to you shortly.
Join The Conversation
More On The Blog
8 Best Ruby On Rails Gems For eCommerce Applications
Everyone within the eCommerce space knows of Ruby On Rails. This framework is used by approximately 3,866,870 websites right now, showing just how efficient it can be for creating efficient yet beautiful web applications. Now, this unique Ruby-based framework comes with its fair share of add-ons and extra features to discover as well. One of the most important ones is the gems in Ruby On Rails.
Sol Dieguez — Nov 30, 2022
How To Improve Your eCommerce With PHP
With the ever-changing state of the IT industry and the fluctuating eCommerce development trends, it’s more than necessary to be flexible in trying out different tech stacks for your eCommerce site. Now, PHP is one of the most popular programming languages out there, and one with a long-standing track record.
Sol Dieguez — Nov 24, 2022
Tips For Getting The Most Out Of Your AWS Free Tier
This cloud computing service currently has over one million users, with enterprise-scale customers making up about 10% of their clients. This shows just how widely used AWS is and gives a solid reason to try it out: it seems to work for most eCommerce businesses out there. Now, there’s a way to check out AWS for free and see if it works for your online business.
Sol Dieguez — Nov 18, 2022