Jolly

JollySep 10, 2026

I made an AI assistant for me to help people know more about me easily… It can do some cool things like search my knowledge base, help you with learning more about my projects and experiences, recommend relevant links to my projects, blogs and videos. It can even book meetings for me and notify me about it! Will monitor it for some time to fix any issues and look for hallucinations. Check it out at https://ayaan.dev

JollySep 21, 2026

Last week, I took on a challenge: clone Fathom AI in just 24 hours. And I did it. Meet 8x-Fathom an AI-powered meeting notetaker that syncs with Google Calendar, automatically joins Google Meet calls, records meetings, and gives you: • Meeting playback • AI summaries (you can recreate this using different templates) • Highlights and scratchpad notes (You record them mid call!!) • Action items • Transcripts and participants • All chat messages • 'Ask Fathom' an AI assistant to ask questions about your meetings • One-click sharing The core platform was live and functional end-to-end within 24 hours. I’m still improving it as time permits, but this was a great reminder of what you can build when you’re completely locked in 😛. Really an 8x thing to do. Check it out: Walkthrough: https://lnkd.in/dvM-NGip App (You need a google account to explore!): https://lnkd.in/d6hTpNZk Demo shared meeting: https://lnkd.in/dKMv9GB5 Source code (if you are interested): https://lnkd.in/dW8ZQ8mG

JollyJun 10, 2026

If package.json already exists… Why do we need package-lock.json? At first glance, they seem to store the same thing. But they don’t. Suppose your package.json contains: { "dependencies": { "react": "^19.0.0" } } Notice the ^. It means npm can install newer compatible versions. So today, npm install might install: [email protected] A month later, the same command might install: [email protected] Even though your package.json never changed. Now imagine this: The application works perfectly on your machine. But breaks on your teammate’s machine. Same code. Different dependency versions. That’s exactly the problem package-lock.json solves. It records the exact versions that were installed for the project initially, including nested dependencies. This ensures that everyone on the team gets the same dependency tree. Not just similar versions. The exact same versions. That’s why deleting package-lock.json can sometimes introduce bugs without changing a single line of your code. In short: package.json describes the dependencies your project needs. package-lock.json records the exact dependency versions that were installed. If you want to understand this visually, https://lnkd.in/dawXShU9 (Hindi) #javascript #nodejs #webdevelopment #webdev #softwareengineering #npm #programming #coding #backend #frontend #developers