Ashish

Developer and designer. Wants to join an idea as a co-founder.

Frankfurt, GermanyOn FounderCloud since 2020

Want to talk to Ashish?

Join free to message founders, save the ones you like and post your own idea.

About

Technical Background, I'm a Full Stack Developer with versatile experience.

I understand what it needs to start from 0 and how to end what you thought in the beginning but when you create something you'll get new ideas almost everyday. It's easy to have idea but it's hard to implement it and even after implementing it is harder to stay with it to keep it alive and let your hard work survive through the period when nobody knows about you.

I'm a Passionate Developer who it ready to forge ideas into reality and work endlessly.

Contact me only if you are serious, when you can work at least 30 hours per week, willing to discuss the idea, has an prior…

Answers in the Nest

Why does it seem EVERYONE is looking for a CTO?“A CTO makes a difference by saving you tons of money and vision inside his head to have a technical answer how to achieve a software product as soon as the requirement is narrated to them. Forgive me for my straight words here but they used to keep things simple and short. 1. A lame could not understand what could be achieved for free in terms of application, website, or any software product. 2. Where to host your services, security features, copyrights, how to bundle the product, which tech is more suited for your business case. 3. Help to achieve major things like scale application up and down, have knowledge of top trend used by competition on tips from across domains. 4. CTO usually understand Domain and business requirement fast and then how questions when thrown get answered. Some CTO do design complete architecture of application, these architecture design is like bones of software based on which different layer of application are made. These layer could be thought of as muscles to the application. Usually a good business owner should get the insight about the product architecture and should keep themselves involved why because it is their idea. This layers and architecture when products become big help individual teams to work independently and they usually have no knowledge about the whole functioning of application. This's very good and required objective for obvious reason everyone should not have complete knowledge of product. 5. CTO also decide which tech to use for which layer, think of it as Netflix is not all designed in 1 tech or the Facebook etc. They could but they shouldn't be for performance, security, hacking a multi tech application is hard compared to 1 that use just 1. 6. CTO creates DNA of your architecture and code base like a smart CTO would think of generic code base and tech in use or the hosting services to bare bone level so that in future you are not exploited by a 3rd party due to price rise of depreciating a feature. As a part of contingency they suggest to build heavy used layer of application in more than 1 tech so that if required they could stop using a tech all together with no impact.”