Maybe I should have written it more clearly, but the mini-frameworks I described in the article are not makeshift -- instead they're permanent and stay forever, expanding as time goes, until being replaced by something else.
I wrote this article to reflect a pattern I observed (and hate) while working in Google, but I'm sure this is not a company specific problem. Would be interested to hear other people's stories :)
Definitely agree. Sorry if the article sounds a bit negative, but I'm overall still in favor of building in public, for various reasons like the ones you mentioned.
Thanks for sharing. I had the same feeling that browsering Twitter timeline is not so helpful overall, though there are good posts from time to time so you still can't ignore it.
I actually enjoy reading levelsio's non-indie-related posts, but that 's me personally.
With his influence and followers, I think @levelsio has made sure that, even if he has competitors, he's gonna gain more attraction than others and do better
Author here. I'm glad to see so many meaningful discussions triggered by this post. Despite raising concerns, overall I still see "building in public" as a positive trend. Like all trends, things emerge and change over time, so we'll see how "building in public" evolves.
If you'd like to sponsor my work, feel free to check out an app I developed:
With one-click, Xylect explains your selected text using an AI knowledge engine, no matter which app you're currently using. It's like bringing Perplexity + dictionary to every app.
I'm also on Twitter/X and Mastodon. I'll share more thoughts in the future:
Since joining the indie hacker community a few months ago, I've been observing what everyone is doing with great curiosity. One thing I immediately noticed, is that everyone talks about "build in public".
At first I thought, "OK, everyone is doing it, it must be good". But a few months later, I'm starting to have some questions. I write about them in this article.