One thing 15 years taught me:
Users don't care how clever your architecture is.
They care whether they can find what they're looking for.
Fast.
Everything else is secondary.
A useful engineering rule:
If adding a feature makes the core product worse, it's probably the wrong place for that feature.
That's how we ended up with plugins.
The search engine stays lean.
Additional capabilities stay separate.
Everybody wins.
Most people think file search is solved.
Until they need to find:
- One line in 100,000 files
- A forgotten project
- An old invoice
- A configuration setting
Search is one of those problems that feels trivial...
Right up until it matters.
your codebase search is embarrassingly slow 💀
ripgrep (rg) finds any pattern across every file in ~0.3s
faster than grep. smarter than your IDE.
7 steps to set it up 👇
@Nikokow Hi so... I'm working on quite a few projects.
Searchmonkey is just one of them. See https://t.co/ELqcuvX9HB for the full list.
Founder, builder, CTO - the usual! Feel free to dm me.
@Nikokow@mobileossfinds Hey, would you be able to help get my Searchmonkey some traction?
We've been around for 15+ years but I am terrible about marketing our open source software on X. 😢
Dm me to chat - I'm a founder of a few projects.
A surprising amount of software engineering is learning what NOT to build.
You don't need:
• A database
• An indexer
• A background service
• A cloud account
to search your own files.
Sometimes the simplest solution is also the fastest.