162 karma · joined December 6, 2011
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.
You can always try to create definitions to suit your preferred narrative. But Nalanda was multi-subject beyond teaching religion.
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.
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.
Medium for developers and other tech folks. Or like dev.to, but "hopefully" better UX for driving discussions etc. Also supports live audio sessions.
Supply = Num of people in nearly same timezone interest in wfh
Currently supply >> demand, so if your company is embracing remote work, you need to now be good at your job when compared to a larger pool of people.
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.
2. Either the client prepares the requirements document and you review it or you bill the client to prepare a requirements document.
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)
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.
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) ?
There are tens of thousands of mobile developers building all kinds of apps, which group of devs actually need to add different polls / survey in their app every week ?
You made it to scratch your own itch.. but what exactly was your itch ? And how frequently did you want to switch the poll, survey that you conduct ?
When a user has a pain-point then we need to evaluate the following as well i.e. a user with a pain-point by itself is not sufficient, we have to check for problem-solution fit as well ~ 1. What are the alternative solutions and what do they lack in and how much more value does our offering create in comparison to the alternative ? 2. How often do users face the pain-point ? 3. When do users face the pain-point ?
More than just taking notes (which are more effective than not taking notes), when you try to present something (or explain to others) is when you really capture the knowledge in your head for a really really long time.
I have actually been working on building a Product/Market Fit (Customer Dev) as Service product for the last 12 months and before that I had been advising (mostly on shaping up ideas to get the product definition right) / helping out two new startup teams every month, for about 7 years now. This happened primarily because I enjoy meeting startups and because I was part of a large alumni network which would reach out.
The key assumption for the P/M-F service is whether something like this can be scalable and work in a self-serve mode (i.e. where I am not in the room)
So I have kept iterating on the framework, took inputs from the founders I had advised in the past. My key question to them was "How did I help you even though I was not really a expert in the marketing you were targeting?"
I also conducted lean canvas workshops with startups in US and India (and across sectors including one 7-year old pharma company trying to launch a product) till I could start standardizing (so that it could then be coded into software) the P/M-F process and build a self-serve tool. The tool has now taken the shape of an "intelligent" software which asks startup founders questions and assigns them tasks to do.
There is a lot of complexity in the tool. And it needs to be much more intelligent as well. We have explored using machine learning at the backend, but so far the intelligence is based more on a decision tree structure, rather than any machine learning.
Currently in private alpha, testing with some startups and an accelerator, and will release this soon for others, hopefully by end of this month.
I would say wit.ai looks very interesting.
The dev stack is the same as always ~ Sublime + AWS