Paras Sharma

@kingdavidmiles Appreciate it! Just trying to show up daily and document the journey 🙏 means a lot!”

@Parass227 this is the energy we need more of

Day 20 Dev Progress 🛠️ Big focus on frontend integration today 1) Connected auth flow to React 2) Fetching problems from backend & rendering them on the frontend Will work on Error handling and connecting submission flow now. #buildinpublic #webdev

@ray_kovalev That’s a good point. Right now I’m focusing on the core workflow - listing problems, solving them, and code execution. Once that’s stable, I plan to improve the UX with features like search, filtering, bookmarks, progress tracking, sharing, and other quality-of-life improvements.

aha, now I've got you. Then think about how your users will use such data. Give them the best experience. For example just simple button that they can click and get full info of the issue in their clipboard. Give them ability to export whole bunch of issues in csv file and so on

@ray_kovalev The frontend fetches and displays the list of problems, allowing users to select one, read its description, write a solution, and submit it. On submission, the code and problem ID are sent to the backend for execution, and the results are returned to the user.

@Parass227 what for do you plan to fetch them?

Day 20 DSA Progress ⚡ 7 Array problems done: 1) Two Sum 2) Sort 0s 1s and 2s 3) Majority Element 4) Kadane's Algorithm 5) Print Subarray with Max Sum 6) Stock Buy and Sell 7) Rearrange Array Elements by Sign #buildinpublic #dsa

Day 19 Dev Progress 🛠️ Completed the full Auth flow 1) JWT Access + Refresh Tokens 2) Logout with token invalidation 3) Protected routes 4) RBAC - role based access control Also built the React frontend for the project Backend + frontend both taking shape now #buildinpublic

Day 19 DSA Progress ⚡ Wrapped up Easy Arrays & started Medium 1) Union of Two Sorted Arrays 2) Find Missing Number 3) Maximum Consecutive Ones 4) Find the number appearing once (others twice) 5) Longest Subarray with Sum K (positives & negatives) #buildinpublic #dsa

@mooned_dev Exactly that was one of the reasons I implemented Redis Pub/Sub(update on new post). I wanted the Judge Service to remain completely decoupled from the service managing the WebSocket connections. Right now it's split into two separate services (Problem Service and Judge Service).

Day 17 Dev Progress 🛠️ Added WebSocket so that result can be returned back to the frontend in real time after user submits the code. Got the basic connection working. Learning about redis pub/sub to make it more efficient. #buildinpublic #webdev

@ray_kovalev Thanks! I’ll definitely explore NATS next. Always looking to learn technologies that fit distributed systems better.

@Parass227 TBH - a lot. It's a strong technology used widely. nats.io

Day 18 Dev Progress 🛠️ Implemented Redis Pub/Sub for communication between microservices and Socket io for real-time result delivery whenever result is returned from the worker during code execution. User can see each status change now. #buildinpublic #WebDev

@ray_kovalev Interesting! I went with Redis since BullMQ was already part of my stack, so Pub/Sub felt like a natural fit. I haven’t worked with NATS yet but I’d be interested to hear what advantages you’ve found over Redis Pub/Sub.

@Parass227 I prefer to use NATS broker for communitations and Redis mostly for caching and sometimes as a persistent storage. I like to watch people who builds in public, shares their journey, maybe help with advices

@ray_kovalev Yes. BullMQ handles asynchronous job execution, while Redis Pub/Sub is used for inter-service communication instead of direct HTTP callbacks. It keeps the services loosely coupled. Happy to discuss the architecture further in DMs if you are interested!

@Parass227 do you use Redis as a communication layer between your services?

Day 18 DSA Progress ⚡ Solving Array problems now: 1) Check if Array is Sorted II 2) Remove Duplicates from Sorted Array 3) Left Rotate by One & by K Places 4) Move Zeros to End 5) Linear Search Easy problems but great for building intuition #buildinpublic #dsa

@soham_nayak04 Hey, lets connect!

If you're a dev under 1k followers grinding build-in-public, drop your handle. I'll actually follow back and read your stuff. My feed's gone stale, and I want new builders in it.

Day 17 DSA Progress ⚡ Heavy revision day -- 21 problems across 4 topics 1) Basic Recursion (9/9) 2) Basic Hashing (3/3) 3) Sorting -- Selection, Bubble, Insertion, Merge, Quick (7/7) 4) Array problems -- Largest & Second Largest (2/40) #buildinpublic #dsa

@ray_kovalev I’m learning these algorithms to strengthen my problem solving skills. The exact problems might not appear in production, but the concepts behind them helps when optimizing applications, choosing the right data structures, and designing efficient systems.

@Parass227 where do you plan to use these algorithms? do you have any plans on them?

Day 15 DSA Progress ⚡ Learnt 3 Hard string algorithms today: 1) Rabin Karp Algorithm 2) Z Function 3) KMP Algorithm (LPS Array) These were hard to understand but finally got hold on it #buildinpublic #dsa

Day 16 DSA Progress ⚡ Refreshing the fundamentals -- Basic Maths Completed all 7 problems: 1) Count all Digits of a Number 2) Reverse a Number 3) Palindrome Number 4) GCD of Two Numbers 5) Armstrong Number 6) Print all Divisors 7) Check for Prime Number #buildinpublic #dsa

Day 16 Dev Progress 🛠️ Judge service is fully working! User submits code -> stores in DB -> pushed to Redis queue -> worker picks it up -> executes code async -> updates DB with final verdict. Compile errors, runtime errors & TLE all handled properly #buildinpublic #WebDev