Paras Sharma

@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

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

Day 15 Dev Progress 🛠️ Built the Submission model & logic today which stores the submission(code,problemId,etc) of a problem. Now the worker receives just a submission ID fetches the code, executes it. #buildinpublic #webdev

@connoratlunon github.com/paras027

Hiring SWE Interns The late night coders. The hackathon winners. The ones who ship for fun and can't stop building. Come build AI that does what consulting firms charge millions for. $40/hr, remote. Drop your GitHub below. I'll be personally reviewing all of them.

@0armaan025 Thanks! Just trying to stay consistent and be better

@Parass227 Man, you're consistent, and cooking! 🔥

Day 14 Dev Progress 🛠️ Before, the backend directly called the judge service via Axios on every submission. Now it pushes the job to a Redis queue and the worker inside the judge service picks it up & runs the code asynchronously Still working on SSE/WebSocket to return results

Day 14 DSA Progress ⚡ Started Advanced Strings 1) Minimum Bracket Reversals to Balance an Expression 2) Count and Say 3) Hashing in Strings (Theory) Next up: Rabin Karp, KMP & other string algorithms #buildinpublic #dsa

Day 13 Progress ⚡ DSA: Solved 2 Trie problems: 1) Maximum XOR of Two Numbers in an Array 2) Maximum XOR with an Element from an Array Starting Strings now Dev: Implemented Redis + BullMQ and entire code execution now runs through the worker queue #buildinpublic #dsa #webdev

Day 12 Dev progress ⚡ Set up Redis + Queue Worker for the judge service today. Connection between Node.js and Redis is up Also cleaned up the submission code. Next: wiring the worker to the queue so it actually picks up & runs submitted code #buildinpublic #webdev

Day 12 DSA progress ⚡ Finally learning & implementing Tries 1) Trie Implementation & Operations 2) Longest Word with All Prefixes 3) Distinct Substrings in a String 4) Bit Prerequisites for Tries learnt how Tries can be used for above questions. #buildinpublic #dsa

Day 11 Progress ⚡ Full learning day today -- DSA: Dived into Tries -- Learnt the core structure & implementation from scratch. Dev: Explored how to integrate Workers & Redis into the judge service for a proper async code execution flow #buildinpublic #dsa #webdev

Day 10 Progress ⚡ DSA: Completed Partition DP with 2 tough problems: 1) Minimum Cost to Cut a Stick 2) Burst Balloons Starting Tries from tomorrow Dev: Added basic execution runtime tracking to the judge service. Will optimize it further once workers are in place

Day 9 Dev progress 🛠️ Judge service can now detect runtime errors too The tricky part -- both compile errors & runtime errors were thrown via stderr, so it all looked the same at first. Fix: separated compile step & run step so each handles its own errors cleanly

Day 9 DSA progress ⚡ 3 problems solved today: 1) Number of Longest Increasing Subsequence 2) Longest Bitonic Subsequence 3) Matrix Chain Multiplication MCM pattern is actually hard to understand but still trying to solve it.

Day 8 Dev progress 🛠️ No new features today — spent time cleaning up the codebase instead. Refactored messy code, fixed naming, removed clutter. Not flashy, but future me will thank present me. still working on and understanding the runtime error feature.