After nine years of grinding, Replit found its market. Can it keep it?
1–10 of 146 posts
Re: After nine years of grinding, Replit found its market. Can it keep it?
#2I gotta wonder who the median techcrunch reader is if the writer/editor felt it necessary to explain the point of having a staging and prod environment, and with such a pointless analogy. We surely cannot understand what a database is unless we're told it's like a filing cabinet, right?
Re: After nine years of grinding, Replit found its market. Can it keep it?
#3Re: After nine years of grinding, Replit found its market. Can it keep it?
#4>Rather than becoming defensive, Masad and his team owned the problem. In fact, says Masad, within two days, they rolled out an automatic safety system that separates a user’s “practice” database from their “real” one. The way Masad describes it, it’s a little like having two versions of a website’s filing cabinet — the AI agent can experiment freely in a development database, but the production database, which is th…
That's a basic concept of writing. Journalism should be accessible, so even if you know what a database is and how to deploy it in different envs, you shouldn't write assuming that. If a large portion of your readers don't know what you're saying, you've failed as a writer. If your readership includes high school students, you write with that as the baseline.
Richard Feynman certainly didn't write as if he assumed the reader knew particle physics. Be like Richard Feynman.
Re: After nine years of grinding, Replit found its market. Can it keep it?
#5>Rather than becoming defensive, Masad and his team owned the problem. In fact, says Masad, within two days, they rolled out an automatic safety system that separates a user’s “practice” database from their “real” one. The way Masad describes it, it’s a little like having two versions of a website’s filing cabinet — the AI agent can experiment freely in a development database, but the production database, which is th…
Re: After nine years of grinding, Replit found its market. Can it keep it?
#6I also used Replit's embedded widgets for occasional lessons, but they kept changing the UI and behavior, making it difficult to write consistent reliable documentation for beginners.
I think by now it's clear that the product is not meant for educators, like it was originally, so that's ok.
[0]: https://web.archive.org/web/20240924020257/https://blog.repl...
Re: After nine years of grinding, Replit found its market. Can it keep it?
#7>Rather than becoming defensive, Masad and his team owned the problem. In fact, says Masad, within two days, they rolled out an automatic safety system that separates a user’s “practice” database from their “real” one. The way Masad describes it, it’s a little like having two versions of a website’s filing cabinet — the AI agent can experiment freely in a development database, but the production database, which is th…
You don't write for your median reader, you write for the vast majority of your readers. That's a basic concept of writing. Journalism should be accessible, so even if you know what a database is and how to deploy it in different envs, you shouldn't write assuming that. If a large portion of your readers don't know what you're saying, you've failed as a writer. If your readership includes high school students, you wr…
Re: After nine years of grinding, Replit found its market. Can it keep it?
#8Earlier quoted context omitted.
You don't write for your median reader, you write for the vast majority of your readers. That's a basic concept of writing. Journalism should be accessible, so even if you know what a database is and how to deploy it in different envs, you shouldn't write assuming that. If a large portion of your readers don't know what you're saying, you've failed as a writer. If your readership includes high school students, you wr…
Richard Feynman didn’t use poor analogies.
Re: After nine years of grinding, Replit found its market. Can it keep it?
#9>Rather than becoming defensive, Masad and his team owned the problem. In fact, says Masad, within two days, they rolled out an automatic safety system that separates a user’s “practice” database from their “real” one. The way Masad describes it, it’s a little like having two versions of a website’s filing cabinet — the AI agent can experiment freely in a development database, but the production database, which is th…
Re: After nine years of grinding, Replit found its market. Can it keep it?
#10>Rather than becoming defensive, Masad and his team owned the problem. In fact, says Masad, within two days, they rolled out an automatic safety system that separates a user’s “practice” database from their “real” one. The way Masad describes it, it’s a little like having two versions of a website’s filing cabinet — the AI agent can experiment freely in a development database, but the production database, which is th…
The bigger question here is why prod/staging wasn't an obvious design choice in the first place!