Flycut[2] has certainly saved me a lot of time and changed the way I write code. Have a good clipboard history has really changed my flow.
[1]: https://github.com/cantino/mcfly [2]: https://github.com/TermiT/Flycut
91–100 of 574 posts
Flycut[2] has certainly saved me a lot of time and changed the way I write code. Have a good clipboard history has really changed my flow.
[1]: https://github.com/cantino/mcfly [2]: https://github.com/TermiT/Flycut
RedwoodJS 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.
JetBrains software.
Otherwise the number of times I "show usages" or refactor shortcuts (rename, extract method / variable) throughout the day...
All of it out of the box as well, it's great value for money.
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…
Not 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.
As a bonus, you'll be able to write insufferable comments like these in HN threads.
Greenshot - free, lightweight and just the right set of features for marking up screenshots and making new UI mockups based on existing screenshots of apps. I've tried a lot of other alternatives but they were either too complicated to use or lack a key feature.
Each 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…
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?
Automatic UV unwrapping.
LSP. The Language Server Protocol. Entirely changed my life for the better this year, once I took the time to get it integrated into Emacs and get the various backends I needed installed. Easily has saved me hundreds of hours so far, being able to view function prototypes quickly, pull up documentation as an overlay on the code, jumping to the next error, and even down to getting simple things like enumerated 'case'…
And once in a while I'd randomly have to look at some code that is not my primary work language, but everything will just work out of the box. Working with Emacs has never been better.
Huge shoutout to Magit mode, which I dearly love and definitely saved me bunch of time otherwise spent context switching to command line or another UI. 100hr = 6000min, I've been using Magit for 8 years at-least.
Assuming I'm doing some coding at-least 4 days a week, 4days * 4weeks * 12months * 8years = 1536 days of work. Let say it saves me 30 second on average by not switching window, selecting hunk individually that I love doing, doing arbitrary VCS operations (I love looking at diffs and just hitting enter to go to the source), I just need to open it 8 times per day to make it 100 hours so far. Definitely have used more than that I think. But even if this calculation is way off, and I'm not really saving time, its a very pleasant experience that is unmatched if you use Emacs IMO.