Finding a developer to pick up where we left off
I have a product that was developed and soft launched in 2018 with great success. However our developer left right when we were picking up momentum. The product is very well built, but at the time we couldn't find a new developer to take over.
I'd like to relaunch the product with some improvements. Is it better to build from scratch or is it possible to build on top of what we have now?
The product is very well built, but at the time we couldn't find a new developer to take over. How do you know that? I'd like to relaunch the product with some improvements. Is it better to build from scratch or is it possible to build on top of what we have now?It depends. You'd need to analyse the technology stack in line with the business & operational goals to determine that. Would you like me to take a look at it?
sounds interesting Paul, maybe I can help as I'm a technical founder myself you can have a look at my profile and if you think I'm suitable don't hesitate to contact me
Perhaps I can help if you provide more details about the technical background of the project. What is the technical stack and what improvements are needed?
I run a company that specialises in helping people like you, my company employs developers and then contracts them out to other companies.
You will find there are many benefits to this approach, you don't have to deal with hiring or HR, once the project is delivered it is then your choice on how you want the product maintained, as in take on a permanent developer if there is enough work to justify, or if there are only a few changes here and there you can just ask us to make them for you.
You can be sure that the person we send across is skilled and trustworthy as they are hired by us and we only hire highly skilled and experienced developers.
If you want us to get someone in to pick up the project and finish it for you send me a message and we can take things from there.
Without looking at the source code, lets assume your previous developer adhered to best practices. Also assuming you have good test coverage, a good CI/CD pipeline, and it is deployed on a platform like AWS - it should be relatively straight forward to keep the existing product and continue to add features. Perhaps some patterns might need to be modified, but overall I would save time and keep what you have.
I would personally only re-write an entire platform if I was moving away from a MVP (ruby on rails) and desiring to move to Java Spring for a more professional setup. As I recall, Airbnb started on Ruby on rails and eventually moved to Java for the backend, and a JS framework for the front end after they had grown and had full dev teams.