So lemme show you what i am working on rn Klick (might change the name later) It’s basically gonna be a cursor click animation library, you will be able to add really cool click animations to your cards, pages, and components with just one CLI command. And this is the homepage i designed for it, tell me how it looks This project is gonna be crazy, i have spent a lot of time making sure everything feels really polished and good, just wait till i complete it, it’s gonna be insane

made this simple tcp-based file transfer server/client in golang while learning tcp (first tcp project). not the most idiomatic implementation and more of a quick fafo project. it supports uploading and downloading files

Just watched 3 episodes of Monster and i immediately know this is going to be a good watch

so yes guys im finished with this mini-protoc actually finished it 2 days earlier i was figuring out how can i integrate it into my mini-rpc. so still working on integrating it have to change its whole design, for now im just shipping this one what it does: -> compiles a .proto file with a limited subset of the proto grammar. -> currently supports a few primitive data types and unary rpc only. -> has a lexer and parser written from scratch that parse the .proto file, build an AST, validate it, and generate Go structs, service interfaces, client stubs, and registration stubs. repo in replies

Learning Git and GitHub in detail from this video by @ThePrimeagen

In the last few days, I recreated a TCP server from scratch multiple times (6 times to be precise). I intentionally started with the simplest version possible, without any Goroutines or any abstractions, just a basic server and client model, because I wanted to understand exactly what was happening at each step and why and also the other thing was to train my muscle memory by repeatedly implementing the same concepts instead of just reading about them. I got stuck multiple times on blocking behavior and even managed to create race conditions like situations even with a single client. After enough iterations, I finally got a basic version working without goroutines and without relying on AI just docs and one video. Then I added a single goroutine and was surprised to see the server handle multiple clients concurrently without blocking(3 clients at a time) Whatever the assumptions I had about concurrency became obvious after rebuilding the same thing over and over again. Next, I want to understand what happens when the number of clients grows significantly and explore concepts like worker pools, queues, and efficient goroutine management.

Time to learn about Git and GitHub in detail, Does anyone have any good resources?

Right now, i am working on a project where you can add these awesome cursor click animations to your components with just a single CLI command

The Zeno waitlist is now live <3 A lot of developers learn how to write code but very few get the chance to practice working in code they didn't write. Zeno is being built for that exact gap. A place to work through realistic codebases, solve issues, and get feedback in an environment that feels closer to real software engineering. LINK IN REPLIES. would love to have you along for the journey :)

i'm done with my current project it's a background job processing system / worker system built because i wanted to spend time working with golang, redis and concurrency. i've shared the repo and architecture write-up in replies. i also experimented with multiple queues. there's a priority queue and a default queue and workers can be reassigned between them based on demand. also build a simple sort of autoscaling mechanism that shifts workers toward the priority queue when jobs start waiting too long and moves them back once things settle down i also wanted to see how far i could get with making it run across multiple instances without weird behavior. i don't have a lot of experience designing systems like that yet but it was a good learning experience and gave me plenty of things to think about it was my first time writing a write-up so i'm sure there's room for improvement but had to start somewhere

Just shipped GitMaxxing , a GitHub stats tracker I built from scratch over the past 2 weeks. What's under the hood: - GitHub App webhooks with HMAC signature verification - Event log pattern : raw events stored first, cron aggregates later - GraphQL backfill for full contribution history - Streak calculation from daily stats - Public shareable profile cards with export - Sync Now button to manually run the api endpoint for cron jobs, as vercel only allows one cron jobs per day on their free plan The most interesting part was the webhook and cron separation. Webhooks just log raw events. A cron job aggregates them into daily stats. If aggregation logic has a bug, raw data is intact and you can re-run. Built with: Next.js, Better Auth, Prisma, PostgreSQL, GitHub GraphQL API Try it: github-stats-tracker.vercel.… #buildinpublic #nextjs #webdev

first time someone from my class complimented my linkedin profile daaamn 😭

No daily log for some days, going to nani ke ghar in college vacations 😋

ok so now 2 players can play a proper chess game, the main logical work is done, and now it's time to work on the other features some issues right now: > one player can make moves for both black and white > it do not show the result, the board stop moving if the game is finished > there are no time controls yet > the UI UX is pretty bad