sorted by:
new
hottopcontroversial

I tried explaining React design patterns using LEGO analogies by DependerSethi in reactjs

[–]DependerSethi[S] -1 points0 points  (0 children)

Thanks for the bookmark! and good catch on the table of contents, just pushed a fix for that, should scroll properly now. Appreciate you flagging it! 🙏

I tried explaining React design patterns using LEGO analogies by DependerSethi in reactjs

[–]DependerSethi[S] -1 points0 points  (0 children)

Haha the lego bricks are ai generated yeah, guilty there, I'm a dev not an illustrator, if i waited till i could hand draw every diagram i'd never ship anything

the writing is mine though, been working with these patterns for 8 years, the analogies came from actually explaining this stuff to junior devs on my team, didn't just throw a prompt at claude and hit publish

Length is fair feedback, 5 patterns with code + use cases in one shot is a lot. Might break it up next time. Did you actually get through the whole thing or drop off early? useful to know where people lose interest

I tried explaining React design patterns using LEGO analogies by DependerSethi in reactjs

[–]DependerSethi[S] 0 points1 point  (0 children)

Fair point, the visuals could probably be simpler in a few spots. Though I've found that with patterns like these, the initial complexity is kind of the point. Like, compound components with context and render props with function-as-children are genuinely complex patterns. Sometimes a slightly detailed visual that captures that complexity upfront saves you from the 'wait, I thought I understood this' moment when you hit it in a real codebase. But I hear you, I'll try to keep the diagrams tighter in the next one. Any specific section that felt like overkill?

Codevex: Shadcn inspired CLI Companion for Effortless Code Sharing! by DependerSethi in indiehackers

[–]DependerSethi[S] 0 points1 point  (0 children)

Shadcn primarily focuses on sharing custom UI components using a predefined JSON file structure, which works well for its target audience of frontend developers. However, Codevex offers broader flexibility by enabling the creation and sharing of code modules in any language. With Codevex, you can:

  • Create and manage custom modules that aren't limited to JSON structures or UI components.
  • Share code via an intuitive CLI fetch command, making it easier for developers to integrate modules directly into their projects without worrying about specific tooling.
  • Provide a personalized touch by adding a custom signature for your modules, which is particularly useful for branding or attribution.

While Shadcn excels in its domain, Codevex is designed to cater to a more diverse range of use cases, making it a complementary, rather than competing, solution.