In a similar way it’s possible to quibble over the definition of the word democracy.
If the ability of women to vote is considered essential for democracy, then the world’s oldest democracy is New Zealand and not the US.
But rather than going by dictated definitions, if we go by popular perceptions of the words, then Nalanda is a university and US became a democracy before New Zealand.
Nalanda was multi-subject and other than theology, they also taught medicine, mathematics, astronomy, meta physics, grammar, etc. That sounds like a university to me.
You can always try to create definitions to suit your preferred narrative. But Nalanda was multi-subject beyond teaching religion.
MIT license builds the trust to use it and contribute to it, or at least use it freely.
But that also enables someone to use your software as a starting point for their own competing SaaS solution.
Which is what encourages companies to at some point of time shift to a BSL license, as you might also at some point of time.
The goal is of course to build Enterprise features which are hard to replicate for others, but these imply more complex engineering challenges are being solved.
That could be plugins to integrate into other Enterprise tools like Snowflake or Salesforce for e.g.
Another interesting observation is that in next 4-5 years we could expect a robust open source MIT licensed stack for pretty much everything.
But it only feels like that, because we will start to have quantum computing and then all software will need to get rebuilt.
Cloudflare has non-transparent pricing, unlike AWS, which will charge you for every thing with detailed usage tracking.
When ever there is non-transparent pricing, it's scary to try and use an infrastructure related service.
The sales teams can't go around saying that you are not a profitable customer, and they can't argue with the marketing team to be more honest about pricing on the pricing page.
So, end result, let's bump of these small free loaders. Large enterprise deals is what gets us the bonus anyways.
I like fly.io pricing in that sense. And I am sure there might be others offering a more transparent pricing, otherwise like me still stuck on AWS.
Uber is being banned for skipping the process of police verification which would have prevented this incident from happening. If verification had been done then that driver would have never gotten hired. Other cab companies are following this process, so why should Uber skip it ? Companies which are negligent in their duties towards their customers will face repercussions.
Step 1. Make sure that I am disagreeing in the right spirit and communicating in the right way. See disagreement diagram: http://commons.wikimedia.org/wiki/File:Graham%27s_Hierarchy_... Typically this should ensure that the following discussion is done in the right spirit because I would guess developers tend to be logic driven.
Step 2. In the scenario that even this does not work or cannot be applied easily, then ask that "If we wanted to test out which option between these two, three approaches will work better, than what test could we conduct ?" Focus on defining a test to validate assumptions, rather than arguing for or against an option.
There are three different things, 1. MLP, 2. MVP, 3. MSP which kind of come in order.
1 MLP is Minimum Learnable Product i.e. anything which helps you learn something about what product you should be building. It can be an email that you send out pitching your product or a landing page.
2. MVP is Minimum Viable Product i.e. by viability we imply usability. If it is not usable then it is not viable. So landing pages, wireframes are ruled out. Mailers might work if you start to provide a service (which will get eventually productized, automated, etc) via the mailer. So an ugly looking product would also do as long as users find it usable.
3. MSP is Minimum Saleable Product i.e. the product based on which you can start making revenue (if you so wanted)
I thought some more about it and I think the issue is that the value proposition of your product is not strong enough to get traction. One of the ways you can improve it is by converting it into a monetization channel for app developers.
So say a free game app has a 100K users playing the game and you know the location ( enable GPS in your SDK) of these users and the times when they are active (start tracking that too) etc then those users could answer a quick survey for larger brands (who pay per survey completed). So the survey is not about the game users are playing, but about a new movie that is launched or a new Xbox Game title that is launched etc. The free app could continue to be freely used if the user answers 1 survey every 20 times he or she plays the game. Survey can even allow you to show a relevant targeted ad next time or promote some other app game too.
I got an answer to the third question on problem-solution fit, but not to the first two questions, i.e. ~
1. What are the alternative solutions (can be dev coding it themselves) and what do they lack in and how much more value (approx. time saved in coding this functionality as a percentage of time taken to code the rest of the app) does your offering create in comparison to the alternative ?
2. How often do your users face the pain-point (i.e. how often do they need to create a different type of survey) ?
