laike9m

Can't agree more

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.

Exactly

Thanks for the comment. I think you're spot on, and I should have explained more clearly what "concept" means in this context.

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 :)

I can be found here:

https://x.com/laike9m

https://mastodon.social/@laike9m

+1, well said

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.

Good question. I'm curious as well. From what I can tell, more and more indiehackers seem to be focusing on building tools for other indiehackers...

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:

https://xylect.app/

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:

- https://twitter.com/laike9m

- https://mastodon.social/@laike9m

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.

Thanks for the kind words. Still feel uneasy when rejecting a feature request

:)

As long as it passed, it's considered a valid solution. The provided solution is only for reference.

I like the proposal, I can change it to showing the solution link once user has run it.

emm, the default value can be anything really...

Sorry about the confusion. This issue has been fixed. New line is not needed anymore.

Your solution is fine. Pyright can infer the return types, so you don't need to annotate the return type.

In fact this is describe in the solution https://github.com/laike9m/Python-Type-Challenges/blob/main/...

That's great to know. I actually made it so I can really learn and understand Python typing.

I definitely considered adding hints. But it's gonna be a ton of work to create proper hints and I'm yet to prioritize it.

The "any" challenge is special, it's the only one where you don't need to make any changes :)

Fair enough. I'll refine the solution to avoid direct copies.

I'll also encourage people to contribute and make the challenges better.

I switched from Poetry to PDM and is feeling great.

If there's one reason to use PDM: the maintainer fixes bugs fairly quickly, not like Poetry, where many bugs are left open and nobody is taking care of it.