James Drummond Senior developer from London: finance and startup

Which tech stack should I use for my product or service? The answer: (sorry!) it depends. Some tech stacks are ideal for very technical applications but developers are very expensive and hard to find. On the other hand some tech stacks are widely used, developers available and cheap but are not easily scalable; they are unsuitable for handling very high volumes of traffic + data. Does your MVP really need to be built to handle 1 million+ visits / day when a simpler stack can get you to the next investment round for a fraction of the cost? So many questions! I'd love to use the 13 years experience I have working as a developer at a senior level in the corporate and finance sector in London to answer them for you.

Amazon Web Services (AWS) can offer extraordinary services and scalability for your web service. But, these services come at a high price - both financially as well as in terms of technical risk to your company. Are there cheaper and less complex options? How will your choice of host affect the views of your investors? Call me to talk it over!

Poor quality software can kill your product and company. Web users are not patient, if they encounter bugs + usability issues with your product they generally will not tell you - they will just move on to another service. Let's talk about how to ensure the quality of your product - the systems, processes and tools that you as (perhaps) a non technical manager can put in place to ensure quality - regardless of the expertise of your developers.