If you want to stop fighting your own tools, try it out.
- npx @mohitmishra7/never-cli init
Github: github.com/mohitmishra7...
If you want to stop fighting your own tools, try it out.
- npx @mohitmishra7/never-cli init
Github: github.com/mohitmishra7...
The MCP server and VS Code extension work, but they are rough around the edges. I am pushing updates daily to smooth out the init and scan logic.
Now, every time you prompt, the AI knows the boundaries. No more "don't use that library" corrections.
These are still early numbers, but it's good to see some traction already.
1. The CLI package: npmjs.com/package/@moh... (681 downloads)
2. The MCP server package: npmjs.com/package/@moh... (785 downloads)
3. The core package: npmjs.com/package/@moh... (865 downloads)
The response has been kind of wild.
I honestly didn't expect this to blow up, but we saw over 2,300 downloads in the last 48 hours. It seems I am not the only one frustrated by this.
Here is how it works:
- Install "npm install -g @mohitmishra7/never-cli"
- Run npx @mohitmishra7/never-cli scan
- It detects you are using Next.js, Tailwind, or Supabase.
- It generates/updates a .cursor/rules (or compatible) file.
It scans your repo, detects your tech stack, and locks in the rules. Your AI stops guessing and starts following your actual architecture.
The concept is simple. It acts as a guardrail for your AI. Instead of typing "never use emojis in commit messages or code comments" or "never output verbose prose like 'Here is the updated code...'" every single time, you define it once. Never enforces it.
https://www.npmjs.com/package/@mohitmishra7/never-cli
I got tired of repeating myself to my coding tools (cursor/claude code etc).
It feels like managing a junior dev with amnesia. You set the rules, they forget them the next day, and you spend more time reviewing generic code than shipping features.
So I built a fix
๐๐ผ๐บ๐ถ๐ป๐ด ๐๐ผ๐ผ๐ป:
* Subscriptions for updates as they happen.
* Email summaries based on what you like.
* Suggestions just for you.
๐๐ฒ๐ ๐ฏ๐ฒ๐ป๐ฒ๐ณ๐ถ๐๐:
* Fresh timeline of events from around the world.
* Interactive map to find stuff nearby or far away.
* Filters for topics like AI or DevOps, spots, or ones with funding help.
* Speaker mode to see open calls for papers and due dates fast.
* One click to add any event to your calendar.
It was a pain, so I put together this free tool that gathers all global tech conferences in one place by scraping those sources, making it way easier to stay on top of things.
I made ๐๐ผ๐ป๐ณ๐ฆ๐ฐ๐ผ๐๐ I loves tech events but hated digging through scattered sites like ๐ช๐ถ๐ธ๐ถ๐๐๐ฃ, ๐๐๐๐, and ๐๐๐ to find them.
you can check it our here: www.confscout.site
#TechConferences #DeveloperEvents #TechCommunity #CallForPapers #Innovation
this is the part 4 of the Understading the C/C++ Compilation Process series which focuses on Linking, go check it out and also it has a small task in the end that you can try which will help strengthen the understanding more ;-)
also let me know if any suggestions
Linking It All: Static Glue and Dynamic Surprises
open.substack.com/pub/chessman...
Assembling the Pieces: From Assembly Text to Binary Objects
open.substack.com/pub/chessman...
La bonne URL (sinon 404) :
github.com/implement-fr...
Thankyou
Memory Allocator From Scratch in C Guide
A production-style, thread-safe memory allocator built from scratch, designed to demonstrate advanced systems programming concepts and memory management techniques.
You can see it here: website-seven-murex-43.vercel.app/memory-alloc...
Github Repo: github.com/implement-fr...
Github Organization: github.com/implement-fr...
Memory Allocator From Scratch in C Guide
A production-style, thread-safe memory allocator built from scratch, designed to demonstrate advanced systems programming concepts and memory management techniques.
Inside the Compiler: Trees, Parsing, and That First Assembly Glimpse
this is the part 3 of the Understanding the C/C++ Compilation Process series is out, go check it out and also it has a small task in the end
open.substack.com/pub/chessman...
Preprocessing Magic: Copy-Paste and Guards That Save Your Sanity
open.substack.com/pub/chessman...
Iโm really excited to tell you all that my book is finally up for pre-order.
๐๐
๐ฒ๐ฐ๐๐๐ฎ๐ฏ๐น๐ฒ ๐๐ถ๐น๐ฒ๐ ๐ณ๐ผ๐ฟ ๐๐ถ๐ป๐๐
: ๐จ๐ป๐ฑ๐ฒ๐ฟ ๐๐ต๐ฒ ๐๐ผ๐ผ๐ฑ ๐ผ๐ณ ๐๐๐๐ ๐ณ๐ผ๐ฟ ๐๐น๐ฒ๐
๐ถ๐ฏ๐น๐ฒ ๐ฎ๐ป๐ฑ ๐ฆ๐ฒ๐ฐ๐๐ฟ๐ฒ ๐๐ผ๐-๐๐ฒ๐๐ฒ๐น ๐๐ผ๐ฑ๐ถ๐ป๐ด(๐๐ฝ๐ฟ๐ฒ๐๐, ๐ฎ๐ฌ๐ฎ๐ฒ)
๐๐ป๐ฑ๐ถ๐ฎ ๐น๐ถ๐ป๐ธ: amazon.in/dp/B0FQTTBB79
๐๐ป๐๐ฒ๐ฟ๐ป๐ฎ๐๐ถ๐ผ๐ป๐ฎ๐น ๐น๐ถ๐ป๐ธ: amazon.com/dp/B0FQTTBB79
Still doesnโt feel completely real that this is out there. Hope some of you find it useful. Let me know what you think when you get your hands on it.
Huge thanks to the ๐๐ฝ๐ฟ๐ฒ๐๐ ๐๐ฒ๐ฎ๐บ who were incredibly patient with me, and to everyone who kept asking โwhen is the book coming out?โ โ youโre the reason it actually happened.
Itโs written for people who write operating systems, firmware, exploit payloads, performance-critical code, or just like knowing how things really work.
Release date is 28 April 2026, but you can grab it now at the pre-order price.
If youโve ever wondered what actually happens between hitting Enter on ./๐ฝ๐ฟ๐ผ๐ด๐ฟ๐ฎ๐บ and the first instruction running, this is that story.
The book is a exploration into how ๐๐๐ works from start to finish: compilation, linking, loading, dynamic linking, symbol resolution, the kernelโs execve path, patching binaries, writing custom linker scripts, the whole thing.
After years of working on ๐ธ๐ฒ๐ฟ๐ป๐ฒ๐น๐, reversing binaries, and digging into exploitation techniques, I finally managed to put everything I know (or at least everything that fit) into one place.
Iโm really excited to tell you all that my book is finally up for pre-order.
๐๐
๐ฒ๐ฐ๐๐๐ฎ๐ฏ๐น๐ฒ ๐๐ถ๐น๐ฒ๐ ๐ณ๐ผ๐ฟ ๐๐ถ๐ป๐๐
: ๐จ๐ป๐ฑ๐ฒ๐ฟ ๐๐ต๐ฒ ๐๐ผ๐ผ๐ฑ ๐ผ๐ณ ๐๐๐๐ ๐ณ๐ผ๐ฟ ๐๐น๐ฒ๐
๐ถ๐ฏ๐น๐ฒ ๐ฎ๐ป๐ฑ ๐ฆ๐ฒ๐ฐ๐๐ฟ๐ฒ ๐๐ผ๐-๐๐ฒ๐๐ฒ๐น ๐๐ผ๐ฑ๐ถ๐ป๐ด(๐๐ฝ๐ฟ๐ฒ๐๐, ๐ฎ๐ฌ๐ฎ๐ฒ)
๐๐ป๐ฑ๐ถ๐ฎ ๐น๐ถ๐ป๐ธ: amazon.in/dp/B0FQTTBB79
๐๐ป๐๐ฒ๐ฟ๐ป๐ฎ๐๐ถ๐ผ๐ป๐ฎ๐น ๐น๐ถ๐ป๐ธ: amazon.com/dp/B0FQTTBB79