Yes. You could raise well already from the serious ones based off current performance. 😳
People raise on much less experience & skill. It's not needed if you can do the early work (code, content, traction).
Money is control in these kinds of scenarios (it's clear you could repeat what is happening here, regardless of raise). MZ can do what he wants with FB due to early retention (look at fb cap table or whatever).
For dev, communities tend to run naturally in cycles a bit like product. The concerns become non-technical usually: "I remember the old days when Ben & team would answer & say nice things but nowadays you only see them on a yacht on IG & Ive been banned on DEV 3mths for calling it an ice-cream horse!!". It's more often mismanagement + some competitor pressure (medium?) not technical issues or missing features. Usually, those issues were always there underneath the whole time. The great digg > reddit migration was mostly that (the v4 redesign didn't help). Look at what happened to other big communities to determine the fate of yours, there are a bunch of cases.
Fb is an example of how to extend lifecycle (know existing ageing audience, capture new ones by being well monetized to take competitors, pivot whole org etc).
Everything like goo & craigslist followed this adhoc style to some degree as people were making things up as they went (Apple being a key exception).
Arriving in tech today seems way more intimidating than watching the useless nonsense as it turned into 'industry standard' ways of doing things. To anyone new reading this, free up 18mths (ramen startup), copy Ben's technique of rolling start & be fearless. 👍
Start soon as change is underway. 😊
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes. You could raise well already from the serious ones based off current performance. 😳
People raise on much less experience & skill. It's not needed if you can do the early work (code, content, traction).
Money is control in these kinds of scenarios (it's clear you could repeat what is happening here, regardless of raise). MZ can do what he wants with FB due to early retention (look at fb cap table or whatever).
For dev, communities tend to run naturally in cycles a bit like product. The concerns become non-technical usually: "I remember the old days when Ben & team would answer & say nice things but nowadays you only see them on a yacht on IG & Ive been banned on DEV 3mths for calling it an ice-cream horse!!". It's more often mismanagement + some competitor pressure (medium?) not technical issues or missing features. Usually, those issues were always there underneath the whole time. The great digg > reddit migration was mostly that (the v4 redesign didn't help). Look at what happened to other big communities to determine the fate of yours, there are a bunch of cases.
Fb is an example of how to extend lifecycle (know existing ageing audience, capture new ones by being well monetized to take competitors, pivot whole org etc).
trends.google.com/trends/explore?d... product lifecycle.
trends.google.com/trends/explore?d... when you drill down.
trends.google.com/trends/explore?d... devto is pre Aug 08 here it seems (in the cycle, not scale).
trends.google.com/trends/explore?d... you can just see it lifting at the end.
trends.google.com/trends/explore?d... + power marketing
trends.google.com/trends/explore?d... saturating what's next?
Everything like goo & craigslist followed this adhoc style to some degree as people were making things up as they went (Apple being a key exception).
Arriving in tech today seems way more intimidating than watching the useless nonsense as it turned into 'industry standard' ways of doing things. To anyone new reading this, free up 18mths (ramen startup), copy Ben's technique of rolling start & be fearless. 👍
Start soon as change is underway. 😊