I am Navnath

leetcode

github

Navnath Kadam • Peerlist

TRAK is a developer learning workspace tool that turns structured learning blueprints into ready-to-use local workspaces. Instead of starting with an empty folder when learning a new language, tool, or technology, use: trak init lang/go TRAK fetches the selected blueprint from its remote registry and scaffolds the complete learning structure locally. The registry is community-driven, allowing developers to create and contribute their own learning blueprints across languages, tools, databases, frameworks, and more. TRAK also provides a web interface for discovering tracks and working with blueprints. Highlights: - Local-first CLI- Community-driven registry- 19+ official tracks and 350+ modules- Cross-platform support- Remote blueprint fetching- Blueprint validation and filesystem safety- Blueprint Studio- Open source Built with Go, Cobra, GitHub-based registry workflows, and Next.js.

TRAK — Developer Learning Workspace

Most system design resources show architectures as static diagrams.I wanted to build something where you can actually create an architecture, configure it, run it, and understand what happens inside the system.FlowFrame is an interactive system design simulator and learning environment built around that idea.With FlowFrame, you can:<ul><li>Create workspaces and multiple system diagrams</li><li>Build architectures using an interactive canvas</li><li>Configure components and their behavior</li><li>Define architectures using the FlowFrame DSL</li><li>Learn the DSL through its syntax and rules</li><li>Run REST API requests through your architecture</li><li>Play, pause, and step through simulations</li><li>Visualize request and packet flows</li><li>Run multiple requests simultaneously</li><li>Inspect system events, cache hits, database operations, routing, and queues</li><li>Explore Load Balancers, API Gateways, Servers, Redis, PostgreSQL, Connection Pools, Message Queues, Pub/Sub, Workers, and more</li><li>Experiment with FIFO, LIFO, and Priority queue processing</li><li>Explore caching, load balancing, database pooling, microservices, monoliths, and event-driven architectures</li><li>Work through guided system-design scenarios with validation</li><li>Learn distributed-system concepts through a searchable glossary</li><li>Import and export architectures</li><li>Save and share system designs</li><li>Use the Demo Sandbox without signing in</li></ul>The goal is simple:Instead of only looking at a system design diagram, build it, run it, and see how it behaves.FlowFrame focuses on making the logical behavior of distributed systems easier to understand through experimentation and visualization.I'm still building and expanding it, so I'd love to know:What distributed-system concept, architecture, or failure scenario should I add next?