Helping businesses deliver their digital strategy with bespoke software

How we work

Engage

We engage with our customers to properly understand the problem they are trying to solve.

Automate

We automate the build, test and deployment process so we can concentrate on developing new features.

Deliver

We work with businesses to identify which features add the most value and regularly deliver fully working, usable software.

Our Values

You might recognise our values. When we came together as a partnership one of the first things we did was to list all the things we would always do and all the things we would never do. For example, some of things that appeared in the 'always do' list were to be open and transparent about what we do, communicate both good and bad news, work collaboratively and deliver software we are proud of. Some of the things in the 'never do' list included ignoring customer feedback and delivering low quality work. When we looked at what we had come up with we realised that all of these things are summed up nicely by the Extreme Programming values.

Respect

Respect is about giving and feeling respect as a valued team member. We respect the expertise of the people we work with. We work with people who respect our expertise and who respect our right to accept responsibility and receive authority over our own work.

Courage

Courage is about doing the right thing. We will tell the truth about progress and estimates. We will adapt to changes whenever they happen. We don't fear anything because no one ever works alone.

Communication

Communication is a big part of bringing our values to life. We believe smaller teams communicate and work more effectively than larger teams. Everyone is part of the team and we communicate daily. We work together on everything from requirements to code. We create the best solution to your problem we can, together.

Simplicity

Simplicity is about doing just enough and no more than is needed. Working in small, simple steps means we can get feedback sooner. This, in turn, allows people we work with to make more informed decisions about what to develop next and allows the early mitigation of failures. Another benefit of simplicty is that the cost of change is lowered, making our software easier to maintain and extend.

Feedback

Feedback is about delivering working software in each iteration so that we can demonstrate our software early and often. In doing so we are able to gain feedback from the people we are working with and can plan what to do next based on that feedback. We will talk about the project and remain flexible enough to adapt our process to it, not the other way around.

Start a conversation

Technologies

Elastic Mint are a team of .NET experts each with over 15 years experience in developing software.

We have worked on a wide variety of applications ranging from e-commerce sites written in ASP .Net deployed to both AWS and Azure, to small web applications deployed on a single server. We view ourselves as full-stack developers, working on all layers from the UI to the database, and specialising on the backend.

We value practices such as Continuous Integration and Deployment, and Test Driven Development, which give rapid feedback on our work and any problems that may arise.

Case Study

The Client

Preqin is a leading source of data and intelligence for the alternative assets industry. Through their online tools, they provide data and information on investment funds in the private equity, real estate, hedge fund, infrastructure, private debt and natural resource sectors to support fundraising, marketing and market research.

The Challenge

Preqin were approaching the end of a project to develop a new version of their investment intelligence software to provide a better experience for their users.

Under pressure to meet their deadlines, they engaged Elastic Mint to provide some “extra muscle”. Key to their requirements was that Elastic Mint could provide a team experienced enough to hit the ground running so as not to add a burden to their already busy team.

Our Solution

An Elastic Mint team was deployed to focus on moving fund-related data from their SQL Server database into Elasticsearch, and then exposing that data through a .Net Core web service to the user interface.

Our first task was to understand their business, meet the development team and get up to speed with the current state of the project...quickly!

Through open conversation and collaboration we rapidly built trust with the existing team. Recognising the tight deadline they were working to, and the challenges they had already faced on the project, we looked to where we could add the most value in the least disruptive way.

Focussing specifically on the hedge fund area of the application, we were involved in making design and architectural decisions, carrying out spikes to test ideas, and investigating solutions to problems that arose. We worked closely with developers from Preqin, helping to solve problems both inside and outside of the immediate scope of work, sharing knowledge and ultimately producing a solution that met Preqin’s needs.

Technology Stack

Throughout this project I received feedback on how well Elastic Mint worked with our team. They were always accessible, responding quickly to messages and ready to help us think through any challenges
Daniel Barnes
Senior Vice President Engineering

Ready to talk?

As always, the best way to start is with a conversation. Send us your details and let's start talking!

Address

Elastic Mint
13-14 Orchard Street
Bristol
BS1 5EH
UK


Tel: +44 (0)7845 663 874
Email: info@elasticmint.com

From our blog

Do We Still Need Orms?

By Andy Garner on Nov 2 2018

Do you remember the first time you used an ORM (Object Relational Mapper)? For me it was something I wrote to make it easier to map data related to testing electronic devices into a SQL database. Different devices generated different test data, and so I used a convention to map the property names on the classes to the SQL tables and columns. At the time I didn’t even know what an ORM was.

Continue reading

Bespoke software

By Gordon Barrs on Sep 24 2018

What is bespoke software? Bespoke is just a fancy word for custom, right? Well, yes. And no. According to putthison.com the word ‘originated in shoemaking, but gained in popularity through custom tailoring in England, where lengths of cloths were said to be “spoken for” or “bespoken” by another customer.’ 1 There are several levels of custom-made clothes: Made-to-order - only the materials are customised Made-to-measure - the materials and the cut are tailored based on a single fitting Bespoke - garments are made through a series of fittings Translating this into software development, we can think of ‘made-to-measure’ as being like a fixed-scope, Waterfall development process, where we get the requirements up-front, build the software and then deliver it.

Continue reading

The Curse of IoC and Why We Write Too Many Useless Tests

By Andy Garner on Sep 11 2018

Sometimes it seems that we simply go from one extreme to another. Once upon a time developers didn’t bother to write tests. Everything was tested manually. When changes were made the whole thing would need to be manually tested again. Sometimes we used test scripts, other times we just played around trying to break functionally. And then we couldn’t remember what we had done to break it! Managers would roll their eyes in frustration when developers talked about writing unit tests.

Continue reading

We need to talk about legacy software

By Andy Garner on Aug 29 2018

Sometimes we forget how much old software is out there. We talk about the software industry still being young and perhaps quite immature, but actually, word processing software started reaching offices in the early 1970s - over 40 years ago. The first version of PowerPoint was released in 1987, public use of the internet began in 1989 and then exploded during the 1990s. Looking back it is striking how much has changed in a short period of time.

Continue reading