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 know what you mean! I've lived through those myself.
However, for a beginner, specially if said beginner never worked in a larger company with resources to produce an internal framework, they might think you're referring to Flask or something like that (btw Flask-style microframework use can go very wrong but it's another completely different issue).
That's why I'm being nitpicky. The people who'll get the post are likely already experienced enough to evaluate those frameworks themselves.
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 :)
Thanks for the article. I generally agree that adding more layers in an attempt to "fix" lower layers is often a fools errand. And just a quick typo I noticed and I'm smugling in this comment: legondary->legendary.
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.
I'd rather read a book / listen to a podcast from someone like Rob Walling, then navigate the Twitter feed of endless "welp, someone copied my SaaS" in order to get an occasional gem.
I also like his tweets, but it has nothing to do with learning how to build a business.
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
reply