Ask HN: What dev tools do you rely on that nobody talks about?

https://github.com/atuinsh/atuin for fuzzy shell history (ctrl+r)

https://github.com/sharkdp/bat (nice coloured cat replacement)

https://github.com/abiosoft/colima (so I don't need docker desktop)

https://github.com/duckdb/duckdb (performant database that lets you directly query JSON, parquet, csv files with SQL queries and convert one to the other.

https://github.com/eradman/entr (rerun commands automatically when provided files change) (useful for rerunning test commands automatically once you save the file you're editing.

https://github.com/martinvonz/jj and https://github.com/idursun/jjui (Jujutsu VCS, been using it for three months and I really enjoy it)

https://github.com/jesseduffield/lazydocker (managing containers, images, volumes easily)

https://github.com/jesseduffield/lazygit (best tui for git and outside niche git commands, the fastest way to use git.)

https://github.com/jdx/mise (fast asdf, direnv, and task runner replacement) (install pretty much version of tool, language, env vars in a per directory level. (Or global if you want))

https://github.com/ajeetdsouza/zoxide (intelligent cd to move between directories incredibly quickly)

1. https://github.com/junegunn/fzf for fuzzy search. Great for easily searching and selecting git branches + tags + commits, commands from shell history, files, shell jobs, processes, etc.

2. https://github.com/casey/just for more structured scripting.

I love deepwiki for understanding deep code architectures: https://deepwiki.com/

I think people are missing the "hidden gems" part of the question here.

This resonates. I actually ended up building a tool last year (CapSize) because I needed to churn out screenshots at a specific frame size for my day job and couldn't find anything that would just "lock" to 800x600 without a fight.

I'm not a dev by trade, so I did use AI as a power-tool to wrestle with the C++ and Electron parts. It turned into a bit of a rabbit hole—I ended up obsessed with keeping it entirely local/offline (no cloud APIs or telemetry) just to see if I could do things like local OCR in RAM. I ended up building two more tools to help me with making the one tool so it kind of spiraled into a small suite, but the main goal was just a no-frills utility that didn't require a login or a subscription just to crop an image.

I've been using ack for a very long time, maybe 15 years.

It's like grep but faster and easier to use. I still use it all the time, even in the era of Claude.

https://beyondgrep.com/

For me it has to be mock. With it I can create and automate APIs easily.

https://dhuan.github.io/mock/latest/examples.html

Efficiency is doing more with less. I'm not sure more tools is the path to productivity.

I'm not sure it counts as a dev tool, but I use Nushell and I'm always surprised at how few devs know about it.

HTTP mock servers

I’m working on mockaton, which is mainly a filename convention based router.

https://github.com/ericfortis/mockaton

multitouch+stylus screen, plus the windows ink demo app https://www.microsoft.com/en-us/garage/profiles/sketch-pal/

its low latency, can do multiple layers, and its easy to pick out a standard set of colours to draw with.

It lets me make good rhetorical diagrams, and I've also used it for drawing quick mockups to get genai to make webpages

also, Quip as a design document/review tool. Its fantastic having a design review where you get comment threads going along different parts of the requirements and design, that you can then focus on in discussion time. it also lowers the barrier to giving feedback, so newer devs can ask questions without feeling like theyre taking up valuable meeting time

https://github.com/devlensio/devlensOSS -> its helpful for me to check the blast radius of my changes. (built by me but not a promotion)

code-server, instead of VSCode. I can build my own podman image on top of it with whatever dev tools I need for whatever languages I'm working with, and if I have to install something weird or something breaks I can just restart the container. Especially on my work machine that isn't Linux, I have this running in a VM and can just use in my browser and don't have to jump through hoops to get the dev environment I want. On my personal instance I also use it for automating building stuff from source. Before I had this, I just had build tools on pretty much every single machine I was building for and it was a hot mess.

https://github.com/coder/code-server

Why should I tell if it's supposed to be hidden? :-)

But here we go, Common Lisp for rapid prototyping at my FAANG job, so I'm actually paid to do that!!!

edit: minor typo

CapRover for self hosted PaaS Dozzle for self hosted logs DuckDB was a life savior for some data analysis I needed to do Rollbar for app error alerting - v generous free tier

Having been running so many claude terminals in parallel, now switching to https://lanes.sh

Use TextMate[0] as my daily driver.

[0] https://macromates.com/

high on my own supply :-) i use https://easyanalytica.com/tools/html-playground frequently as it allows me to open html in new window and use dev tools like any other page.

A VS Code/Visual Studio extension for creating mind maps with nodes linked to code called Code Mind Map.

Tmux

Notepad++

:)

`gdu`, which is like `du` with a TUI.

cat some-file | pbcopy

Copies it to your clipboard on osx. I use this a lot.

Tilix + shell scripts to create a Tilix session, open windows inside Tilix and run commands, so that I can immediately create a session to debug say Linux kernel development -- 3 windows, one for gdb, one for compiling and running, and one for minicom.

I'm sure Tmux can do it, but I really hate the Ctrl+B thing. Alt + Arrow keys are way more intuitive.

CUE and Dagger, though they are talked about by more than nobody

They are central to my personal dev tool

https://github.com/hofstadter-io/hof

gitk and git gui

It's amazing, how rarely people talk about fish (https://fishshell.com/)

I love it so much that I pity people that use Bash, Zsh.

Ragas for anyone building RAG pipelines. It evaluates your retrieval quality before you've written a single line of product code. Faithfulness, answer relevance, context recall are all measurable and automatable. Most teams I've seen find out their retrieval is broken in production. Ragas tells you in Week 0. Completely changes how you scope the build.