Of all the software I can think of quickly, the one I think may have saved the most time in my life is Google Maps.
How come it saves 100 hours for you? In the old days we had paper maps and I checked routes before I left: not doing that anymore has cost me time rather than saved me time. Many a time Google maps has sent me to the wrong place. Once to the middle of a mustard field in France which was a destination it changed to mid-route to a house called La Mutardier. 5 hours wrong lost there. Less than useless on a motorbike due…
Ask HN: Programs that saved you 100 hours? (2022 edition)
111–120 of 574 posts
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#112Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#113RedwoodJS https://github.com/redwoodjs/redwood I launched my startup from 0 to first customer in 3 months thanks to this guy. Most of my time saved was because of a solid collection of libraries, brilliantly integrated together (backend to frontend), and I didn't have to suffer analysis paralysis every time I needed something.
Very interesting project, It's interesting to see trends coming back to bundled BE/FE. What would you say are the biggest issues you have with Redwood?
Another issue is that it doesn’t expose a server.js file, so its hard to do stuff like integrate an APM.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#114Seeing a lot of “fiddly” software being listed here. Stuff that lets you configure and tune a workflow endlessly. It’s ironic that this is the sort of thing most of us will think of, since it doesn’t really account for time saved so much as time spent fiddling… Keeping an eye out for software that you barely use, as this is the kind with the most potential to truly save me time.
From that perspective, using Ctrl+R and Ctrl+S for reverse-i-search in a shell saves me so much time from writing commands especially big Kubernetes ones.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#115Seeing a lot of “fiddly” software being listed here. Stuff that lets you configure and tune a workflow endlessly. It’s ironic that this is the sort of thing most of us will think of, since it doesn’t really account for time saved so much as time spent fiddling… Keeping an eye out for software that you barely use, as this is the kind with the most potential to truly save me time.
From that perspective, using Ctrl+R and Ctrl+S for reverse-i-search in a shell saves me so much time from writing commands especially big Kubernetes ones.
https://github.com/junegunn/fzf
It's also useful to remove duplicate commands and store infinite history. Add this to ~/.bashrc:
export HISTFILESIZE=
export HISTSIZE=
export HISTCONTROL=ignoredupsRe: Ask HN: Programs that saved you 100 hours? (2022 edition)
#116Everything Search by Voidtools.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#117Seeing a lot of “fiddly” software being listed here. Stuff that lets you configure and tune a workflow endlessly. It’s ironic that this is the sort of thing most of us will think of, since it doesn’t really account for time saved so much as time spent fiddling… Keeping an eye out for software that you barely use, as this is the kind with the most potential to truly save me time.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#118Earlier quoted context omitted.
From that perspective, using Ctrl+R and Ctrl+S for reverse-i-search in a shell saves me so much time from writing commands especially big Kubernetes ones.
The 'history' command is helpful the 1% of the time Ctrl-R and Ctrl-S fail you.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#119Each of the following is in the 1000 hours saved club (in no particular order): jq, perl, grep, gnu textutils, gnu parallel, bash, xargs, gkrellm, nload. Make deserves a special shout out. If you think it's only useful for building software, you've completely missed the point (similarly, if you think some language-specific tool is superior, you're doing things completely wrong): Anyway, this document saved me at leas…
> " If you think it's only useful for building software, you've completely missed the point " I clicked on your link with 16 pages of just contents links to find what the point is, and found "the make utility automatically determines which pieces of a large program need to be recompiled, and issues commands to recompile them". What's the point you see?
It takes about an afternoon to set up NFS + SSH primitives that automatically distribute the computation across clusters of machines. Since it is restartable, it automatically tolerates hardware faults (up to dozens of machines, in practice).
Basically, you get Map Reduce, but for arbitrary data processing DAGs, and it supports any language that works well on Unix-style operating systems.
Re: Ask HN: Programs that saved you 100 hours? (2022 edition)
#120Not a program, but the concept of functional programming and pure functions. It makes it a lot easier to think about code, and also makes it easier to test and parallelize code. Although be warned, it can also have the "side-effect" (functional programming pun!) of making you somewhat insufferable as you try to convince everyone around you that functional programming is amazing.
I ask, because I used to feel very similar about the OO paradigm (it helped me model the world easier, made me insufferable because of my zeal, etc). But, I had the privilege of doing that with nearly 20 years of Smalltalk. A battle worn path of ObjectiveC, Swift, Java, Python, Kotlin, and JavaScript later, I feel the pain. It's like being in forestry, one day you work with a chainsaw, and the next day they give you a fan with spoons welded for the blades.
These days I'm doing some Elixir... and I love it. I don't know how welcome it is in the "functional programming and pure functions" club, but I think it's awesome.
I have a working theory that what has made these paradigms loved or hated, is less about them theirselves, and more about the execution thereof. What made and makes both Smalltalk and Elixir appealing to me is their simplicity and straightforwardness. There's a mechanism you learn to reason about the problems you're trying to solve, and then you can excel at it, instead of constantly stumbling on edge cases where "hybrid" languages try to reconcile all of the paradigms together.
YMMV