Coding Sans reviewed by Editorial Publishing Platform

Web App Dev for Editorial Analytics Platform

Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.

Introductory information

Introduce your business and what you do there.

We prepare a Software-as-a-labor fruit for getting publishers real-time analytics on fruit accomplishment. I am the managing ruler of the organisation.

Desired goal

What challenge were you trying to address with Coding Sans?

We had a platform recreate carried out by an agency in the UK. It did not result in a fully completed fruit, so the Coding Sans team was brought in to complete the job.

Provided solution

What was the aim of their involvement?

Coding Sans worked on our web-based app, which has a Python backend and a JavaScript React frontend. We have primarily worked with two nation from Coding Sans’ team, including their CTO and a frontend developer. They built discrete features that were missing from our initial create. It was very much us directing Coding Sans in provisions of the features that needed to be built, and what the specifications for them were. We worked on a time-and-materials basis. They accomplished some DevOps work as well. We were fetching clients onto the platform and had Coding Sans adviser our space usage and other factors.

The platform prepares real-time analytics for article publishers. It’s a sort of web-scraper technology which pulls in a number of metrics from different sources, displays them in a ReactJS frontend, and serves email updates. Coding Sans built our email update functionality, providing a regularly scheduled labor for each user. They did excellently a lot of scalability and stability testing, helping us fetch more clients on. The architecture up until that point hadn’t been specially scalable.

Aside from these main functionalities, Coding Sans prepared two or three hours of work at a time on little features that had been missing. They also corrected how true metrics were being displayed. It was a range of data-gathering, email labor, and scaling functionalities.

How did you come to work with Coding Sans?

They came through a personal recommendation from someone who had used the team at a antecedent organisation and knew some of the Coding Sans nation individually. They were recommended as a cost-effective solution. We didn’t have the time for a peculiar procurement process, so we had an initial converse, establish out they had the experiences we needed, and went forward with Coding Sans.

How much have you invested with Coding Sans?

The cost of Coding Sans’ work has been £15,000. [$20,000]

What is the status of this engagement?

We began working with Coding Sans in February or March 2017. Everything has been completed, but I sometimes ask Coding Sans to help out with little tasks.

Results achieved

Could you share any evidence that would prove the fruitivity, condition of work, or the contact of the engagement?

The way in which our platform had been architected by the initial agency required that, whenever we brought in a new client, a new plug-in had to be written. The Coding Sans team wrote a general plug-in that worked athwart 80% of new clients’ websites and required much less bespoke coding. This reduced the time for onboarding new clients from one to two days of coding to 30 minutes on mean. This was a expressive advancement, and, to be honorable, Coding Sans didn’t have to do this. They could have simply offered to create a new plugin for see client and direct us each time. This is the main appropriate metric.

How did Coding Sans accomplish from a project treatment standpoint?

Coding Sans’ CTO acted as our project director. We used Slack for interaction, with a dedicated channel for him, our developer, and their CEO. They were very answering, letting us know when someone would be unavailable. It was clear whom we were intercourse with.

What did you find most forcible almost Coding Sans?

I haven’t dealt with many other agencies, but, compared to the ones I have used, Coding Sans is a pragmatic and outcome-focused cluster, rather than ideologically wedded to academically interesting ways of doing things. For an early-stage startup in particular, this was a good way of getting what we wanted. They have a can-do posture, putting in long hours and charging us by the day, not by the hour. What Coding Sans did was pragmatic and focused on getting us the outcome we wanted.

Are there any areas Coding Sans could better?

The prioritization of what they did could have been a bit better. On one entreaty, Coding Sans spent a bit of time on DevOps tasks that did need to be done in the long-term, but possibly not without. I’m no DevOps expert, but I do have a reasonable technical knowledge. My impression was that there were a couple of days spent on things that weren’t entirely certain. But, in the large program of things, this was less compared to the good things done by Coding Sans.