Code District is a high-end technology company specializing in delivering cutting-edge solutions and thought leadership for custom web and mobile application development through multiple technology stacks.
We have also worked with companies like Neilson, Maxwell Forest, Bank of Montreal, FIFSG, Barclays, Family Dollar, AstraZeneca, NBC Universal, Groupon, etc. You can view our detailed company profile deck here.
To also get an overall idea of the quality of the services that we offer, you can view our clutch profile by clicking here.
We have also been recognized by Clutch as its top development partner by getting the Top developers award in the US both in 2019 and 2020.
“Delivering software products beyond expectations on time and within budget.”
Core values & how they impact work
We are a full customer-centric organization providing absolute value to our prospects and clients by being very thorough and vivid in our dealings from the very beginning till the end. Some of our core value propositions are listed below:
We are an end to end custom development company offering a wide range of services in the technology space, which includes:
We have received the following 3 Top Developers in the US Awards in three consecutive years:
1. Good Firms “Top Developers in the US Award 2021”
2. Clutch “Top Developers in the US Award 2021”
3. Clutch “Top Developers in the US Award 2020”
4. Clutch “Top Developers in the US Award 2019”
How do we assess project needs and requirements?
We usually engage with our clients using 2 different engagement models. One of them is the Risk Buster approach to software development where we get a 10 thousand feet overview from your side of what you want to get done. Following the initial discussions, we do a detailed discovery workshop in which we prepare a clickable prototype, prepare a functional specification document, do the technical evaluations and eventually prepare a detailed estimation and delivery plan before sending the project off for development. Once the project is done, the final step is to launch the product. All of the above-mentioned steps allow us to avoid any of the client’s budget overflows, fluctuations in the timeline, and the chances of the product’s expectations not being met.
Our second engagement model is the Dedicated Teams Model. In this model we provide companies extra hands through our Dedicated Teams Model on a short- or long-term basis, to assist them with their workload and save them from the hassle of having to recruit more people. The process involves first understanding what kind of resources the client needs. Based on that, we provide the resources with the necessary experience along with a Project Manager to supervise the work. We have a trial offer by the name, "POC" (Proof Of Concept). In that, we let you test run our engineers for 40 hours for free to review our capability. Once reviewed, only then you can decide whether you want to move forward with us or not.
We dive deep into those requirements and have a couple of Q/A sessions with you to better understand the product, what needs to be built, how it needs to come together, what are the possible solutions and once we think that we're at a stage where we have a significant amount of understanding, that's where we put together a detailed feature breakdown document and put in the estimated number of hours against that and present to you a tentative quote that based on our initial understanding, we think that this project is going to take somewhere between x to y dollars and somewhere between x to y hours to build all this.
UI/UX Design standards
We follow the industry standards coupled with best practices to make sure that we give our clients the best and most creative designs consistently. We make use of the modern minimalistic approach and methods to maintain a flawless user experience.
Project Acceptance Criteria
We usually make the project completed if:
The system delivered has 5 or fewer minor bugs and 10 or fewer trivial bugs. The client will release the final payment as soon as the system stands accepted OR Two phases of final UAT have been performed as described above.
Definitions of bugs:
How would you architect a Canonizer to be massively scalable?
For an application to be massively scalable, we need to make sure of the following:
We will be using AWS Managed Relational Database Service (RDS), as our primary database. This ensures backup of the database every single day and we can also encrypt any part of the database if required.
Logs are extremely important when working on a live project. Therefore we will be utilizing AWS CloudWatch to log every action on the website so that we can always pinpoint bugs even when millions of users are using the system. All assets will be stored in AWS S3. AWS Load Balancer with CloudFront will be used for the efficient delivery of all of the website pages and assets. We will also be utilizing Redis cache and SQL indexing for even more efficient delivery of data to the end client.
What type of team management or prioritization tools are normally used, if any?
As far as our delivery process is concerned, to ensure that you are well informed and updated regarding the progress of your project, we employ multiple things:
What is your philosophy on code reviews by team members, or strategies such as team or pair coding?
We configure GitHub or BitBucket in a way such that whenever one of the team members pushes the code to the repository, a pull request is created. This pull request is then reviewed by the team lead who can either accept or reject that pull request. Upon rejection, the developer who created the request goes back to take necessary action on it.
Furthermore, we will develop three environments:
What experience do you have setting up and maintaining systems that are 100% continuous delivery enabled, including automated tests that prove 100% of functionality still works with each modification made to the code, along with automatic deployment of such fully tested changes.
In order to ensure that the work is successfully done, we make use of the DevOps approach which is described below:
How can we contribute to improving Canonizer and its goals: We have certain coding standards that are followed through our company to eradicate any inconsistencies within the written code, thus, creating no gaps for any possible bugs.
Do you have any examples of times when you went beyond what was being asked of you by your immediate supervisor to further the goals of the company or humanity as a whole?
We make sure that we don’t overcharge our incoming clients with exaggerated estimates as we believe in establishing long-term relationships with our existing clients rather than one-off engagements.
We also understand exactly what challenges the client is facing in order to provide the most optimal solution. Apart from that, we also are open to making suggestions to our clients on a continuous basis throughout the process to ensure that the client gets the maximum benefit because it is never wise to reinvent the wheel for something that has already been tried and tested.
A good example of this would be a client who had approached us a few months back with the intention of having Domo integrated into his system. The client was paying a sum of nearly $15000 a year and wanted a custom solution. We instead pitched Tableau with the same level of functionality that was initially required which saved him thousands of dollars.